I tried switching my Zigbee coordinator from SMLBZ06 to SMLBZ-MR2 so I could use Matter and the stronger hardware.
Since both have the same chip, I wanted to migrate without re-pairing devices.
What happened:
First attempt worked with same IEEE address, IP, and port – all devices were there.
After a firmware update on the MR2, Matter worked again, but Zigbee2MQTT would no longer start.
Errors in the log:
Cannot set properties of undefined (setting 'extendedPanID')
network commissioning timed out - most likely network with the same panId or extendedPanId already exists nearby
Changing the PAN ID lets it start, but all devices are gone.
Plugging the old 06 stick back in works instantly with no issues.
Questions:
What’s the correct procedure to migrate from 06 to MR2 without re-pairing devices?
Does the coordinator_backup.json need to be modified?
yes this is what i did last time, to get it work. but after the firmware update, first matter stopped working, then i updated matter firmware. matter worked again. then zigbee stopped working, i updated zigbee firmware with the same version as before. but i cant get it running.
always the same error with panId or something else.
and it seems the performance is pretty bad compared to the slzb06, i think its because of any kind of bad routing. i dont know.
is there nothing like backup → new hardware → import → done
its kinda fustrating, what if a device breaks.
and im wondering, after i messed up the firmware stuff on mr2 I tried the no power and 15min no antenna trick, nothing worked. so i took my old slbz06, powerd up and instant all fine. no antenna trick nothing.
after switching to the SMLBZ-MR2 a few days ago, most things are working again, but I’ve noticed a new problem:
Some Zigbee devices take a very long time to respond – sometimes up to 5 seconds delay.
With my old SMLBZ06 this was not the case, devices reacted almost instant.
Does anyone know what could cause this or what I can do to improve the response times again?