-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Enddevices unreachable because rejoin=false #1474
Comments
Removed all Osram plugs and ZBT bulbs from network. All 4 motion sensor stable for 24 hours :-) (then cc2531 crashed, but different story :-/ ) No one out there with hue motion sensors? |
I'm running HASSIO with Zigbee2MQTT plugin and an cc2531 as an coordinator. Got some IKEA and HUE bulbs, HUE motion sensors, dimmer switches, xiaomi devices and these OSRAM plugs. Every day I got another issue, first I thought it was the signal strenght of the cc2531 so I added an cc2530+cc2591 to my network but it got even worse. Motion sensor and the xiaomi devices stopped working randomly. |
i also have only the conbee stick, with ONLY 4 x aqara motion sensors, all is stable for about 2-3 weeks, then suddenly 1 aqara motion is unavailable, i need to repair is this the same issue? |
@sti0 Thanks for the report. I hope we find a third one that can confirm, than it will be worth a try to contact the manufacturer
@pergolafabio Sorry, seems not to be related. This issue is that router devices kick the sensor. But you don't have any router in your network. |
well @allofmex , i also had Osram Smart plugs, then my issue with end devices was much more frequent, like 5-8 days, then my end devices were kiced see screenshot, ignore the red circle , thats something else :) |
Hello, My setup is : Enddevices : Only the hue motion sensor act like this all the others devices are working just fine Unfortunately I don't have the tools to sniff zigbee packets but here my logs when it's working i have : and when it stopped working I have only : I hope this can help you |
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. |
@allofmex not that it helps, but its worth noting i have hue motion sensors connected to the same network that my hue dimmer is dropping on, and those are very stable reporting on motion consistently and never dropping out for many weeks now. |
Is the sensor close to one of the router? It chooses the parent out of the strongest neighbors. But if it is stable, even if frequently connecting the suspicious router, than this may not be the reason for your drops. |
its about 5 cm away from the hue remote and in the same room. Both devices are about 1 meter away from the same router, another router at 3 meters, another router at 6 meters and then the hub is in total about 6-7 meters away from this room |
Section 9.4 Leave Network:
So the Hue enddevices are working correct. The problem is with the OSRAM (and others) router. It sends an incorrect leave request. Did anyone found info's if there is new firmware available for OSRAM/Lightify Plugs? |
Bug Report
Not a zigbee2mqtt bug but effects all zigbee(-shepherd) user
See also Enddevices unreachable because route not updating (similar effects but different reason)
What happened
Enddevices (mainly hue motion sensor) get disconnected from network and are not working anymore
How to reproduce it (minimal and precise)
Motion sensor stops working after some hours.
Those with previous firmware (6.1.0.18912) rejoin after some time (up to 30 minutes)
Those with latest firmware (6.1.1.27575) shut down completely, setup button or battery reset needed
Debug Info
The problem seems to be:
Some of my routers are kicking out devices be sending
LEAVE
with REJOIN=FALSEMotion sensor (src64=...62:77) sends some last messages incl. own
LEAVE
anouncement and disconnects permanently from network. Next is coordinatorsroute request
that will never be answered anymore.Have seen this REJOIN=FALSE for following parent router
latest ioBroker dev version
CC253X firmware version: custom firmware close to 20190425
Expected behavior would be REJOIN=TRUE, as it happens on most of the parent changes:
I don't expect that we can fix this ourselfs :-(
First step should be to gather some more details:
(This may effect mainly (but not only) hue motion sensor owners since these sensor show a very annoying "parent hopping" behavior. Thats why they are much more in risk to be kicked out by one if it's many parents.)
The text was updated successfully, but these errors were encountered: