Thread is a modern wireless networking protocol built specifically for smart home devices. It creates a low-power mesh network where devices can communicate with each other and with the internet, all without a traditional hub. Because Thread is IP-based, each device gets its own address on your local network, which simplifies direct connections and remote access. Thread often appears alongside Matter, and understanding how border routers, routers, and sleepy end devices work will help you choose the right products and avoid connection headaches.
What Is Thread and How Does It Work?
Thread is a mesh networking standard that uses the 2.4 GHz radio band (the same as Wi-Fi and Bluetooth). What sets it apart is that it is built on Internet Protocol version 6 (IPv6). Every Thread device gets its own IP address, allowing it to talk directly to other devices on your local network or to the internet through a border router. The mesh means that devices can relay messages for one another, extending range and improving reliability compared to a simple star network.
A Thread network has two types of nodes:
- Routers – These are mains-powered devices (plugged into wall outlets) that keep the mesh alive. They forward messages, manage routes, and stay awake all the time. Examples include smart plugs, always-on light bulbs, and certain smart speakers.
- Sleepy End Devices – Battery-powered sensors, buttons, or locks that spend most of their time asleep to save power. They wake up periodically to send data or listen for commands, relying on nearby routers to relay messages.
The most critical component in a Thread network is the border router. This device bridges the Thread mesh to your local Wi-Fi or Ethernet network, enabling internet access for Thread devices and allowing you to control them from your smart home app or voice assistant. A border router can be built into a smart speaker, a smart display, a dedicated bridge, or even a router/access point. Without at least one border router, Thread devices can only talk to each other locally and cannot be controlled remotely.
Thread vs Zigbee: Key Differences
Thread and Zigbee are both low-power mesh protocols operating in the same 2.4 GHz band, but they have fundamental architectural differences. The table below summarizes the main points.
| Feature | Thread | Zigbee |
|---|---|---|
| Network layer | IP-based (IPv6) | Non-IP (Zigbee cluster library) |
| Hub requirement | One or more border routers | One coordinator (hub) per network |
| Mesh topology | Self-healing mesh | Self-healing mesh |
| Interoperability | Designed for multi-vendor, often paired with Matter | Depends on profile; many products use proprietary profiles |
| Battery efficiency | Good (sleepy end devices) | Good (end devices sleep) |
| Maturity | Newer, growing ecosystem | Mature, large installed base |
| Typical use | Smart home lighting, sensors, locks; often with Matter | Lighting, sensors, locks; often vendor-specific hubs |
The biggest practical difference is that Thread is IP-based. This means that any device on your network (including a computer, phone, or a Matter controller) can talk to a Thread device through its IP address, as long as there is a border router in place. Zigbee, on the other hand, requires a dedicated Zigbee coordinator (usually a hub) that translates between the Zigbee network and your home network. That hub often locks you into the hub manufacturer’s ecosystem unless you use a universal bridge.
Thread also benefits from strong integration with the Matter standard. Many new Thread devices are sold as Matter-compatible, which means they can be controlled by any Matter-certified platform (Apple Home, Google Home, SmartThings, and others) without needing a proprietary hub—only a Thread border router from that platform. However, not all Thread devices come with Matter support, so check the box or manufacturer specifications before buying.
Why Thread Devices Often Come with Matter
Thread and Matter are complementary technologies. Matter is an application-layer standard that defines how smart home devices can be discovered, controlled, and secured across different ecosystems. Thread provides a robust, low-power mesh network transport for Matter. Together, they make it possible to build a highly interoperable smart home that needs border routers rather than a proprietary hub.
Most new smart home devices that support Thread also support Matter because that combination gives consumers the broadest compatibility. A device that uses Thread but not Matter might only work with one ecosystem (for example, a platform’s own accessory protocol running over Thread). By adding Matter, the same device can be added to any Matter-compatible app. Manufacturers are increasingly labeling products as “Matter over Thread” to indicate this pairing.
That said, there are still Thread-only devices that do not support Matter. Some older smart locks or sensors use Thread with a proprietary protocol. You will need to verify compatibility with your preferred smart home platform. If you want future-proof flexibility, look for Matter certification on the device packaging.
Border Routers and Network Fragmentation
One of the most important practical issues with Thread is what happens when you have multiple border routers on the same property. Each border router can create its own Thread network with a unique PAN ID (Personal Area Network Identifier). If two border routers belong to different ecosystems (for example, from two different platforms), they may create separate Thread networks that cannot communicate with each other. This is called network fragmentation.
Fragmentation means that a Thread light bulb joined to one platform’s Thread network may not be reachable through another platform’s border router, even though both are physically present. The device is on one Thread mesh, and the other border router does not have permission to route messages to it.
To avoid fragmentation:
- Stick with one ecosystem for your Thread border routers. For instance, if your main platform is Apple Home or Google Home, use that platform’s own hubs, speakers or displays as your border routers.
- If you must mix ecosystems, look for border routers that allow you to configure the same network credentials (a Thread “operational dataset”). Some newer border routers let you share credentials via a QR code or manual input, but this is not yet universal.
- Consider using a dedicated Thread border router that is neutral, such as a Wi-Fi router with built-in Thread radio that can be configured to serve all platforms. However, such devices are still rare.
Another related issue: if you have multiple border routers from the same ecosystem, they typically share the same Thread network automatically. That is fine—it actually improves coverage. The fragmentation problem arises when different ecosystems are involved.
Buying Tips for Thread Devices
Before you purchase a Thread smart home device, consider these points:
- Check for Matter support. Matter over Thread gives you the freedom to switch ecosystems later. Look for the Matter logo or “Works with Matter” on the packaging.
- Ensure you have at least one Thread border router that is compatible with your chosen ecosystem. Common border routers include smart speakers, smart displays, and some Wi-Fi routers. If you do not have one, the Thread device will only work locally (if at all).
- Plan for power sources. Battery-operated Thread devices (sensors, buttons, locks) are sleepy end devices. They do not help extend the mesh. For a strong network, make sure you have enough mains-powered Thread devices (smart plugs, lights, or border routers) to act as routers.
- Avoid mixing ecosystems initially. Start with one smart home platform and add Thread devices that work with it. If you later want to mix, be prepared to manage multiple Thread networks or remove one ecosystem’s border routers.
- Read the fine print on specifications. Not every device with “Thread” on the box will work with every Thread border router. Certification to the Thread Group’s requirements is important, but compatibility also depends on the application layer (Matter or proprietary). Check the manufacturer’s support page before buying.
Thread is still a relatively new standard compared to Zigbee, and device availability varies by category. For lighting and sensors, you already have many choices. For locks and thermostats, the selection is growing. The main advantage of Thread is the future potential for a unified, hub-free smart home—especially when paired with Matter.
Do You Need a Smart Home Hub for Thread?
Thread eliminates the need for a traditional “hub” that acts as a single point of control. Instead, you need a Thread border router, which is often built into devices you might already own, such as a smart speaker or streaming box. If you are starting from scratch, you can buy a border router as a standalone purchase or choose a smart speaker that includes one. Some combination Wi-Fi routers also have Thread radios.
In short, you do not need a dedicated Zigbee-style hub, but you do need at least one border router that is always powered on. Without it, your Thread devices will not be reachable from the internet or from your phone when you are away from home. For more details, read our guide on whether you need a smart home hub.
FAQ
Do I need a smart home hub for Thread?
Not a traditional hub, but you need a Thread border router. That can be a smart speaker, smart display, or a dedicated device that connects the Thread mesh to your home network. Without at least one border router, Thread devices can only talk to each other locally.
Is Thread better than Zigbee?
Thread is designed for easier interoperability, especially with Matter, and uses IP addressing, which simplifies direct connections. Zigbee has a larger installed base and more device options today. The best choice depends on what devices you want and which ecosystem you prefer. Both are reliable mesh networks.
Can I mix Thread and Zigbee devices in one system?
Yes, but they use different radios. You will need both a Thread border router and a Zigbee hub (or a bridge that translates between them). Many smart home platforms support both protocols simultaneously. If you use a Matter-compatible bridge, you can even control Zigbee devices through the same app as your Thread devices.
What happens if I have multiple border routers from different brands?
They may create separate Thread networks, causing fragmentation. Your Thread devices will only be controllable by the ecosystem that the border router belongs to. To avoid this, stick with one ecosystem, or look for border routers that can be configured to share the same network credentials.
Will all Thread devices work with Matter?
No. Many Thread devices are Matter-certified, but older or simpler devices may use Thread with a proprietary protocol. Always check the packaging or manufacturer specifications for Matter support. If a device only lists one platform’s accessory program (over Thread), it may not work with other platforms unless it also supports Matter.
Thread brings a promising blend of low-power mesh and IP connectivity to the smart home, especially when paired with Matter. By understanding border routers, fragmentation, and device types, you can build a network that is both reliable and flexible. Always verify compatibility before purchasing, and consider starting with one ecosystem to keep things simple. As the standard matures, Thread is likely to become a common backbone for smart home devices of all kinds.

