Thread is a low-power wireless mesh network protocol that gives battery-powered devices a native IPv6 address. A Thread door sensor is reachable with an ordinary IP packet from a phone on the same Wi-Fi network, through a border router, without any protocol translation. That single property is what distinguishes it from Zigbee and Z-Wave, which use their own network layers and need a hub to speak to the IP world on their behalf.
Thread was developed by the Thread Group, founded in 2014, and became prominent when Matter adopted it as its low-power transport. Border routers are now built into many smart speakers, displays, hubs and some Wi-Fi access points, which means a Thread network often exists in a home before the first Thread device is installed. This guide explains the stack, the mesh roles, how devices are commissioned and secured, and the decision between Thread and Zigbee.
The stack: 802.15.4 plus IP
The bottom of Thread is IEEE 802.15.4 at 2.4 GHz, the same radio Zigbee uses, with the same 250 kbit/s raw rate and the same small frames. Above it, Thread runs 6LoWPAN, an IETF adaptation layer that compresses IPv6 headers and fragments packets so that they fit in 127-byte radio frames. On top of that sits standard IPv6 and UDP. Thread deliberately defines nothing above the transport layer; applications bring their own protocol, most commonly CoAP or Matter.
Building on open IETF standards means a Thread device uses the same addressing and security primitives as any other IP device. The reference implementation, OpenThread, is open source and used in most commercial stacks.
Mesh roles
Devices in a Thread network take one of several roles, and the roles change dynamically.
Routers are mains-powered devices that forward traffic and let new devices attach. A network supports up to 32 active routers, which is enough for a large home or a floor of a building.
Router-eligible end devices can become routers if the network needs more, and step down if it has too many. The network tunes its own router count.
End devices attach to a parent router and do not forward traffic. Sleepy end devices are the battery-powered variant: they sleep, wake on their own schedule, and poll their parent for queued messages. A newer synchronized sleepy mode allows parent and child to agree on wake times for lower latency at very low power.
One router is elected leader and manages router address assignment and network configuration. If the leader fails, another router takes over automatically. There is no coordinator in the Zigbee sense; no single device is essential to the network’s operation.
Routing uses a distance-vector protocol with link quality measured in both directions, and the mesh repairs itself when devices disappear. If a network splits because a link fails, the two partitions each elect a leader and continue, and they merge again when connectivity returns.
Border routers
A border router is a device with both a Thread radio and another IP interface, usually Wi-Fi or Ethernet. It forwards packets between the Thread mesh and the home network, advertises the Thread network’s prefix so that other devices can route to it, and provides services such as address translation to reach IPv4-only destinations and service discovery so that phones can find Thread devices by name.
Any number of border routers can serve one Thread network, and if one is unplugged the others carry on. Since Thread 1.3 the border router behavior is standardized so that border routers from different vendors can share a single network. Credential sharing between vendors has been a practical friction point in multi-vendor homes, and it is improving as platforms adopt the standard mechanisms.
Commissioning and security
A Thread network is identified by a set of credentials: a network name, an extended PAN ID, a channel and a network key. Devices that hold the credentials can join directly. Devices that do not are commissioned: a commissioner, typically a phone app, authenticates the new device using a code printed on it or in a QR code, establishes a DTLS session through a router acting as a joiner relay, and delivers the credentials over that encrypted channel. The network key is never sent in the clear.
All traffic on the mesh is encrypted and authenticated at the 802.15.4 layer with AES, using keys derived from the network key and rotated on a schedule. Because Thread is IP, applications add their own end-to-end security on top, which in Matter’s case is a separate session layer between controller and device. A Thread network can therefore have layered protection: link-layer encryption against outsiders and application-layer encryption so that even a device on the same mesh cannot read another’s traffic.
Thread and Matter
Thread is one of three transports that Matter runs over, alongside Wi-Fi and Ethernet. Matter needs an IP network and Thread provides one for devices that cannot afford Wi-Fi. This pairing has driven most Thread adoption: a Matter-over-Thread sensor or lock joins through a border router and is then controlled by any Matter controller in the home, from any ecosystem.
Thread can be used without Matter; commercial and building systems run it with CoAP or their own application protocols. The Matter guide covers the application side.
Thread versus Zigbee
The two share the radio and the broad mesh idea, so the differences are in the choices above them.
Thread’s advantage is IP. End-to-end addressing from any device on the home network, multiple redundant border routers, standard tooling, and no translation layer between the mesh and the cloud. The leader election and partition handling remove the single point of failure that a Zigbee coordinator represents.
Zigbee’s advantage is maturity. It has a complete application layer in the Zigbee Cluster Library, a much larger installed base, well-understood commissioning, and native group addressing that lighting systems rely on. Thread has no application layer of its own, so a Thread product without Matter or another standard on top is just a network with nothing to say.
Range, power and interference behavior are comparable because the radio is the same.
For a new consumer product aimed at the major smart home ecosystems, Thread with Matter is the direction the platforms are investing in. For a lighting system with established tooling, a utility deployment, or anything needing Zigbee’s specific features, Zigbee remains a reasonable choice. The Zigbee guide gives the other perspective.
When Thread fits
Choose Thread when you are building battery-powered or low-power devices that need to be IP-reachable, especially for the smart home under Matter, and when you can rely on border routers being present. Prefer it where multiple vendors’ hubs must coexist on one network. Avoid it where bandwidth needs exceed what 802.15.4 can carry, where devices are outdoors or spread over distances beyond a mesh’s reach, or where no border router infrastructure will exist.
Where to go next
- Matter explained covers the application layer most Thread devices use.
- Zigbee explained describes the closest alternative in depth.
- CoAP explained covers the protocol Thread uses for its own management and that many Thread applications use.
- IoT connectivity overview compares Thread with the other radio options.
Topics: Thread, mesh, IPv6, smart home, protocols