diff --git a/source/_integrations/matter.markdown b/source/_integrations/matter.markdown index df427facef1..dcab06ce586 100644 --- a/source/_integrations/matter.markdown +++ b/source/_integrations/matter.markdown @@ -7,11 +7,11 @@ ha_category: - Lock - Sensor - Switch -ha_release: '2022.12' +ha_release: "2022.12" ha_iot_class: Local Push ha_config_flow: true ha_codeowners: - - '@home-assistant/matter' + - "@home-assistant/matter" ha_domain: matter ha_platforms: - binary_sensor @@ -23,62 +23,101 @@ ha_platforms: ha_integration_type: integration --- -The Matter integration allows you to control Matter devices on your local WiFi or Thread network. +The Matter integration allows you to control Matter devices on your local Wi-Fi or {% term Thread %} network. -Matter is [the new standard for home automation](https://en.wikipedia.org/wiki/Matter_(standard)) which has just been released. It is in the process of being adopted by the tech industry. Matter is a local protocol, device control is done without the need of any cloud. You can use a Matter compatible device with Home Assistant without having to connect to a vendor specific cloud. +
-Both the Matter standard itself and its implementation within Home Assistant are in a very early stage where only the basics are working and/or breaking changes can still happen. Using it in production is not recommended yet until it matures a bit more. -
+Home Assistant is a so-called _controller_, it can control Matter based devices. Other examples of Matter controllers are the Google Nest speakers, Apple HomePods, and a SmartThings Station. -One of the great features of Matter is the so called _Multi Fabric_ feature: you can join the same device to multiple controllers. For example: add it to Google Home, Apple Home, and Home Assistant at the same time. +## Bridge devices -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, the official integration brings all Hue unique features like (dynamic) scenes, entertainment mode, etc. +One of the great things about Matter is that you can have both Wi-Fi and Thread based devices on the same controller. +Next to actual devices (like actors or sensors), you will also see bridges. The bridge connects the network over Ethernet or Wi-Fi and bridges multiple devices into a Matter network. A great example is the Philips Hue V2 bridge, which is a Zigbee hub and a Matter bridge. This bridge exposes all Zigbee devices already connected to the bridge as Matter devices on the network. Also, Aqara, SwitchBot, and IKEA have launched such Hub devices. --The Matter protocol relies on (local) IPv6 and mDNS (multicast traffic) which should be able to travel freely in your network. Matter devices (and any Thread Border routers) must be on the same LAN/VLAN as Home Assistant. Implementations like mDNS reflectors usually do more harm than good. -
++At this time it is not yet possible to share a device from Home Assistant to another platform. This feature should be added after the Matter SDK 1.1 is released. +
-Because availability of actual Matter devices is sparse and proper HOWTO documentation even more, we provide a few step by step instructions for devices we have currently tested. +## Experiment with Matter using a ESP32 dev board -### TP-Link Tapo P125M (power plug) - -This device runs Matter out of the box, so you can add it directly to the controller(s) of your choice! - -Look for the M addition in the model name, a device without the M (regular P125) is not Matter compliant. This device is available in the US only. - -[TP-Link Tapo P125M on Amazon](https://amzn.to/3RILJah) - -### ESP32 dev board running Matter example app - -This is the most convenient and easy way to start playing with Matter. We have [prepared a page for you](https://nabucasa.github.io/matter-example-apps/) where you can easily flash Matter firmware to a supported ESP32 development board. We actually recommend the M5 Stamp C3 device running the Lightning app. +You do not yet have any Matter-compatible hardware but you do like to try it out or maybe create your own DIY Matter device? We have [prepared a page for you](https://nabucasa.github.io/matter-example-apps/) where you can easily flash Matter firmware to a supported ESP32 development board. We recommend the M5 Stamp C3 device running the Lightning app. NOTE for Android users: You need to follow the instructions at the bottom of the page to add the test device to the Google developer console, otherwise commissioning will fail. iOS users will not have this issue but they will get a prompt during commissioning asking if you trust the development device. -1) Make sure you are using the Google Chrome or Microsoft Edge browser. -2) Open https://nabucasa.github.io/matter-example-apps/ -3) Attach the ESP32 device using an USB cable. -4) Click the radiobutton next to the example you like to setup, in case of an M5 Stamp, click `Lightning app for M5STAMP C3`. -5) Press `Connect`. -6) In the popup dialog that appears choose the correct serial device, in most cases this will be something like "cu-usbserial" or alike. -7) Click `Install Matter Lightning app example` and let it install the firmware on the device, this will take a few minutes. -8) Once the device is flashed with the Matter firmware, connect to the device again but this time choose `Logs & console`. -9) You are presented with a console interface where you see live logging of events. This is actually an interactive shell where you can type commands. For a list of all commands, type `matter help` and press enter. -10) To add the device, we need the QR code. In the console type in `matter onboardingcodes ble` and copy/paste the URL in your browser. -11) Use the QR code to add the device using one of the above instructions on your phone, e.g. using the Home Assistant Companion app. +1. Make sure you use Google Chrome or Microsoft Edge browser. +2. Open https://nabucasa.github.io/matter-example-apps/ +3. Attach the ESP32 device using a USB cable. +4. Select the radio button next to the example you like to set up, in case of an M5 Stamp, click **Lightning app for M5STAMP C3**. +5. Select **Connect**. +6. In the popup dialog that appears, choose the correct serial device. This will usually be something like "cu-usbserial" or alike. +7. Click **Install Matter Lightning app example** and let it install the firmware on the device. This will take a few minutes. +8. Once the device is flashed with the Matter firmware, connect to the device again but this time choose **Logs & console**. +9. You are presented with a console interface where you see live logging of events. This is an interactive shell where you can type commands. For a list of all commands, type **matter help** and press enter. +10. To add the device, we need the QR code. In the console, type in `matter onboardingcodes ble` and copy/paste the URL into your browser. +11. Use the QR code to add the device using one of the above instructions on your phone, e.g. using the Home Assistant Companion app. + +## Known working devices + +Because the availability of actual Matter devices (and their documentation) is sparse, we provide a list of all known working devices that are tested by the Home Assistant Matter developers and/or the community to help you find the device you need. Note: The list below is ordered alphabetically, and some links contain affiliate links. + +Did you test a device that is not listed below? It would be greatly appreciated if you share your experience either on the Matter discord channel or contribute a PR (or suggestion) to this documentation page so you can help others, thanks in advance! + +### Aqara M2 Hub + +- Bridges Aqara (Zigbee) devices connected to the hub to Matter. +- You need to enable Matter support/firmware in the Aqara app. +- You will need an Aqara (cloud) account and the app before you can use Matter. +- See [this Aqara landingpage](https://www.aqara.com/en/article-1583275073188196352.html) for more information, including what devices are bridged. +- Thermostat devices (climate platform) are not supported yet (but are currently in development). +- Device events, for example for the wall rockers and Cube, are not supported. ### Eve Energy (power plug), Eve Door & Window (contact sensor), Eve Motion (motion sensor) -1) Look for the Thread logo on the box to ensure you have the new device which is compatible with Matter. -2) The Eve device runs on HomeKit by default, you will need an iOS device to set it up out of the box. -3) The Eve device uses Thread for communication, therefore you will need to have a Thread Border Router configured in your network setup, such as the Apple TV 4K (2021/2022), Homepod Mini, or Homepod V2. -4) You need to join the [Eve Beta program here](https://www.evehome.com/en/meet-matter) and wait for instructions per email. -5) Update the firmware of your Eve device using the Eve beta app to Matter. -6) During the update process the Eve app will create a new QR code for you to save somewhere safe. This QR code is required when you want to add the device to a Matter controller. The normal QR code attached to the device will no longer work! -7) During the upgrade process, the Eve app will join the device to Apple Home using Matter. -8) Confirm that the device is working properly within Apple Home. -9) Follow our instructions above to share the device from Apple Home to Home Assistant. +- If you see a Matter logo on the box, the device runs Matter already and you can add it to HA immediately. +- If there is a Thread logo, you need to install the Matter firmware using the Eve app. +- No Matter logo and no Thread logo on the box? The device is not Matter compatible. +- The energy metering feature of the Eve plug will not work in Home Assistant (Apple only feature). +- Eve has just released official Matter support so ignore any documentation about the beta program. -Once the initial firmware upgrade to Matter is complete, the device can also be paired to non-Apple based Thread networks, like Google Home or later Home Assistant's own Thread implementation based on OTBR but you do need an Apple ecosystem running (iOS phone + Border router) for the first time setup. +[Eve Energy on Amazon](https://amzn.to/3YuO62P) +[Eve Door & Window on Amazon](https://amzn.to/3RIU6ml) +[Eve Motion on Amazon](https://amzn.to/3jDujiP) -- [Eve Energy on Amazon](https://amzn.to/3YuO62P) -- [Eve Door & Window on Amazon](https://amzn.to/3RIU6ml) -- [Eve Motion on Amazon](https://amzn.to/3jDujiP) +### Nanoleaf Matter bulbs and Lightstrips + +- Although the products work great once commissioned, multiple users have reported that commissioning them can be a bit difficult and requires some patience and multiple resets or optimizations to your home network. +- Check the [Nanoleaf Matter infopage](https://nanoleaf.me/en-EU/integration/matter/) for all supported products and instructions. + +### Philips Hue (V2) Bridge + +The Philips Hue V2 bridge supports Matter since a recent update (the beta program closed, it is now officially available). You can enable Matter support from the Hue app after which you can commission it to Home Assistant and other fabrics. + +- Binding the Hue bridge to Home Assistant does not make sense because you will lose functionality over the default Hue integration in Home Assistant, such as button press events and (dynamic) scenes. +- You will need a Hue/Signify (cloud) account and the app before you can use Matter. +- Device events for example for dimmer remotes are not supported. +- Only basic control of lights is supported, no scenes, events, effects etc. + +### TP-Link Tapo P125M (power plug) + +- Look for the M addition in the model name, a device without the M (regular P125) is not Matter compliant. +- This device is available in the US only. + +[TP-Link Tapo P125M on Amazon](https://amzn.to/3RILJah) ## Troubleshooting -### I do not see the option to add a Matter device in the settings -We've added the option to **Add a Matter device** from the **Settings**>**Devices** in a recent version of the Home Assistant frontend, available from version 2023.3 and upwards or if you're running the Home Assistant nightly channel. If you are on a previous version of Home Assistant, you should see a button **Configure** on the Matter integration card within **Settings**>**Devices & Services**>**Integrations**. Click that **Configure** button and you should be able to see the **Commission** button on the Companion app. +### General recommendations + +- Using Thread-based Matter devices in Home Assistant requires Home Assistant OS (version 10 and above) because of kernel patches to solve routing issues. Not using HAOS (and thus the official Matter add-on) is at your own risk. + +- To use Thread devices you will need a Thread Network with at least one Thread Border Router in your network nearby the Thread device(s). Apple users need for example the Apple TV 4K or the HomePod Mini, while Google users need a Nest Hub V2. Use the Thread integration in Home Assistant to diagnose your Thread network(s). + +- Start simple and work from there, keep your network easy and add for example an ESP32 test device. Once that works, move on to the next step or more devices. + +- Realize that you are an early adopter, both on the hardware side and on the software (controller) side so you may run into compatibility issues or features that are still missing. Report any issues you may find and help out others if you find a workaround or tested a device. + +- Make sure IPv6 (multicast) traffic travels freely from your network to the Home Assistant host. There is no requirement to have an IPv6-enabled internet connection or DHCPv6 server. However, IPv6 support has to be enabled (it's enabled by default on Home Assistant OS). ### I do not see the button "Commission using the Companion app" + This button will only be visible within the Home Assistant Companion App (so not in the browser) and your device meets all requirements for Matter support. + - For iOS, minimum version is iOS 16 (minimal 16.3 is preferred) and the most recent version of the HA companion app. - For Android, minimum version is 8.1 and the most recent version of both the Google Home app and the (full) HA Companion app, downloaded from the app store. ### When I'm trying to commission using the Android app, I get an error stating "Matter is currently unavailable" -See above, make sure your device meets all requirements to support Matter. Update Android to the latest version and the Google Home and Home Assistant Companion app. To quickly verify if your device meets all requirements to support Matter, on your Android device go to **Settings**>**Google**>**Devices & Sharing**. There should be an entry there for **Matter devices**. + +See above, make sure your device meets all requirements to support Matter. Update Android to the latest version and the Google Home and Home Assistant Companion app. To quickly verify if your device meets all requirements to support Matter, on your Android device, go to **Settings** > **Google** > **Devices & Sharing**. There should be an entry there for **Matter devices**. + +Some users have reported that uninstalling and reinstalling the Google Home app fixed this issue for them. +Also see this [extended troubleshooting guide](https://developers.home.google.com/matter/verify-services) from Google. ### Unable to commission devices, it keeps giving errors or stops working randomly -We've seen cases (e.g. on UniFi hardware) where IPv6 derived from the Internet Provider causes issues with the discovery of Matter devices. Keep this in mind when you experience issues trying to add or control Matter devices. Protocols like Matter are designed for regular residential network setups and do not play nice with enterprise solutions like VLAN's, Multicast filtering, and IGMP snooping. To avoid issues, try to keep your network as simple and flat as possible. -## Advanced installation instructions +The Matter protocol relies on (local) IPv6 and mDNS (multicast traffic) which should be able to travel freely in your network. Matter devices that use Wi-Fi (including Thread Border routers) must be on the same LAN/VLAN as Home Assistant. Matter devices that only use Thread must be joined to Thread networks for which there is at least one border router connected to the Home Assistant LAN. -If you are using Home Assistant Container, Home Assistant Core, or you don't want to use the built-in Matter Server add-on, you will need to run the Matter Server yourself, to which the Matter integration will connect. - -### Running Matter Server - -This application provides the connection between your Matter network (called Fabric in technical terms) and Home Assistant. The Home Assistant Matter integration connects to this server via a websocket connection. You need to run the Matter Server before you can use the integration. - -There are multiple ways to run the server: - -**Option 1: The official Matter Server add-on, as described above** - -_This option is only available for Home Assistant OS (the recommended installation type) and Home Assistant Supervised installations._ - -**Option 2: Run the Matter server yourself** - -This option is considered a very advanced setup and only for experienced users. You can find instructions on how to run the Matter Server in the [project repository](https://github.com/home-assistant-libs/python-matter-server). - -_Disclaimer: Some links on this page are affiliate links._ +Investigate your network topology if you experience any issues with discovering devices (like the initial commission keeps failing) or if devices become unavailable randomly. For instance, a setting on your router or Wi-Fi access point to "optimize" multicast traffic can harm the (discovery) traffic from Matter devices. Keep this in mind when you experience issues trying to add or control Matter devices. Protocols like Matter are designed for regular residential network setups and do not play nicely with enterprise networking solutions like VLANs, Multicast filtering, and IGMP snooping. Try to keep your network as simple and flat as possible to avoid issues. diff --git a/source/images/integrations/matter/matter_thread_infographic.webp b/source/images/integrations/matter/matter_thread_infographic.webp new file mode 100644 index 00000000000..b4bc57284a3 Binary files /dev/null and b/source/images/integrations/matter/matter_thread_infographic.webp differ