ZHA vs Zigbee2MQTT: Which Should You Use? (2026)

Disclosure: This article contains affiliate links. As an Amazon Associate, I earn from qualifying purchases. If you buy through the links on this page, I may earn a small commission at no extra cost to you.

If you run Home Assistant and want Zigbee devices without vendor hubs, you will meet the same fork everyone does: ZHA, the Zigbee integration built into Home Assistant, or Zigbee2MQTT, the separate project that talks to Home Assistant over MQTT. Forums are full of strong opinions on both.

Both are mature, both run your Zigbee network locally, and both work well with the right coordinator. The real differences are architectural, and every practical difference follows from them. This guide explains that architecture, compares the two side by side, and then does something most comparisons skip: it checks, setting by setting, what two popular radiator valves actually expose in each. If Zigbee2MQTT is new to you, start with our Zigbee2MQTT beginner guide.

Device support and feature lists change with every release. The comparisons below were checked against the ZHA and Zigbee2MQTT documentation and source code in October 2026.


Table of Contents

  1. Quick Answer
  2. How Each One Works
  3. Side-by-Side Comparison
  4. Same Device, Two Views
  5. Reliability Is Mostly Your Mesh
  6. Switching From One to the Other
  7. Decision Guide
  8. FAQ

Quick Answer

If you…Choose
Are new to Home Assistant and want the fewest moving partsZHA
Mostly use mainstream devices (IKEA, Philips Hue, standard Sonoff sensors and plugs)ZHA
Own many Tuya or Aqara devices, or buy new models soon after releaseZigbee2MQTT
Need vendor-specific settings, such as feeding an external sensor to a radiator valveZigbee2MQTT (check the device first)
Want Zigbee to keep running when Home Assistant restarts, or to run it on a separate machineZigbee2MQTT
Are happy with your current setupStay where you are. Switching has a real cost.

How Each One Works

ZHA (Zigbee Home Automation) is an integration inside Home Assistant. It uses the zigpy Python library to talk to your coordinator, and the ZHA Device Handlers project (“quirks”) to fix devices that don’t follow the Zigbee standard. Devices become Home Assistant entities directly. There is no other software to install.

Zigbee2MQTT is a standalone application. It uses its own Zigbee stack and a large library of device converters, and it publishes every device to an MQTT broker. Home Assistant picks the devices up through its MQTT integration using MQTT discovery. On Home Assistant OS, both Zigbee2MQTT and the Mosquitto broker run as apps (formerly called add-ons), but Zigbee2MQTT can just as well run on any Linux machine or in Docker.

ZHA vs Zigbee2MQTT architecture ZHA runs inside Home Assistant and talks to the coordinator directly. Zigbee2MQTT runs as a separate application, publishes devices to an MQTT broker, and Home Assistant reads them through its MQTT integration. ZHA Zigbee2MQTT Zigbee devices Coordinator (USB or Ethernet) Home Assistant ZHA integration (zigpy + quirks) Entities Zigbee devices Coordinator (USB or Ethernet) Zigbee2MQTT app (converters) MQTT broker (Mosquitto) Home Assistant MQTT integration (discovery) Entities
ZHA lives inside Home Assistant. Zigbee2MQTT sits beside it and hands devices over through MQTT.

Everything else follows from that picture. ZHA has fewer parts to install and maintain, but your Zigbee network restarts whenever Home Assistant restarts. Zigbee2MQTT adds a broker and a second application, but it keeps running on its own, it can live on a different machine, and it has its own web interface for devices, logs and the network map.

Both are fully local. Neither needs a cloud account, and both keep working without internet. That matters more than the ZHA-versus-Z2M choice itself; see local vs cloud automations.

Side-by-Side Comparison

AspectZHAZigbee2MQTT
Where it runsInside Home Assistant, as an integrationSeparate app on Home Assistant OS, or any Linux host or Docker
Extra componentsNoneMQTT broker (usually Mosquitto) plus Home Assistant’s MQTT integration
Setup effortAdd the integration, select the radio, doneInstall broker, install Zigbee2MQTT, point it at the adapter, confirm discovery
Device support modelStandard devices work natively; non-standard ones need a quirk (Python)Converters (JavaScript); the project lists over 5,700 supported devices from 600+ vendors
Vendor-specific settingsComparable for many popular devices; gaps on some Tuya and Aqara modelsUsually the more complete of the two for vendor extras
OTA firmware updatesUpdate entities; several vendors’ providers on by defaultFrom its frontend, also shown as Home Assistant update entities
BackupsAutomatic network backups; radio migration between Silicon Labs, TI and ConBee adaptersCoordinator backup file for zStack and EmberZNet adapters
Network map and UIMap and device pages inside Home AssistantOwn web frontend: map, device pages, logs, settings
Resource useRuns inside Home Assistant’s processTwo extra processes (app and broker); modest on current hardware
Independence from Home AssistantRestarts with Home AssistantKeeps running when Home Assistant restarts; can run on another machine
Coordinator stacksSilicon Labs (EZSP), TI (ZNP), deCONZ, ZiGate, XBeeRecommended: TI zStack, Silicon Labs EmberZNet, deCONZ. ZiGate unmaintained, ZBOSS experimental

A note on new devices: anything that follows the Zigbee 3.0 standard clusters for its basic functions works in both without extra code (see what Zigbee 3.0 standardises). The difference appears with vendor-specific features, and that is exactly where the next section looks.

Sources: ZHA documentation, Zigbee2MQTT supported adapters, Zigbee2MQTT supported devices.

Same Device, Two Views

Generic comparisons say “Zigbee2MQTT exposes more settings”. That is often true, but the gap depends entirely on the device. Here are two radiator valves we cover in our guide to Zigbee TRVs in Home Assistant, checked against ZHA’s source code and the Zigbee2MQTT device pages.

Sonoff TRVZB: near parity

SettingZHAZigbee2MQTT
Setpoint, mode, temperature, heating stateClimate entityClimate entity
Temperature offsetYesYes
PID control on/offYes (“Adaptive mode”)Yes (smart temperature control)
HysteresisYes (“Temperature control accuracy”)Yes (temperature accuracy)
Valve opening and closing degreeYesYes
External temperature sensorOn/off switch plus valueSource select (including an “external source offline” state) plus value
Boost and timer modesYes (buttons, duration, timer temperature)Yes (mode select, duration, timer temperature)
Child lock, open window, frost protectionYesYes
Weekly schedule stored in the valveNot exposedYes (per-day schedules, used in auto mode)
Motor diagnostics (calibration steps, motor voltages)Not exposedYes (read-only)

For the TRVZB, ZHA has caught up on everything you need day to day. Zigbee2MQTT adds the on-device schedule and diagnostic values that help when a valve won’t calibrate. If you schedule heating in Home Assistant anyway, either works. Device page: TRVZB on Zigbee2MQTT.

Aqara Radiator Thermostat E1: a real gap

SettingZHAZigbee2MQTT
Setpoint, mode, preset, away temperatureYesYes
Window detection and window-open stateYesYes
Valve detection and valve alarmYesYes
Child lockYesYes
Calibration statusYes (read-only)Yes (read-only)
Start a valve calibrationNot exposedYes (action)
Choose internal or external sensorShows which is active, can’t change itYes (select)
Send an external temperatureNot exposedYes (0–55 °C)
Schedule stored in the valveNot exposedYes

This is the difference that matters in practice. Feeding a room sensor into the valve is the single most effective fix for inaccurate TRVs. With the E1 it is available in Zigbee2MQTT and has no entity in ZHA. ZHA’s device management panel can read and write raw cluster attributes, but that’s not a practical substitute for an everyday automation. Device page: SRTS-A01 on Zigbee2MQTT.

The rule that follows: before you choose, look up your three most important devices in both. If a feature you need exists in only one, that decides it. Tuya devices are where this happens most often; our Aqara vs Tuya comparison explains why.

Reliability Is Mostly Your Mesh

People switch from ZHA to Zigbee2MQTT (or back) to fix dropouts, and are disappointed when nothing changes. Both use the same Zigbee radio and the same mesh. When devices go unavailable, the cause is almost always below the software:

  • Too few routers. Battery sensors depend on mains-powered devices (plugs, bulbs, wired switches) to relay their traffic. See Zigbee range problems.
  • Wi-Fi overlap. Zigbee and Wi-Fi share 2.4 GHz. Choosing the Zigbee channel against your Wi-Fi channels matters more than the software: Zigbee channels in EU homes and Wi-Fi interference in apartments.
  • Coordinator placement. Use a USB extension cable to keep the coordinator away from USB 3 ports and metal cases, or use an Ethernet coordinator placed centrally.
  • Network coordinators over Wi-Fi. Zigbee2MQTT’s documentation warns that Wi-Fi-connected adapters are less stable, because the serial protocol has little fault tolerance for packet loss. Use USB or wired Ethernet.

If devices keep dropping, work through why Zigbee devices lose connection before you consider switching platforms.

Switching From One to the Other

Plan for re-pairing every device. ZHA’s built-in radio migration only restores backups made in ZHA. The Zigbee2MQTT FAQ states that switching adapters requires re-pairing, with a possible, officially unsupported exception between TI zStack and Silicon Labs EmberZNet adapters. Community tools that convert network backups between the two do exist, but treat them as a bonus, not a plan.

Carries overDoes not carry over
Your coordinator, if both support its stackDevice pairings (expect to re-pair)
Physical installation and device placementEntity IDs and device names
The logic of your automationsAutomations’ entity references (must be updated)
Your Zigbee channel choicePlatform-specific settings and quirk options

A migration plan that keeps the house working:

  1. Inventory first. List every device, its room and the automations that use it.
  2. Consider a second coordinator. One coordinator can serve only one application. A second one lets you run both platforms in parallel on different channels and move devices room by room, instead of switching everything in one evening.
  3. Install the new platform. For Zigbee2MQTT: install Mosquitto, then Zigbee2MQTT, and set the channel and adapter. If you reuse the same coordinator, remove it from the old platform first.
  4. Pair routers before end devices. Start with mains-powered devices so the new mesh has a backbone, then pair battery devices in their final positions.
  5. Reuse the old names. Name devices as before so entity IDs come out similar, then fix the automations that broke.
  6. Retire the old platform only when every device and automation has moved.

Decision Guide

Choose ZHA if you are starting out, your devices are mainstream, and you want Zigbee to be one more integration rather than a system to maintain. It is the path Home Assistant’s own hardware is built around, and it handles common devices well.

  • You value fewer components over more options.
  • Your devices are IKEA, Philips Hue, standard Sonoff, or other well-known Zigbee 3.0 models.
  • You don’t need vendor extras such as external sensor input on every device.

Choose Zigbee2MQTT if your network is large or varied, you buy Tuya and Aqara devices, or you want Zigbee to be independent of Home Assistant.

  • You own many Tuya or Aqara devices, including budget ones (see cheap Zigbee devices that actually work).
  • You need specific vendor settings, as in the E1 example above.
  • You want the Zigbee network to survive Home Assistant restarts, or to run on a separate machine near the centre of the house.
  • You like having logs and a dedicated interface for the Zigbee layer.

For a typical EU home with Aqara and Sonoff sensors, a few Tuya devices and smart radiator valves, Zigbee2MQTT is the safer long-term choice. For a first network built from mainstream door and window sensors and motion sensors, ZHA will rarely hold you back. If you’re still deciding between Home Assistant and a vendor hub, see our Zigbee hubs comparison first.

Don’t have a coordinator yet? Both platforms depend on it more than on each other. Read our guide to choosing a Zigbee coordinator for Home Assistant before you buy.

ZHA and Zigbee2MQTT are two good answers to the same question. The architecture decides the trade-off: ZHA is simpler because it lives inside Home Assistant, and Zigbee2MQTT is more flexible because it doesn’t.

Don’t choose on forum reputation. Check how your most important devices are supported in each, build a solid mesh, and make the choice once, because switching later means re-pairing. If you’re setting up from scratch, our Home Assistant Zigbee setup guide walks through the first steps.


FAQ

  • Can I run ZHA and Zigbee2MQTT at the same time?
    Yes, with two coordinators. Each platform runs its own Zigbee network, and each device joins only one of them. A coordinator can only be used by one application at a time. Put the two networks on different channels.
  • Does Zigbee2MQTT need a separate machine?
    No. On Home Assistant OS it runs as an app, next to the Mosquitto broker app. A separate machine is optional and is useful if you want the coordinator in a central spot or want Zigbee to run independently of Home Assistant.
  • Which is more stable, ZHA or Zigbee2MQTT?
    With a supported coordinator and a healthy mesh, both are stable. Most instability comes from too few routers, Wi-Fi overlap or poor coordinator placement. Zigbee2MQTT has one structural advantage: it keeps running while Home Assistant restarts.
  • Do I need MQTT to use ZHA?
    No. ZHA talks to the coordinator directly from inside Home Assistant. MQTT is only needed for Zigbee2MQTT.
  • Can I move my ZHA network to Zigbee2MQTT without re-pairing?
    Plan to re-pair. ZHA’s migration only restores ZHA backups, and Zigbee2MQTT’s documentation says switching adapters requires re-pairing except, unofficially, between TI zStack and Silicon Labs EmberZNet. Community conversion tools exist, but results vary.
  • Will my devices work the same in both?
    Basic functions of standard Zigbee 3.0 devices, yes. Vendor-specific settings can differ a lot. For example, the Aqara E1 radiator valve accepts an external temperature in Zigbee2MQTT but not in ZHA. Check your key devices before choosing.
Panos K. - Smart Home Engineer

About the author: Panos K.

Panos K. is a Smart Home Engineer and Digital Systems Specialist with over 15 years of experience in wireless automation, Zigbee ecosystems, Matter/Thread technologies, and EU-based smart home deployments. He focuses on practical, reliable, low-power smart home design.

View full profile →