Home Assistant Daily: ZHA Groups Become Their Own Devices
ZHA groups now get dedicated devices in a breaking change, while a wave of new sensors and efficiency fixes lands across energy, MQTT, and polling integrations. The main pattern is cleaner device modeling paired with less wasted polling and parsing.
Duration: PT2M50S
Episode overview
This episode is a short developer briefing from Home Assistant Daily.
It explains recent repository work in plain language.
- Show: Home Assistant Daily
- Published: 2026-10-28T06:02:35Z
- Audio duration: PT2M50S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good morning, it's October 28th, 2026 — this is Home Assistant Daily.
The big story today is device identity — led by a breaking change that gives ZHA groups their own devices.
In pull request 188830, group entities move off the coordinator device onto a new device named for the group.
Entity IDs and custom names, areas and settings are preserved, so dashboards and scripts keep working — unless you targeted the coordinator device itself.
A follow-up, pull request 188982, hardens that migration by ignoring registry updates for devices without a proxy, preventing a harmless assertion error when upgrading from the October to November releases.
For developers, the takeaway is to test group automations against the new device structure and avoid assuming the coordinator owns everything.
Nearby episodes from Home Assistant Daily
- Config Flow Cleanup and Discovery Upgrades
- Undefined Sentinel Cleanup and Presence Fixes
- Cloud URL Fixes and Softer Failures
- Enums Push and Reliability Fixes
- Child Devices, Package Cleanup, and Core Hardening
- Weekly Recap - Setup Consistency, Backup Maturity, and AI Tooling
- Backup Hardening and Assistant Control
- AI Reasoning Controls and Integration Quality Push