Zigbee2MQTT in Home Assistant (2026): Best Zigbee Coordinators, Add-on vs Docker

Running Zigbee2MQTT in Home Assistant gives you local, cloud-free control of Zigbee devices from Philips Hue, IKEA, Aqara and Tuya in a single mesh — no vendor bridge, no account, no internet dependency. The catch is well documented: the coordinator stick you buy determines which firmware stack Zigbee2MQTT talks to, and picking one whose chipset doesn’t match the expected adapter setting doesn’t produce a merely suboptimal network — it produces a network that refuses to start. This guide covers the coordinators worth buying in the UK, the add-on versus Docker install decision, and the specific configuration failures that account for most abandoned first attempts.

Everything below is drawn from manufacturer specifications, the Zigbee2MQTT project’s own documentation and changelog, named retailer listings and aggregated owner and community feedback. It is not based on hands-on testing.

Quick Picks

What Zigbee2MQTT Adds Over ZHA

Home Assistant ships with its own Zigbee stack, ZHA, and for plenty of households ZHA is entirely adequate. Zigbee2MQTT exists in the gap between that and a paid, cloud-tied ecosystem.

According to the project’s supported-devices page, Zigbee2MQTT currently lists approximately 3,800 devices as of early 2026 — a figure that grows continuously, so it is worth checking the page at the point of purchase rather than trusting any fixed number. The zigpy project’s device-handler repository maintains its own comparable list on the same date; the two overlap heavily but are not identical, so a device supported in one stack may not yet be listed in the other. In practice, the quirky Tuya and Aqara models that cause trouble elsewhere frequently land in Zigbee2MQTT first.

The second difference is architectural. Zigbee2MQTT publishes every device to a standard MQTT topic — zigbee2mqtt/kitchen_sensor for state, zigbee2mqtt/kitchen_sensor/set for commands — and subscribes back for control. That decoupling matters more than it sounds: your Zigbee mesh is not welded to Home Assistant, so you can restart Home Assistant without dropping the network, and you can feed the same data into Node-RED or a second dashboard simultaneously. It also means the underlying control is genuinely local, with no vendor server in the loop.

The third is granularity. Zigbee2MQTT exposes device-level settings — sensitivity, calibration, indicator LEDs, binding — that ZHA often hides behind a single generic entity.

The trade-off is real complexity. ZHA is a few clicks. Zigbee2MQTT means an MQTT broker, a configuration file you have to understand, and a coordinator chosen deliberately rather than grabbed off a shelf. ZHA remains the better answer for a small, mainstream device list and a user who never wants to open a YAML file; a Philips Hue Bridge remains the better answer if every bulb in the house is a Hue bulb. Zigbee2MQTT wins when the device mix is messy, when everything must stay local, or when MQTT is already running for something else.

How to Choose a Coordinator

Chipset first, because it dictates firmware stack

The single most important specification is not range, antenna gain or price — it is the radio chipset, because it determines which firmware stack Zigbee2MQTT is configured to speak to. Texas Instruments’ CC2652P runs the zstack stack. Silicon Labs’ EFR32MG21 runs the ember stack. Those two settings are not interchangeable, and a coordinator whose configuration key doesn’t match its chipset will fail to start rather than degrade gracefully.

This is why coordinator problems dominate setup complaints. Issues labelled coordinator on the Zigbee2MQTT GitHub repository and threads on the Z2M community forum are consistently among the most frequently cited blockers reported by new users, and a mismatch between the stick’s chipset and the configured adapter value is one of the most common causes. Treat that as community-reported consensus rather than a formal statistic.

USB stick or networked radio?

A USB coordinator plugs into the machine running Home Assistant. It is cheap and simple, but it sits directly in the electrical noise field of the host’s USB 3.0 ports — a documented Zigbee2MQTT issue, since USB 3.0 traffic radiates in the 2.4GHz band that Zigbee uses. An Ethernet coordinator with Power over Ethernet solves this structurally: the radio can sit metres away from the server on the end of a network cable, powered by the switch, entirely outside that interference.

Ecosystem maturity

Beyond the hardware, consider how quickly a coordinator’s firmware receives device-support updates. CC2652-based sticks have the deepest pool of community troubleshooting material; Silicon Labs EFR32 hardware has matured substantially but has a different flashing workflow and a shorter track record in Zigbee2MQTT specifically; deCONZ-first hardware carries its own trade-offs, covered below.

Channel planning before you buy anything

Zigbee channels 11 to 26 sit in the 2.4GHz band alongside Wi-Fi. Zigbee channels 15, 20 and 25 are the least overlapping with the standard Wi-Fi channels 1, 6 and 11 — the three settings most UK routers default to. Decide your channel before you pair 40 devices, because changing it later forces every device to rejoin.

The Best Zigbee Coordinators for Home Assistant

Sonoff ZBDongle-P — the default choice

Best for: the majority of Home Assistant users who want the lowest-cost, best-documented entry point.

The ZBDongle-P uses the CC2652P chipset and runs zstack firmware, which means its adapter value in the Zigbee2MQTT configuration must be set to zstack. It is widely available in the UK from Amazon and AliExpress, typically around £18–£22.

Standout strength: it has the largest community troubleshooting base of any coordinator in this list, which matters enormously when something goes wrong at 11pm — nearly every error message you’ll encounter has already been answered by someone running the same silicon.

Honest caveat: its enormous popularity creates a specific trap. Because so many guides mention “the Sonoff dongle”, buyers assume the ZBDongle-P and ZBDongle-E are interchangeable. They are not — the adapter value for the -E is ember, not zstack, and copying a -P configuration onto a -E stick will stop the network from starting.

Verdict: if you want one answer and no drama, buy this one and set adapter: zstack.

Where to buy: Amazon UK; also AliExpress.

Sonoff ZBDongle-E — the EFR32 sibling

Best for: buyers who specifically want Silicon Labs EFR32 hardware in a low-cost USB stick.

The ZBDongle-E runs the EFR32MG21 chip, which puts it on the ember firmware stack and requires the distinct adapter: ember configuration value. Like the -P it is sold through Amazon UK and itead.cc, at a broadly similar price of around £18–£22.

Standout strength: it gives you the same chip family as Home Assistant’s own official hardware (see the ZBT-1 below) at roughly half the price, which is attractive if you’re standardising on EFR32 across several homes or installations.

Honest caveat: the flashing story and the community’s accumulated maturity differ from the -P. There is simply less historical forum material to draw on when a firmware update goes sideways, so troubleshooting takes slightly longer.

Verdict: a perfectly capable stick, but a deliberate purchase rather than a default one — and never a drop-in copy of a -P configuration.

Where to buy: Amazon UK and itead.cc.

Home Assistant Connect ZBT-1 — official hardware, one firmware decision

Best for: Home Assistant Green and Yellow owners who want first-party hardware that fits the ecosystem cleanly.

The ZBT-1 uses the EFR32MG21 chipset and therefore speaks ember firmware. Critically, it is identical hardware to the retired SkyConnect — the same radio, rebranded. That single fact resolves a great deal of confusion among the large existing SkyConnect installed base, who may already own the correct hardware and simply need to treat it as a ZBT-1.

It ships with multiprotocol firmware by default, which is fine for some setups but not ideal for a Zigbee2MQTT-only deployment. For dedicated Zigbee2MQTT use, the recommended path is to flash it to Zigbee-only firmware through Home Assistant’s Settings > Hardware panel, following the manufacturer’s flashing documentation published at nabucasa.com.

Standout strength: it is the tidiest option for HA Green and Yellow owners, and the Zigbee-only flash gives a clean, single-purpose radio.

Honest caveat: that firmware decision is an extra step that USB sticks from Sonoff don’t require, and the price reflects the official branding — around £35–£40 in the UK through Nabu Casa and the Home Assistant shop. Note also that while the ZBT-1 is covered here, the newer ZBT-2 is not: its shipping status has varied, so check Nabu Casa’s own listings before assuming availability rather than relying on any secondary source.

Verdict: buy it if you want official hardware and don’t mind flashing once; skip it if you want the cheapest path.

Where to buy: the Home Assistant shop at nabucasa.com.

SMLIGHT SLZB-06M and SLZB-06P7 — Ethernet and PoE

Best for: installations where the server sits in a metal rack, a cupboard or a corner of the house far from the mesh, or where USB 3.0 interference has already wrecked a USB-based setup.

These are networked coordinators: Ethernet with Power over Ethernet, so a single cable carries both data and power. The SLZB-06M uses the CC2652P chipset; the SLZB-06P7 uses an EFR32 variant. That difference matters for the same reason as above — the -M speaks zstack and the -P7 speaks ember. UK pricing is typically around £45–£65 depending on variant and stock.

Standout strength: the radio can sit physically away from the server entirely, which eliminates the documented USB 3.0 interference problem at the source rather than trying to mitigate it. For anyone whose Zigbee network is flaky only during heavy network or disk activity, this is the structural fix.

Honest caveat: you pay roughly double the Sonoff price, and you take on a network device that needs its own IP address, firmware updates over the network, and a little more configuration care than a USB stick.

Verdict: the right answer for awkward layouts and PoE homes; overkill for a small flat with the server and the mesh in the same room.

Where to buy: specialist UK hobbyist retailers including The Pi Hut and Pimoroni, as well as Amazon UK.

ConBee III — for people already in the deCONZ world

Best for: households already running Dresden Elektronik’s deCONZ ecosystem who want to evaluate Zigbee2MQTT without discarding hardware.

The ConBee III comes from Dresden Elektronik, and deCONZ is its primary ecosystem. Zigbee2MQTT support exists, so it is a legitimate path rather than a dead end. Expect to pay typically around £40–£50 in the UK.

Standout strength: if you already own deCONZ hardware and a working setup, this is the least disruptive way to trial Zigbee2MQTT alongside it.

Honest caveat: community reports consistently describe slower device-support updates than on CC2652-based sticks, which means newly released sensors and bulbs may take longer to appear.

Verdict: a sensible migration tool for existing deCONZ users, but not the coordinator to buy fresh in 2026 if device support speed is your priority.

Where to buy: Amazon UK and specialist UK home-automation retailers.

Aeotec Zi-Stick — the Z-Wave crossover

Best for: Z-Wave users who already trust Aeotec and want to add Zigbee under the same roof.

The Zi-Stick uses the CC2652P chipset — so zstack firmware and adapter: zstack — and is explicitly marketed toward Z-Wave users crossing over to Zigbee. It’s typically around £30 in the UK.

Standout strength: it slots naturally into an existing Z-Wave-with-Aeotec setup, and the CC2652P chip means you inherit the same deep community knowledge base as the Sonoff ZBDongle-P.

Honest caveat: it costs meaningfully more than the Sonoff ZBDongle-P for broadly the same silicon — roughly £8–£12 more — so you’re paying for the brand continuity rather than any hardware advantage.

Verdict: a comfortable choice if you’re already an Aeotec household; otherwise the ZBDongle-P does the same job for less.

Where to buy: Amazon UK and specialist home-automation retailers.

SkyConnect — retired, but still usable

Best for: existing owners deciding whether to replace hardware they already have.

The SkyConnect has been retired, but it is identical hardware to the Home Assistant Connect ZBT-1. That means owners can flash it to ZBT-1-equivalent firmware rather than buying anything new, following the same manufacturer flashing documentation at nabucasa.com and the same Settings > Hardware path in Home Assistant.

Standout strength: nothing to buy. An existing SkyConnect, correctly flashed, is a current-generation EFR32MG21 coordinator.

Honest caveat: it ships with multiprotocol firmware by default, so the Zigbee-only flash is not optional if you want dedicated Zigbee2MQTT operation.

Verdict: don’t replace it — reflash it.

Where to buy: no longer sold new; source a ZBT-1 instead.

Add-on vs Docker: What You Actually Give Up

If you run Home Assistant OS or a Supervised installation, the add-on is the easiest and best-supported path, and the Zigbee2MQTT documentation says so directly.

The two routes are not identical, and it’s worth being precise about what the add-on adds:

• Ingress UI — the Zigbee2MQTT web interface opens inside the Home Assistant sidebar rather than on a separate port you have to remember.
• Supervisor watchdog — the Supervisor monitors the add-on and restarts it if it dies, rather than leaving you to notice a silent failure.
• Integrated backup — add-on data is captured by Home Assistant’s own backup system, so a restore brings Zigbee2MQTT back with it.
• Automatic updates — add-on updates are surfaced and applied through the Home Assistant interface.

Running Zigbee2MQTT in Docker is entirely legitimate and gives you more control, but it requires four things you must configure yourself, and the project’s official Docker Compose documentation is the reference to follow:

1. A by-id device path, not /dev/ttyUSB0. Device nodes like ttyUSB0 can change between reboots or when other USB devices are added, so a fixed identity path is what stops the container losing its coordinator.
2. An explicit user group — the container user must be in the dialout group to get permission to open the serial device.
3. A named volume mounted at /app/data, so your paired devices, configuration and database survive container recreation.
4. A restart policy, so the container comes back after a host reboot or a crash.

The 64-Bit-Only Rule

The Zigbee2MQTT add-on supports aarch64 and amd64 only. The project’s add-on config.yaml lists those architectures, and a dated changelog entry records when 32-bit support was dropped. In practical terms: armv7 and i386 are unsupported, which excludes the Raspberry Pi 3 and any 32-bit mini PC. A Pi 4 or Pi 5 is the practical minimum. If you’re on a Pi 3, the add-on won’t install at all — that’s a hardware decision you need to make before buying a coordinator, not after.

The Mosquitto Broker Layer

Zigbee2MQTT needs an MQTT broker. In practice you install the Mosquitto broker add-on, install Zigbee2MQTT, point it at the broker, and Home Assistant’s MQTT integration discovers your devices automatically. You do not need to write MQTT topics by hand.

Two details trip people up. First, the default broker port is 1883, which is unencrypted — do not enable anonymous access, and do not expose the broker beyond localhost or your own network. Second, the discovery topic prefix defaults to homeassistant/, and it must match the prefix configured in Home Assistant’s MQTT integration. If those two settings disagree, devices pair successfully in Zigbee2MQTT and then simply never appear in Home Assistant.

Troubleshooting the Common Failures

/dev/ttyUSB0 permission denied. This almost always means the user running Zigbee2MQTT is not in the dialout group, so it lacks permission to open the serial device. Fix the group membership and restart the service.

Adapter mismatch. The Sonoff ZBDongle-P requires adapter: zstack. The Sonoff ZBDongle-E and the Home Assistant Connect ZBT-1 require adapter: ember. These values are documented in the Zigbee2MQTT configuration documentation and are not interchangeable — get this wrong and the network won’t start.

Zigbee2MQTT v2.x breaking changes. The v2 series introduced configuration-key renames that break older configs on upgrade. Check the official changelog before updating, particularly if your setup has been untouched for a year.

Channel conflict. Zigbee channels 11–26 overlap the 2.4GHz Wi-Fi band. Channels 15, 20 and 25 are the least overlapping with Wi-Fi channels 1, 6 and 11, which are the most common UK router defaults.

UK Buying Notes

The coordinators in this guide are stocked by Amazon UK, The Pi Hut, Pimoroni, itead.cc (which ships to the UK) and the Home Assistant shop at nabucasa.com. There is no specific UK regulatory hurdle beyond the standard CE/UKCA marking that all the listed devices carry — nothing extra to check for a UK installation beyond the usual electrical marking compliance.

FAQ

Which Zigbee channel should I use in the UK? Zigbee channels 15, 20 and 25 are the least likely to overlap with your Wi-Fi, because UK routers most often default to Wi-Fi channels 1, 6 and 11, and those are exactly the channels those three Zigbee channels sit furthest from. Pick one of those three before you start pairing. Changing the channel afterwards forces every device to rejoin the network, so it’s a decision worth making on day one.

Is port 1883 safe for the Mosquitto broker? Port 1883 is MQTT’s default and it is unencrypted, which is fine on a trusted home network but not fine if the broker is reachable from the internet. Leave anonymous access disabled and keep the broker bound to your local network. If you need to reach Zigbee2MQTT from outside the house, use a VPN rather than port-forwarding the broker.

Can I run Zigbee2MQTT on a Raspberry Pi 3? No. The add-on supports aarch64 and amd64 only, and a Raspberry Pi 3 is armv7, which is explicitly unsupported in the add-on’s architecture list. You need a Pi 4 or Pi 5, or any 64-bit mini PC. Docker users on 32-bit hardware run into the same wall, so check your architecture before buying a coordinator.

My dongle shows a /dev/ttyUSB0 permission denied error — what’s wrong? The user running Zigbee2MQTT isn’t in the dialout group, so it can’t open the serial device. Add the user to that group and restart the service. In Docker, this has to be set explicitly on the container — it isn’t inherited automatically.

I already own a SkyConnect. Do I need to buy a ZBT-1? No. The SkyConnect and the Connect ZBT-1 are identical hardware, so your existing unit is already a current-generation EFR32MG21 coordinator. Flash it to Zigbee-only firmware via Home Assistant’s Settings > Hardware panel using the manufacturer documentation at nabucasa.com, and treat it as a ZBT-1 from then on.

Why does the Zigbee2MQTT configuration reject my adapter setting? The adapter value must match your coordinator’s chipset. CC2652P hardware such as the Sonoff ZBDongle-P, the SMLIGHT SLZB-06M and the Aeotec Zi-Stick needs zstack. EFR32MG21 hardware such as the Sonoff ZBDongle-E, the Home Assistant Connect ZBT-1 and the SLZB-06P7 needs ember. A mismatch stops the network from starting — it doesn’t just run badly.

Do I need a separate Zigbee2MQTT certificate or approval to use these in the UK? No. All the coordinators listed here carry standard CE/UKCA marking, and there’s no additional UK-specific approval or registration involved in running Zigbee2MQTT. The only genuinely UK-relevant planning decisions are which retailer you buy from and which Zigbee channel you pick to avoid your Wi-Fi.

The Bottom Line

Choose your coordinator by chipset, not by price or brand — CC2652P means zstack, EFR32MG21 means ember, and the two are never interchangeable. For most UK buyers the Sonoff ZBDongle-P at around £18–£22 remains the safest start because its community troubleshooting base is unmatched, while anyone fighting USB 3.0 interference or running a server in a cupboard should go straight to an SMLIGHT SLZB-06 variant at around £45–£65 and put the radio on the end of an Ethernet cable. Home Assistant Green and Yellow owners are well served by the official Connect ZBT-1 at around £35–£40, provided they accept the one-off Zigbee-only firmware flash. Whichever you choose, confirm your host is 64-bit before anything else — that single check rules out more failed builds than any other.