Update to Core 2025.2.X mixing up my Thermostat Entitys

[CodeWanderer7331]

The problem

Hi all,
I first noticed it when I looked at my heating dashboard after the update. The tiles for setting my thermostats just showed "not available". I then tried to straighten the tile again and saw that, for example, climate.heating_bedroom_thermostat was no longer available, but only climate.heating_bedroom_thermostat_2. This is also the case for several entities of the radiator thermostat. This affects all thermostats and, as I said, occurred both when I tried to update *.0 and *.1. I have not checked whether other devices besides the thermostats exhibit this behavior.

I attached some screenshots.

What version of Home Assistant Core has the issue?

core-2025.2.1

What was the last working version of Home Assistant Core?

core-2025.1.4

What type of installation are you running?

Home Assistant OS

Integration causing the issue

zha

Link to integration documentation on our website

https://www.home-assistant.io/integrations/zha/

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

[home-assistant]

Hey there @dmulcahey, @Adminiuga, @puddly, @TheJulianJES, mind taking a look at this issue as it has been labeled with an integration (zha) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of zha can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign zha Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

zha documentation
zha source
_{^{(message by IssueLinks)}}

[Coninox]

I have the same problem. a lot of entities have been renamed. (for example, all "climate.xxxxx" have been renamed to "climate.xxxx_thermostat")

All my automations related to heaters are broken. I had to rewrite them urgently since it's winter...

[puddly]

Please upload diagnostic JSON for each affected device.

[Coninox]

The diagnostic JSON of one of my TRV valves (all my affected devices are the same model)

zha-01J8NDN18PBPSHRZZY3KPSTRT5-_TZE200_c88teujp TS0601-66fd00be6b3f256ae8e297e4ce9ff7ab.json

[TheJulianJES]

We're tracking some TRV related issues in the quirks repo. E.g. in zigpy/zha-device-handlers#3837 and zigpy/zha-device-handlers#3834.

For your devices, do/did you use any custom quirks?

[Coninox]

in my case I did not use any custom quirk.
And I discovered that, even after rename all my entities in my automations, the service set hvac_mode doesn't work anymore. It doesn't work either from the thermostat card. I can't see any change on my valves when I try to turn them on or off.

[CodeWanderer7331]

@TheJulianJES yes, sorry that I forgot to mention it: I use two different custom quirks, because my 2 sorts of trv are not support out of the box by zha correctly.
I have those two types (and for both the issue happened):

_TZE200_h4cgnbzg
_TZE200_9xfjixap

Okay I just looked through your mentioned bugs. So I'll first be a bit patient for upcoming releases, when the things will more clear up and will then try again to update. Thank you!