Having recently discovered a GitHub device driver for a SONOFF switch I was wondering if there was anything out there for the above device. I have 4 of these but when added as a Generic Z-Wave Sensor all I get back from them is Battery and Tampering events. Can a user defined device driver code make something work which does not register events as I've described. When I added the device code to my SONOFF Zigbee contact sensor it wasn't to get extra functionality but to see if it prevented it from hanging after about 12 hours. I'm new to this hub so I'm not sure when a problem is found with a device if it's down to the core operating system/application of Hubitat or something which can be coded by the end user ?
Those sensors should be supported straight out of the Hub.
Have you tried the Aeotec Door / Window sensor 7 or the Aeotec water sensor drivers as I’m guessing that they’re likely to have very similar capabilities.
I'll give them a try
Ok - so this is the situation. I excluded the device from ST. I included the device with HE.
Initially on the device's event log it showed open/close and tamper events. So I added a tile to my dashboard - tried both contact sensor and door status but I don't think this matters. As I had both sides of the contact sensor with me I was able to test easily. I noted that sometimes the tile status would stop updating. I went to the logs and I could see that events had also stopped appearing in the log. I rebooted the hub and could not see any change. Finally I removed and re-inserted the battery of the contact sensor. At this point events started appearing for a while and the tile showed the correct status. However I could only see this for maybe 10 open/closes before it would get stuck.
I went in the device settings - advanced where I could see that the device was marked as NOT_RESPONDING. Viewing the log for the device I can see that sometimes during an open or close it will send 2 notifications of the same type in very quick succession - a few milliseconds apart. Not sure if this is typical for devices or maybe something which is confusing HE. Anyway I excluded from HE and added back to ST and now it's working as before without getting "stuck"
Hmm definitely weird.
So previously I’ve heard, anecdotally, that that the ST radios are stronger than those on HE hubs ( certainly pre C7 ).
Could the sensors battery be an issue here ?
Sensor initially working then battery draining and unable to reliably contact the HE hub ?
When your testing with the HE is the ST hub still powered up ?
Just wondering if that might be causing RF issues.
