Thread

Thread is the IPv6-native mesh networking protocol that underpins most new Matter-certified smart home and building automation designs, sharing its IEEE 802.15.4 radio layer with Zigbee but routing traffic as native IP rather than through a proprietary application-layer gateway. This subtopic covers Thread from protocol fundamentals through practical deployment: standing up a self-hosted OpenThread Border Router, choosing between Thread and Zigbee for a new product, and configuring battery-powered end devices.

What Is Thread?

Thread is a low-power IPv6 mesh protocol built on IEEE 802.15.4, using 6LoWPAN header compression so every device gets a genuine, routable IP address without an application-layer translation gateway. Roles are assigned dynamically (Leader, Router, REED, MED, and Sleepy End Device), and at least one Thread Border Router is required to bridge the mesh to the wider IP network. For the full protocol explanation, device roles, and how Thread compares to Zigbee and Matter, see What Is Thread?

This subtopic is part of the Wireless topic.

Why Thread Matters

• Thread alone is not a working product. It's a transport layer with no application layer of its own — a Thread-only device still needs Matter (or a proprietary layer built on top) to define its actual behaviour to a controller. Budgeting for Thread without budgeting for Matter certification is the single most common architectural misunderstanding in this space.
• Native IP routing removes a whole class of gateway complexity that Zigbee products carry — every Thread device is directly addressable over IPv6, which simplifies cloud connectivity and local network integration considerably compared to bridging a proprietary mesh protocol.
• The Border Router is infrastructure your product usually doesn't need to build. Most consumer deployments already have one (a smart speaker or hub from another vendor) — designing a custom Border Router into a product adds cost and certification scope that's often unnecessary.
• Sleepy End Device tuning is a genuine battery-life engineering decision, not a default to leave alone — poll period, child timeout margin, and system-level sleep configuration together determine whether a battery-powered Thread device lasts months or years in the field.

Key Concepts

• Leader / Router / REED / MED / SED — the five Thread network roles, assigned dynamically rather than fixed at manufacture; exactly one Leader is elected per network partition, with automatic re-election if it goes offline. See What Is Thread?
• 6LoWPAN — the IPv6-header-compression scheme that lets Thread route standard IPv6 traffic efficiently over small IEEE 802.15.4 frames, the defining architectural difference from Zigbee's proprietary mesh routing.
• Thread Border Router — the gateway device bridging the Thread mesh to the wider IPv6 network, hosting commissioning services and mDNS/SRP service discovery. See How Do You Set Up an OpenThread Border Router?
• OpenThread — Google's open-source, BSD-3-licensed reference implementation of the Thread stack, ported by silicon vendors (Nordic, Silicon Labs, TI, NXP) rather than each vendor writing an independent stack from scratch.
• Sleepy End Device (SED) poll period — how often a battery-powered end device wakes its radio to check for buffered data with its parent Router, the primary battery-life-vs-responsiveness tuning knob. See Configuring an nRF52840 as a Battery-Powered OpenThread Sleepy End Device

Common Mistakes

• Choosing Thread without budgeting for Matter. Thread is a transport, not an application-layer standard — a Thread-only device has no defined behaviour without Matter or an equivalent layer on top.
• Building a custom Border Router when a commercial one already covers the target deployment. Most consumer homes already have Border Router functionality in existing hub hardware; duplicating it adds unnecessary certification and maintenance burden.
• Setting a Sleepy End Device's poll period only marginally shorter than its child timeout, so ordinary scheduling jitter or a single missed poll window triggers an unnecessary and comparatively expensive re-attach cycle.
• Assuming Thread and Zigbee devices can join the same network because they share a radio. They use the same IEEE 802.15.4 PHY but are incompatible network stacks — a translation gateway or Matter Bridge is required to bridge the two.

Common Questions

Do I need Thread if I'm already shipping a Zigbee product?

Not necessarily. Extending an existing Zigbee product line usually means sticking with Zigbee unless a specific ecosystem requirement forces a change: adding Thread/Matter to an established line means a second certification process and a second firmware stack to maintain. Thread is the stronger default for genuinely new designs targeting Apple Home, Google Home, or Amazon Alexa. See Thread vs Zigbee: which should you choose for a new product? for the full decision framework.

Can I use the same radio silicon for either protocol?

Usually yes. Thread and Zigbee share the same IEEE 802.15.4 radio layer, so most current-generation multiprotocol SoCs (Silicon Labs EFR32MG21/24, Nordic nRF52840/nRF5340, TI CC2652R) support both. This keeps the hardware decision and the protocol decision largely independent, though committing to one protocol per SKU in firmware is still the right approach rather than attempting true concurrent dual-stack operation on a single-purpose product.

What's the fastest way to get hands-on with a real Thread network during development?

Standing up a self-hosted OpenThread Border Router (typically Google's official OTBR Docker image on a Raspberry Pi with an nRF52840 dongle flashed as a Radio Co-Processor), rather than relying solely on a commercial hub's opaque implementation. See How Do You Set Up an OpenThread Border Router? for the practical deployment and ot-ctl workflow.

How do I configure a battery-powered Thread device so it doesn't drain the battery?

Configure it as a Minimal Thread Device with sleepy behaviour enabled (CONFIG_OPENTHREAD_MTD_SED in the nRF Connect SDK), then tune the poll period against the application's actual downlink-latency requirement while leaving real margin below the parent's configured child timeout. Zeus Design designs battery-optimised Thread and Matter products on Nordic nRF52/nRF53 silicon, from initial protocol strategy through to production firmware.

Knowledge Base

Fundamentals

• What Is Thread? — IPv6/6LoWPAN mesh networking, device roles, OpenThread, and how Thread compares to Zigbee and Matter

Product Decision

• Thread vs Zigbee: Which Should You Choose for a New Product? — target ecosystem, existing product lines, multiprotocol silicon, and migration paths

Deployment

• How Do You Set Up an OpenThread Border Router? — OTBR Docker deployment on a Raspberry Pi, ot-ctl commands, and device commissioning

Battery-Powered Devices

• How Do You Configure an nRF52840 as a Battery-Powered OpenThread Sleepy End Device? — MTD/SED Kconfig options, poll period tuning, child timeout margin, and Coordinated Sample Listening

Forum Discussions

• OpenThread joiner times out every time — the commissioner-not-started gotcha behind a joiner that fails silently with no useful error