Brief
Home Assistant 2026.7 makes purpose-specific triggers and conditions the default for automations
Home Assistant 2026.7 graduates purpose-specific triggers and conditions from Labs to the default for all users. Integrations can now teach the automation engine their own triggers and conditions.
The release shifts automation creation from starting with Home Assistant internals—which entity, which state, which trigger type—to starting with intent, such as 'When the bedroom drops below 18°C, turn on the heating.' Existing automations keep working. The useful detail for builders is that integrations can provide their own triggers and conditions, so the set of available building blocks can expand as integrations add them. This changes a workflow step from selecting low-level entities to selecting purpose-built triggers, and it means integration authors can expose higher-level automation primitives.
Our reading
Our reading is that this reduces the need to memorize Home Assistant internals when building automations, and it opens a path for integrations to contribute higher-level building blocks.
Source details and supporting facts
Each line is stated by the page named above it.
Stated by home-assistant.io
- Purpose-specific triggers and conditions graduate from Labs and become the new default for everyone.
- Integrations can teach the automation engine their own triggers and conditions.
- All existing automations keep working.
- Activity (logbook) has been rebuilt into a timeline that groups entries by day.
- There is a new update-all button, dedicated panels for infrared and radio frequency, an overhauled ZHA Zigbee device management, and 10 new integrations from the community.
Sources
- Home Assistant blogText stored 14 September 2026
How this story was checked. Written from the 1 page listed above, stored 14 September 2026; claims checked against that stored text on 14 September 2026.
What that means
- 5 of 5 reported statements were confirmed against the page that carries them; the rest were removed rather than published.
- Figures in the text were required to appear in the stored source text: yes. Identifiers: yes.
- The check reads stored text only: no claim rests on a fresh look that did not happen.
- Where the reporting was silent, the text says so instead of filling the gap.