CT100 Plus - Temperature Settings Shifting

[h0ckeysk8er (Bruce Pinsky)]

@jeff1

tl;dr - I’ve been using CT100 and CT100 Plus thermostats for years. Starting a few weeks ago I started seeing my heat temperature settings shifting up by .2 to .5 degrees. I set the heat setpoint to 65, and it changes fine. Then within a few seconds it shifts to 65.2. Or 65.5. I have 4 of these thermostats across two different hubs, and they all started doing this recently.

Why does that matter? Because these thermostats kick in emergency heat + stage 2 heating after a > 2 temperature differential of actual vs setpoint. I have a number of routines to gradually heat my homes before I arrive, using only the heat pump (takes hours but saves $$). Those routines break when that extra increase in the setpoint triggers the heating strips. e.g. the 10k heating strips fire up immediately.

I HATE it when devices that work for years suddenly stop working . Any insights would be appreciated.

See this post.

Heating Set Point off by 0.2°F

Since the latest updates to the iOS and Android Apps, the introduction of the thermostatHeatingSetpoint and thermostatCoolingSetpoint capabilities does not allow temperature changes other than multiples of the interval (step) defined in the profile, by default 1°, starting at the lower temperature limit defined in the profile. Before it did allow it. The problem is that the temperature range is in °C and when it is converted to °F it will normally have decimals. For location in °C there’s not decimals problem The base-thermostat profile of the zwave driver has a range of 4°c to 28°c. Others profiles can have different range which in °F is 39.2°F to 82.4°F. - id: thermostatHeatingSetpoint version: 1 config: values: - key: "heatingSetpoint.value" range: [ 4, 28 ] On this profile, the a…