Keep your setup yours.
Choose components, pin their versions and keep household configuration in your own private project.
Create a project ↗OPEN SOURCE / BUILT FOR AI-ASSISTED SETUP
The open framework
for Home Assistant.
Reusable components. An agent that knows the project. A home configuration you own.
DomoSenso gives Claude Code and Codex the instructions, device requirements and tools to help configure your setup. Start from shared components and keep your home’s settings in a separate repository.
10 versioned catalog entriesHome Assistant ContainerApache-2.0 · commercial use welcome
From your devices to a working plan.
EXAMPLE BRIEF
“Help me set up Home Assistant with the devices I already have. Start with backups, then a wall tablet.”
- 01
Understand the home
The agent asks about your host and goals. With the access you provide, it reads your Home Assistant devices and integrations.
- 02
Match the components
It checks the catalog’s requirements, identifies missing hardware and explains what fits. You choose the scope.
- 03
Prepare your project
It creates a separate home repository, starts with backup configuration, renders files and prepares a deployment plan.
- 04
Review, then apply
You review the changes. Live writes need your explicit approval; configuration checks and verification support the next step.
Illustrative workflow using the onboard-home skill. Runs in your coding agent, with your access. This website does not connect to your home.
FIELD NOTES / THE FRAMEWORK IN USE
Installation 001.
Inside the first installation.
A concrete example of the framework’s components, running together in the maintainer’s home.
↳
Follow a numbered detail to the component behind it. These are photographs of one personal installation, not a customer project or a live demo.
SETTINGMaintainer’s home
HOSTHome Assistant Container
MATURITYEarly stage · one home
Start your project A CHANGE WORTH WRITING DOWN
A dashboard should fit
the home it lives in.
Not every home has plant sensors. Not every tablet needs a photo album.
In Ramka 0.2.0, climate, air, plants and photos became optional. Leave out an input and the corresponding page is left out of the rendered dashboard and its rotation.
The shared component stays the same. Each home decides what belongs on its screen.
Read the actual release notes
A photograph, not a live reading.
IN THE WORKSHOP How an agent helps with this change
EXAMPLE REQUEST
“I don’t have plant sensors. Leave that page out.”
- Read the contract. The agent checks that
plantsis an optional input in the selected release. - Prepare the configuration. It omits that input in your separate home project and renders the dashboard.
- Review before applying. You inspect the deployment plan and approve any change to the live installation.
Illustrative workflow · Claude Code or Codex · no connection to your home from this website
THE REUSABLE PART
Component index
Each entry has a version, requirements
and a record of what was tested.
COMPONENTRELEASEROLEFIELD EVIDENCE
01Awnings0.2.0Installable componentTested in 1 home02Backups0.1.0Installable componentTested in 1 home03Room presence0.2.0Installable componentTested in 1 home04Calendar0.1.0Integration guideTested in 1 home05Climate & air0.2.0Installable componentTested in 1 home06Lighting0.2.0Installable componentTested in 1 home07Connected audio0.1.0Integration guideTested in 1 home08Plant care0.2.0Installable componentTested in 1 home09Ramka wall tablet0.2.0Installable componentTested in 1 home10Weather0.1.0Integration guideTested in 1 homeNOTE One installation is a starting point. Automated checks validate configuration; suitability for another home still needs to be tested.
AN OPEN FOUNDATION
Build with it. Help it grow.
For home builders, developers
and professional installers.
Contribute what travels.
Add device support, improve agent skills or document a test in another home. Share reusable work through pull requests.
Contribution guide ↗Build services on it.
Apache-2.0 allows commercial use. Installers can build client projects on the framework; implementation and support are separate services.
Professional services ↗Early-stage project maintained by ZeroStoryPoints GmbH. Current field evidence comes from one personal installation; broader hardware and home coverage is work to contribute.
Start with your home.
DomoSenso is a framework for building Home Assistant setups with coding agents and versioned components. Your home’s configuration lives in its own repository.