Zigbee Devices in Home Assistant: ZHA or Zigbee2MQTT?
Home Assistant can talk to Zigbee devices two ways -- through the built-in ZHA integration or via Zigbee2MQTT. Both run locally on your own network. Here's an honest comparison to help you pick the right one for your home.
How to choose: 4 steps
Start with a coordinator
Both ZHA and Zigbee2MQTT need a Zigbee coordinator -- a USB stick or module. Neither integration works without one.
Weigh how much you value simplicity
If you want to get going fast with everything configured inside the Home Assistant UI, ZHA is the more direct path -- no extra services to run.
Check device support for your gear
Planning to use less common or niche-brand devices? Check Zigbee2MQTT's device list -- it's often updated faster and covers more ground.
See if you already run MQTT
Zigbee2MQTT needs an MQTT broker. If you already use MQTT for other things, adding Zigbee2MQTT is less extra work.
ZHA vs Zigbee2MQTT -- what to expect
Both are a trade-off
ZHA is simpler to start with since everything lives inside Home Assistant. Zigbee2MQTT adds one extra piece (an MQTT broker) but often has broader, faster-updated device support. The right choice depends on your devices and how much extra configuration you're willing to take on.
Setup process
ZHA is configured directly in the Home Assistant UI -- add the coordinator, pair devices. Zigbee2MQTT also needs an MQTT broker set up and connected to HA through the MQTT integration.
Device and quirk support
Both integrations maintain their own device compatibility lists and fixes for non-standard devices ('quirks'). The Zigbee2MQTT community list is often updated faster, though ZHA's keeps expanding too.
A coordinator is required either way
Whichever you pick, you'll need a Zigbee coordinator USB stick or module -- it's the radio bridge between your Zigbee network and Home Assistant.
Automations work the same
Once a device shows up in Home Assistant as an entity, triggers, conditions and actions in automations behave identically -- it doesn't matter whether the device came in through ZHA or Zigbee2MQTT.
Switching later means re-pairing
Moving from one to the other means re-pairing your devices -- it's not a simple toggle, so choosing carefully upfront saves time.
What you need to get started
Whichever way you go, ZHA or Zigbee2MQTT, the core kit is much the same.
- A Zigbee coordinator (USB stick or module)
- A Home Assistant install -- OS, Container, or Core
- Zigbee end devices (sensors, switches, and so on)
- An MQTT broker -- only if you choose Zigbee2MQTT
- Time to pair devices and build your first automations
Frequently asked questions
Which is easier for a beginner, ZHA or Zigbee2MQTT?
ZHA is usually easier to start with, since everything is configured inside the Home Assistant UI with no extra services. Zigbee2MQTT also requires setting up and connecting an MQTT broker, which is one more step.
Which one supports more devices?
Both have broad device lists, but the Zigbee2MQTT community often adds support for new or niche devices faster. If you have a specific unusual device in mind, check both projects' device lists before deciding.
Can I run ZHA and Zigbee2MQTT at the same time?
Each integration needs its own Zigbee coordinator, since one device can't belong to two separate Zigbee network instances at once. In practice, people pick one approach rather than mixing both on the same network.
Is Zigbee2MQTT harder to maintain long-term?
It means one extra component -- the MQTT broker -- that needs to be kept running and updated alongside Home Assistant. If you already run MQTT for other purposes, the extra burden is small; if not, it's a new service to think about.
Do I need a specific Zigbee coordinator?
Yes -- both ZHA and Zigbee2MQTT need a Zigbee coordinator (a USB stick or module) that bridges the Zigbee radio network to Home Assistant. Without one, neither integration can see your devices.
Ready to add Zigbee to your home?
Browse Zigbee devices and coordinators in the store -- pick based on your plan, not the hype.