If you own, read about, or manage a lot of smart home gear, you’ve probably heard of Thread. Thread is a low-power wireless network that allows smart home devices to communicate directly with each other in a mesh. It’s backed by Matter, a common language that makes smart devices from different brands work together more easily, and that’s why smart hubs are no longer such a necessity. In fact, we recommend using Thread exclusively in your smart home as one of our smart home gadget rules if you want to future-proof your setup.
Although Thread devices can communicate seamlessly with each other within the mesh, they need a little help communicating with outside networks like Wi-Fi or Ethernet. Enter a Thread Border Router (TBR). The role of a TBR is to connect the Thread mesh to one of these external networks and transmit data between it and the mesh. This allows Thread devices to be controlled by a smartphone or PC connected to your home’s Wi-Fi network, for example. In contrast, a Wi-Fi router creates and manages the Wi-Fi network for general-purpose devices.
A Thread Border router is distinct from a Thread router, which is a device that helps manage the Thread mesh itself and plays no role in connecting it to outside networks. A Thread Router routes data and manages connections inside the Thread mesh, while a TBR is the mesh’s ambassador to external networks and devices.
How do I know if I have a Thread Border router?
To check if you have a TBR, review your smart home app or device list for a hub or controller labeled “Thread” or “Matter over Thread.” Common examples are a HomePod mini, HomePod 2nd generation, Google Nest WiFi Pro, and the SmartThings Hub. If you have an Apple setup, the “Home Hubs & Bridges” section of the Home app is the quickest place to see if any of your hubs are serving as a TBR.
Many Thread devices come with a TBR included and serve as redundancies for others. If one of the TBR devices fails or loses connection, another can seamlessly assume the role and ensure your Thread mesh remains connected to the larger network. Unlike most IoT devices, which require a dedicated enclosure to translate IP protocol packages into the device language, Thread devices do not require any translation, meaning TBR functionality can be included in devices without the addition of bulky additional hardware.
