Hello, I found an issue regarding the functionality of at least SONOFF SNZB-03 Zigbee motion sensor. After implementation of it everything is ok (I have 9 of them installed in all my house) but some time one of them (random) stays always on (motion active) even if the sensor blink me when I move my body in front of. I suppose it is about a problem regarding the management of it, not a sensor issue, in Hubitat and on the dashboard I see it is always active, and no response even if I want to execute a status refresh. Some time it works again after few hours, some time I should reinstall, so I need to delete it from all apps and reinstall as new... Anybody found this issue regarding the motion sensors or we need for an driver update?
To mention, that is installed as Generic Zigbee Motion sensor.
Thank you!
I have had this and it was a battery issue. It was a new battery but had mysteriously "unseated" itself after an activation. Once I removed refitted the battery it operated as normal. Its worth checking and/or replacing the battery
I tried first 
not work...
I have at least 60 of them in at least 6 locations. I see this once in a while and it does not create a problem for me. I have multiple motions in each area and use motion combiner to eliminate false motions but as a side effect it eliminates the stuck active issues as well.
I have the same problem with all my 3 Jasco Dimmers/MS.
These are hard wired, so there is no battery related problem.
All my battery powered MSs are perfectly fine but exhibits
similar problem when battery is near discharged
(reported "active" but missing "inactive", better to be opposite).
My "fix" for the Jasco Dimmer?MS is a special rule(s) doing
periodic (every 5min) refreshment for these toys as soon as
they reported "active" state and until becomes "inactive".
However this approach may not work for battery powered devices.
I decided to sell all my Sonoff MS's (apart from 2) on ebay as I kept getting false motion detection with them.
It started after having them for about 6 - 12 months. Changing to new batteries or increasing tension in the battery terminals had no effect.
It was a shame as I really like them. I tried one the other week by putting it in a box so no motion could be detected. Anything between 4 and 8 days it would give a false motion event.
In hindsight I could have doubled them up to eliminate false motion detection but got too impatient.
It's possible that you're doing everything right and you just got a "dud." They're so cheap that I basically expect this to happen once in a while. 
(I've never had it happen myself, but I only have a few.) The troubleshooting you've received above is good, and the only other thing I'd add is to make sure you have a strong Zigbee mesh. That's a good idea in general, but some people report that these devices have weak radios, so it might be particularly important for them (e.g., having a repeater nearby). The http://<ipAddress>/hub/zigbee/getChildAndRouteInfo output can show you some stats, but not all devices may appear in that table; the Settings > Zigbee Details live logs may show you some of these stats as well. (Interpretation of all of this isn't formally documented, but you can find some threads here plus this for the logs: https://docs.hubitat.com/index.php?title=Zigbee_Logs).
This should not affect your motion readings, but the best built-in driver for this device is "Generic Zigbee Motion Sensor (no temp)."
Just to add. Possible it's related to your ZigBee mesh as well. Maybe a healing is needed or more repeaters for stronger mesh.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
