Zigbee vs Z-Wave vs Thread vs Wi-Fi: home-automation protocols compared
A plain-language comparison of Wi-Fi, Bluetooth, Zigbee, Z-Wave, Thread and wired KNX — plus why Matter isn't a radio, and how to choose.
Buy two smart bulbs from two different brands and you may find they refuse to share an app, a hub or even a network — despite doing almost identical jobs. The reason usually comes down to the invisible layer underneath: the wireless (or wired) language each device uses to talk. Get that layer right and a smart home feels calm and reliable. Get it wrong and you end up with a drawer of incompatible bridges and an automation that works four days out of five.
This guide walks through the main ways smart-home devices communicate — Wi-Fi, Bluetooth Low Energy, Zigbee, Z-Wave, Thread and wired KNX — and compares them on the things that decide whether a setup is pleasant to live with: network shape, power use, range, radio band, whether you need a hub, and how well kit from different makers plays together. It also clears up the most common confusion: where Matter fits, and why it is not a rival radio at all.
Radios and languages are different things
A useful way to think about it is to separate the radio from the language. The radio is the physical way bits move through the air (or down a wire): its frequency band, how far it reaches, how much battery it drains. The language, or application layer, is the agreed vocabulary that lets a light understand the word “off” from a switch it has never met before. Most arguments about smart-home standards are really arguments about one or the other, muddled together.
Zigbee, Z-Wave, Thread, Wi-Fi and Bluetooth are transports — ways of carrying data. Matter, by contrast, is a language that rides on top of some of them. For the wider context of how connected devices exchange data, the guide to how IoT works covers the layers beneath the badge on the box.
The six ways devices talk
Wi-Fi
Wi-Fi is the one everybody already has. Devices join your existing router directly, so there is no extra hub to buy, and each gadget gets its own internet connection. That convenience is also its weakness. Wi-Fi is comparatively power-hungry, so battery sensors tend to have short lives or need frequent charging; it suits mains-powered kit such as cameras, plugs and speakers far better. It runs mostly on the crowded 2.4 GHz band (and 5 GHz for higher-bandwidth devices), and it uses a star shape — everything talks back to the router rather than to each other. A household of forty Wi-Fi gadgets can also strain a consumer router.
Bluetooth and Bluetooth Low Energy (BLE)
Bluetooth Low Energy is built for short bursts of data from small batteries, which is why it turns up in door locks, thermometers, plant sensors and wearables. Its party trick is setup: a phone can talk to a new device directly, with no hub, which is why many other standards borrow BLE just for the initial pairing step. Range is short — think one or two rooms — and standard BLE links a device to a single phone or bridge at a time, though Bluetooth Mesh exists for lighting-scale use. On its own it rarely gives reliable whole-home automation, because something has to bridge it to the internet when your phone leaves the house.
Zigbee
Zigbee is a long-established low-power standard built around a mesh network. Battery devices sleep most of the time and act as leaves, while every mains-powered device (a smart plug, a wired bulb) doubles as a repeater, passing messages along for its neighbours — so the more permanently powered kit you add, the sturdier the network becomes. Zigbee needs a coordinator — a hub or gateway — to run the show, and it uses its own application layer rather than internet protocol (IP). It shares the 2.4 GHz band with Wi-Fi, which occasionally causes interference. Its weak spot has historically been interoperability: two Zigbee devices usually connect, but advanced features from one brand may not show up in another brand’s hub.
Z-Wave
Z-Wave is Zigbee’s closest rival in spirit — also a low-power mesh, also hub-dependent — but it makes different trade-offs. Crucially it uses a sub-gigahertz radio band (around 800–900 MHz, varying by region) rather than 2.4 GHz. Lower frequencies pass through walls and floors more easily and dodge Wi-Fi congestion entirely, which tends to make Z-Wave feel dependable, at the cost of lower data rates. Historically it was a proprietary technology controlled by a single chip supplier; the specification has since been opened up. Its strongest selling point is discipline: certification has long required that any certified device interoperate with any certified controller, so cross-brand mixing is more predictable than with Zigbee. A single network holds a couple of hundred devices — ample for a home.
Thread
Thread uses the same underlying 2.4 GHz radio technology as Zigbee, but with a very different design goal: every device speaks IP directly (specifically IPv6). That means a Thread sensor is, in networking terms, a first-class citizen of your network rather than something trapped behind a translator. Thread forms a self-healing mesh with no single controller to fail — if one node drops out, traffic reroutes. It still needs a border router to reach the wider internet, but that role is increasingly built into devices you already own, such as smart speakers, so it rarely feels like a separate purchase. Thread was designed from the start to carry Matter, which is why the two names are so often said together — a pairing covered in detail in Matter and Thread, explained.
Wired KNX
KNX is the odd one out: it is primarily a wired bus standard, common in European new-builds and higher-end fit-outs, where lighting, blinds, heating and more are cabled onto a shared two-wire bus during construction. There is no central brain that everything depends on — devices are configured to talk to each other directly, so the system keeps working even if a visualisation server is switched off. Because it is wired, KNX sidesteps radio interference, battery worries and range limits altogether, and is known for lasting decades. The trade-offs are obvious: it needs cabling planned in advance and professional configuration software — a poor fit for renters or quick retrofits.
Where Matter fits (and why it isn’t a radio)
Here is the point that trips up almost everyone. Matter is not a competitor to Thread, Wi-Fi or Zigbee. It is an application layer — a shared language for describing what a device is (a dimmable light, a lock, a thermostat) and how to command it — that runs on top of existing transports. Today a Matter device reaches the network over Wi-Fi, Thread or Ethernet, and typically uses Bluetooth LE only for the brief setup handshake.
So a “Matter over Thread” bulb and a “Matter over Wi-Fi” plug are both Matter, and can appear side by side in the same app even though their radios differ. Matter’s promise is interoperability at the language level: a device carrying the Matter badge should be controllable by any Matter platform, whoever made it. It does nothing to change the physics of range or battery life — those still come from whichever radio sits underneath.
The comparison at a glance
In short: Zigbee, Z-Wave and Thread are low-power mesh radios; Wi-Fi and Bluetooth are the ones already in your phone and router; KNX is the wired option for new builds. Matter is a shared language that runs on top of Wi-Fi and Thread, not a radio of its own — so "Matter vs Thread" is a false contest.
| Standard | Topology | Radio band | Typical power draw | Practical range | Hub / gateway needed? | Cross-brand interoperability |
|---|---|---|---|---|---|---|
| Wi-Fi | Star (all via router) | 2.4 / 5 GHz | High — best for mains devices | Whole home, one router | No dedicated hub; often a vendor cloud/app | IP-level yes; app-level fragmented |
| Bluetooth LE | Point-to-point / star (mesh optional) | 2.4 GHz | Very low | One or two rooms | Phone for setup; a bridge for remote access | Standard profiles, but smart-home use varies |
| Zigbee | Mesh | 2.4 GHz | Low | Short per hop; extended by mesh | Yes — a coordinator/hub | Usually connects; advanced features can be patchy |
| Z-Wave | Mesh | Sub-GHz (~800–900 MHz, region-specific) | Low | Good per hop; extended by mesh | Yes — a controller/hub | Strong, via mandatory certification |
| Thread | Self-healing mesh | 2.4 GHz | Low | Short per hop; extended by mesh | A border router (often built into other kit) | Designed for it; underpins Matter |
| KNX (wired) | Bus | Wired (no radio) | Bus / mains powered | Limited by cable length | No central controller required | Strong within KNX certification |
How to choose
You rarely pick just one, and you needn’t. The sensible approach is to match the radio to the job rather than chase a single “winner”.
- Start with what you already have. If you own a recent smart speaker or hub, check whether it is a Thread border router and a Matter controller. If it is, Matter-over-Thread devices give you low-power, hub-light kit with the best current shot at cross-brand tidiness.
- Use Wi-Fi for the power-hungry things. Cameras, streaming devices and always-on plugs are fine on Wi-Fi; just watch your router’s device count and prefer kit that also offers local control.
- Reach for a mesh radio for battery sensors. Door contacts, motion sensors and remote buttons last far longer on Zigbee, Z-Wave or Thread than on Wi-Fi. If a thick-walled or multi-storey home is giving you range trouble on 2.4 GHz, Z-Wave’s sub-gigahertz band is often the fix.
- Value guaranteed compatibility? Z-Wave’s strict certification makes mixing brands the most predictable of the mesh options. Prefer the newest, IP-native path? Thread and Matter are where the industry is heading.
- Building or renovating? If the walls are open, wired KNX buys reliability that no radio can match — at the price of planning and professional setup.
A practical way to start
No single protocol wins on every measure, and the sensible smart home usually speaks two or three. Pick a hub that bridges several radios, lean on Matter and Thread for new low-power devices, keep mains-powered workhorses on Wi-Fi, and reserve wired options for the fabric of a building rather than its gadgets. Above all, favour devices that keep working when the internet drops — local control is the quiet feature that separates a home you can rely on from a collection of apps. As the ecosystem settles around a shared language, the radio underneath should matter less over time, which is rather the point.