setpoint no longer show the "SetPoint"

[hestia]

Hi,
I've upgraded to 2023.2 (build 15555) and after a while I've discovered that it's no longer possible to update the "setpoint" of my heater (temperature) by the GUI.
But still possible by dzVents.

Code: Select all

dz.devices(SETPOINT_ID).updateSetPoint(SETPOINT_TEMP)

Screenshot 2023-12-19 213332.png (20.29 KiB) Viewed 2817 times

Same with the today's beta (for the GUI).

Is it by purpose?
In that case, how to use it?

[willemd]

It looks like "protected" is switched on ?

[waltervl]

My setpoint device in latest beta 15738 is doing just fine. Did you clear your browser cache? Do you have multiple versions of Domoticz in your house (eg test environment)?

[hestia]

sorry, I think I wasn't clear enough.

Before an update there was only 1 temp value in the setpoint devices, the one that I could still update by dzVents.
Now the are several values!

I've found an old screen shot of the GUI in domoticz-homeautomation-workbook.pdf that shows there was only 1 temp value

setpoint.png (264.74 KiB) Viewed 2682 times

[waltervl]

I really do not understand what the problem is. Please write down the exact steps to reproduce your issue.

[hestia]

In a former version I could update the sValue of Setpoint with the GUI

setpoint_before.png (34.58 KiB) Viewed 2614 times

After an update the GUI changed and it's no longer possible to update the sValue

setpoint_now.png (20.29 KiB) Viewed 2614 times

The sValue is not in the Edit GUI

[waltervl]

OK, and why do you want to do that through the gui in that way? Seems complicated instead of clicking on the button.

[hestia]

ok,
that's the answer!
And the change!
I didn't know it was working like this

setpoint.png (31.52 KiB) Viewed 2609 times

Not it was like this when I set it up, some years ago

[waltervl]

a Thermostat has always been like this as far as I know....

[andrehj]

Thanks @hestia for posting this issue, I just ran into exactly the same problem.
And thanks @waltervl for posting the solution. After years of using Domoticz, I never found out that you can simply click on an icon of a setpoint device to change a thermostat setpoint. Always used the same method as described by @hestia.

This function is not very intuitive though. (It is actually extremely counterintuitive).
The setpoint can be edited in the utility tab, in which it is not possible to click on any of the other icons. How should the user know that to edit the setpoint, he has to click on the icon, and that the most logical option (the edit button) cannot be used to edit the value?

[waltervl]

On all other action devices like on/off switches it is normal to click on the icon. There it is normal. The only thing is that thermostats are the only action devices in the utility tab.

[dami10]

No longer working since Beta Version 2024.5 (July 7th 2024).
For few months (summer!) Utility setpoint was not updating the device's set temperature, I could see in the log a setpoint command sent but nothing done, so I thought it could be a zwave issue.
After some time with zwave node refresh working as expected I decided to delete the node, delete the devices, then re-include the node. Association worked as expected but ended up with only 3 new devices (LaCrosse TX3, Thermostat Mode, Thermostat Operating State) instead of 4, missing the Utility device used for setpoint.

I can now only see the device in Temperature, no device in Utility, any one has the same issue?

[waltervl]

I can now only see the device in Temperature, no device in Utility, any one has the same issue?

That is heard before. The old OpenZwave integration does not support the new Setpoint/thermostat device. You have to switch to Zwave-JS-UI with Domoticz MQTT Autodiscover integration https://www.domoticz.com/wiki/Zwave-JS-UI

[dami10]

I can now only see the device in Temperature, no device in Utility, any one has the same issue?

That is heard before. The old OpenZwave integration does not support the new Setpoint/thermostat device. You have to switch to Zwave-JS-UI with Domoticz MQTT Autodiscover integration https://www.domoticz.com/wiki/Zwave-JS-UI

Thank you waltervl you rock!
Finaly I took time to migrate from OpenZwave to Zwave-JS-UI, found this setpoint device now working.