Introducing child devices
Child devices give integrations a first-class way to model the parts of one physical product, like the outlets of a power strip, instead of splitting it into several devices linked with via_device.
8 min read
Help buildthe open home
Code, design, documentation, translations, or community. Whatever you bring, this is where you start.
What do you want to do?
Build the software
- Build integrationsPython, core, and the integration platform.
- Work on the frontendDashboards, panels, and dialogs.
- Build appsPackage software that runs next to Home Assistant.
- Share what you buildPublish integrations, cards, themes, and blueprints for others to install.
- Work on the companion appsAndroid, iOS, and macOS.
- Work on the OS and SupervisorThe operating system, boards, and updates.
Design, write, translate
Run the project
- Grow the communityModeration, social media, and events.
- Test betas and releasesTry the beta, report what breaks, and see how a release comes together.
- See where we're headingHow ideas become planned work, and where you can help shape what comes next.
- Join an eventCommunity syncs and release days, and how to add them to your own calendar.
Understand how it works
From the blog
All postsShow form fields based on other fields
As of Home Assistant Core 2026.11, config flows, options flows, and blueprints can show a field only while other fields have certain values.
1 min readIntegrations have categories now
Integrations now say what they are for, like Lighting or Energy. What that means for your manifest, and how custom integrations can join in.
1 min read
Coming up
All events and how to joinRelease days, meetups, and community syncs: video calls about one project, open to everyone who is interested. Select an event to see what it is about and how to join.