BT entity not avaliable if trv is set to "offset based"

[thitcher]

Prerequisites

• [ TS0601 TZE200_hue3yfsn] Model name of your Devices

Description

I use a lot of these devices in combination with BT.
In the living room, there are four of the devices combined to one BT entity.
Normally, all TRV´s are set to "offset based calibration", but since a couple of weeks, the living room combination does not work anymore (not available).
I figured out, that the TRV1 is the problem, every time it is involved in the combination, BT stops to work.
The TRV itself works fine without issues....
So I changed this TRV against another one from another room, re-paired it, created a new group --> same behavior.
And now the strange message:
I figured out when I change the setting from only this TRV from "offset based" to "target temperature based", BT start to work!
So I suggest, there are some old-hidden data that cause this behavior?
Did several re-installations of BT and today the newest update, the behavior retains the same.

EDIT:
Did some further tests, re-paired an existing device (another room with only one TRV) and re-addes it in BT.
Now it shows the same behaviour: If it is set to "offset based" the BT entity is not avaliable, if it is set to "target temperatur based" it comes back and is working.
Maybe it´s a quirk problem? I use this:
ZHA_Quirk

maybe it is the wrong one?

Versions

[karba78]

same happens to me,,, went unavailable, but this time even changing from offset to target temperature does not bring it back

[thitcher]

Did some more tests:
Changed the quirk to this one: jacekk015/zha_quirks/ts0601_trv_zonnsmart.py
With this quirk it is possible to set the TRV´s to offset based without getting them unresponsible, but the valves do not work properly, I noticed that the offsets are changing, but the TRV´s do nothing, so the bathroom was cold and the wife not amused 😋.
After that realization, I changed the TRV´s back to target temperature based, and they immediately started to work as expected.
Now, this morning, I changed the quirk back to this one:
zha-device-handlers
With this quirk, it is acting as before, can not set to offset based without losing the entity availability.
So I think it is a problem related to the combination of BT and the quirk.

[thitcher]

Since today, none of my entities are up and running.
There were updates on my proxmox-server, which runs HAOS as VM (Kernel updates, etc.).
After processing the updates, all entities from BT got unavailable.
I removed one of the rooms and re-added it again from scratch (with temperature based-option), but no luck.
At HA, there was only an update for mushroom-cards, but I think that this update did not force the problem.
Restored an older core-version from HA, BT didn´t work, so I think there is something that has to do with the proxmos-updates?

EDIT:

you won't believe it!

exactly last night my netatmo lost the connection, because I use it as an outside temperature sensor, it was no longer available in HA and that is exactly what is causing BT to stop working. I restarted the Netatmo and everything is back.

Perhaps you could add an error message here instead of deactivating all entities.

The problem with the offset remains, however

[Ulrar]

Switching to target temperature fixes it, good tip! So same here

[jakobmoessner]

Same for me with "Spirit Zigbee wireless heater thermostat (SPZB0001) von Eurotronic" Firmware: 22190930 using Zigbee2MQTT.
But only for 1 TRV out of 2, exactly the same model and FW.

Update:
I found a difference between the 2 TRVs. The TRV mode was not set. The functional TRV was set to "2".
But its still a bit wierd. It worked, than stopped again, than one recovered, the other one needed a HA restart. We will see if it keeps runing now.

[vayed]

Same for me with Tuya thermostat ckud7u2l and b6wax7g0. When I downgrade BT to Version 1.4.0 everything is working fine.

Edit: I had to deactivate BT this night. It's heating up to 27°C for no reason even if the thermostat ist switched off in BT