How To Migrate Zigbee2MQTT Devices To New Coordinator

<section class="review-transcript"> <p>Hi, I’m Tim. In this video I’m showing how to upgrade an SMLIGHT SLZB Zigbee coordinator and <strong>move your Zigbee2MQTT (Z2M) network to a new coordinator without re-pairing devices</strong>.</p> <p><strong>Important note:</strong> this method depends on staying within the same chipset family. If your Zigbee2MQTT setup uses a <strong>Z-Stack</strong> coordinator, you can migrate to another Z-Stack coordinator. If you use an <strong>Ember</strong> coordinator, you can migrate to another Ember coordinator. You generally <strong>cannot</strong> migrate directly between Ember and Z-Stack without re-pairing.</p> <h3>Example upgrade shown</h3> <p>The example migration shown is from an <strong>SLZB-MR3</strong> to an <strong>SLZB-Ultima</strong>, using the Texas Instruments Zigbee radio path (Z-Stack). The SLZB-MR3 contains multiple radios, including:</p> <ul> <li><strong>EFR32</strong> (Ember-based radio)</li> <li><strong>CC26xx / CC2674P10</strong> (Z-Stack-based radio)</li> </ul> <h3>Step-by-step: migrate Zigbee2MQTT without re-pairing</h3> <ol> <li> <p><strong>Open the coordinator web UI</strong> (old coordinator).</p> <p>Go to <strong>Z2M &amp; ZHA</strong> and identify which radio Zigbee2MQTT is using. Note:</p> <ul> <li>Adapter type (e.g., <strong>Z-Stack</strong>)</li> <li>Baud rate (example shown: <strong>115200</strong>)</li> </ul> </li> <li> <p><strong>Read and copy the coordinator address/identity</strong> from the correct radio section.</p> <p>In the CC26xx / CC2674 section, use the option like <strong>Read factory</strong> to display the value. Copy it into a text note (Notepad, etc.).</p> </li> <li> <p><strong>Stop Zigbee2MQTT</strong> in Home Assistant.</p> <p>In Home Assistant, go to <strong>Settings → Add-ons → Zigbee2MQTT</strong>, then click <strong>Stop</strong> and wait until the service fully stops.</p> </li> <li> <p><strong>Swap hardware: unplug the old coordinator and connect the new coordinator</strong>.</p> <p>Allow the new device to boot, then open its web interface.</p> </li> <li> <p><strong>Write the copied identity to the new coordinator</strong>.</p> <p>On the new coordinator, go to <strong>Z2M &amp; ZHA</strong>, find the matching radio section (e.g., CC2674 / Z-Stack), paste the copied value into the <strong>Flash custom address</strong> field, then click <strong>Write address</strong> (confirm the reflash prompt). Wait until you see a success message.</p> </li> <li> <p><strong>Update Zigbee2MQTT connection settings</strong> to point to the new coordinator.</p> <p>Back in Home Assistant Zigbee2MQTT configuration, update the <strong>Serial / Port</strong> string to the new coordinator address (mDNS name or IP) and ensure the port is correct (example shown: <strong>7638</strong> for the CC26xx socket port, depending on your radio and configuration).</p> <p>Keep the adapter type consistent (e.g., <strong>Z-Stack</strong>) and confirm the baud rate (example: <strong>115200</strong>).</p> </li> <li> <p><strong>Start Zigbee2MQTT</strong> and verify.</p> <p>Start Zigbee2MQTT again, check the logs for normal startup (green/white messages), then open the Zigbee2MQTT UI. Your devices should appear without needing to re-pair.</p> </li> </ol> <h3>Result</h3> <p>Once the coordinator identity is migrated and Zigbee2MQTT is pointed to the new coordinator, devices can come back automatically. Startup time depends on how many devices you have and how quickly your system rebuilds the network state.</p> <p>If you’re considering an upgrade (for example, moving to an <strong>SMLIGHT SLZB-MR3</strong> or to a multi-radio device like <strong>SLZB-Ultima</strong>), this is a practical approach that can save a lot of time—<strong>as long as you stay within the same Zigbee chipset family</strong>.</p> </section>