Thread
Thread is a low-power wireless mesh protocol built on IEEE 802.15.4 radio (2.4 GHz, the same silicon as Zigbee) that speaks native IPv6. It is the network most battery-powered Matter devices use: sensors, buttons, and locks join a self-healing mesh and reach your home network through a Thread border router.
Thread solves the problem Wi-Fi cannot: multi-year battery life. An 802.15.4 radio draws a fraction of a Wi-Fi radio’s power, and the mesh topology means mains-powered Thread devices (plugs, bulbs) route traffic for battery ones, so coverage improves with every powered device you add. Unlike Zigbee, Thread carries IPv6 packets natively — a Thread device is addressable from your LAN like any other IP device, with no protocol translation, just routing.
Thread has no application layer of its own; it is purely transport. Matter provides the application layer on top, which is why the pairing badge usually reads “Matter over Thread.” Since Thread 1.3, border routers support standardized credential sharing, so border routers from different vendors (an Apple TV and a Nest Hub, say) can join the same Thread network instead of building parallel meshes — see the Thread border router entry for what that hardware does.
| Radio | IEEE 802.15.4 at 2.4 GHz, 250 kbit/s, channels 11–26 — identical hardware to Zigbee |
|---|---|
| Network layer | Native IPv6 over 6LoWPAN, UDP with DTLS — no protocol translation at the border |
| Active routers per network | Up to 32; each parents hundreds of sleepy end devices |
| Governance | Thread Group, formed in 2014; specification 1.3 (2023) is the Matter baseline |
| Typical hop range | 10–30 m indoors, extended by every mains-powered Thread device you add |
| Battery life | Years on a coin cell for a sleepy end device — the reason Thread exists |
Same silicon as Zigbee, completely different network
Thread and Zigbee use the same radio: IEEE 802.15.4 at 2.4 GHz, 250 kbit/s, the same sixteen channels numbered 11 to 26. A chip that can do one can usually do the other, which is why so many hubs advertise both — though most single-radio designs run one protocol at a time, or split duty in firmware with a measurable cost to both.
Everything above the radio diverges. Zigbee invented its own network and application layers; Thread carries IPv6 packets compressed with 6LoWPAN, and stops there. A Thread device has a real IPv6 address, reachable from your LAN through the border router with routing rather than translation. That is the architectural difference people mean when they say Thread is “IP-native”, and it is why a Thread border router is a simpler, less opinionated piece of infrastructure than a Zigbee coordinator.
Because the band is shared, so is the interference. Thread, Zigbee, Wi-Fi, Bluetooth, and microwave ovens all sit in the same 2.4 GHz space, and a Thread mesh on a channel overlapping a busy Wi-Fi channel will drop packets exactly the way Zigbee does. Thread channel selection is automatic and largely hidden from you, which makes this harder to diagnose than on Zigbee, where every coordinator exposes the channel.
Leaders, routers, and sleepy end devices
A Thread network assigns roles dynamically. Mains-powered devices become routers, forwarding traffic for their neighbours. One router is elected leader and hands out router IDs and network data; if it disappears, another takes over within seconds, and no device is lost. This is the main structural advantage over Zigbee, where the single coordinator holds the network and its failure is an event.
Battery devices join as end devices. A sleepy end device keeps its radio off almost all the time and polls its parent router for anything addressed to it, which is what turns a coin cell into years of service instead of weeks. Sleepy devices route nothing, so a lone battery sensor at the edge of coverage has the same problem it would on Zigbee: it needs a mains-powered device between it and the rest of the mesh.
A network supports up to 32 active routers at once, with router-eligible end devices promoted and demoted automatically as the topology changes. In a house this ceiling is theoretical — it is coverage, not capacity, that limits real deployments. The practical advice is the same as for Zigbee: a Thread-capable smart plug or bulb in a dead spot fixes far more problems than moving the hub.
What Thread is honestly good and bad at
Good at: multi-year battery life on small sensors, buttons, and locks; fast local response, because there is no cloud and no translation step; and graceful degradation, since the mesh has no single point of failure and healing is automatic. Thread also predates Matter in shipping products — Apple ran HomeKit over Thread from 2020, on devices like Eve Energy and Nanoleaf Essentials, before Matter existed.
Bad at: being diagnosable. Almost no consumer ecosystem shows you a Thread topology, a channel, or a per-device link quality, so when a sensor goes unresponsive there is very little to look at. Bad, too, at network hygiene across vendors — before Thread 1.3 credential sharing, an Apple TV and a Nest Hub would each build their own Thread network in the same house, halving the routers available to each. That is fixed on paper and mostly fixed in practice as of mid-2026, but implementations still lag.
And Thread carries nothing on its own. Without Matter (or, historically, HomeKit) there is no application layer, so “Thread support” in a spec sheet is meaningless by itself. When comparing a Thread sensor against a Zigbee one, the real question is not radio quality — the radios are the same — but which catalogue and which platform you want to live in.
Frequently asked questions
Is Thread the same as Zigbee?
They share a radio standard, IEEE 802.15.4 at 2.4 GHz, and nothing above it. Zigbee uses its own networking and application layers and needs a coordinator; Thread carries IPv6 and needs a border router, with Matter supplying the application layer on top. They cannot talk to each other, and a Zigbee device will never join a Thread network no matter what firmware you flash.
Do Thread devices need Wi-Fi?
The devices themselves do not — they use an 802.15.4 radio, not Wi-Fi. But the mesh reaches your phone and your controller through a Thread border router, and that border router sits on your Wi-Fi or Ethernet network. So Thread devices need a working home network to be useful, even though they never join it directly.
How many devices can a Thread network handle?
Up to 32 devices act as routers at any moment, with hundreds of sleepy battery devices parented beneath them. Home networks run out of radio coverage long before they run out of slots. If devices at the edge of the house are dropping out, the fix is another mains-powered Thread device in between, not a bigger network.
Why will my Thread device not pair?
Most failures are border-router problems, not device problems. Check that a border router is actually present and online, that its ecosystem is the one you are pairing in, that your router has IPv6 enabled, and that the phone doing the setup is on the same LAN with multicast allowed. Guest networks, client isolation, and VLAN separation between the phone and the border router are the usual culprits.
Should I buy Thread sensors or Zigbee sensors?
Thread if you want devices to work directly in Apple Home, Google Home, or Alexa with no extra hub beyond a border router you probably already own. Zigbee if you want the widest, cheapest catalogue — 5,405 supported devices in this dataset against a much smaller Thread selection — and you are willing to run a coordinator. Battery life and radio range are broadly comparable, because it is the same radio.