I received from feedback from another developer that says that simply having the step value in the profile should be sufficient to fix the issue. That being said, the feedback also suggested that simply changing drivers would result in the strange behaviors you observed.
So, I’ve changed the range back to the original driver values and added the step value. Please either 1) reinstall the driver using the CLI; or 2) delete the driver via AWA and reinstall from the channel. Then re-pair your device using this most recent update.
Had to correct my post… I couldn’t resist trying this. After i installed this driver, re-paired the device and also booted the hub, it’s close !!!
the out of range still happens for me on the slider bar as soon as I select the thermostat, but…I can adjust the setpoint by clicking the setpoint temp and then scrolling from the 39f that it starts on and even though it will still return the “out of range” error, it does update the T-stat setpoint.
It’s better than what I had previously to change the T-stat remotely which was using a Routine.
No, you start by creating a fork of the ST repo on GitHub. You can then clone that repo to some development machine/environment where you can run the CLI to package the driver for publishing to a channel and/or installing to a hub. DM me if you need more details.
Did some more testing. Here’s some addition details on what happens.
If I use the slider to adjust the heating setpoint , it works it goes in increments of .2 usually but not always, and results in the out of range error unless I pick one that ends in .0. 69.0 is one of the only choices in an acceptable range. If I pick that from the slider, no error and the t-stat gets updated.
If I click the temperature to adjust directly , the scroll wheel selection starts at 39.2 (if last action gave out of range error) and goes in increments of .1
I posted earlier that support had me download an older Android version of ST (1.8.21) from December and my heating setpoints worked once again. I turned off suto-updating of ST and all is working perfectly. I may be missing some unknown new features but they don’t seem worth the effort to do a work-around to control my thermostats.
This is the link support sent me to access all of the old Android versions:
I wish they could , but apparently not. That was all I asked for in my first contact to them , but iOS apps aren’t archived anywhere like android apps.
It’s been two months of back and forth with them but the test driver from Bruce posted above is really close. The only issue is with the slider for the heat setting. If I just don’t use that and never try to, the temp can be set by clicking the temp setting and scroll to a new setting. Just don’t pick anything other than a whole number or it reverts to the out of range error and then you have to scroll starting from 30 something in .1 increments.
My hub got the new firmware today (56.00009) and also seems to be a new Z-wave thermostat driver (2025-03-17T20:11:50.62564114)
The issue with the out of range heating set point is better now. It’s slightly wanky now, but no out of range errors and am able to set the temperature now.
The only odd thing is that the set point still changes by .2
Ie. If the thermostat is set to 70, when you open the app and click on the device it will show the setpoint at 70, then it will change to 70.2. If you change the set point via the app, it will increment by .2 and set the thermostat correctly.