You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wrote some javascript classes to implement a heating control. Since a long time, I have the problem that 4 of 7 thermostats change their values in the property zigbee.0...target_temperature automatically and without intervention of the javascript classes. This bypasses the complete control of the temperatures.
I've switched from deconz to ZigBee, but this did not solve the problem.
After more than a year of searching, I now came across the same bug on another channel (zigpy): zigpy/zha-device-handlers#1815.
The problem seems to have been fixed there: zigpy/zha-device-handlers#1816
Is it possible to implement such a solution for the ZigBee adapter?
Or am I on the subject completely wrong here?
Hence some more data:
iobroker: 6.3.5
Node.js: v16.19.0(16.19.1)
NPM: 8.19.3
Zigbee: v1.8.10
Thermostat manufacturer: _TZE200_yw7cahqs
Thanks for a replay.
Kind regards, Uwe
The text was updated successfully, but these errors were encountered:
I wrote some javascript classes to implement a heating control. Since a long time, I have the problem that 4 of 7 thermostats change their values in the property zigbee.0...target_temperature automatically and without intervention of the javascript classes. This bypasses the complete control of the temperatures.
I've switched from deconz to ZigBee, but this did not solve the problem.
After more than a year of searching, I now came across the same bug on another channel (zigpy): zigpy/zha-device-handlers#1815.
The problem seems to have been fixed there: zigpy/zha-device-handlers#1816
Is it possible to implement such a solution for the ZigBee adapter?
Or am I on the subject completely wrong here?
Hence some more data:
iobroker: 6.3.5
Node.js: v16.19.0(16.19.1)
NPM: 8.19.3
Zigbee: v1.8.10
Thermostat manufacturer: _TZE200_yw7cahqs
Thanks for a replay.
Kind regards, Uwe
The text was updated successfully, but these errors were encountered: