#Z2M PAN ID conflict
1 messages ยท Page 1 of 1 (latest)
Here, let's move this discussion into a thread
@hoary salmon Z2M has problems re-forming an existing network when the PAN ID is being broadcast by routers
zigpy-cli can restore your old network settings, which should allow Z2M to start up normally
so same pan id would have magically worked due to different channel right?
PAN ID has to stay the same, as otherwise it's a "new" network
yeah - so i read...
Just run the restore /path/to/coordinator-backup.json zigpy command and it should work
Then Z2M should start up fine
restoring
i have a habit of tarring up y zigbee2mqtt dir every now and again just in case
hmm no restore cmd
zigpy restore zigbee2mqtt/coordinator_backup.json
Same format as your energy scan command
zigpy -vv radio znp /dev/serial/by-id/... restore zigbee2mqtt/coordinator_backup.json
aaaahradio znp ...
it's thinking about it
maybe i should have -vv'd
done. no errors.
Z2M now should start up without complaining
Also, restoring old backups isn't a great idea: the network frame counter will roll back, causing some devices to refuse to respond to coordinator requests until they're power cycled or the transmit counter rolls forward to exceed its previous value
hmmm bugger.
Though I think Z2M is smart enough not to do that if the network doesn't change
hmm might move coordinator back to its spot too -i moved it wondering if relocation might improve signal
but it was sitting next to my other coordintor (yes - the zb sticks were a good 30-50cm apart)
So does Z2M start back up now? Or is it still complaining about the PAN ID?
it does
but nigh on everythng is offline
i think maybe trying to re-pair the routers i have (they are the little ikea ones that come with a usb power brick - but my power socket all happen to have usb-a on them so they actually conveniently plug right into all my power sockets directly so are small little nubs)
and now i moved it (powered off and on - well pulled out plug) its timing out on start
oh wait starte dnow
needs to try start a bunch of times
So if it boots up, then it's happy with your network settings and at least they're correct
Now you can do the channel change command and edit the Z2M config file and backup file
yeah - its come back up
but most stuff is offline ๐ฆ
or well not responding
warn 2023-03-17 18:42:22: Failed to ping '0_kitchen_back_8' (attempt 1/1, Read 0x9035eafffe2a9f3c/1 genBasic(["zclVersion"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":true,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms))
that kind of thing - all over the place
would the channel change work even if stuff is off line and not responding?
i assume the channel chnage is a network boradcast telling everyone to move?
err broadcast
It is a broadcast
so it might be even unresponsive devices get it?
It's possible, the broadcast is relayed by every device that hears it so hopefully some of them got it
But it's very possible that some didn't
well i'll find out
it may cut the work
that assumes i can get it back up and stable at all to then change channel...
I suspect that it's going to be a chicken and egg problem: your network is unstable and devices won't receive the broadcast to change channels because the channel is congested
hmmm
going to just accept i will have to re-pair things and that means screwdrivers and poking around electrical connections yet again
i'm getting good at it ๐
But at the same time, the channel change broadcast won't hurt: even if it doesn't work at all, you'll just have to rejoin devices, as you originally planned
i probably shoudl change pan id anyway
so maybe just start again it seems
z2m shuts down after 2 or 3 mins due to all the timeuts it gets trying to get data from devices
The PAN ID conflict is just a Z2M bug, you don't need to change the PAN ID
hmmm well getting it back up at all is a challenge....
zigpy.exceptions.FormationFailure: Network formation refused: there is too much RF interference. Make sure your coordinator is on a USB 2.0 extension cable and away from any sources of interference, like USB 3.0 ports, SSDs, 2.4GHz routers, motherboards, etc.
chicken and egg... yay
so my 4000ms timeouts at start are probably the interference?
lets try turn my own 2.4ghz wifi off and see