Heads-up: Home Assistant 2026.6 can double the room name in new entity IDs

[hiall-fyi]

If you're on Home Assistant 2026.6 or newer and you do a fresh install of Tado CE, you might notice some entity IDs come out with the room name twice, like sensor.lounge_lounge_temperature or climate.lounge_lounge instead of sensor.lounge_temperature / climate.lounge.

I want to be upfront about this: it isn't a Tado CE bug. It's a change in Home Assistant Core itself, and it affects any integration whose devices sit in an area of the same name (which is the normal Tado layout, where each zone device lives in its own room area).

What actually changed

HA 2026.6 (PR #170560) started adding the area name to the entity ID when an entity is first created, on top of the device name it already used. There's no de-duplication between the two, so when the area and the device share a name ("Lounge" device in the "Lounge" area), you get "Lounge" twice in the slug. There's an open request to make this optional or roll it back (issue #173125), but nothing's been decided upstream yet.

I found this while building the new per-device Identify button for the next beta, so I've had a proper look at it.

Who's affected

• Existing installs upgrading Tado CE: not affected. Once an entity ID is written to the registry, HA never auto-renames it, so your slugs stay exactly as they are through any upgrade.
• Fresh installs on HA 2026.6+: affected, but only cosmetically. The entities still work normally, the friendly names are still correct (you'll see "Lounge Temperature", not "Lounge Lounge Temperature"), and history, automations, and dashboards all function. It's just the slug that reads a bit odd.

What you can do

If a doubled slug bothers you, you can rename it yourself in Settings → Devices and HA will keep your chosen name. I'd hold off doing it wholesale for now, since HA may yet change this behaviour and that would be wasted effort.

I've already set the new Identify button to use a fixed entity ID so it isn't affected. For the rest, I'm holding back on a blanket workaround on purpose: pinning every entity ID would mean carrying a large slug map forever, and if HA changes course it'd all have to come back out. I'd rather watch how upstream settles than take on that maintenance for a cosmetic issue. If it turns out HA keeps the behaviour long-term, I'll revisit.

Happy to answer questions here if anything's unclear.

#Joe

[hiall-fyi]

A quick update, and one thing worth adding to the original post.

Upstream still hasn't decided. The rollback request over at home-assistant/core is still open. A maintainer said on 25 June that they're watching it but haven't made a call, and that they can't realistically add an opt-out toggle for every change. The fix that would sort our case specifically, skipping the area prefix when the device name already has the area in it, hasn't been taken up either. So nothing's changed: no fix, no timeline. I'm still holding off on a workaround rather than chase something that might move.

One thing I should have flagged the first time round. I said existing installs aren't affected, and that's true for normal upgrades. But there's one action that will change your slugs even on an existing install: HA's "Recreate entity IDs" button. On 2026.6+ it re-applies the new scheme, so running it on your Tado entities turns sensor.lounge_temperature into sensor.lounge_lounge_temperature, and anything referencing the old slug breaks. Removing and re-adding the integration does the same. So if you're on 2026.6+, leave "Recreate entity IDs" alone for your Tado entities for now.

Everything else stands: fresh installs get the doubled slug (cosmetic, entities work fine), normal upgrades are untouched, and you can rename any slug you don't like under Settings → Devices. I'll post again here once upstream settles.

#Joe