Moving Home Assistant’s Thread border router role onto a SkyConnect dongle should be a one-afternoon project. In practice, migrations fail when the old Open Thread Border Router dataset still thinks it owns the network, when Zigbee and Thread channels collide, or when Supervisor has not finished flashing the multipan firmware you assumed was already there.

Failed migration rarely means a bad SkyConnect stick. It usually means Home Assistant and your previous border router disagree about which operational dataset is law.

Before you touch firmware

Back up Home Assistant (Settings → System → Backups) before changing radio firmware or Thread network settings. Thread dataset mistakes are recoverable, but only if you can roll back YAML and integration state.

Confirm your SkyConnect is on a supported firmware path for Thread — not still running a Zigbee-only image you forgot to switch. The Silicon Labs multipan route is common; follow the current Home Assistant documentation for your exact stick revision rather than a two-year-old forum thread.

If Apple Home or Google Home still runs another border router on the same LAN, write down which fabrics Matter devices already joined. Migration on the HA side does not automatically retarget accessories commissioned elsewhere.

Read the failure signature

Integration will not start: check Supervisor logs and Settings → System → Logs for otbr or thread errors. USB power issues show up as repeated disconnects — try a short extension cable and a direct port on the host, not a flaky hub.

Devices vanished after migration: the Thread partition likely changed. Accessories still on the old dataset will not hop silently; they need recommissioning or a carefully imported dataset.

Channel conflict: if Zigbee and Thread share crowded 2.4 GHz space, migration can “succeed” while performance collapses. Note your Zigbee channel before changing Thread parameters.

Migration that actually sticks

Export or record the existing operational dataset if OTBR exposes it. Home Assistant’s Thread panel and third-party tools differ by version — use what your install documents today, not screenshots from older releases.

Shut down other border routers temporarily during cutover. Apple TVs and Nest hubs can re-announce quickly, but simultaneous claims during migration extend failure windows.

In Settings → Devices & Services → Thread, adopt the SkyConnect border router following the wizard. If adoption loops, remove stale OTBR integrations, restart Supervisor, and reload only the Thread integration before re-adding.

Match the channel plan to your home. If you cannot move Zigbee, pick a Thread channel with less overlap and accept that some accessories may need another reset.

Rejoin one test device — a simple Matter or Thread bulb — before re-migrating the whole house. Stand near the SkyConnect host with the stick on a USB extension away from metal cases.

When not to keep forcing migration

If your Home Assistant host is an underpowered SBC sharing USB with SSD and Z-Wave, border router duty may be unstable regardless of software. Moving OTBR to a dedicated Apple or Google hub while HA remains a Matter controller is valid architecture.

Do not import random dataset files from forums. A mismatched PAN ID bricks convenience, not safety, but recovery time is real.

Prove migration worked

Thread diagnostics in Home Assistant should show the SkyConnect router as active with neighbors listed. Run automations on migrated endpoints for twenty-four hours. Power-cycle the host once; devices should reattach without manual re-pair on the majority of your fleet.

Official sources