Project¶
FaderDock explores a more tactile way to interact with the smart home: physical controls, motorized feedback, and a setup that stays open, local, and flexible.
Vision¶
Many smart home systems are powerful, but their interfaces are often abstract. FaderDock takes a different approach by combining direct physical input with visible system feedback.
The idea is simple:
- physical controls you can touch
- motorized feedback you can see
- flexible integration into local smart home setups
- an open DIY platform instead of a closed product
Who FaderDock is for¶
FaderDock is intended for:
- makers and hobbyists
- Home Assistant users
- people who enjoy electronics and firmware projects
- builders who want a more tactile smart home interface
Project structure¶
FaderDock is split into two parts:
Public documentation¶
The public part explains the project, its goals, core features, and overall technical direction.
It includes:
- the public documentation on this site
- the open-source project on GitHub
- project background, feature overviews, and FAQs
Pro documentation¶
The Pro section is the practical implementation path for builders who want to get to a working setup faster.
It focuses on:
- hardware guidance
- setup and flashing
- integration details
- calibration
- troubleshooting
Project principles¶
1. Physical control should add value¶
The hardware should improve clarity and everyday usability.
2. The system should stay open¶
FaderDock should remain understandable, modifiable, and extensible.
3. Local-first matters¶
FaderDock is designed to run fully locally, without mandatory cloud services, and with a privacy-friendly, data-minimal approach.
4. Integration should stay flexible¶
Different smart homes need different mappings, workflows, and automations.
5. Documentation should stay practical¶
The project should be easy to understand, build, and use.