I have the SONOFF coordinator and trying to move to SkyConnect
I’m following the instructions in here: Home Assistant SkyConnect
But the UI does not show me the option to overwrite the IEEE adrress of the coordinator. The flow just ends in the step before that and the new coordinater gets a new adress and nothing seems to know abou it.
Is it a bug in the UI?
Can I manually change it?
I’m running 2024.3.0
I had to restart Home Assistant, then click Settings. A modal dialog popped up saying:
“Your Zigbee radio’s settings are inconsistent with the most recent network backup…”
A couple clicks later and the issue was fixed. At least some of my devices are connected now, and I expect the others will come online with power cycling or a little patience.
Adding a data point for anyone finding this thread while migrating to a different coordinator than SkyConnect: I hit the exact same failure mode migrating from a SONOFF Zigbee 3.0 Dongle-M (EZSP/EFR32) to a SMLIGHT SLZB-MR4U (ZNP/CC2674, connected via socket over LAN, not USB), so this isn’t SkyConnect-specific.
Symptoms: radio type (ZNP), flow control (none, confirmed against the device’s own hardware-flow-control setting), baud rate, and IP:port were all verified correct. Test-NetConnection/nc confirmed the TCP socket was reachable and accepting connections. Both the automatic “Migrate radio” flow and the manual migration flow (with a socket:// connection string) still failed to connect, with no more detail than “Connection failed” in the UI.
Root cause (as far as I can tell): the new coordinator’s IEEE address is baked into the chip and differs from the old one. The migration wizard is supposed to handle this (“replace the radio IEEE address” per the docs), but that step never appeared for me either — same as OP.
Workaround that got me a fully working migration with zero dropouts since:
Read the old coordinator’s IEEE address (visible in ZHA’s device info for the coordinator).
On the new coordinator, manually set its IEEE address to the old one (SMLIGHT’s SLZB-OS web UI has a field for this under the radio settings — remove the colons from the address before entering it). Save.
Start the manual migration in ZHA, enter the new radio’s connection string, but stop right after that step — don’t click “Next” yet.
Power off the old coordinator now (before continuing).
Click Next. ZHA will warn that it can’t reset the old adapter to factory defaults — that’s expected, proceed anyway.
Finish the migration. Devices and ZHA now treat the new radio as the same coordinator as before, no re-pairing needed.
Caveat: never power the old coordinator back on with its original IEEE while the new one has the same identity — you’ll get a duplicate-IEEE conflict on the mesh.