Use thermostat setpoint byte size and precision from capabilities report

[kvolden]

The Zwave binding does not work properly with certain thermostats, because apparently it doesn't use the byte size and precision given by the thermostat through the Thermostat Setpoint Capabilities Get Command. In the case of HeatIt ZTRM3, it reports (and expects) a two byte setpoint, while it seems OH uses only one byte when setpoint is set below 25.5. In effect, the setpoint cannot be set to anything less than 25.5 degrees.

This was also discovered and fixed in OpenZWave, and it would be great if a similar patch could be made to the OH binding.

https://github.com/OpenZWave/open-zwave/pull/2458

OH version: 3.2.0 Zwave binding version: 3.2.0

[openhab-bot]

This issue has been mentioned on openHAB Community. There might be relevant details there:

https://community.openhab.org/t/heatit-z-trm3-temp-setpoint-not-working/97063/73

[olemr]

FYI. This is an analysis done by heatit: Test of thermostat Setpoint Command Class.pdf

[olemr]

@cdjackson sorry to ping you, but what is your take on this?

[cdjackson]

Sorry - there's nothing further than was discussed previously (as above) as I've not had the time to look at this.

[openhab-bot]

This issue has been mentioned on openHAB Community. There might be relevant details there:

https://community.openhab.org/t/smart-thermostat-for-electrical-floor-heating-system/150181/14

[openhab-bot]

This issue has been mentioned on openHAB Community. There might be relevant details there:

https://community.openhab.org/t/heatit-z-trm3-temp-setpoint-not-working/97063/82