Home Assistant 2026.11 introduces child devices and simplified entity naming logic
Home Assistant is moving to a hierarchical naming system where names are built from context (area, device, entity) rather than being hardcoded strings, preventing redundant naming and improving organization.
Summary
The upcoming Home Assistant 2026.11 release implements a major overhaul of how devices, areas, and entities are named and displayed within the ecosystem. This change addresses long-standing issues with redundant naming and inconsistent context, such as when an entity name was manually changed but failed to reflect the parent device's name.
Users will now name components based on their individual identity, while the software dynamically assembles the full context on dashboards and settings pages. To support more complex hardware, the update also introduces child devices, allowing multi-part hardware like power strips to treat individual sockets as distinct entities with their own names and areas.
Structural changes in naming and device hierarchy
- Contextual Name Assembly: Instead of storing a single 'friendly name' string that combines all metadata, the UI now builds names dynamically using the area, device, and entity name to ensure consistency across different views.
- Child Device Implementation: Hardware consisting of multiple components (e.g., a power strip with multiple sockets) can now be represented as a parent device with individual child devices, each capable of having its own unique name and assigned area.
- Main Entity Designation: A new 'Main entity of the device' setting allows specific entities to act as the primary control for a device, enabling the UI to display only the device name for that specific control point.
- Backward Compatibility: The update preserves existing entity IDs, automations, scripts, scenes, and dashboards, ensuring that logic-heavy configurations remain functional despite changes to the visual display layer.
Why it matters
This update reduces the manual maintenance burden for smart home administrators by eliminating the need for complex, manual naming schemes to maintain consistency. It provides a more scalable way to manage large-scale IoT deployments where hardware components must be moved between different rooms or logical areas without breaking the naming hierarchy.
Original reference: www.home-assistant.io →