Nice.. no need for me to write it then
Take it and do what you wish with it. I created it to get over a few things and a few people need to do the same so stuck it there. Nothing special or neat about it so it could probably be cleaned up and made more use of.
1 Like
No need.. As long as it works.. And is available to people..
2 Likes
It worked, thanks! No more sleppy. (And no more CDO triggering. 
)
2 Likes
Changelog:
2020-05-03 - importURL
I noticed some 'null' entries in my log overnight, and I think they're related to temperature reporting. They occur hourly alongside the power reporting. I switched to debug and forced the report, and think I have it, but let me know if you need anything else. It doesn't appear to be affecting functionality (current reported temperature is correct), so this is more of an FYI than a bugfix request.
Overnight Logs (portion of):
Debug Log:
1 Like
I think I know what it is already.. Will push an update shortly..
1 Like
1 Like
Thanks! It's loaded up. The reporting occurs naturally at :42 past the hour, so I'll let it soak for a bit.
1 Like
Good news, bad news...
Good news: It's no longer null.
Bad news: Um... 
I took the liberty of fixing the code on my own:
2 Likes
Doh 
Fixing now
1 Like
Released too many drivers this weekend.. Got some things mixed up apparently..
1 Like
v1.3 pushed.. fixed
2 Likes
This driver is forcing the sensor to report its temperatures in Fahrenheit, could we please get an option to use Celsius?
There are three places where it's doing it I think, all like:
cmds.add(zwave.sensorMultilevelV5.sensorMultilevelGet(scale: 1, sensorType: 1))
Scale 1 is F, scale 0 is C. This device does have a configuration parameter (64) that controls whether it sends C or F. Could that be a setting, and then you use the value of the setting when doing the sensormultilevelget()?
FYI other drivers for this device don't have this problem as they don't seem to specifically request the temperature, they just let the device send it when it wakes up. It sends it in the scale it's configured to use.
1 Like
Yes.. Absolutely.. Will have that fixed today..
From the docs.. It appeared that it was automatically set to C and report C based on the region.. So I wrongly assumed it would report the value from that region..
@pjam73 this should fix you up.. let me know if you still have any issues
Changelog:
1.4
- Fix for location based temperature scale
1 Like
Thanks a bunch! I'd been looking for this capability.
2 Likes
Dude, you rock! I just bought one of these!
1 Like
Another thing I knew must exist, and here you are making magic!
unfortunately.. I'm getting the following error when I try to import v1.4:
unable to resolve class hubitat.zwave.commands.notificationv7.NotificationReport @ line 261, column 17. unable to resolve class hubitat.zwave.commands.versionv2.VersionReport @ line 462, column 17.
Any thoughts what might be the issue?
thanks!
Andrew
1 Like
What Hubitat platform version are you running? My guess it is before 2.1.8.x - you will need to update to 2.1.8 or newer to use this driver.
Please see the release notes for platform 2.1.8 - I'm pretty sure it will explain the issue you've run into.
1 Like
