The key distinction: a radio protocol is not an integration
Zigbee is a wireless communication standard.
Zigbee 3.0 describes a standards generation/profile,
but is not a product-specific promise about Home Assistant entities.
ZHA is Home Assistant's built-in Zigbee integration;
Zigbee2MQTT is a separate gateway application that
communicates with Home Assistant over MQTT. Both require suitable
Zigbee radio hardware and a compatible network, but use different
software implementations and device-specific support mechanisms.
A label such as "works with Zigbee" is not enough to confirm
pairing, reporting, OTA updates, exposed controls or firmware support.
Verify the exact hardware identifier and integration path.
What differs between ZHA and Zigbee2MQTT?
| Question | ZHA |
Zigbee2MQTT |
|---|
| Where does the gateway run? | Inside Home Assistant's
integration stack | Separate gateway service, often alongside Home Assistant |
| What is required? | Supported coordinator and ZHA setup |
Supported coordinator, Zigbee2MQTT, MQTT broker and HA discovery |
| Device-specific extensions | Standard ZCL support and
zigpy/ZHA quirks for specific devices | zigbee-herdsman-converters
definitions and device exposes |
| Can a device listing confirm the other path? | No | No |
| Where to check? | ZHA docs |
Zigbee2MQTT supported devices |
Home Assistant documents that ZHA does not have a complete official
device compatibility list. A missing ZHA list entry therefore
cannot prove a device is incompatible.
A reliable compatibility check before ordering
- Identify the exact manufacturer, model and revision;
do not rely on a retailer's generic product title.
- Identify which integration path you plan to run,
including the coordinator model and its firmware.
- Look for a matching documentation entry and inspect the
individual features, pairing notes and caveats.
- Verify critical features: battery reporting, sensor state,
alarms, switches, group binding or OTA support, as applicable.
- Plan the Zigbee mesh: mains-powered routers, radio placement
and interference can matter as much as the device model.
- Retain the option to return the device if your exact
combination is not documented or tested.
Search our source-linked Zigbee2MQTT model explorer →
Results describe published converter capabilities, not independently
tested setups.
Z-Wave, Thread and Matter are different questions
Z-Wave uses a different radio system and the
Home Assistant Z-Wave JS integration.
Radio-frequency regions matter: a device sold for a different
region may not work with your controller. Verify your regional
frequency before buying, especially when importing hardware.
Matter is an application-layer interoperability
standard that may run over Wi-Fi or Thread. Thread
is an IP-based mesh network and is not synonymous with Matter.
Matter-over-Thread needs an appropriate Thread border router;
simply owning a Zigbee USB radio is not proof of an operable
Matter-over-Thread setup. See Home Assistant's
Matter guide and
Thread guide.
Questions buyers ask
Does Zigbee 3.0 mean ZHA supports every feature?
No. Protocol/profile compliance and feature support through
a particular Home Assistant integration are different issues.
Can I run one Zigbee device with ZHA and Zigbee2MQTT at once?
Typically a Zigbee end device is joined to one Zigbee network.
Migrating between network coordinators or gateway implementations
usually requires deliberate network migration or re-pairing;
review your gateway's instructions first.
Does a missing catalog entry mean a device does not work?
No. The available source is incomplete as an exhaustive
Home Assistant support list. Treat a missing match as
insufficient evidence, not an incompatibility verdict.
Official sources and methodology
Primary references:
Home Assistant ZHA,
Zigbee2MQTT HA discovery,
Z-Wave JS,
Matter.
No model claims in this guide constitute independent testing.