Close
0%
0%

TiltForge — a repairable, Matter-native blind tilt

Hidden-in-the-headrail tilt motor for ordinary blinds. Friction-clutch drive, absolute encoder, Matter — and the pull cord always works.

Public Chat
Similar projects worth following
Motorize the tilt on ordinary 2” horizontal blinds with nothing visible on the window — everything lives inside the headrail and drives the tilt rod directly. Matter over Wi-Fi: HomeKit, Google Home, Alexa, Home Assistant — no hub, no cloud, no app. Born from eight windows of dead commercial motors that killed the pull cord on the way out. Three rules: the cord always works, the blind always knows its real position, and when something wears out you replace a cheap part, not the product.

The Project

Motorize the tilt on ordinary 2" horizontal blinds with nothing visible on the window: no pod stuck to the glass, no replacement wand. Everything lives inside the headrail and drives the tilt rod directly. Matter over Wi-Fi means it shows up in HomeKit, Google Home, Alexa, or Home Assistant with no hub, no bridge, no cloud, no app.

The production drivetrain, running
The production drivetrain running on the coffee table (the printer had the bench).

The project started the way most do: eight windows retrofitted with commercial smart-tilt motors that all died — batteries that wouldn't hold charge, stripped gears, $200-per-window replacements. Worse, installing them had required removing the native cord spool, so every dead motor left a window with no manual control at all. The requirements wrote themselves:

  1. The pull cord always works — motorized or dead
  2. The blind always knows its real position, even after a manual move
  3. When something wears out, you replace a cheap part, not the product

Eight months of gearbox architectures later — planetary, harmonic drive (4.5 versions), magnetic gearing, TPU belts, three separate cycloidal campaigns, a capstan — the transmission that won is a preloaded friction clutch: a stack of washers pressed to a set torque. One mechanism is simultaneously the drive coupling, the overload protection, the manual override, and the end-stop tolerance. The failure I'd spent months engineering against became the feature.

The whole eight-month build journal: https://www.tiltforge.com/blog

Position feedback comes from an AS5600 magnetic absolute encoder reading the drivetrain itself, so clutch slip never loses position — and when a human grabs the cord and tilts the blinds by hand, the encoder sees the real position and the smart home stays in sync. No competitor does that.

One confession up front: every part of this was designed in TinkerCAD. Laugh, then watch the video.

What's open and what isn't — honestly, because that word gets abused: the build journal and docs are free to read and share (that's what this page's CC license covers). The dead architectures from the journal — the cycloid drive and friends — are headed to Printables as free models. The shipping kit's STLs come with the hardware, or as a $20 Studio pack licensed for personal use — because the wear parts you might ever need to reprint should never be hostage to the company. And the device itself is local-first Matter: no cloud, no account, no bridge, no app. Every wearing part is available as a cheap replacement, and the whole thing is documented as it's built — this page is the living build log.

The technical story

Why every gearbox failed. The headrail's own worm gearing is not backdrivable, and the cord spool needs a 90° direction change plus reduction — exactly what the worm already does. So the only way to keep the cord working is to drive the same axis the worm and spool live on. A planetary, harmonic, or cycloid stage sitting in-line on the tilt rod ends up on the wrong side of the worm, where a cord pull can't reach it: dead cord, dead requirement. Each architecture failed this same geometry test before it got the chance to fail on its own terms. (Full teardown of each attempt in the build journal, linked below.)

What won. A custom N20 gearmotor (Hotec HT-SOG12C, 60 RPM @ 6 V) — built to spec with an M4-threaded shaft after months of fighting D-shaft geometry — drives the tilt rod through a preloaded friction stack that threads directly onto the motor-side spur: fiber clutch washers under set compression, slip torque set by locknut preload ("set preload, check feel" — a coil spring auditioned and lost). Putting the clutch on the motor side eliminated the middle axle that once carried it, collapsing the drivetrain to the motor plus one fixed axle (driven gear, worm, spool) — and the blind's own worm gearing downstream keeps the pull cord alive. The clutch slips at end-of-travel, slips when a kid yanks the blinds, and slips below motor...

Read more »

  • Project Log #3 — Wand mode, solved by a sugar packet

    Joe Hill08/22/2026 at 13:17 0 comments

    Half the blinds out there don’t have a tilt cord — they have a wand, a plastic rod hanging vertically off a hook that you twist. The TiltRod’s drive axle exits the case horizontally. Twist a vertical stick, turn a horizontal axle: that was the last open mechanical problem on this project.


    Every dangling-hardware answer (shackles, chain links, hooks) dies on the same physics: hanging linkages carry tension, not torque — twist one end
    of a slack chain and the far end doesn’t turn, the twist just winds into the hang. Along the way I designed a two-piece, four-ball printed snap knuckle — two identical parts, snap together, ~30° of articulation with zero rotational slack under hang tension, pops off on overload instead of breaking — and then discovered Carl Weiss patented its kinematic heart in 1923 (the Bendix-Weiss joint that steered WWII Jeeps). Arrived 103 years late, kept the part anyway.


    The actual fix came from how native wand tilters do it: they incline the input shaft so the wand and the drive axis nearly line up — nobody transmits twist through the dangle. Our version: the TiltRod clamps
    around the tilt rod, and the worm mesh doesn’t care what clock angle the body takes around that rod. So wand mode is an install orientation, not a mechanism — clock the unit ~30–35° from vertical (a pendulum leaning on a foot), and the axle points down inside the knuckle’s reach of the hanging wand.

    What registers the angle? That got solved at the coffee counter with a Sweet’N Low packet: tear a corner off and you’re holding the shell’s cross-section with a chamfer cut into the bottom edge — a flat that seats square on the headrail at the wand-mode angle. Tear the opposite corner for mirrored installs. Zero new mechanisms: one chamfer on an existing
    part, plus a printed hanger eye that snaps onto the same axle end the cord spool uses. Your existing wand hooks right in.

    The full story (with the knuckle animation and the packet):
    https://www.tiltforge.com/blog/sweet-n-low?utm_source=hackaday&utm_medium=project&utm_campaign=wand

    Fit tests on the printed knuckle, spool socket, and hanger eye are running now; the chamfer geometry rides the beta shell revision. Next log is still the one that matters: the drivetrain goes into the headrail.

    TiltForge pre-orders are open (founders pricing on the first 100 units); beta units ship September. The journal has the whole story: https://www.tiltforge.com/blog?utm_source=hackaday&utm_medium=project&utm_campaign=wand

  • Project log #2 — The drivetrain is done

    Joe Hill08/20/2026 at 23:28 0 comments

    The new production motors arrived earlier this month — custom N20s with a 4 mm threaded shaft and direct-plug leads — and with them the last missing piece of the drivetrain. Motor, clutch-on-spur, worm, spool, tilt rod: assembled with the parts that will actually ship, running on the bench, on camera. Quietly, a second first: the Rev D control board ran the test — production electronics driving the production drivetrain.

    Video: https://www.tiltforge.com/blog/it-works?utm_source=hackaday&utm_medium=project&utm_campaign=drivetrain

    Watch the last angle: you can see the friction clutch engage — the part that entered this project as overload protection, physically transmitting the drive it eventually took over entirely.

    Full honesty, alpha edition: the gear mesh spacing is a hair off on these alpha shells — you can see it in how the spool runs — and the center-distance fix is already queued for beta. The only other casualties of assembly week were in firmware: the wrong build for the manual button functions and a flipped direction map. Remap, reflash, run. That's the good kind of punch list: the kind you fix in an editor instead of a slicer.

    Next log: the drivetrain goes into a headrail, and the blinds that started this whole project — dead commercial motors, no manual control, the works — function again.

    TiltForge pre-orders are open (founders pricing on the first 100 units); beta units ship September. The journal has the whole story: https://www.tiltforge.com/blog?utm_source=hackaday&utm_medium=project&utm_campaign=drivetrain

  • Project log #1 — Where Rev D landed

    Joe Hill08/20/2026 at 23:27 0 comments

    Kicking off the log at the Rev D milestone. The board consolidated the sensors and shrank the footprint, the clutch placement got refined, and the firmware picked up one-press calibration and ladder-free fault recovery. Next up: getting a clean install video of it running a real blind on a schedule, and documenting the print/assembly steps. Follow along — feedback welcome.

View all 3 project logs

Enjoy this project?

Share

Discussions

Similar Projects

Does this project spark your interest?

Become a member to follow this project and never miss any updates