-
Notifications
You must be signed in to change notification settings - Fork 506
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sonoff SNZB-03 #2991
Comments
Product Page: |
Please add the missing information as mentioned in the device request, thanks! |
The IAS Zone cluster is still missing. |
Hi devs - thanks so much. I'm also looking to use this device. I went to supplement this request but it looks like the screenshots above include the (1) Cluster Info panel, (2) Node Info panel, and the supplemental screenshot (3) has the IAS Zone information. I'm a new user, but wanted to help. Can you indicate what info is still needed, and where in the codebase I can find the device definition files? I perused the source but didn't find it. I'd like to contribute PR. |
Yes, thanks. That's what I needed. |
Closing this as device is now supported with .79 beta. |
Hi all, |
@pippo73 Feel free to open a own Issue (User question). |
PR is already prepared. |
This is now working in 2.05.84 but it doesn't show within Phoscon App (just as events in HA). Furthermore, I'm pretty underwhelmed by it compared to a Hue motion sensor. I guess it's to be expected with such a cheap price... Shame. (hoping that it can be improved through better integration with deconz perhaps?) |
Deconz is not Phoscon. If its missing there, feel free to raise it in the Phoscon repo. What better integration in deconz do you expect? It is done and you get what you paid for. |
Yes, perhaps should have left Phoscon out as it's not related (but thought it would be useful for the many people who will be using it). I'm not expecting anything, just stating that for my setup the sensor doesn't work that well. I wasn't sure whether that was due to preliminary support in deconz that will be enhanced, or whether it is just symptomatic of the device and therefore nothing can be done. From your response, I take it's the latter. |
It's unfortunately not too uncommon that devices do not work too well or differently than expected. And than mainly happens for cheaper devices. I specifically recal the Hive motion sensor here... If you could be a bit more elaborate on hat the device does (or doesn't do), we might judge if it is device related. |
Sure. My only comparison is with the Hue Sensor. Compared to the Hue sensor the Sonoff is a lot less reliable. Motion is typically not detected as well (can walk past sometimes and nothing happens, other times fine), the same is witnessed when I have a no motion automation e.g. "2 mins", it doesn't seem to fire reliably. The Hue never skips a beat on that front. Wondering if the reset time of the firing of events can be adjusted? |
I would like to ask if somebody else have an following issue with the Sonoff Zigbee motion sensors. I have two of them in different rooms for about 2 weeks and I have realized that they trigger motions it selfs almost periodically. It doesn't matter if is night or day, one of them is triggering exactly every 1,5 hour and the other one every 2 hours. I am using several Aqara Motion sensors too but without this strange behavior. The connection in deconz is green line therefore the issue must be somewhere else. |
I just checked mine and I got a simillar behavior. The sensor seems to be
unstable and fire event when there is nothing to detect.
I cannot test much now but I think SonOff stuff is not very good quality.
… |
@damajor I agree with you. Another magical thing is the blind time which in my case is 10 min! If somebody have any idea how to deal with this It would be great. Thanks |
Can you guys please open a separate issue for that? What you experience has nothing to do with the initial device support. Please take note that we'd require some logs catching this automatic trigger, occurring every 1.5hrs. It should have dbg-info=2 and dbg-error=2 included. |
Device
Screenshots
The text was updated successfully, but these errors were encountered: