-
Notifications
You must be signed in to change notification settings - Fork 729
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
[Device Support Request] Sonoff SNZB-04p Zigbee Door/Window Sensor #3308
Comments
Despite the fact that two binary sensors appear on the ZHA, the second non-functional sensor is not the tamper. |
Some news about the support ? |
+1 |
Right now I can see 1 or 2 issue but should not be incredibly hard to fix.
One hypothesis would be that the contact entity comes from the IAS cluster and the other one from the on/off one but it is not working as intended. I have written to ITead support to have some information on this device. For my reference, their manufacturer code. Things to do :
Cluster testing for my referenceObtenir le status : service: zha_toolkit.conf_report_read data: ieee: 0c:ef:f6:ff:fe:90:46:16 endpoint: 1 cluster: 0x0500 attribute: 0x0000 manf: 0x1286Configuration attribut : Obtenir le status : Configuration attribut : |
I tried to configure reporting on the IAS zone state but it does not look promising : |
Hey there @liangjia2019, sorry to bother you. I saw you implemented the ZigBee2MQTT part for this device for Itead, would you mind sharing cluster details about this device so I can properly handle it? Especially 0xFC57 and 0xFC11? More importantly, would it be possible to update the device to do reporting on the IAS cluster for every 10-15 minutes like the SNZB-05P? |
Hi mguaylam , I'm glad to receive your message. Here are some relevant information I know: Cluster: 0xFC57 was Works with All Hubs (WWAH) Cluster,He currently only works on Amazon Hub,You can ignore. He is currently unable to report to the cluster within 10-15 minutes, but he may achieve it in the near future. |
Thank you for your fast reply @liangjia2019! Really appreciate your help on this matter. Unfortunately I see two major issues :
Things that need to be fixed in the firmware :
We would love to have your help on this matter in order to make this sensor a great recommendation for ZHA. Would you guys be interested into fixing those issues? Thank you for your help. |
They will solve it in the near future. Thank you for your feedback. |
Problem description
The device successfully pairs, and the primary binary sensor operates as expected.
However, the secondary binary sensor (tamper switch) does not function correctly; it remains in a "closed" state regardless of tampering or not.
Solution description
The tamper switch (rectius: secondary binary sensor) should detect and report any tampering by changing state from "closed" to "open" when triggered (or other proper states).
Screenshots/Video
Screenshots/Video
[Paste/upload your media here]
Device signature
Device signature
Diagnostic information
Diagnostic information
Logs
Logs
Custom quirk
Custom quirk
Additional information
The official Sonoff webpage shows the tamper alert doesn't work in ZHA: https://sonoff.tech/product/gateway-and-sensors/snzb-04p/
The text was updated successfully, but these errors were encountered: