Zigbee vs Z-Wave vs Matter vs Thread
A practical comparison of the four smart home protocols that matter: what each is good at, where it falls short, and which to choose for a local-first home.
Protocol debates generate more heat than light in smart home forums. Here’s the version that actually helps you buy things.
Zigbee is the best starting protocol for most Home Assistant users today. Z-Wave is a strong alternative with different tradeoffs. Thread is promising but early. Matter is an interoperability layer, not a radio protocol, and it isn’t ready to be your whole strategy yet.
Zigbee
Zigbee is the most widely used protocol in the Home Assistant ecosystem, and it’s where I’d start.
Strengths:
- huge device selection across every category
- excellent Home Assistant support via ZHA and Zigbee2MQTT
- mesh networking, where devices relay signals to extend range
- mature, well-understood protocol
- generally inexpensive devices
Weaknesses:
- operates on 2.4 GHz, which means potential Wi-Fi interference
- coordinator quality matters a lot (a bad coordinator makes everything worse)
- mesh health can be hard to diagnose for beginners
- device compatibility is generally good but not perfectly universal across all coordinators
Zigbee is the default recommendation because the device ecosystem is enormous, the Home Assistant integration is deep, and the community knowledge base is the strongest. If you’re starting from scratch, Zigbee is the easiest protocol to build a large, capable local setup around, and there’s a wide range of Zigbee sensors for Home Assistant covering motion, contact, temperature, and more.
The coordinator is the foundation of your Zigbee network. I have a dedicated guide for that: Best Zigbee coordinators for Home Assistant.
Z-Wave
Z-Wave is the other established mesh protocol, and it has some real advantages that keep it relevant. It runs on sub-1 GHz frequencies, so it avoids the usual Wi-Fi interference headaches and tends to punch through walls better than Zigbee. The certification story is also cleaner: every Z-Wave device is supposed to interoperate properly, which means fewer weird compatibility surprises once you start mixing brands.
The tradeoff is that the ecosystem is smaller and the devices usually cost more. You see the difference most clearly outside the core categories. Switches, locks, thermostats, and security sensors are strong, but the long tail is thinner than Zigbee. Regional frequency differences also mean you need to buy the right version for your market, which is mildly annoying but manageable.
Z-Wave isn’t the protocol I recommend first, but it’s better than Zigbee for specific situations. If you have a larger home where range through walls matters, or if you want certified interoperability without worrying about coordinator compatibility quirks, Z-Wave has real advantages.
I run both Zigbee and Z-Wave here, and plenty of serious Home Assistant setups do. That is completely fine and sometimes the smartest approach.
Range: the realistic numbers
Z-Wave runs in the sub-GHz band (around 800-900 MHz depending on region), and the marketing range figures for both protocols are not what you get indoors. A single Z-Wave hop is roughly 30 meters through typical residential walls and up to around 100 meters line-of-sight outdoors; Zigbee’s per-hop indoor range is usually cited at 10-20 meters. Neither reaches across a house on its own, so both depend on the mesh, but in a large or multi-floor home Z-Wave often needs fewer hops to reach the same corners. You still want mains-powered devices spread around as repeaters, such as a hardwired switch or a plug like the Zooz ZEN04 800LR, which repeats only when you include it as an ordinary mesh device rather than in Long Range mode. Z-Wave Long Range is the separate variant that reaches much farther, but it uses a star topology back to the controller instead of a mesh, and not every device supports it.
Check what radio your controller has before assuming. A Home Assistant Yellow (discontinued in October 2025, so a secondary-market find now) carries a Silicon Labs Zigbee/Thread radio and no Z-Wave, so you add a Z-Wave stick separately; the Homey Pro ships with Z-Wave hardware built in.
Interference and security
Z-Wave’s band sits well clear of Wi-Fi, Bluetooth and everything else crowding 2.4 GHz. Zigbee shares that band with Wi-Fi, and overlapping channels show up as delayed responses or dropped commands in RF-dense homes. Careful Zigbee channel selection mitigates it; Z-Wave sidesteps it. For devices where a missed command is a real problem, such as a lock like the Yale Assure Lock 2 or a water leak sensor, the quieter band is worth paying for.
On encryption, the difference is smaller than the forum version suggests. Since April 2017 the S2 framework has been mandatory for every newly certified Z-Wave product, so any modern Z-Wave device ships with it. Zigbee 3.0 also encrypts traffic with AES-128 using install codes and trust-center link keys. The distinction is that Z-Wave’s baseline is uniformly enforced through certification, not that Zigbee lacks one.
Cost, longevity and switching controllers
Z-Wave devices cost more, often $30-50 for a smart switch against $15-25 for an equivalent Zigbee one. What you get for that is a certification program built around long-term interoperability: older certified devices generally keep working with newer controllers, which matters if you are installing switches and sensors once and want them left alone for years.
Do not assume that longevity extends to swapping controllers freely. A Z-Wave migration works through an NVM backup and restore between compatible sticks, it generally needs the same Z-Wave chip series and matching firmware to succeed, and the routing table often has to rebuild afterwards. Moving between, say, a Hubitat Elevation C-8 (discontinued in March 2026, though the C-8 Pro behaves the same way here) and an Aeotec Smart Home Hub is possible, but plan it rather than assume it. My guide on how to pick a Z-Wave controller walks through the stick and hub options.
Where Z-Wave has the better device
A few categories are simply better served on Z-Wave. Fan control is one: the Leviton ZW4SF gives proper four-speed control for a paddle fan and repeats for the rest of the mesh. Water shutoff is another: the Zooz ZAC36 Titan automates the valve with no cloud, and it can close the valve from its wired probe even if the controller is offline; the Z-Wave water valve roundup compares it with the cheaper Dome DMWV1.
Thread
Thread is the newer mesh networking protocol that is getting a lot of attention, partly because of its relationship with Matter. The pitch is good: low-power devices, IP-based networking, and a mesh that doesn’t revolve around a single coordinator the way Zigbee does. In theory, that should make it cleaner, more modern, and easier to integrate into normal home networks over time.
In practice, Thread is still early enough that the ecosystem feels thinner and rougher than the hype suggests, and the real-world differences between Zigbee and Thread matter more day to day than the spec sheets imply. Border router setup is better than it was, but not always smooth, and the pool of battle-tested devices is still much smaller than Zigbee or Z-Wave. Home Assistant support is improving, which is why I’m optimistic about it, but this still feels like an expansion path more than a foundation.
If you’re buying a Home Assistant Connect ZBT-2 - or you already have the ZBT-1 it replaced, discontinued in November 2025 - it can also serve as a Thread border router, which gives you a low-risk way to start experimenting with Thread devices. It runs one protocol at a time, though, so a ZBT stick on Thread duty is not also your Zigbee coordinator.
Matter
Matter isn’t a radio protocol. It’s the rules layer sitting above radios like Thread or Wi-Fi, meant to make the same device usable across Home Assistant, Apple Home, Google Home, and Alexa without a weird vendor bridge in the middle. In the best case, that means less compatibility drama and a cleaner local-control story.
The catch is that Matter still behaves more like a promising framework than a finished universal answer. Some devices are excellent, some are barely better than their old platform-specific versions, and multi-admin still breaks often enough that I would not build a whole buying strategy around it yet. Treat Matter as a useful extra when the underlying product is already good, not as proof that the product is good. Which devices clear that bar is a shorter list than the number of badges on shop shelves suggests, so I keep a category-by-category list of the best Matter devices worth buying.
Which protocol to choose
Start with Zigbee if…
- you want the largest device selection
- you’re building around Home Assistant
- you want the deepest community support and documentation
- you’re price-conscious
Choose Z-Wave if…
- you have a larger home where range through walls matters
- you want certified interoperability
- you prefer locks, thermostats, or sensors where Z-Wave has strong options
- you’re okay with higher per-device cost for fewer compatibility surprises
Add Thread when…
- you already have a Thread border router (a Connect ZBT-2 running Thread firmware in Home Assistant, a HomePod mini, etc.)
- a specific Thread device is the best option in its category
- you want to start future-proofing alongside your existing setup
Treat Matter as…
- a nice-to-have, not a primary buying criterion
- a long-term bet that isn’t ready to be your whole strategy
- something worth following but not worth waiting for
The Home Assistant perspective
Home Assistant supports all four protocols well, which means you don’t have to pick just one. Most mature Home Assistant setups use a mix of Zigbee and Z-Wave, with Thread devices coming in as the ecosystem grows.
Your hub and software layer matter more than any single protocol choice. Home Assistant abstracts the protocol differences so your automations don’t care whether a sensor is Zigbee, Z-Wave, or Thread. Pick the best device for the job, regardless of protocol.
That said, if you’re starting fresh and want one protocol to begin with, start with Zigbee. The device selection, price points, and community support make it the easiest on-ramp. If you want the numbers behind that, the Local-First Index is my live census of cloud dependency by protocol.