Namron 4512757 z-wave thermostat not able to set even/whole temperatures

[tronsdal]

Checklist

• I have read and followed the above instructions

• I have checked the troubleshooting section and my problem is not described there.

• I have read the changelog and my problem was not mentioned there or the fix did not work.

Describe the issue

What is happening?
When I try to set the temp to whole degrees (e.g 17.0, 18.0 etc.) there is an error, and nothing gets updated. If I set it to 17.1, the thermostat gets updated. The same with 17.01 (the thermostat then shows 17.0 in the physical display). I have tried two different thermostats with and without security, and I have tried both with the original z-wave-js and with z-wave-js-ui.

This is very unfortunate, bacause I have a smart integration with my electricity company Tibber, but they only send whole degrees, thus no smart change of temperatures are working. I also have a Homey Pro 2019, and there everything works.

What did you expect to happen instead?
The temp setpoint set to 17.0

Steps to reproduce the behavior:
Try to set the Namron Thermostat entity to an even number like 17 or 17.0 fails. Half degrees like 17.5 works.

Anything else we should know?

Software versions

Driver (node-zwave-js): 12.5.5

Z-Wave JS UI: 9.11.1

Home Assistant Z-Wave Integration: Not sure (1.35.0-beta.1 ?)

Home Assistant Z-Wave JS Addon: 3.5.0

ioBroker.zwave2 Adapter: Aeotec Z-Stick Gen 5

If you are using something non-standard, tell us here: nope

Device information

Manufacturer: Namron
Model name: 16 A Thermostat - White - 4512757
Node ID: 034 (insecure) and 037 (secure)

Checklist

• I made sure to provide a driver log on level debug.

• The log includes a re-interview of the problematic device (if applicable).

• The log includes the problematic interaction with the device (if applicable).

• I provided the node ID of the problematic device (if applicable).

Upload Logfile

zwave-js-ui-store.zip

[AlCalzone]

I've seen this before with other thermostats. Essentially they expect the setpoint to always have exactly one decimal digit, so 17.0 instead of 17.

[AlCalzone]

Escalated to an issue: #6792

[AlCalzone]

@tronsdal The fix has been merged, but I'll likely not make a new release until the week after the next since I'll be traveling.
If you want to test it before that, you can follow these steps with this file.

[tronsdal]

Great! Thank you so much. That worked perfectly :-)