Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse

Smarthome Forum — Smart Home Community for Matter, Zigbee & HomeKit

  1. Home
  2. Show and Tell
  3. How to Migrate from ZHA to Z2M on the Same SLZB-06M Gateway (Without Re-Pairing Everything)

How to Migrate from ZHA to Z2M on the Same SLZB-06M Gateway (Without Re-Pairing Everything)

Scheduled Pinned Locked Moved Show and Tell
1 Posts 1 Posters 29 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S Offline
    S Offline
    Sarah_D
    wrote last edited by
    #1

    Most guides on switching from ZHA to Zigbee2MQTT assume you're using a USB coordinator and tell you to re-pair every device from scratch. If you're running a SLZB-06M ethernet gateway, there's a lower-effort path that a few people in the Home Assistant community forum have pieced together, though it's still light on detail, so treat this as a starting point rather than a guaranteed walkthrough.
    Why the naive approach fails
    Just deleting the ZHA integration and spinning up Z2M on the same gateway doesn't work by default. Your Zigbee devices are bound to a specific PAN ID and extended PAN ID. If Z2M starts a fresh network with different IDs, your devices simply won't recognize the new controller and every one of them has to be factory reset and re-joined.
    The workaround

    Update your SLZB-06M firmware first. Firmware 2.7.1 and later added the ability for the gateway to associate with more than one client at once, which is what makes this approach possible at all.
    Back up your ZHA coordinator configuration before touching anything. This is your safety net if the migration goes sideways.
    Copy your ZHA network settings into Z2M. Instead of letting Z2M generate a new network, configure it with the same PAN ID, extended PAN ID, and network key that ZHA is already using. This is the step that avoids the re-pairing problem entirely.
    Export your ZHA device list and use it to build your Z2M device configuration. This saves you from manually re-entering every device.
    Run "interview" on each device from the Z2M UI. This is what lets Z2M actually recognize and populate details for devices it didn't originally pair.
    Once you've confirmed everything shows up correctly in Z2M, disable the ZHA integration. Running both at once will give you duplicate entities for every device.

    A safer alternative if you don't want to risk your live network
    If you'd rather not experiment directly on your working setup, one option is to temporarily move ZHA onto a cheaper secondary coordinator, freeing up the SLZB-06M to become your fresh Z2M coordinator. You can then repurpose the original USB coordinator as a dedicated Zigbee router afterward instead of letting it go to waste.
    A word of caution
    This method hasn't been fully documented step by step by anyone who's actually done it end to end. The one person who described it didn't go into detail on how the "interview" step behaves in practice, so budget time for trial and error, and definitely don't skip the backup step.
    Has anyone here actually completed this migration on a SLZB-06M? Curious what the interview step looked like in practice and whether all device types carried over cleanly.

    1 Reply Last reply
    0

    Hello! It looks like you're interested in this conversation, but you don't have an account yet.

    Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

    With your input, this post could be even better 💗

    Register Login
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • World
    • Users
    • Groups