Matter~

#define USE_MATTER_DEVICE

What is Matter?~

Matter is a new secure, reliable, local standard/protocol for smart devices launched at the end of 2022. Learn more about Matter.

Tasmota supports Matter over IP (Wi-Fi or Ethernet) as an end-device. This means that you can connect a Tasmota device to a Matter gateway, using standard and well defined protocols. The Matter communication is completely local.

Matter cannot be supported on ESP8266 due to limited memory resources. We are exploring the possibility to use a single ESP32 as a Matter bridge to control ESP8266 devices through the bridge.

Supported platforms~

Tasmota Matter is confirmed to work with:

• Apple Home - requirements
• Amazon Alexa - requirements
• Espressif-Matter iOS/Mac app
• Google Home - only works after following these instructions
• Home Assistant

More information on pairing with above mentioned smart home systems.

Getting Started~

Install Tasmota with Matter support. Unofficial binaries are available for ESP32 variants in our web installer at the bottom of the list under unofficial builds.

Go to Configuration --> Configure Matter and enable Matter.

After a restart device commissioning will be open for 10 minutes.

Add the device in your smart home solution by scanning the QR code or with the "Manual pairing code" if code scanning is not possible.

Configuration~

After Matter support is enabled the Configuration --> Configure Matter menu is used to configure options.

Matter Passcode~

You can change the passcode and ID of the device or force it to use IPv4 only.

Current Configuration~

Configure your device for Matter discovery. Tasmota tries to configure supported features automatically.

You can add or remove features manually in this menu.

Changing these options requires a device restart.

Endpoint~

To add new features you need to add Endpoints.

They're labelled as Ep. in the table. They don't need to have sequential numbers but 0 is always reserved for "Root node" type.

Type~

Select your endpoint type from the drop down. Types are limited by the Matter specification.

Param~

To link a Tasmota power output (light/relay) to an endpoint set its param equal to the power output number.

To link a Tasmota sensor to an endpoint add the rule trigger of the sensor to the Param value.

MQT: tele/tasmota_4BC990/SENSOR = {"Time":"2023-05-28T20:04:27","SCD40":{"CarbonDioxide":618,"eCO2":623,"Temperature":23.8,"Humidity":61.1,"DewPoint":15.8},"TempUnit":"C"}

Fabrics~

In short fabrics are Matter node identifiers. Long story here....

Deleting a Fabric will remove its commissioned status related to the commissioner.

Known Limitations~

Matter support is still highly experimental, there are some limitations:

• Matter requires IPv6 support, yet IPv4 is often tolerated. For debug purpose you can force Tasmota to manage Matter only on IPv4
• Tasmota devices with dual active networks (Ethernet + Wifi) are not yet supported. You need to disable Wifi or Ethernet. For example use Ethernet Network Flipper
• Tasmota cannot be Matter certified, it uses development vendor id's, which typically raise user warnings when commissioning the device

What's not suported:

• ESP8266 because of limited memory resources and lack of Berry support
• Thread as it requires a separate MCU. The number of Thread devices is still very limited.
• Zigbee

Commands~

Events~

Events published as JSON MQTT that can be captured in rules:

{"Matter":{"Initialized":1}}
when the device is configured (all endpoints created)

{"Matter":{"Commissioning":1,"PairingCode":"00054912336","QRCode":"MT:Y.K90IRV01YZ.548G00"}}
when commissioning is open

{"Matter":{"Commissioning":0}}
when commissioning is closed

Internal Operation~

Read more about the internal operation