Please note that there has been an update to the Thermostat support in domoticz, where these devices could and now do appear as "Thermostat 6" type (since Dec 2025). This is a combined setpoint and temperature device for which the standard device.updateSetpoint() command will no longer work. Hence ...

For thermostat 6 with temp or temp/hum or temp/hum/baro device use dzvents command:
device.updateThermostat(temperature, setPoint, humidity, humidityStatus, barometer, forecast)
See also https://github.com/domoticz/domoticz/pull/6477


Thanks, but I think this is a dangerous move and means we ...

Gravityz wrote: Wednesday 04 February 2026 19:24 are they detected through MQTT-AD, if they are then this seems to be a MQTT-AD issue

Yes, I have ZWAVE JS UI & MQTT configured.

yes, that is what I am saying. In my view, this is dangerous.

If you look at https://github.com/domoticz/domoticz/pull/6477 you will see that newly added devices (and I believe those that are replaced too...) will become Thermostat 6 devices. I was surprised by this, and even if new ones only would ...

I also experienced this recently with my Spirit valves, because on replacing a failed one they ended up now being "Thermostat 6" devices which combine the setpoint and temperature sensors (previously there were 2 separate devices defined when including them in the Zwave mesh).

Now, since the update ...

Hi You have to do the opposite command.

a) when the window is closed and you send an open command, you can stop it somewhere by sending a close command.
b) when the window is open and you send a close command, they will begin to close. if you want it to stop somewhere before they are fully closed ...

I am seeing similar issues where Domoticz state and remote device state is different, causing in my case issues with the heating system, see https://www.domoticz.com/forum/viewtopi ... =6&t=31559 for details. I would be interested in your view...