Home

Physical smart home control for Home Assistant.

FaderDock is an ESP32-based motorized fader controller that brings real physical controls, automatic feedback, and a more tactile smart home experience.

Project Overview Pro Documentation Open Source

What is FaderDock?¶

FaderDock is a DIY motorized fader project for makers, tinkerers, and smart home enthusiasts who want more than touchscreens and phone apps.

It combines motorized faders, local control, and flexible smart home integration to create a physical interface for lights, scenes, rooms, media, and custom automations.

Note

FaderDock is an independent project and brand.
It can be integrated into custom smart home setups, including platforms such as Home Assistant.

Why FaderDock?¶

Physical feedback¶

Use real motorized faders instead of controlling everything through apps and dashboards alone.

Two-way sync¶

FaderDock is designed to reflect changing system states, not just send commands.

DIY-friendly¶

Built for people who enjoy assembling, flashing, testing, and customizing their own hardware.

Open and flexible¶

Use the public project resources, build around your own workflows, and extend the system to fit your setup.

Choose your path¶

Public¶

The public part of FaderDock explains the concept, feature set, current status, and high-level technical approach.

project overview
feature highlights
public documentation
open-source scope
roadmap and FAQs

Go to Open Source

Pro¶

The Pro section is the practical implementation path for builders who want to get to a working setup faster.

getting started
bill of materials
wiring and setup
flashing
integration
calibration
troubleshooting
downloads

Go to Pro Docs

Who is this for?¶

FaderDock is a good fit if you want:

a tactile smart home controller
motorized faders with real physical presence
a DIY hardware project with a polished result
a system you can understand, modify, and extend yourself

Start here¶

Read the Project Overview
Explore the Open Source section
Continue with Pro Documentation for the full build path

See the FAQ for common questions and the Changelog for project progress.