What Thread is, and why it exists

The one-sentence model#

Thread turns a room full of coin-cell devices into a self-healing IP network without a coordinator that can take the whole thing down.

Everything else follows from that sentence. IP means your controller can address a sensor directly instead of asking a vendor bridge to translate. Self-healing means the routing table rebuilds when a relay is unplugged. No coordinator means there is no single node whose failure ends the network, which is the structural difference from Zigbee, where one coordinator owns the Trust Center role.

The cost of that design is that Thread is only half a solution. It moves packets. It does not know what a packet means. That is why you almost never buy "a Thread device": you buy a Matter device that happens to use Thread as its transport. What Matter is covers the other half.

The radio, in numbers#

Thread's physical layer is IEEE 802.15.4 in the 2.4 GHz band.

Two consequences people get wrong. Thread is not long range: it is short range with relays, which is a different thing. And low power does not mean low interference sensitivity, because a 250 kbit/s narrowband signal sharing spectrum with a 20 MHz Wi-Fi channel is the weaker party. See 2.4 GHz interference and channel planning and the channel planner.

Roles: who relays, who sleeps#

This is the part that decides whether your mesh works, and it is invisible in every consumer app.

One Leader exists per partition. It is elected, and if it disappears another router takes the role. There is no configuration step and no user-visible "main" device, which is exactly the point.

A sleepy end device is the reason a Thread contact sensor runs for years on a CR2032. Its radio is off almost all the time. It wakes on a schedule, polls its parent router for anything queued, sends anything it has, and goes back to sleep. All of its traffic passes through that one parent. It never relays for anyone else, because it cannot: it is not listening.

Thread 1.4 renamed the Router role to Mesh Extender in specification language. Older documentation, most controller apps and every diagnostic screen still say Router. They mean the same node.

What "IPv6 to the device" actually buys you#

Each Thread device holds several IPv6 addresses, including a routing locator derived from its position in the topology: a router ID plus a child ID, packed into the last 16 bits of the address. When a device moves to a different parent, that address changes, because it describes where the device sits, not who it is. Devices also hold a stable mesh-local address that does not change with topology.

The practical payoffs:

• No protocol translation. Your controller talks to the device. Compare a Matter bridge, where a vendor hub converts between two models and drops whatever does not map cleanly.
• Multiple controllers, same device. Because addressing is IP, several controllers can hold their own credentials for one device. That is what makes Matter multi-admin possible.
• Routing repairs itself. Route cost is computed from link quality, not hop count. The maximum route cost is 124, which corresponds to 31 hops at the worst usable link cost of 4. You will never approach that in a house, which tells you something useful: hop count is not your constraint, link quality is.

What a border router does, and does not do#

A border router is a mains-powered device with both an 802.15.4 radio and a LAN connection. It provides bidirectional IPv6 routing between the Thread mesh and your Ethernet or Wi-Fi network, advertises an on-mesh prefix, and runs service discovery in both directions: SRP on the Thread side, where devices register their services, and mDNS/DNS-SD on the LAN side, so controllers can find them. Thread 1.4 adds NAT64 and DNS64 plus DHCPv6 prefix delegation, and TREL (Thread over Infrastructure), which encapsulates 802.15.4 frames in UDP/IPv6 so two parts of one mesh can talk across your Wi-Fi or Ethernet instead of splitting.

What it does not do: a border router is not a Matter controller. It does not add devices to your fabric, does not run your automations, and does not own your devices. Buying a HomePod mini gives Apple Home a border router. It does not give Google Home one. The distinction is spelled out in hubs, bridges, controllers and border routers, and the full US hardware directory is in Thread border routers.

Where Thread breaks, and what that reveals#

Reliability problems cluster into three buckets, and each one exposes a design decision.

1. Discovery, not radio. By a wide margin the most common Thread failure is that the mesh is fine and your LAN will not carry the announcement. mDNS is a multicast protocol, and home networks are full of things that quietly kill multicast: aggressive IGMP snooping, client isolation on a guest or IoT SSID, mDNS repeaters that half-work, and VLAN boundaries with no reflector configured. The symptom looks like a dead device. The cause is a router setting. Thread troubleshooting starts there for exactly this reason, and the network setup a smart home wants covers the fix.

2. Fragmentation. Each ecosystem forms its own Thread network with its own credentials unless you deliberately share them. Thread 1.4 made credential sharing mandatory for certified border routers, but it is user triggered and single use, not automatic. Two networks in one house halve your relay count and mean a device can only be reached through the one it joined. See why you have three Thread networks.

3. Spectrum. When OpenThread logs ChannelAccessFailure, the radio tried to transmit and never found the channel clear. That is congestion: a Wi-Fi network sitting on the same frequencies, a microwave, a video baby monitor, or USB 3.0 noise from the port your radio dongle is plugged into. Home Assistant's documentation recommends channel 26 in heavy Wi-Fi interference, because it sits furthest from US Wi-Fi channels 1, 6 and 11.

Thread versions, briefly#

Thread 1.4 also included TCAT, commissioning over an authenticated TLS session carried by Bluetooth LE. It is optional and aimed at commercial deployments. It is widely reported that new border router certifications moved to 1.4 only at the start of 2026; treat the exact terms as unconfirmed, and note that certification rules govern new products, not the firmware in your house.

When Thread is the right answer#

Choose Thread when the device is battery powered, needs low latency, and lives in a home with a border router and a couple of mains-powered Thread devices to relay: sensors, buttons, locks, shades. Choose Wi-Fi when the device is mains powered and needs bandwidth. Choose Z-Wave to reach a large house or a detached structure, because 908.42 MHz in the US penetrates far better than 2.4 GHz and Z-Wave Long Range gives a star topology at up to 4,000 nodes. Which radio for which job makes this a table.