What Thread Is
Thread is a low-power mesh networking protocol designed specifically for smart home devices. It runs on the IEEE 802.15.4 radio standard at 2.4 GHz — the same physical radio layer as Zigbee — but uses IPv6 for addressing and routing rather than Zigbee's proprietary network layer. This means Thread devices are directly addressable on an IP network, which is a significant architectural difference from Zigbee or Z-Wave, where a hub must translate between the proprietary protocol and IP.
Thread was developed by a consortium including Apple, Google, Amazon, ARM, and others, and became the preferred radio transport for Matter devices in the low-power device category. A Thread network requires at least one border router — a device that connects the Thread mesh to the Wi-Fi/Ethernet IP network.
Thread vs Zigbee vs Wi-Fi
| Property | Thread | Zigbee | Wi-Fi |
|---|---|---|---|
| Radio | IEEE 802.15.4 (2.4 GHz) | IEEE 802.15.4 (2.4 GHz) | 802.11 b/g/n/ac/ax (2.4 / 5 / 6 GHz) |
| Network layer | IPv6 (6LoWPAN) | Proprietary Zigbee network layer | IPv4/IPv6 |
| Mesh topology | Yes — routers and end devices | Yes — coordinators, routers, end devices | No (star topology, device → router) |
| Hub required | Border router required (not a hub per se) | Zigbee coordinator/hub required | No hub (connects directly to Wi-Fi router) |
| Battery life | Excellent — similar to Zigbee | Excellent | Poor |
| IP addressability | Yes — each device has an IPv6 address | No — IP translation happens at hub | Yes — each device has an IP address |
| Matter compatibility | Native (Matter over Thread) | Not directly (Zigbee ≠ Thread) | Yes (Matter over Wi-Fi) |
Thread Border Routers
A Thread border router connects the Thread mesh to your IP network, allowing Thread devices to be reached from the internet or your local network and enabling cloud services to communicate with them. Border routers are built into several mainstream devices:
- Apple HomePod mini and HomePod (2nd gen): Thread border routers built in; managed through the Apple Home app.
- Apple TV 4K (3rd gen): Thread border router.
- Google Nest Hub (2nd gen) and Nest Hub Max: Thread border routers.
- Google Nest WiFi Pro: Thread border router built into each node.
- Amazon Echo (4th gen) and Echo Show 10: Thread border routers.
- Home Assistant Yellow and SkyConnect USB dongle: Thread border router for Home Assistant users.
Multiple border routers in the same home form a more resilient Thread network — if one border router is powered off, others take over. The Thread devices themselves automatically form and heal the mesh.
Frequently Asked Questions
Do I need to do anything special to set up Thread devices?
In most cases, no — Thread setup is handled transparently by the Matter commissioning process. When you add a Matter-over-Thread device through the Apple Home app, Google Home app, or Amazon Alexa app, the app automatically connects the device to the Thread network managed by the border router in your ecosystem. You do not need to configure Thread manually. The complexity is hidden by the platform. The requirement is simply that you have at least one compatible border router device (HomePod mini, Nest Hub 2nd gen, Echo 4th gen, etc.) already set up in your home.
Is Thread the same as Zigbee?
No — they share the same physical radio (IEEE 802.15.4 at 2.4 GHz) but are incompatible at the network layer. A Zigbee device cannot join a Thread network and vice versa. Thread uses IPv6 routing; Zigbee uses its own proprietary network stack. This means your existing Zigbee devices do not benefit from Thread infrastructure, and you cannot use a Thread border router as a Zigbee coordinator. They coexist in the same home but on separate, independent networks.
What happens to Thread devices if my internet goes down?
Thread devices continue to function locally — the mesh network and local control operate independently of internet connectivity. The border router bridges Thread to the local IP network, not specifically to the internet. Automations that run on a local hub (Home Assistant, HomePod for HomeKit automations) continue executing. Cloud-dependent features (remote access from outside the home, voice commands through Alexa or Google Assistant which require cloud processing) will not work during an internet outage, but local control through a local hub or the platform's local processing continues.