Thread

showstack / protocols / thread

A low-power IPv6 mesh network on 802.15.4 radio. Every device gets a real IP address and routes to its neighbours, so there is no translating hub in the middle and the mesh heals around a node that dies. The transport Matter was designed for.

Network transportOpen, free sign-upThread GroupReported

Control Small, urgent, must arrive

Small messages that either repeat constantly or fire once. Bandwidth is almost never the problem.

What kills it. Latency and loss on the messages that fire once. A repeating level survives a dropped packet; a GO does not.

Why this one, and not what the category suggests. A low-power mesh, and in a venue what crosses it is device control.

The four flows, and why the model is worth having →

Multicast

IPv6 multicast across the mesh.

What goes wrong

Mesh is resilient and not quick — every hop adds latency and jitter. Fine for a sensor, wrong for a cue.

It needs a border router to reach the rest of the network, and that border router is the thing that fails.

Shares the 2.4 GHz band with Wi-Fi and everything else. See the RF map before assuming it is quiet.

What speaks Thread (1)

Product	Direction	Notes
Home Assistant Open Home Foundation	bidirectional	Via a border router.

Typical use

Battery sensors and controls across an installation, with no mains at the device.
Anything that must survive a single node failing.

Sources

Thread — Thread Group primary

Understand the mechanism

Robots, animatronics and connected things

Something wrong, or missing?

Known gaps on this entry: default_ports, implementations. If you can source one of them, that is a ten minute pull request.

Edit this entry on GitHub — one file, editable in your browser, and your handle goes on it permanently.

Work at Thread Group? Confirm or correct this entry — it is free, it stays free, and nothing about it is for sale.