Open thitcher opened 1 week ago
same happens to me,,, went unavailable, but this time even changing from offset to target temperature does not bring it back
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.
Prerequisites
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