I’m using zigbee2mqtt as an add-on within Home Assistant. Last night I decided I wanted to swap the usb cable that my sonoff 3.0 usb dongle was connected with to a longer one so I could get it away from my setup a little more. I’m still in the same port, just a longer cable.
I replaced the cable and restarted zigbee2mqtt it loaded without any issues and I thought everything was working. This morning I realized that even though all my devices are present NONE of them are communicating to my sonoff coordinator. I have 8 sonoff zbmini which act as a router I believe, 6 ikea motion dectors, 2 ikea buttons, and one third reality button.
They all show up in my devices list, but none of them are connecting to my coordinator!
I’ve swapped out the usb cable and have everything put back to the way it was last night, but I’m still getting nothing.
Do I have to re-pair my zigbee devices EVERY TIME I loose power or unplug my zigbee stick?
Edit: As I was reading over this post I realized that one of my sonoff zbmini relays is NOT listed in my network. I’m new to all this so my knowledge is somewhat lacking, but is it possible when I unplugged my usb stick the devices made a new network with the one device that isn’t on my network without being put in pairing mode???
Its more likely your Zigbee2MQTT instance is having trouble connecting to your stick. If you’re not addressing it using its by-id path it may have changed when you unplugged and replugged it.
The log shows the zigbee devices being loaded and when I re-paired one of the buttons it was able to do so without any issue, so I know zigbee2MQTT is connected to it (I am connecting to it with /dev/serial/by-id/[device-id]
The log on boot is filled with this kind of message
When I try to run a scan to map it I get messages like this:
Zigbee2MQTT:error 2022-06-27 13:03:15: Failed to execute LQI for 'Garage Lights'
Zigbee2MQTT:debug 2022-06-27 13:03:15: Error: AREQ - ZDO - mgmtLqiRsp after 10000ms
at Timeout._onTimeout (/app/node_modules/zigbee-herdsman/src/utils/waitress.ts:64:35)
at listOnTimeout (node:internal/timers:559:17)
at processTimers (node:internal/timers:502:7)
If everything was connected through my zbmini switches and those switches just gave up on talking to the coordinator because they couldn’t reach it for a few minutes, would my entire network die? Even the stuff that’s right next to my coordinator isn’t respond though until I re-pair it for some reason.
In fact, I had re-paired a device then did a restore to my configuration from a day ago before I unpluged my usb thinking that maybe my channel or pan id was changed somehow. I paired a button after I did that, but when I saw it wasn’t working a restored to a backup made today and the button I re-paired is no longer able to communicate again.
Anyone coming to this thread in the future, I never found out why this happened. The usb dongle still had the same dev-id and was picked up by zigbee2mqtt, I could pair devices to it and most interestingly once I paired one of my zbminis and did a map of my zigbee network, it showed a connection to the other zbminis (as a dashed line), but they would not communicate to those devices without re-pairing them.
It’s almost like all the network information stayed the same except for the network key? I don’t know, my solution was just to repair things. I’m also going to try to move off my synolgy NAS and onto truenas where I’ll use docker to control things.
I’ll follow up if unplugging the usb dongle causes this huge freak out on the new setup as well.