-
Notifications
You must be signed in to change notification settings - Fork 502
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
Zigbee lights switch on randomly across various vendors #5194
Comments
Hi there. |
Before putting effort into a new issue, read #5113 |
Yes 😉
It is an super old issue with various requests. Yes I will open one, but is was never solved even with direct contact to DE.
BR, Harald
Von: Dennis D ***@***.***>
Gesendet: Mittwoch, 11. August 2021 11:18
An: dresden-elektronik/deconz-rest-plugin ***@***.***>
Cc: Knoll, Harald ***@***.***>; Author ***@***.***>
Betreff: Re: [dresden-elektronik/deconz-rest-plugin] Zigbee lights switch on randomly across various vendors (#5194)
Before putting effort into a new issue, read #5113<#5113>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#5194 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AQNUS5MS3KQ5IOKWKK4BCJTT4I53ZANCNFSM5B52MOFA>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>.
|
Zigbee lights switch on randomly across various vendors. Usually between 8h and 24h. In my case dresden-elektronik.de, Paul Neuhaus and others as well. I have this issue for a long time now with deCONZ across all production and beta versions. A number of users reported this issue, but all “bug reports” are closed without a solution. I had in the “early days” a lot of discussions with dresden-elektronik, but no solution was found. It is not related to a specific version or hardware. I had this with ConBee, ConBee II, RasBee as well as I have it now with RasBee II. It seems to some degree dependent on the number of nodes involved. I segregated my network to limit the number of nodes per Zigbee network. Interesting enough – my “test network” with 9 nodes never had this problem. The problem seems to start with a higher number of – active – nodes (Routers). In other networks with 64 nodes or 53 nodes I have this behavior every day. Occasionally I have this behavior in networks with 20 nodes as well.
Please see also, because it is likely related to deCONZ, but it allways ends up without a solution
The text was updated successfully, but these errors were encountered: