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.
Useful Automation/Report
MCP Changes Integration from Fixed Endpoints to Dynamic Tool Discovery
n8n has published a guide comparing the Model Context Protocol (MCP) with traditional APIs, explaining when to use each and how to combine them…
