Zigbee vs Z-Wave vs Thread: Which Mesh to Build

Most smart homes end up running two or three low-power meshes because nobody ever made the decision on purpose. A Zigbee bulb here, a Z-Wave lock there, a Thread sensor that came with a Matter logo, and now there are three coordinators, three failure modes and three sets of routing problems in one house.

Pick one to be the backbone. Add a second only for a device class the first genuinely cannot serve. To do that you need to know what actually differs, and it is less about the marketing and more about spectrum, routing and which piece of software is in charge.

They are not the same kind of thing

This is the distinction that makes the rest make sense.

Zigbee is a complete stack. It defines the radio (IEEE 802.15.4 in the 2.4 GHz band) and the application layer that says what a light or a lock is. A Zigbee coordinator plus Zigbee devices is a working system.

Thread is a radio and a network layer only. The Thread documentation states it plainly: Thread uses the same RF technology as Zigbee (IEEE 802.15.4) but provides IP connectivity, and by itself does not allow controlling devices. It is just a communication protocol. Control requires a higher-level protocol on top, which in practice means Matter or Apple HomeKit.

Z-Wave is also a complete stack, but on sub-GHz spectrum instead of 2.4 GHz.

So “Zigbee vs Thread” is not a like-for-like comparison. The real comparison is Zigbee versus Matter-over-Thread versus Z-Wave.

And there is a trap in the labelling. The Matter docs warn that many devices use Thread for radio and Matter for control, but this is not guaranteed: some Thread devices support HomeKit or a vendor protocol instead, and some need a beta firmware update to enable Matter. Do not assume Matter support from a Thread logo.

Spectrum decides most of your problems

Zigbee and Thread share the 2.4 GHz band with Wi-Fi, Bluetooth and a microwave oven. The ZHA documentation explains that the Zigbee specification divides that band into 16 channels, that not all devices support all channels, and that the general recommendation is to use only channels 15, 20 or 25 to avoid interoperability problems.

Z-Wave sits on sub-GHz spectrum, which is quieter and propagates through building materials better. The ZWA-2 product page makes the same argument from the vendor side: Wi-Fi, Bluetooth, Zigbee and Thread are all competing for the same airspace, and sub-GHz waves are better suited to thick walls and large houses.

That is the single most useful difference in the whole comparison. If your problem is a detached garage, a basement, or three courses of brick, spectrum will beat any amount of mesh tuning.

Who routes, and what happens when it does not

Zigbee relies entirely on mains-powered devices becoming routers. The docs are direct: Zigbee networks depend heavily on having multiple router devices to expand coverage and increase device capacity, and router devices are meant to be always available. There is also a hard ceiling to be aware of. The zigpy library that ZHA depends on has an upper limit of 32 direct children on the coordinator; you can still run hundreds of devices, but only indirectly, through routers. A Zigbee network with no mains-powered devices does not scale and does not stay up.

Thread handles this differently and better. The docs note that unlike other protocols, Thread can use multiple border routers in a single network, increasing coverage and reducing the risk of a single point of failure. Mains-powered Thread devices act as routers within the mesh, and the border router is the bridge to your IP network rather than the brain of the system.

Z-Wave meshes through mains-powered devices too, but adds an escape hatch. During inclusion of a Long Range capable device you choose between joining the classic mesh or joining as a Long Range node, and the docs recommend Long Range when the device is far away, in a spot that has had connection problems, or when battery life matters. You can run both networks simultaneously on one adapter.

The software layer is where install decisions bite

In Home Assistant these three are not administered the same way.

• Zigbee runs as an integration. ZHA talks to the coordinator directly, so it works on any installation type.
• Z-Wave needs a separate Z-Wave JS server. The docs describe the normal setup as the Z-Wave JS app (formerly known as an add-on), installed on the Home Assistant server.
• Thread needs a border router, and Matter control needs the Matter Server, which the Matter docs also describe as running as an app (formerly an add-on).

The consequence is stated in the installation docs: some integrations, including Thread and Z-Wave, are controlled by apps, and there is no out-of-the-box support for these on Container installations. If you are running Home Assistant in Docker, Zigbee is the path of least resistance and everything else means standing up and maintaining another service yourself. The install method comparison covers what else changes with that choice.

Security and pairing

Z-Wave has the clearest security story. Per the docs, there are two generations of encryption: S0 imposes significant additional traffic on the mesh and is recommended only for older devices that require encryption to work, such as door locks, while S2 adds no extra network traffic and adds acknowledgement of reports. Z-Wave prefers S2 when supported. SmartStart devices pair by scanning a QR code.

Zigbee 3.0 supports install-code and QR-based secure provisioning, but the docs record a real limitation: the Home Assistant UI does not currently support scanning a Zigbee QR code, so pre-commissioning requires the zha.permit action with a qr_code parameter.

Matter devices almost always carry a Bluetooth chip used during commissioning, which is why phones are involved in Thread and Matter onboarding in a way they never are with Zigbee or Z-Wave.

The radios you would actually buy

Official adapters set a useful baseline. The Connect ZBT-2 handles Zigbee or Thread, dedicated to one at a time, at $49 / 45 EUR MSRP. The Connect ZWA-2 is an 800-series Z-Wave adapter with Long Range support at $69 / 59 EUR. For Z-Wave generally, the docs recommend an 800-series adapter with firmware 7.23.2 or later for anyone starting out.

On the Zigbee side the recommended list is broader: Silicon Labs EmberZNet radios (ZBT-1, ZBT-2, the MGM210P inside Home Assistant Yellow, the SONOFF ZBDongle-E, SMLIGHT SLZB-07), current Texas Instruments CC2652 and CC1352 parts, and the ConBee III. Older CC2530 and CC2531 sticks are explicitly not recommended and the docs note they will not work properly beyond 15 to 20 devices.

One coordinator rule applies to Zigbee regardless of brand: a Zigbee network can have only one coordinator, and a device can only belong to one network. Moving a device between systems means a factory reset.

Quick reference

	Zigbee	Thread (with Matter)	Z-Wave
Radio	802.15.4, 2.4 GHz	802.15.4, 2.4 GHz	Sub-GHz
Shares spectrum with Wi-Fi	Yes	Yes	No
Control layer	Built in	Matter or HomeKit, separate	Built in
Routing devices	Mains-powered devices	Mains-powered devices, multiple border routers	Mains-powered devices, plus Long Range
Runs on HA Container out of the box	Yes	No	No
Encryption model	Zigbee 3.0, install codes	Matter fabric, Bluetooth commissioning	S0 legacy, S2 preferred
Direct children limit	32 on the coordinator (zigpy)	Not the same constraint	Mesh or Long Range per device
Device availability	Very broad, cheap	Growing, uneven labelling	Broad, generally pricier

How to choose

Choose Zigbee if you want the largest and cheapest device catalogue, you are running Home Assistant in a container, or you want the simplest software stack. Accept that it lives in a crowded band and that you must deliberately build a router backbone out of mains-powered devices.

Choose Z-Wave if range through walls is your actual problem, if you care about locks and other security devices where S2 matters, or if your 2.4 GHz band is already saturated. Accept the higher device prices and the extra server component.

Choose Thread and Matter if you are buying new and want devices that also work with other ecosystems, and you already have or plan a border router. Accept that the docs still describe the Home Assistant Thread integration as a work in progress, that enabling Thread on Home Assistant hardware currently involves manual steps, and that the labelling on device packaging is not yet trustworthy.

There is a fourth answer that is not a mesh at all: build the sensor yourself on Wi-Fi with ESPHome. That trades mesh complexity for power management complexity, which is a real trade rather than a free lunch. The ESPHome multi-sensor power and battery sizer will size the battery and estimate deep-sleep life before you build anything.

Migration is survivable, so do not over-plan

Committing to a backbone is less frightening than it sounds. ZHA takes automatic backups of the Zigbee network and supports migrating between Silicon Labs, Texas Instruments and ConBee adapters, including overwriting the radio IEEE address so devices do not need re-pairing. Z-Wave stores its mesh on the adapter itself and supports migration to a new adapter.

What does not migrate is a device between protocols. That is the decision worth thinking about, and it is made one purchase at a time.

See also

• Home Assistant hardware for hubs, radio budget and where to physically put the coordinator.
• Home Assistant OS vs Container for why the install type constrains Thread and Z-Wave.
• Zigbee devices going unavailable for what a weak Zigbee router backbone looks like once it is built.