Thread is a low-power, IPv6-based mesh networking protocol for connected devices, governed by the Thread Group. It provides the self-healing wireless mesh that Matter runs over, giving every device a routable IPv6 address rather than requiring a proprietary hub translation layer.
Thread
Thread is the network layer under much of the modern connected home. Built on IEEE 802.15.4 radios and IPv6, it forms a self-healing mesh in which routers extend range and the failure of any one node does not partition the network.
- IPv6 to the device - Every node is individually addressable, which removes the proprietary hub translation that Zigbee deployments needed.
- Mesh and self-healing - Mains-powered devices route; battery devices sleep as end nodes.
- No application semantics - Thread moves packets. What those packets mean is Matter’s job.
- Border routers - A border router bridges the Thread mesh to the home IP network, and is where an API surface, if any, appears.
Thread is worth cataloguing alongside Matter because together they are the one place in the hardware market where a genuine, open, layered interoperability stack exists. The State of Compute & Hardware APIs found it at four providers in a devices layer averaging 11.9 — the silicon vendors selling the radios rather than the device makers using them. The stack is sound; the adoption is at the component tier, and the products built on it mostly do not publish anything a machine outside the home can call.
Referenced in API Evangelist papers
This standard shows up in my published research. These reports read the machine-readable evidence provider by provider — and put this standard in the context of a real sector.
The State of Compute & Hardware APIs
Present at four providers in the devices layer — Silicon Labs, Atmosic, BouffaloLab, Axiado — the networking foundation under Matter, in a layer averaging 11.9.
