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 app will now only accept values from 39.2°F to 82.2°F, with 1° interval (39.2, 40.2, 41.2, …, 57.2, 58.2, …, 82.2), although the thermostat may have the temperature set without decimals, if you set it with a routine or on the thermostat instead of the app.
If they don’t fix it, a workaround might be to set a 0.1° interval although it may be more cumbersome
For the CT100 thermostat, which should be exclusive to the USA, a profile specific has been created with decimals in °C so that it does not have decimals in °F
- id: thermostatHeatingSetpoint
version: 1
config:
values:
- key: "heatingSetpoint.value"
range: [ 1.6, 33.3 ]