-
-
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
Almost (not quite) all devices suddenly lost connectivity #19071
Comments
It can also be due to other devices or the computer itself interference. Note there is nothing I can do from z2m to fix this error. |
I have the same problem, it started after I upgraded to 1.33 and updated the FW to 20230507 on my Sonoff ZDongle-P. I have a second setup at a different localtion where I don't have any issue, the only difference is the adapter, it's the ZZH instead of the Sonoff. Also I don't have the MAC error bu these two on all routers: |
@Koenkk - So I moved the dongle to somewhere else in the room and I am getting connectivity now. Only moved it by about 1 metre, plus it's on a 2 metre extension lead so the dongle itself it at least 1 metre from nearest computer. I have Tx power set to 20 on the 4 routers/coordinator. Most, but not all, the devices are showing green again but... Several of them are showing green but are not working. For example, my Physically operating the switch
Operating switch via HA
Any ideas how to fix this? Re-pairing is a big inconvenience because I have to undo all the switch plates. |
I see you are running the 20230507 firmware which is not considered stable, can you try 20230923? |
@Koenkk - I updated to 20230923. I didn't know whether it should be launch coordinator or other coordinator. I couldn't find out what this meant. So I went with launch coordinator. I found a missing router (when I requested coordinator check) which I removed from the network. Now I get a clean reply The same 3 devices are showing their on/off status correct but are not controllable. |
Hi
As you have the Sonoff ZDongle-P, the firmware is the CC1352P2_CC2652P_launchpad_coordinator* |
@blacknell so it seems the device is not reachable and no other device has a route to it.
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
What happened?
I've had my zigbee setup running pretty well without incident for about 2 years when suddenly I noticed almost all devices were reported offline.
After some digging I found this error.
This pointed at probably Wifi interference. I was using Zigbee channel 15 which does overlap partially with wifi channels 1 & 6. I changed my wifi access radios to fix with channel 11 (which shouldn't overlap at all). It all worked again for a few days.
Then it stopped once more. This time I tried wifi channel 13 (no luck).
Then I switched off all the 2.4GHz radios. Still no luck. I should add that wifi signals from neighbours are very weak.
What did you expect to happen?
I expect to see all my devices online.
Instead most but not all are suddenly now constantly offline.
I don't think this is channel interference (it's happening with wifi OFF). It could be a hardware failure but I have no clue how to validate this.
Would really really appreciate some help from @Koenkk and the community
How to reproduce it (minimal and precise)
Difficult to say the least. It's happening 100% on my set up as follows:-
I have one coordinator (of course), 3 dedicated routers (distributed across the house), 15 powered devices (not all can route) and 8 battery devices. The coordinator and dedicated routers are all Sonoff Zigbee 3.0 USB Dongle Plus with the zStack3x0 firmware with 20230507 (coord) and 20221102 (router) from @Koenkk.
The LQI's were all pretty high when it was working.
I keep all the addons and firmware upto date (last change was to 1.33 about 3 weeks ago).
Zigbee2MQTT version
1.33.0-1
Adapter firmware version
20230507
Adapter
Sonoff Zigbee 3.0 USB Dongle Plus
Debug log
log-20230925.txt
The text was updated successfully, but these errors were encountered: