Zigbee, Z-Wave, Wi-Fi or Thread: choosing a protocol

Four wireless standards compete for the same job inside a house: getting a battery-powered sensor, a door lock or a light switch talking to a hub without running a cable. Zigbee, Z-Wave, Wi-Fi and Thread each solve that job with a different radio, a different network shape and a different tolerance for battery drain. None is simply better than the rest. Each was built around a specific compromise between range, power, throughput and how many devices one network can carry before it strains.

The most consequential difference between them is not price or ecosystem size. It is frequency. Zigbee, Thread and Wi-Fi itself all share the 2.4 GHz band, so three of the four protocols compete for the same spectrum before a single device is switched on. Z-Wave avoids that fight by design, operating below 1 GHz throughout. What follows sets out how each protocol builds its mesh, what that mesh costs in power, how many devices the specification actually permits against what a real installation will hit, and which of the four fits which job.

Frequency bands and why they differ

Zigbee runs at 2.4 GHz worldwide across 16 channels at 250 kbps, with two regional sub-gigahertz options: 915 MHz in the Americas across 27 channels at 500 kbps, and 868 MHz in Europe across 8 channels at 100 kbps, according to the Connectivity Standards Alliance, which maintains the Zigbee specification. The sub-gigahertz bands trade speed for distance. The Alliance states they can reach a kilometre or more, against 10 to 100 metres for the 2.4 GHz version.

Z-Wave never goes near 2.4 GHz. It sits in the sub-1 GHz band throughout: 908.42 MHz in the United States, 868.42 MHz in Europe. Z-Wave Long Range, the variant the Z-Wave Alliance made commercially available from the third quarter of 2023, stays in the same sub-gigahertz territory but raises transmit power to 30 dBm, pushing range past 1.5 miles line of sight. Thread sits at 2.4 GHz only, built entirely on the IEEE 802.15.4 radio, the same band Zigbee uses, with no sub-gigahertz variant in commercial use. Wi-Fi now spans three bands: 2.4 GHz and 5 GHz since Wi-Fi 5, and 6 GHz since Wi-Fi 6E, per the Wi-Fi Alliance.

How each protocol builds its mesh

Zigbee and Z-Wave both mesh, under the same restriction: only mains-powered devices repeat traffic. A battery sensor joins the network and talks through a repeater; it never relays anyone else's messages, because that would drain its own battery. Z-Wave layers a hard limit on top of that rule: a message may cross no more than four hops between mains-powered repeaters before it reaches its destination, a bound chosen to keep the routing calculation cheap enough for an inexpensive microcontroller. Z-Wave Long Range removes the mesh altogether. Every device connects directly to the hub in a star topology at higher transmit power, which is how the Z-Wave Alliance says it eliminates the need for repeaters, at the cost of a mesh's ability to route around a dead spot.

Thread meshes differently again. It runs on IPv6 rather than a proprietary network layer, and the Thread Group describes the result as having no single point of failure, with the network self-healing when a router drops out. The specification allows up to 32 active routers, each supporting up to 511 child devices, for a theoretical ceiling of 16,384 addressable devices. OpenThread's own guidance, though, is to keep the active router count between 16 and 23: enough for resilience without loading every router's tables past what it needs.

Wi-Fi is not a mesh between end devices at all. Every station connects to one access point in a star. Wi-Fi CERTIFIED EasyMesh, the Wi-Fi Alliance's own multi-vendor mesh standard, meshes access points and extenders together so they can hand a device between them; the smart plug or bulb still makes one direct connection to whichever access point is nearest, and never relays another device's traffic. That is a structurally different kind of mesh from Zigbee, Z-Wave or Thread. Adding more Wi-Fi smart devices adds more direct radio load to the home's access points, not less.

Power draw: the physics behind battery life

Zigbee, Z-Wave and Thread were all built around the IEEE 802.15.4 radio, which spends most of its life asleep. The Connectivity Standards Alliance's Green Power feature for Zigbee combines what it calls ultra-low-power silicon with energy harvesting, letting some devices run for years on a coin cell, or with none at all. Z-Wave Long Range claims up to ten years of battery life from a single coin cell through what the Z-Wave Alliance calls dynamic power control.

Wi-Fi is a different proposition. A Wi-Fi station has historically had to stay associated with its access point and wake for every beacon interval, which costs far more current than an 802.15.4 radio's sleep cycle. Wi-Fi 6 introduced Target Wake Time specifically to close that gap: a device can now negotiate to sleep for seconds, minutes, or, for something that reports in once a day, nearly 24 hours, waking only to transmit. Even with that feature, the underlying Wi-Fi radio and baseband still draw more power than a low-rate 802.15.4 chip doing the same job. That is one reason most battery-powered smart home sensors still ship on Zigbee, Z-Wave or Thread rather than Wi-Fi.

Device limits: what the specification allows

The figures below come from each protocol's own governing body, not a single manufacturer's marketing page. They describe what the specification permits, not what a household will ever approach.

The practical reading matters more than the ceiling. A 232-node limit is not a problem for a typical house, but it is a real constraint on a large multi-unit building, which is exactly the gap Z-Wave Long Range was built to close. Zigbee's headline figure of thousands of nodes is a specification limit, not a working recommendation. A coordinator's own memory for routing and neighbour tables is what actually caps a real installation, well below that number.

Sharing the air with 2.4 GHz Wi-Fi

Zigbee and Thread both compete directly with Wi-Fi for spectrum, because all three sit in the same 2.4 GHz ISM band. The Connectivity Standards Alliance describes Zigbee as having 16 separate 5 MHz-spaced channels in that band, several of which do not overlap with Wi-Fi's channel plan in the US and Europe. A single Wi-Fi channel is still wide enough to sit across several of those Zigbee or Thread channels at once. In a building with several neighbours' routers fighting over the same three non-overlapping Wi-Fi channels, a 2.4 GHz mesh device shares that congestion whether it wants to or not.

Z-Wave has no such problem. Living below 1 GHz means it is never contending with a neighbour's Wi-Fi, a baby monitor or a microwave oven for airtime. That single structural fact is the strongest technical argument for Z-Wave in a dense apartment building, or anywhere 2.4 GHz spectrum is already crowded. Wi-Fi's own answer to that same congestion is to leave the band: the 5 GHz and, more recently, 6 GHz ranges exist because the original 2.4 GHz band became too congested for reliable high-throughput use, per the Wi-Fi Alliance.

Where each protocol is the right answer

Z-Wave suits dense, Wi-Fi-crowded buildings and installs where a hop-limited but predictable mesh matters more than raw device count: door locks and security sensors, mainly, where interference from a neighbour's router is not an acceptable risk. Long Range extends that reach to sites where 232 nodes or four hops will not stretch far enough.

Zigbee still carries the largest catalogue of certified devices on the market, and a mesh that scales further on paper, which keeps it the default for mixed-brand retail installations. It also inherits the 2.4 GHz coexistence problem in full.

Thread earns its place in a new build going all-in on Matter: an IP-native mesh with no gateway translation layer and, per the Thread Group, no single point of failure. Its device catalogue is younger and shallower than Zigbee's or Z-Wave's.

Wi-Fi remains the only sensible choice for anything that needs real bandwidth. None of the other three protocols clears 500 kbps even at their fastest regional variant, which rules out a camera or a video doorbell outright. The trade is bandwidth for battery life, and for the load each device puts directly on the home's own access point.

A Thread network still needs that border router, typically a smart speaker or hub with its own Wi-Fi or Ethernet uplink, to reach anything outside its own mesh. Without one, Thread devices talk to each other but not to a phone on the mobile network. That dependency is easy to miss on a product page advertising no hub required.