ZHA: when adding a new Danfoss Ally thermostat the min and max temperatures are set wrong

Configuration Zigbee
1

Hi,

yesterday I integrated my 11th Danfoss Ally thermostat into HA (after updating HA to 2021.10). First integration went well as did the automatic firmware update to version 1.08 (like with all the other 10 thermostats) which I manually downloaded from Danfoss and put it into my OTAU folder of ZHA.

I already noticed with the first 10 thermostats that I need to remove the device and to newly integrate it after successful firmware update so HA reads the changed min. and max. heat setpoint attributes (5-35).

This went well with the first 10 thermostats, they all correctly are integrated with this temperature range.

Unfortunately the latest addition shows a different temperature range after removing and adding it again (did this twice) after the firmware update. This one can only be controlled from 7-30 °C. If I check the thermostat cluster (abs_min_heat_setpoint_limit, id 0x0003 and abs_max_heat_setpoint_limit, id 0x0004) the are correctly reported to ZHA.

What I am not knowing is which exact component is setting the values of the thermostat in lovelace. I know it is not the zha_device_handlers and it’s quirks.
So … is it zigpy? Is it the ZHA integration? Or even the lovelace thermostat card?

I need to understand this to debug this issue and put the right bug report to the right component (if it is not my own issue :wink:).

Any help appreciated.

2

Well … this problem fixed itself but I don’t know if it has been fixed by updating the core or the supervisor or by the restart of HA due to the updating. So … yeah … selfhealing at its best :joy:

3

I was able to also reset both values (as this happened again) by reading the thermostat cluster attributes “min_heat_setpoint_limit (id: 0x0015)” and “max_heat_setpoint_limit (id: 0x0016)” of the corresponding thermostat with the ZHA UI.