Migrating your Zigbee coordinator in 2026
The coordinator landscape moved: Home Assistant's Connect ZBT-2 (SiLabs EFR32MG24, bigger antenna, USB-C), Sonoff's Dongle Max with the same MG24 chip plus PoE and Wi-Fi options, and a driver transition (the old EZSP way giving way to the ember driver in Zigbee2MQTT) that decides whether a migration is a formality or a weekend of re-pairing. This guide explains the new hardware, the driver story, and the migration that keeps your network — and your automations — intact.
Published Nov 18, 2026
The 2026 hardware map
- Home Assistant Connect ZBT-2 (~$49, when in stock — it has been scalped well above that): MG24 chip, a proper external antenna, USB-C, and the 'official' blessing. The default recommendation for ZHA users upgrading today.
- Sonoff ZBDongle-E Max (MG24) (~$36): the same modern silicon with a trick the ZBT-2 lacks — it can sit on your network via PoE or Wi-Fi instead of a USB port, freeing placement entirely.
- Network coordinators (SLZB family): Ethernet/PoE placement with the coordinator decoupled from the server — our build-list pick for years and still the flexibility champion for Zigbee2MQTT.
- Your current CC2652/older stick: still fine. Chips age gracefully in Zigbee; migrate for placement, antenna, or driver support — not because a newer chip exists.
Ember vs EZSP: the driver detail that decides your weekend
SiLabs-based coordinators (EFR32/MG-series: ZBT-2, Sonoff E/Max, many others) talk to Zigbee2MQTT through a driver. The old EZSP driver is deprecated; the current ember driver is its replacement, and ember wants the coordinator's firmware in a known-good band (roughly the 7.4.x generation — current firmware from the vendor is the safe answer). ZHA users meet the same silicon through its own integration, where the practical rule is simpler: use the migration wizard (below) and current firmware. Either way: update the new coordinator's firmware before migrating, not after — mid-migration firmware surprises are the genre of story nobody enjoys telling.
The migration that keeps your network (ZHA)
- Settings → Devices & Services → ZHA → Configure → Migrate radio. The wizard backs up the current network (PAN ID, channel, network key) and writes it onto the new coordinator.
- Shut down, swap the hardware (same good placement — central, away from USB 3 and Wi-Fi APs, per our flaky-Zigbee guide), start up.
- Devices rejoin against the migrated network identity — because the network moved with you, most devices need no re-pairing at all; battery devices may take a wake cycle to check in.
- Walk the house in the ZHA visualization: confirm router devices are meshing and the previously-weak corners improved (or did not — placement data is migration data).
Zigbee2MQTT coordinators: swap smart
- Stop Z2M and back up its data directory (the network state lives there — coordinator_backup.json is the crown jewel).
- Update the configuration's serial section: new port/TCP address, and adapter: ember for SiLabs sticks (this is the moment EZSP configs must change).
- Same-network trick: Z2M restores the network from its backup onto a same-family coordinator, preserving device pairings. Changing chip families (TI ↔ SiLabs) is the case where some re-pairing may still be required — budget an evening, start with routers, let the mesh heal, then battery devices.
- Start Z2M, watch the map rebuild, and give the network a day before judging stability — Zigbee meshes re-converge on their own schedule.
Channel discipline survives migration: keep the Zigbee channel you planned (our channel planner) unless the new placement changes your Wi-Fi picture. A coordinator swap is not an excuse to re-roll the spectrum dice.
Should you migrate at all?
If your network is stable: no. Coordinator envy is not a maintenance category. Migrate when you are changing stacks (our Z2M vs ZHA guide), when placement is your bottleneck (PoE/network coordinators solve real houses), when your stick's driver line is ending (EZSP-era hardware), or when a dead coordinator makes the decision for you. In every case, the backup-first, same-network approach above turns a feared project into a procedure.
Gear for this build
Prices are editorial and change often; buttons show live prices. Some links may earn a commission at no cost to you — see the disclosure page.
Official documentation and references
- Home Assistant — ZHA, including coordinator backup and migration
- Zigbee2MQTT documentation — supported adapters and firmware notes
- Zigbee2MQTT documentation — configuration and supported devices
Frequently asked questions
Will I have to re-pair every device?
Usually not: ZHA's radio migration and Zigbee2MQTT's network backup both carry the network identity (PAN, channel, key) to the new coordinator, so devices rejoin the same network. Cross-chip-family moves in Z2M are the exception where some re-pairing can occur.
What is the ember driver and do I need it?
Ember is the current Zigbee2MQTT driver for SiLabs-based coordinators, replacing the deprecated EZSP driver. If you run a SiLabs stick on Z2M, ember with reasonably current coordinator firmware is the supported path going forward.
ZBT-2 or Sonoff Dongle Max?
Same MG24 silicon family. The ZBT-2 is the official, simple USB answer; the Sonoff Max adds PoE/Wi-Fi placement freedom. Choose by where the coordinator needs to live, not by chip — the chip is the same.

