mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-15 05:16:49 +00:00
Matter: update Thread section (#31138)
* Matter: update Thread section - make it shorter - move Thread border router / network illustration to Thread integration - as the illustration has a focus on Thread * Add link to Thread documentation * Add subtitle * Move illustartion back into Matter article * Apply suggestions from code review Co-authored-by: Stefan Agner <stefan@agner.ch> --------- Co-authored-by: Stefan Agner <stefan@agner.ch>
This commit is contained in:
parent
0c3ed3943d
commit
80f64dc079
@ -46,13 +46,23 @@ Unlike other common radio-based protocols for IoT, (like Zigbee, Z-Wave, and Blu
|
||||
|
||||
Home Assistant is a so-called "_controller_" in a Matter ecosystem, meaning that it can control Matter-based devices. Other examples of Matter controllers are the Google Nest products, Apple HomePod speakers, Samsung SmartThings Station, and some newer Amazon Echo devices.
|
||||
|
||||
## Thread
|
||||
## What does Thread have to do with Matter?
|
||||
|
||||
Matter goes hand-in-hand with (but is not the same as) {% term Thread %}. {% term Thread %} is a low power radio mesh networking technology. Much like Zigbee, but with the key difference that it is _IP-addressable_, making it the perfect companion transport protocol for Matter.
|
||||
{% term Thread %} is a low power radio mesh networking technology. Much like Zigbee, but with the key difference that it is _IP-addressable_, making it a suitable transport protocol option for Matter.
|
||||
|
||||
<div class='note'>
|
||||
Many devices that (will) hit the market will use {% term Thread %} for radio communication and Matter as a control protocol, but this is not guaranteed. For example, Thread-based devices are available that only support Apple HomeKit or some vendor-specific communication protocol. There are also a few cases where you need to apply for a (beta) firmware update on the device to enable Matter as a communication protocol. Therefore, do not assume Matter support when you see a Thread logo when looking for devices. Please be sure to look for the *Matter* logo itself (on either Wi-Fi/Ethernet-based devices or {% term Thread %}) or any other confirmation by the manufacturer that the device supports Matter.
|
||||
</div>
|
||||
The figure below illustrates the landscape of {% term Matter %}, {% term Thread %}, and Border routers. The Thread border router forwards traffic from the devices in the Thread network to devices outside that network.
|
||||
|
||||

|
||||
|
||||
Image taken from [the Thread Smart Home Fact Sheet](https://www.threadgroup.org/support#Resources) by the Thread Group.
|
||||
|
||||
For more information about Thread, refer to the [Thread documentation](/integrations/thread/).
|
||||
|
||||
### Thread devices don't necessarily support Matter
|
||||
|
||||
Many devices on the market use {% term Thread %} for radio communication and Matter as a control protocol. But this is not guaranteed. Some Thread-based devices support Apple HomeKit or another vendor-specific communication protocol. There are also a few cases where you need to apply for a (beta) firmware update on the device to enable Matter as a communication protocol.
|
||||
|
||||
Don't assume Matter support when you see a Thread logo on a device. Always look for the _Matter_ logo itself (on either Wi-Fi/Ethernet-based devices or {% term Thread %}) or any other confirmation by the manufacturer that the device supports Matter.
|
||||
|
||||
## Bluetooth used during commissioning
|
||||
|
||||
@ -68,9 +78,6 @@ One of the great features of Matter is the so-called _Multi Fabric_ feature: you
|
||||
|
||||
For devices where Home Assistant provides a native integration (with local API), Matter may not be the best option. Matter, being a universal standard, might not have the nitty-gritty features that come with a product-specific protocol. A good example is Philips Hue: the communication over Matter only provides the basic controls over lights, while the official [Hue integration](/integrations/hue) brings all Hue unique features like (dynamic) scenes, entertainment mode, etc.
|
||||
|
||||

|
||||
|
||||
Image taken from [this excellent article by The Verge](https://www.theverge.com/23165855/thread-smart-home-protocol-matter-apple-google-interview) about Matter that shows the landscape of Matter, {% term Thread %}, Border routers and bridges in a nice visualized way.
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
|
@ -56,16 +56,22 @@ Thread uses the same <abbr title="radio frequency">RF</abbr> technology as Zigbe
|
||||
|
||||
The devices use Thread border routers to communicate outside the mesh with any IPv6-capable device. A Thread border router is connected to your network either via Wi-Fi or Ethernet and uses its <abbr title="radio frequency">RF</abbr> radio to communicate with the Thread mesh network. The <abbr title="Thread border router">TBR</abbr> routes packets between your local network and the Thread mesh. It does not look at the content of these packets, it just forwards them.
|
||||
|
||||
Often, Thread border routing is only an auxiliary functionality of a smart home device. For example, the Nest Hub (2nd gen) is a smart display, a Google Home controller, and a Chromecast target, but also has a Thread border router included.
|
||||

|
||||
|
||||
Image taken from [the Thread Smart Home Fact Sheet](https://www.threadgroup.org/support#Resources) by the Thread Group. It illustrates the landscape of {% term Matter %}, {% term Thread %}, and Border routers. Instead of Matter, you could also see another protocol here, such as HomeKit.
|
||||
|
||||
Unlike other protocols, Thread can use multiple border routers in a single network. This increases wireless coverage and reduces the risk of a single point of failure. Ideal for home automation, with a potentially large number of devices spread over a large area.
|
||||
|
||||
#### OpenThread border routers
|
||||
|
||||
OpenThread is an open source implementation of Thread, originally released by Google. Almost all commercially available Thread border routers are based on the open source implementation. However, the configuration of <abbr title="Thread border routers">TBRs</abbr> is not part of the Thread standard. This means that Google and Apple <abbr title="Thread border routers">TBRs</abbr> implementation setup and configured by their respective ecosystems.
|
||||
|
||||
While Home Assistant can *use* any border router, it can *configure* and *control* only OpenThread border routers built with the REST API available in the open source implementation. The OpenThread Border Router add-on (as well as the OpenThread Border Router bundled in the experimental Silicon Labs Multiprotocol add-on) are built from this open source OpenThread code and have the REST API enabled.
|
||||
|
||||
### List of Thread border router devices
|
||||
|
||||
Often, Thread border routing is only an auxiliary functionality of a smart home device. For example, the Nest Hub (2nd gen) is a smart display, a Google Home controller, and a Chromecast target, but also has a Thread border router included.
|
||||
|
||||
Currently, the following <abbr title="Thread border router">TBR</abbr> devices are known to work with Home Assistant.
|
||||
These border routers may require an iPhone or Android phone for onboarding. What the exact requirements are, depends on the home automation protocol ({% term Matter %} or Apple HomeKit) that your devices are using. Before buying a border router, check the prerequisites in the corresponding procedures:
|
||||
|
||||
|
BIN
source/images/integrations/matter/matter_thread_infographic.png
Normal file
BIN
source/images/integrations/matter/matter_thread_infographic.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 235 KiB |
Binary file not shown.
Before Width: | Height: | Size: 54 KiB |
Loading…
x
Reference in New Issue
Block a user