We have two CT100 thermostats that have been working fine for some time, and then when we returned over the holidays… they’ve been acting quite odd. I updated OpenHab2 to the latest version (my Z-wave controller is on a Pi running Openhabian; sorry I can’t remember the actual version number), and reset the thermostat and changed batteries, but the problem persists: it’s not setting its setpoint (which makes it less useful as a thermostat).
Stranger, my logs seem to imply that it IS being set, but is immediately going right back:
2019-01-08 10:24:59.639 [ome.event.ItemCommandEvent] - Item 'UpstairsThermostat_SetpointHeating' received command 64 2019-01-08 10:24:59.649 [nt.ItemStatePredictedEvent] - UpstairsThermostat_SetpointHeating predicted to become 64 2019-01-08 10:24:59.670 [vent.ItemStateChangedEvent] - UpstairsThermostat_SetpointHeating changed from 66 to 64 2019-01-08 10:25:01.142 [vent.ItemStateChangedEvent] - UpstairsThermostat_SetpointHeating changed from 64 to 66
You can see the numbers change back on PaperUI about a second after you send the command. I’m baffled; this was working just fine for a while and as you can see from the time stamps it sets itself back quite quickly. The downstairs thermostat mostly does the same thing, although occasionally it claims it’s been set but I look and discover it is lying.
Any ideas? Mornings have gotten a lot chillier!