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.
I was wondering about that since I had been using the 2.3.0 snapshot when this started giving me trouble.
Well, I went through that procedure, deleted the nodes, uninstalled the snapshot (to the best of my ability; I can’t see any reference to the old one in bundle:list), installed the new one, added all the new nodes.
My security-based devices did need some modifications after that, so I know the update took effect. However, the thermostats are still being recalcitrant:
2019-01-10 16:58:33.922 [ome.event.ItemCommandEvent] - Item 'UpstairsThermostat_SetpointHeating' received command 67
2019-01-10 16:58:33.939 [nt.ItemStatePredictedEvent] - UpstairsThermostat_SetpointHeating predicted to become 67
2019-01-10 16:58:33.949 [vent.ItemStateChangedEvent] - UpstairsThermostat_SetpointHeating changed from 65 to 67
2019-01-10 16:58:35.541 [vent.ItemStateChangedEvent] - UpstairsThermostat_SetpointHeating changed from 67 to 65
2019-01-10 16:58:36.125 [vent.ItemStateChangedEvent] - UpstairsThermostat_BatteryLevel changed from 99 to 94
2019-01-10 16:58:50.484 [vent.ItemStateChangedEvent] - UpstairsThermostat_SensorTemperature changed from 65 to 64.5
2019-01-10 17:02:48.880 [ome.event.ItemCommandEvent] - Item 'DiningThermostat_SetpointHeating' received command 71
2019-01-10 17:02:48.888 [nt.ItemStatePredictedEvent] - DiningThermostat_SetpointHeating predicted to become 71
2019-01-10 17:02:48.903 [vent.ItemStateChangedEvent] - DiningThermostat_SetpointHeating changed from 70 to 71
2019-01-10 17:02:50.283 [vent.ItemStateChangedEvent] - DiningThermostat_SetpointHeating changed from 71 to 70
2019-01-10 17:02:50.792 [vent.ItemStateChangedEvent] - DiningThermostat_BatteryLevel changed from 46 to 41
By god those thermostats are NOT going to accept any orders from me!
It didn’t have anything to do with adding/removing things. Rather subtly, it had to do with my default region in OpenHab not being set, which is interesting because the change happened invisibly to me and I didn’t think openhabian just automatically updated.
Anyway, I noticed that when I set the setpoint to a low number (8), it accepted it (!). I then walked to the thermostat and saw it was set to 46 degrees; Thermostat in F, OpenHab in C.
I set my region in OpenHab (took a while to find) and lo and behold, it works again.
WHEW. That was enormously confusing. Evidently when I was setting it to 60 it thought “60C? Not possible; I just won’t take it.”