SRT 323 - Best practice setup thermostat for OH3

hello guys. I just connected my SRT 323 zwave thermostat to my Openhab 3.2 milestone on zwave binding.

seems to work ok but from my reading here in the forum I understand that in order to get the ability to change the setpoint on the thermostat manually - I need to use the meta data to change to a default list widget and then to a slider widget.

that is ok unless there is a smarter way for that to happen automatically (i have 6 thermostats all together.)

That being said.

if i use the slider i dont get some information about when it actually changes. for example say it was set at 10degrees C and i put the slider at 15, i dont have an obvious to me way of seeing the 10c setting until it actually changes.

ideally i would be able to see. current number - new number requested

is this possible?


See Example Custom List Widgets. You only need to define the widget once then apply it to your six thermostats. You could event use the Humidifier Setpoint as a template.

You have two options here.

With Autoupdate set on, which is the default, a little autoupdate service will receive the command and predict what the Item’s new state will be once the device processes the command and updates the Item accordingly. This results in immediate feedback in the UI that your command was sent but it means that if your device takes some time to process the command the Item will not reflect the true state of the thermostat.

With Autoupdate set to off, which can be done in Item metadata, the Item will not change state until the device reports back that it’s changed state. This can take some time for some devices, some never report back at all, and the Item’s state and UI will not change until the thermostat actually changed in response to the command.

Those are your choices. Most of the time one will output the state of the Item as part of the widget so it might work to turn off Autoupdate and you can watch that output to see when the thermostat changed.

But if these are zwave thermostats they should be changing in less than a second anyway so I don’t know that you’d notice much of a difference (unless they are battery powered in which case it could be hours). If they take longer then that something is wrong with your mesh network.

1 Like

hi @rlkoshak thanks for taking the time! ok good point to mention. SRT323 is battery operated so the command can take up to X seconds (property dependent) to update. which explains why i needs this. basically i am looking for a confirmation that the command went through.

as i understand it the autoupdate set to off will be the case. i will play around. thanks!