I am unsure, I actually wrote this for my 2 ct101s
I did a config then refresh on my 101 it it should look like this. Debug turned on.
When you refresh you should get the hum
Does yours have a different fingerprint. Does it report sensor event E18
Thanks for the reply. I will switch back to your driver and see what the debug says when I get a chance.
I've now more carefully tried all three drivers. The system "Radio Thermostat CT101" driver reports temperature in 0.5F units but also does not give humidity updates. I'm back to the "Generic Z-Wave Thermostat" driver for now. It reports temperature in 1F units and I can get it to report humidity updates by issuing a refresh() command.
Check the finger print If its not the same as mine I may have to add it.
If it works with the others mine should be able to get it to report Humidity.
You may have to press the reset button to clear the memory and let it restore from the hub.
You may already know when switching between drivers like this you may need to use the driver called 'device' to clear everything.
My original complaint was no humidity updates. I am getting humidity updates every 15 minutes this time. I don't know what's different compared to the last time I tried it. I've turned off debug in preferences and it's still good. I'll keep an eye on it.
For reasons unknown this driver went off the rails while I was away this weekend. Chose its own sepoints and I couldn't change them. Humidity reporting stopped. Required a bunch of cleanup to go back to Generic Z-Wave Thermostat driver where I will stay. Thanks for sharing your work and I hope it continues to be useful for you. The rest of you have been warned.
Similar thing just happened to me. I always keep the basement thermostat set at 60 deg. This morning the basement felt very warm. Checked the thermostat and it was set to 70 deg. Looked at the log and the set point was randomly changed four times in the past two days between 60 and 70 deg. I also went back to the generic driver.
You must add the driver under (drivers Code) then it will show up as a option when you add a device. If it ads as a generic thermostat just change to this driver
Here's how its designed . If you turn on auto correct its going to use the temp you set in the app and self correct any local change kids make on the thermostat. It wont do it right away it uses the error counter. Then self corrects back to the last app setting.
But that function can be turned off.
Nothing in the driver sends random temps unless requested to do so by some script or something else on the hub. The temp it sends will be whats displayed. Unless the above function is on then the temp it sends is the last app requested temp.
If its sending random temps then something is making it do that,
I am at a loss to explain any of that as to i just installed another one now have 6 running and dont see anything like that,
