Your names changed after 2026.11: the entity-naming rework, explained

Home Assistant 2026.11 shipped a naming rework four years in the making, and the team says plainly that it is backward-incompatible: some names on your dashboards will look different after updating. Nothing is broken in the scary sense — but voice commands miss, dashboard labels double up, and a few entity IDs surprise you. Here is what the new model is, what actually changed on a real system, and the calm way to fix yours.

Published Nov 18, 2026

The new model: name it once

The old system assembled names from pieces — device name plus entity name plus integration conventions — which is how you ended up with 'Living Room Lamp Lamp' and dashboards labeled by whatever an integration felt like. The rework's principle is name it once: a thing gets one name, in one place, and every surface (dashboards, voice assistants, automations lists) renders from that single source instead of re-deriving its own variant. It is a better model. It also means surfaces that were quietly relying on the old derivations now show the new, single name — which is why things 'look different' rather than broken.

Old model→Name it once→Device vs entity→What renames→Fix dashboards + voice

What actually changes on your system

The fix pass, in order

  1. Walk your main dashboard room by room. Where a label looks wrong, fix the entity or device name itself (Settings → Devices, or the entity's settings) — not the card. The whole point of the rework is that one fix propagates everywhere.
  2. Re-check voice exposure: Settings → Voice assistants → exposed entities. Confirm the names and add aliases for the phrases your household actually says ('couch lamp' next to 'living room lamp').
  3. Search automations and scripts for name-based matching (templates using name filters or state-name comparisons) and switch them to entity IDs, which did not move.
  4. Resist the rename-everything urge. The new model's gift is stability: rename once, deliberately, in the canonical place, and stop.

Upgrading soon? Do the naming pass in the same sitting as the Marketplace migration checklist — 2026.11 makes both changes at once, and one calm hour covers the pair.

Why they did it (and why it is worth it)

Naming sounds cosmetic until you run a house on voice control and shared dashboards: the name IS the interface. The old derive-everywhere approach guaranteed drift — the same light answering to three names depending on which screen you asked. Name-it-once makes the system learnable for the people who did not set it up, which is quietly the theme of this whole release cycle. An hour of renaming now buys back every 'why does it say that?' for years.

Official documentation and references

Frequently asked questions

Did my entity IDs change in 2026.11?

For existing entities, generally no — the rework targets names and how they are derived and displayed. That is why automations mostly survive while dashboards and voice surfaces look different. New entities created after the update follow the new model.

My voice assistant stopped understanding a light. What do I check?

The exposed entity's name and aliases under Settings → Voice assistants. If the display name changed in the rework, add the phrase your household uses as an alias — aliases are the durable fix, because they survive future renames.

Can I opt out of the naming changes?

There is no toggle back to the old derivation model. The practical path is a single deliberate naming pass (this guide's steps) so the new canonical names are the ones you would have chosen anyway.

Related guides