Setpoint problem

[frederico]

Hello,I have added the Honeywell thermostat within Domoticz (version 2020.2) via Hardware. Created API key, API Secret, Access token and Refresh token according to the manual. This went without any problems. After this I see the corresponding Honeywell devices in the device overview, including: also the Setpoint for the thermostat, in my case the Lyric T6. When I want to adjust the temperature via the Setpoint device, this temperature change is NOT visible on the Lyric T6 thermostat. After 5 minutes, the Setpoint returns to its original temperature. My question is why are the changes not coming through.

Kind regards,
Fred Weber

[frederico]

Kan niemand mij helpen met dit probleem?

[waltervl]

Edit: perhaps look/ask here: viewtopic.php?f=31&t=22430&start=40

[pgielen]

I am having the same problem still in 2023: the Setpoint device in Domoticz simply reads the T6 thermostat setting and displays that. If you change the setting of the device in Domoticz to another value, that value will be displayed in Domoticz but not sent to the thermostat. After a couple of minutes, the values are refreshed and the Setpoint device in Domoticz will once again display the original value that was in the thermostat all along. I think that either the Honeywell/Resideo API or the Domoticz plugin for it just is not implemented very well.

[janpep]

If you change the setting of the device in Domoticz to another value, that value will be displayed in Domoticz but not sent to the thermostat. After a couple of minutes, the values are refreshed and the Setpoint device in Domoticz will once again display the original value that was in the thermostat all along.

Same here in 2025! Sometimes it works. Sometimes not. But the result of this is that it is unreliable.
Is the cause and solution known?

[pgielen]

No, the problem remains. Honeywell/Resideo is apparently not interested in updating the API.

[janpep]

No, the problem remains. Honeywell/Resideo is apparently not interested in updating the API.

On your website I read (translated): "This is probably due to a clumsy implementation of the Resideo (Honeywell) API or the Domoticz plugin for it."
- Did you find out which of the two?
- Are there dzvents scripts known that access the api?
- Did I miss it or where did you find the description of the api?

[janpep]

For whom it is useful:
For the time being, I have made a kind of workaround, to at least have a notification when things might go wrong.
(In my case I set the timer for the setpoint from a script)
1. From my script I add timer to the SETpoint device with a temperature (let's say 21 degrees to warm up) and a second time with a temperature (let's say 12 degrees to cool down).
2. I have now created an extra dummy setpoint device and call it CHECKpoint.
3. From my script I also add timer to the CHECKpoint device with same temperatures, but times 7 minutes later than the SETpoint timer.

Then created a script that triggers on change of the CHECKpoint value.
When the script is triggered (7 minutes after the SETpoint change, it gets the value of the checkpoint, the setpoint and the heating state.
I consider three things suspicious:
1. checkpoint == 12 and heatingstate == 'On' or
2. checkpoint => 18 and heatingstate == 'Off' or
3. checkpoint ~= setpoint
In that case it sends me a notification with all the values, so I can be informed quickly and check it.

[Quest24]

I had the same problem. The creation of the device is very complicated, but I have the interfacce working. The only problem was the setpoint. I had removed the devices I didn't need. After setting the hardware to not active, and setting 'allow new sensors', and then update the hardware again to active, the other devices where added again, and suddenly the setpoint started working. So everything is working now!

[janpep]

.... It looks like the setpoint is only read from the thermostat and there is no interface to overwrite the setpoint?

In my case it was not a case of 'never', but every now and then.
It has been working fine for the last few weeks. I do not know what it was.
I am keeping my CHECKpoint just to be safe. At least then I will be warned.