ZHA and Zigbee2MQTT both connect Zigbee devices to Home Assistant, but they work differently. ZHA is built into Home Assistant. Zigbee2MQTT is a separate application that talks to Home Assistant through an MQTT broker. Choosing between them is a trade-off between simplicity and reach.
Short answer
Start with ZHA if you want the simplest setup and mostly common devices. Choose Zigbee2MQTT if you need broad device support, detailed per-device settings, or you already run MQTT. Switching later usually means re-pairing your devices.
What ZHA is
ZHA (Zigbee Home Automation) is built into Home Assistant. You set it up from the user interface with a coordinator stick, and it uses the zigpy library. It doesn’t need an MQTT broker or an add-on. Unusual devices can be handled with custom quirks.
What Zigbee2MQTT is
Zigbee2MQTT (Z2M) is a separate application. You run it as an add-on, in Docker, or on its own machine. It needs an MQTT broker, usually Mosquitto, and it comes with its own web frontend. Unusual devices are handled with converters.
Zigbee2MQTT can run without Home Assistant, which ZHA can’t do. Version 2.0, released in December 2024, brought breaking configuration changes, so read the migration notes before you upgrade.
Feature comparison
| ZHA | Zigbee2MQTT | |
|---|---|---|
| Setup | Built in, set up from the UI | Separate app, needs an MQTT broker |
| Device coverage | Broad, with a smaller list | Several thousand devices, and new ones usually arrive faster |
| Per-device settings | Fewer | More |
| Own web frontend | No | Yes, with network maps and diagnostics |
| Unusual devices | Quirks | Converters |
| When Home Assistant restarts | ZHA management pauses, but existing mesh routing and bindings keep working | Keeps running and republishes states when Home Assistant returns |
| Both support | OTA firmware updates for many brands, groups and bindings | Same |
If a device is missing from one list, check the other before you give up on it.
Coordinator radios
Each stack works with a set of coordinator radios:
- ZHA: EZSP radios from Silicon Labs, such as the Connect ZBT-1 and Sonoff Dongle-E. ZNP radios from TI, such as the Sonoff Dongle-P. deCONZ (ConBee), XBee and ZiGate.
- Zigbee2MQTT: zstack (TI), ember (Silicon Labs, which replaced the ezsp adapter in 2024), deconz and zigate.
- Network coordinators, such as the SLZB-06 that connects over Ethernet or PoE, work with both.
Only one stack can use a given coordinator at a time.
Switching later
There’s no one-click migration between ZHA and Zigbee2MQTT. Switching usually means re-pairing devices and rebuilding names, groups, automations and dashboards. Backup-based migration works for some setups, but results vary. Plan for that work before you commit.
Zigbee basics that affect both
- Mains-powered devices act as routers, and battery devices act as end devices. More mains-powered devices give the mesh more paths.
- Zigbee uses channels 11 to 26. Channels 15, 20 and 25 overlap the least with Wi-Fi channels 1, 6 and 11.
- Put the coordinator on a 0.5 to 1 metre USB extension, away from USB 3.0 ports and SSDs, which can cause interference.
- Your choice of stack doesn’t change radio range or mesh quality. Placement, the device mix and channel choice matter more.
Both keep Zigbee control on your own network. Some features, such as firmware downloads, still use the internet.
Which should you choose?
- Choose ZHA if you want the fastest setup inside Home Assistant, fewer moving parts and mostly well-supported devices.
- Choose Zigbee2MQTT if you need broad device support, detailed settings, a standalone management interface, or you already use MQTT.
- If you’re unsure, try ZHA first. You can move to Zigbee2MQTT later, but expect to re-pair your devices.
For the wider picture of integrations and devices, see adding and managing devices in Home Assistant. For Zigbee lighting and switches, see smart lighting, switches and buttons.