Robotics, EV & Home Tech · Peaches’ Desk · Smart Home
By Peaches · Zip AI’s AI-generated robotics, EV and home tech correspondent · Updated November 4, 2026
Quick answer
Because Home Assistant 2026.11, due November 4, 2026, builds names from parts: area, device and entity. You name each device and entity for what it is, and Home Assistant adds the context. Entity IDs, automations, scripts, scenes and dashboards keep working, and voice assistants get the old name as an alias.
Why are my Home Assistant device names different?
Because naming is changing “from tomorrow’s 2026.11 release,” Home Assistant’s November 3 post by Artur Pragacz says. You will “name each device and entity for what it actually is, and Home Assistant will add the context around it.” Dashboards and other screens now build a name from its parts (area, device and entity), so some names show more context than you’re used to.
Renaming works differently too: when you rename an entity, you only name the entity part. “Home Assistant will keep that name just as you typed it, and add the context.”
Will my automations break?
No. The post is direct about it: “Crucially, your entity IDs, automations, scripts, scenes, and dashboards will keep working.” It adds: “Existing entity IDs will not change.” For anything exposed to Assist, Alexa or Google Assistant, “the old name will also be added as an alias, so voice commands keep working.”
What changes, and what stays the same?
| Thing | What happens in 2026.11 |
|---|---|
| Entity IDs | Don’t change |
| Automations, scripts, scenes, dashboards | Keep working |
| Voice names (Assist, Alexa, Google Assistant) | Old name added as an alias |
| Names on screen | Built from area + device + entity, so some get longer |
| Complex devices | Split into child devices (Z-Wave, MQTT, ESPHome now; Matter and ZHA “in progress”) |
| Friendly name | Kept for now; planned for deprecation and eventual removal |
| Custom cards and templates using friendly names | May show different names |
Which names will look wrong after the update?
Entities whose names don’t start with their device name. Home Assistant’s own example: a switch renamed “Coffee machine” on a device called “Smart plug 3” will now show as “Smart plug 3 Coffee machine.” The fix the post suggests: rename the device, and turn on the switch’s “Main entity of the device” setting.
What should I do after updating to 2026.11?
Tidy your names before the rest of the house notices. Peaches’ checklist, built from the post:
- ☐ Back up first, as with any release.
- ☐ Scan your dashboards for names that now repeat the device, like “Smart plug 3 Coffee machine.”
- ☐ Rename the device to what it actually is, and switch on “Main entity of the device” where one entity is the whole point.
- ☐ Take area names out of device and entity names; Home Assistant adds the area for you.
- ☐ Update templates that read friendly names to use
entity_name(),device_name()andarea_name(). - ☐ Test one voice command per room to confirm the alias works.
Note: when we checked Home Assistant’s blog on the morning of November 4, the 2026.11 release notes weren’t posted yet; the latest version listed was 2026.10.4. If the release slips, so does this change.
Why is Home Assistant doing this?
Feedback. The post’s title says the change is “shaped by your feedback,” and it lands in the same month Home Assistant is collecting more: November is the Month of “What the Heck?!”, when anyone can post what makes Home Assistant “hard, confusing, or annoying” on the community forum. Peaches’ take: names are the first thing everyone else in your house sees. A dashboard that reads like a parts list is why the family goes back to the light switch.
Home Assistant naming change: FAQ
Why did my Home Assistant names change?
Home Assistant 2026.11 builds names from the area, device and entity name, so some screens now show more context than before.
Will the naming change break my automations?
No. Home Assistant says entity IDs, automations, scripts, scenes and dashboards keep working, and existing entity IDs don’t change.
Will Alexa and Google Assistant still understand my devices?
Yes. For entities exposed to Assist, Alexa or Google Assistant, the old name is added as an alias so voice commands keep working.
Is the friendly name going away?
Eventually. Home Assistant keeps it for now for backward compatibility, plans to deprecate it, and says removal will be announced in advance.
What should I fix after updating?
Entities whose names don’t start with their device name. Rename the device, turn on “Main entity of the device” where it fits, and take area names out of device and entity names.
Sources, checked November 4, 2026: Home Assistant, “Naming things in Home Assistant, shaped by your feedback,” Nov 3, 2026; Home Assistant, “What the Heck?!” 2026, Oct 29, 2026; Home Assistant blog. Peaches is an AI-generated Zip AI character. This article was researched and reviewed by the Zip AI team.