-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
GLEDOPTO GL-C-008 is killing my mesh (not responding) #924
Comments
Here the some logs, having the GL-C-008, on, off and on again, controlling (blocking) the actors (ids,friendly_names):
Here the log:
Seems like the "router" is cutting the route of the HUE lamps. What is wrong here ? |
These clogging issues should be fixed in the latest dev branch, can you check? |
I upgraded to the latest and greatest dev commit. Still the same.
It somehow takes over some control. Strange. Try to reset the device. |
After resetting and joining the network again, I see the communication still being disturbed. |
This is indeed really strange, could you do some zigbee sniffing, perhaps this could give us a pointer. https://github.com/Koenkk/zigbee2mqtt/blob/dev/docs/how_tos/how_to_sniff_zigbee_traffic.md |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I can reproduce the strange behavior:
When switching the GL-C-008 on my sensor-actor communication seems to be blocked (buffered) somehow: for example, if I press one of my HUE dimmer switches, the flow (node-red) to control a HUE light is not working anymore.
After taking out the GL-C-008 (power off), all the button presses, seems to be processes (like queued) and the light is controlled. After a few seconds the mesh is fully functional again.
Can someone give me a hint, what is going wrong? Or how I can proceed to find the fault?
My logs says I am on
zigbee2mqtt version 0.2.0 (commit #753e8c3)
zigbee2mqtt version 1.0.1 (commit #5718cd0)
Here is the json block (database.db) for the specific device:
The text was updated successfully, but these errors were encountered: