Thread, explained
The mesh radio that carries most battery-powered Matter devices, and the handful of design facts that decide whether it stays reliable.
Who actually needs to care about Thread#
You need to understand Thread if any of these are true.
- You own or want battery Matter devices. Matter sensors, locks and buttons are overwhelmingly Thread devices. A Matter smart plug may be Wi-Fi; a Matter contact sensor almost never is.
- You own more than one ecosystem. Apple, Google, Amazon and SmartThings each build their own Thread network by default. That is the single most common cause of a Thread device that pairs fine and then behaves badly. See why you have three Thread networks.
- Something is dropping. Thread devices that go unresponsive in one app but work in another are usually a discovery problem, not a radio problem. Start with Thread troubleshooting, in order.
- You are choosing hardware. Which speaker, streamer or router you buy decides whether you have a border router at all, and how many. Some obvious-looking boxes are not border routers, including the Hubitat C-8.
If none of those apply, you do not need Thread. A house built on Zigbee or Z-Wave is a perfectly good house, and which radio for which job walks through the trade honestly.
Start here#
Read in this order if Thread is new to you.
- What Thread is and why it exists. The mental model: IPv6 to the device, roles, sleepy end devices, and what Thread deliberately does not do.
- Thread border routers. What the box on your shelf actually provides, plus the full directory of shipping US hardware.
- Why you have three Thread networks. Credential sharing in Thread 1.4 is user triggered, not automatic. This page has the per-ecosystem steps.
- Designing a Thread mesh that holds up. The 32 router limit, parent and child relationships, and where to put mains-powered devices.
- Thread troubleshooting, in order. Discovery first, radio second, because that matches the real distribution of causes.
Comparisons are worth reading once you have the model: Thread vs Zigbee explains why the same radio produces very different networks, and Thread vs Wi-Fi covers battery life, latency and the cases where Wi-Fi is genuinely the better choice.
Everything in this cluster#
- What Thread is, and why it existsThe mental model: IPv6 to every device, mains-powered relays, sleepy children, and no application layer of its own.
- Thread border routers: the complete guideThe full US hardware directory, plus the difference between a border router and a controller that nobody explains at the shelf.
- Why you have three Thread networksCredential sharing explained: the nine-digit passcode, what actually gets copied, and which ecosystems will hand it over.
- Designing a Thread mesh that holds upRouters versus sleepy end devices, the 32 router ceiling, placement rules, and how many devices one network really holds.
- Thread troubleshooting, in orderAn ordered decision tree: discovery on the LAN, then network splits, then topology, then spectrum. With the reason each step comes where it does.
- Thread vs Zigbee: same radio, different stackSame PHY, different network layer. A table of consequences for coordinators, device choice, price and failure modes.
- Thread vs Wi-Fi for smart home devicesThe decision rule by device class, with the airtime and battery mechanics that explain it.
The five facts that explain most Thread problems#
| Fact | Consequence |
|---|---|
| A Thread network allows 32 active routers | Mesh size is capped by relays, not by device count. Adding more mains-powered devices past that point does not extend range. |
| Maximum route cost is 124, which is 31 hops at a link cost of 4 | Hop count is not the practical limit. Link quality is. A weak link costs as much as several good ones. |
| Sleepy end devices keep the radio off between polls | They cannot relay. A house full of battery sensors has no mesh, only spokes. |
| Border routers publish Thread devices to your LAN over mDNS and SRP | If mDNS is filtered, blocked by client isolation, or split across a VLAN, controllers cannot find devices that are perfectly healthy on the mesh. |
| Thread credentials do not sync between ecosystems on their own | Each controller creates its own network unless you deliberately share credentials. |
Every article in this cluster is built around one of those five.
Tools#
- Border router finder. Filter every shipping US border router by ecosystem and Thread version, including the ones that are commonly mistaken for border routers and are not.
- 2.4 GHz channel planner. Enter your Wi-Fi channels, get Thread and Zigbee channels that clear them, with the frequency arithmetic shown.
- Compatibility checker. Device class plus platform plus connection, and what gets lost in between.
Is Thread the same as Matter?
No. Thread is a network layer, Matter is an application layer. Thread moves IPv6 packets between low-power devices; Matter defines what those packets mean, so a lock and a controller from different brands agree on "locked". Matter also runs over Wi-Fi and Ethernet. A Thread device that is not a Matter device exists, and Matter devices that never touch Thread are common. Matter vs Thread has the full breakdown.
Do I need a hub for Thread?
You need a Thread border router, which is not the same thing as a hub, though one box often does both. The border router routes IPv6 between the mesh and your LAN and advertises Thread devices over mDNS. A controller (Apple Home, Google Home, Alexa, SmartThings, Home Assistant) is what actually adds devices to your fabric. See hubs, bridges, controllers and border routers.
How many Thread devices can one network handle?
The protocol allows 32 active routers, and each parent can in theory address 511 children, though real firmware allows far fewer, typically tens. Practical guidance in the field lands around 250 devices per network. In most homes you run out of routers or out of good radio links long before you run out of addresses. Mesh design covers the arithmetic.
Does Thread work when the internet is down?
Yes, at the network layer. Thread is entirely local, and a border router keeps routing between the mesh and your LAN with no upstream connection. Whether your automations still fire depends on the controller, not on Thread. See what still works when the internet goes down.
Is Thread better than Zigbee?
For new battery devices in a Matter home, usually yes, because Thread gives every device an IP address and does not depend on a single coordinator. Zigbee has a far larger device catalog and cheaper hardware. They use the same radio, so if you run both, put them on different channels. Thread vs Zigbee compares them line by line.
Which Thread channel should I use?
Whatever your border router picked, unless you are seeing congestion. If you are, channel 26 sits furthest from US Wi-Fi channels 1, 6 and 11, and Home Assistant recommends it in heavy Wi-Fi interference. Two caveats: many radios reduce transmit power on channel 26 in North America, and it collides with Bluetooth advertising channel 39 at 2480 MHz. Channel planning has the math.
Primary sources
Specification and vendor documentation we checked while writing this page. Where a claim depends on firmware behaviour rather than a published spec, the page says so inline.