I’ve had a Remotec ZTS-500 z-wave thermostat for a few years now. I used it successfully on a now-deleted installation of OH2 as well as Home Assistant. I decided to go back to OH to give version 3 a try and have run into an issue with setting the cooling (and presumably the heating) setpoint, both in the app and in rules. When a new value is commanded, the number is updated and then immediately returned back to the previous value. Log entries follow.
2021-08-12 20:26:06.666 [INFO ] [openhab.event.ItemCommandEvent ] - Item 'Thermostat_Setpointcooling' received command 74 2021-08-12 20:26:06.671 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'Thermostat_Setpointcooling' predicted to become 74 2021-08-12 20:26:06.681 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Thermostat_Setpointcooling' changed from 73 °F to 74 °F 2021-08-12 20:26:08.104 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Thermostat_Setpointcooling' changed from 74 °F to 73 °F
In the app, I can see the set value toggling rapidly from the new value back to the old and, if I persist enough, it might evenually accept the value (or it might not). My knee jerk reaction was that this is an artifact of converting from F to C for the sake of the thermostat and that the value in C was being rounded one way or the other when converted back to F resulting in a net change of 0 degrees, from the viewpoint of the thermostat.
I’ve also found an old thread where others were complaining of the same issue in OH2 when working with degrees F and it makes me wonder if I just need to set up a rule to convert from F to C before sending the command to the thermostat. Does anyone have any suggestions?