Home Assistant Zigbee Gateway: Coordinator Choices Explained
In Home Assistant, a "Zigbee gateway" is not one box you buy. It is a coordinator radio, a stable connection to your host, a software stack that speaks to that radio, and — if you use Zigbee2MQTT — an MQTT broker. Most "gateway" problems are one of those four parts, and this page helps you find which one before you spend anything.
The short answer
The only part that is Zigbee-specific. It forms the network and holds the network key. It is a USB dongle or a network-attached radio with Ethernet or PoE.
The coordinator has to stay on a stable port path and out of the USB 3.0 and Wi-Fi noise around your server. Placement here matters more than the chip on the board.
ZHA or Zigbee2MQTT. This is what Home Assistant talks to. Choose one and stay on it — switching stacks is a bigger job than switching a dongle.
Only required by Zigbee2MQTT. A broker you control, reachable from both the Home Assistant host and the Zigbee2MQTT host. ZHA does not need one.
If you already know your stack, the setup walkthrough is at the end of this page. If you are still choosing between the two stacks, compare them before you buy hardware.
Which coordinator type fits your home
Match your situation to a row. The recommendation is about placement and device count first; the specific model is a detail you settle afterward.
| Your situation | Coordinator type | Why |
|---|---|---|
| Host sits in the open, near the middle of the house, and the dongle can hang clear of the case | USB coordinator on a 1–2 m USB 2.0 extension | The cheapest path, and the one we run ourselves: 46 Zigbee devices on a Sonoff ZBDongle-E in our own home. The extension is doing real work — moving the dongle 1–2 m helped more than a hardware upgrade. |
| Host lives in a closet, rack, basement, or metal cabinet | Network-attached coordinator with Ethernet or PoE | The radio moves to where the devices are while the host stays where it is. SMLIGHT SLZB-06 and TubeZB MGM21 are the Ethernet options covered here. |
| Already running a Sonoff ZBDongle-P on Z-Stack and it works | Stay where you are | Do not migrate for fun. A working Z-Stack network on the P is not improved by swapping hardware. |
| You want Zigbee and Thread from one radio | Multi-protocol coordinator | Sonoff Dongle Plus MG24 is advertised for Zigbee and Thread at the same time; Home Assistant ZBT-2 is the official Home Assistant radio for Zigbee or Thread. |
| First coordinator, tight budget, small home | USB coordinator with an EFR32MG21-class radio | The Sonoff ZBDongle-E is the entry point we recommend for most readers, at around $20–27. |
| 30+ devices plus a noisy host area | Network-attached coordinator first, USB second | When the host area is crowded with radios, getting the coordinator physically away from it does more than any chipset change. |
| Coordinator | Radio / chipset | Best for | Typical price range |
|---|---|---|---|
| Sonoff ZBDongle-E | EFR32MG21 | Most users; the Zigbee2MQTT default | ~$20–27 |
| Sonoff ZBDongle-P | CC2652P | Budget USB; the proven Z-Stack path | ~$25–30 |
| SMLIGHT SLZB-06 | EFR32MG24 | Ethernet or PoE placement, bigger homes | ~$60–85 |
| TubeZB MGM21 | EFR32MG21 | Ethernet coordinator, advanced setups | ~€60+ |
| Home Assistant ZBT-2 | EFR32MG24 | Official Home Assistant hardware, Zigbee or Thread | $49 / €45 |
| Sonoff Dongle Plus MG24 | EFR32MG24 | Zigbee and Thread at the same time | ~$35.50 |
Best Zigbee coordinator for Home Assistant →
- Where will the host physically sit? Closet, rack, or basement points to a network-attached coordinator.
- How many Zigbee devices will this network carry? Past roughly 30, placement and mains-powered routers matter more than the radio model.
- Is there a USB 3.0 port or the host's Wi-Fi antenna within a few centimeters of where the dongle would go? Assume it is a problem and plan the extension or the move.
- Do you already own a working coordinator? If the network is healthy, the answer is usually to keep it.
- Which stack will you run — ZHA or Zigbee2MQTT? This decides whether you also need an MQTT broker.
Diagnostic: match the symptom to the failing stage
Zigbee gateway problems are usually one of five stages. Find your symptom, then run the first check in the right-hand column before you change any setting.
| Symptom | Stage that failed | First check |
|---|---|---|
| The coordinator is not detected by Home Assistant at all | Host and radio path | Look for the stable by-id device path rather than a ttyUSB number, and confirm the radio was passed through to the VM, container, or add-on after the last reboot. |
| A few devices drop off while the rest are fine | Radio placement and interference | Move the coordinator 1–2 m away on a USB 2.0 extension, away from USB 3.0 ports and the host's Wi-Fi radio. Repeat the same test before touching firmware. |
| Devices far from the host behave worse than devices near it | Mesh routing | Check whether the path from the device to the coordinator runs through mains-powered devices. Battery devices generally do not route for the rest of the network. |
| Nothing joins, even devices that worked before | Software stack | Confirm pairing or permit-join is actually open, that you are pairing on the stack you think you are running, and that the device is not still joined to another network or a vendor hub. |
| Everything worked yesterday and the whole network is gone today | Network identity | Check whether the coordinator was replaced, reflashed, or restored without its backup. The network key and network state are what the devices recognize. |
Set up a Zigbee gateway in Home Assistant: ordered steps
The order matters. Each step assumes the previous one is confirmed working, so a failure points at exactly one place.
- Decide the stack first
Choose ZHA or Zigbee2MQTT before you buy anything, because Zigbee2MQTT adds an MQTT broker to the list. Write the choice down; you will need it again in step 6.
- Pick the coordinator from placement, not price
Use the chooser above. If the host is in a closet or rack, prefer Ethernet or PoE. If the host is in the open, a USB coordinator on a 1–2 m USB 2.0 extension is the simpler answer.
- Physically place the radio before you configure it
Keep the coordinator out of the host's case, off USB 3.0 ports, and away from the Wi-Fi antenna. This is the single highest-value step in the list and the cheapest to redo.
- Confirm the host can see the coordinator
Verify the radio is passed through and appears on a stable by-id path that will not change after a reboot. If it does not appear, stop here — nothing later in the list will work.
- Install or enable the stack
For Zigbee2MQTT, get the MQTT broker running and reachable from both hosts first, then point Zigbee2MQTT at the broker and at the coordinator. For ZHA, add the coordinator and let it form the network.
- Write down the network key and take a coordinator backup
Do this before pairing anything you care about. The backup — network key plus network state — is what makes a later coordinator change possible without re-pairing. Our 46-device migration ran with zero re-pairing because the backup existed.
- Pair a small set of devices and confirm they stay
Start with the devices nearest the coordinator and leave them for a while. Confirm stability on a short list before you commit the whole house.
- Add mains-powered devices where the mesh is thin
Mains-powered Zigbee devices usually act as routers and extend the network. Add them between the coordinator and the far end of the house rather than clustering them near the host.
- Record what you changed
Note the stack, coordinator, firmware channel, and date. When something breaks in six months, this is the difference between a ten-minute fix and a rebuild.
Common mistakes
USB placement beats chip marketing. If the dongle is bolted to a case next to a USB 3.0 port, a better radio will not fix the drop-offs.
If you are already on a ZBDongle-P running Z-Stack and the network is healthy, stay on the P. Do not migrate for fun.
Replacing or reflashing a coordinator without its backup is the mistake that costs a weekend. The backup is the network identity, not a convenience.
A vendor Zigbee hub is a coordinator plus a closed software stack. Home Assistant does not need it to run Zigbee — keep it only if you rely on its own app for something else.
A new coordinator, a new channel, and new firmware in one evening gives you a network that works or fails for reasons you cannot name. Change one thing, then wait.
Edge cases
These are the situations where the standard advice needs an amendment.
| Edge case | What to do |
|---|---|
| Home Assistant runs in a VM or container | The coordinator has to be passed through to the guest, not just plugged into the host. Re-check the pass-through after every host reboot or hypervisor update, and keep using the stable by-id path inside the guest. |
| One radio for Zigbee and Thread | A multi-protocol radio is advertised for both. Treat the two networks as separate jobs: changing the Zigbee side can affect the Thread side, so change one and re-check the other. |
| Switching between ZHA and Zigbee2MQTT | This is a stack migration, not a coordinator migration, and devices generally have to be re-paired. Plan it as a project with the coordinator backup taken first. |
| Replacing the coordinator on an existing network | The coordinator backup is the whole trick. Restore the backup onto the new coordinator and keep the network key unchanged. The tested walkthrough for this is linked below. |
| Home Assistant SkyConnect | SkyConnect was discontinued by Nabu Casa and Home Assistant ZBT-2 is the successor. Do not buy a discontinued coordinator at a premium to match an older guide. |
| PoE-powered coordinator | PoE means the network cable carries power. Do not improvise injectors or split a run to save a cable. If you are unsure about your switch, injector, or cabling, stop and consult the coordinator's manual or a qualified professional. |
| Coordinator inside a metal cabinet or rack | Metal blocks the radio. Plan the Ethernet or PoE route out of the enclosure, or move the radio outside it, before you spend on a different model. |
| Firmware or channel guidance from a forum | Vendor procedures differ by model and firmware channel. Stop and check the official manual for your exact coordinator before flashing or changing the network key. |
The tested coordinator-migration walkthrough — including the backup mix-up we hit — is here:
Zigbee coordinator migration without re-pairing
Frequently asked questions
Is a Zigbee gateway the same thing as a coordinator?
Not quite, and the difference is the reason this page exists. A coordinator is the radio that forms the Zigbee network and holds the network key. In Home Assistant, the "gateway" role — turning Zigbee devices into entities and automations — is done by Home Assistant plus ZHA or Zigbee2MQTT. People use the two words interchangeably, but only one of them is hardware.
Do I need a Zigbee hub if I run Home Assistant?
No. A vendor hub is a coordinator plus a closed software stack, and Home Assistant can talk to a coordinator directly. Keep a vendor hub only if you rely on its own app for something else; otherwise it is a second network to maintain.
Can one coordinator run Zigbee and Thread at the same time?
Some radios are advertised for both, including the Sonoff Dongle Plus MG24 and the Home Assistant ZBT-2 for Zigbee or Thread. Treat them as two networks on one radio: change one side at a time and re-check the other.
How do I choose between ZHA and Zigbee2MQTT?
Choose before you buy hardware, because Zigbee2MQTT adds an MQTT broker to your stack. Both are real options and the right answer depends on how much of the plumbing you want to own. Compare them side by side before committing.
Will I have to re-pair every device when I change coordinator?
Not if you restore the coordinator backup and keep the network key unchanged. Our 46-device migration moved with zero re-pairing. Without the backup, you are building the network again from scratch.
Where should the coordinator physically sit?
Out in the open, away from USB 3.0 ports and the host's Wi-Fi radio, on a 1–2 m USB 2.0 extension if it is a USB dongle. If the host sits in a closet or rack, use an Ethernet or PoE coordinator instead and leave the host where it is.
Where to go next
This page is the coordinator-choices decision. The step-by-step installation, the stack comparison, and the tested hardware guide each go deeper.
The full start-to-finish setup sequence, from broker to first paired device.
Start the setup guide →The stack decision, compared on the things that actually change your maintenance load.
Compare the stacks →The coordinator rankings, migration walkthrough, and build logs behind this page.
Read the tested Zigbee guides →