9.4 KiB
Matter Events Example
This example demonstrates how to monitor and handle Matter events using an ESP32 SoC microcontroller.
The application showcases Matter event handling, commissioning, and automatic decommissioning. It provides a comprehensive view of all Matter events that occur during device operation, making it useful for debugging and understanding the Matter protocol behavior.
Supported Targets
| SoC | Wi-Fi | Thread | BLE Commissioning | Status |
|---|---|---|---|---|
| ESP32 | ✅ | ❌ | ❌ | Fully supported |
| ESP32-S2 | ✅ | ❌ | ❌ | Fully supported |
| ESP32-S3 | ✅ | ❌ | ✅ | Fully supported |
| ESP32-C3 | ✅ | ❌ | ✅ | Fully supported |
| ESP32-C5 | ❌ | ✅ | ✅ | Supported (Thread only) |
| ESP32-C6 | ✅ | ❌ | ✅ | Fully supported |
| ESP32-H2 | ❌ | ✅ | ✅ | Supported (Thread only) |
Note on Commissioning:
- ESP32 & ESP32-S2 do not support commissioning over Bluetooth LE. For these chips, you must provide Wi-Fi credentials directly in the sketch code so they can connect to your network manually.
- ESP32-C6 Although it has Thread support, the ESP32 Arduino Matter Library has been pre compiled using Wi-Fi only. In order to configure it for Thread-only operation it is necessary to build the project using Arduino as an IDF Component and to disable the Matter Wi-Fi station feature.
- ESP32-C5 Although it has Wi-Fi 2.4 GHz and 5 GHz support, the ESP32 Arduino Matter Library has been pre compiled using Thread only. In order to configure it for Wi-Fi operation it is necessary to build the project using Arduino as an ESP-IDF component and disable Thread network, keeping only Wi-Fi station.
Features
- Matter protocol implementation with comprehensive event monitoring
- Support for both Wi-Fi and Thread(*) connectivity
- Event callback handler that displays all Matter events to Serial Monitor
- Monitors connectivity changes (Wi-Fi, Thread, Internet, IPv4/IPv6)
- Tracks commissioning lifecycle events
- Monitors fabric management events
- Tracks BLE/CHIPoBLE events
- Automatic decommissioning after 60 seconds for continuous testing
- Matter commissioning via QR code or manual pairing code (*) It is necessary to compile the project using Arduino as IDF Component.
Hardware Requirements
- ESP32 compatible development board (see supported targets table)
Software Setup
Prerequisites
- Install the Arduino IDE (2.0 or newer recommended)
- Install ESP32 Arduino Core with Matter support
- ESP32 Arduino libraries:
MatterWi-Fi(only for ESP32 and ESP32-S2)
Configuration
Before uploading the sketch, configure the following:
- Wi-Fi credentials (if not using BLE commissioning - mandatory for ESP32 | ESP32-S2):
const char *ssid = "your-ssid"; // Change to your Wi-Fi SSID const char *password = "your-password"; // Change to your Wi-Fi password
Building and Flashing
- Open the
MatterEvents.inosketch in the Arduino IDE. - Select your ESP32 board from the Tools > Board menu.
- Select "Huge APP (3MB No OTA/1MB SPIFFS)" from Tools > Partition Scheme menu.
- Enable "Erase All Flash Before Sketch Upload" option from Tools menu.
- Connect your ESP32 board to your computer via USB.
- Click the Upload button to compile and flash the sketch.
Expected Output
Once the sketch is running, open the Serial Monitor at a baud rate of 115200. The Wi-Fi connection messages will be displayed only for ESP32 and ESP32-S2. Other targets will use Matter CHIPoBLE to automatically setup the IP Network. You should see output similar to the following, which provides the necessary information for commissioning and displays Matter events:
Connecting to your-wifi-ssid
.......
Wi-Fi connected
IP address: 192.168.1.100
Starting Matter Commission Test...
Matter Node is not commissioned yet.
Initiate the device discovery in your Matter environment.
Commission it to your Matter hub with the manual pairing code or QR code
Manual pairing code: 34970112332
QR code URL: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A6FCJ142C00KA0648G00
===> Got a Matter Event: CHIPoBLE Advertising Change
===> Got a Matter Event: Commissioning Window Opened
===> Got a Matter Event: Commissioning Session Started
===> Got a Matter Event: Commissioning Complete
===> Got a Matter Event: Operational Network Started
===> Got a Matter Event: Operational Network Enabled
===> Got a Matter Event: Internet Connectivity Change :: IPv4 Connectivity: Established - IP Address: 192.168.1.100
===> Got a Matter Event: IPv4 Address Assigned
===> Got a Matter Event: Server Ready
===> Got a Matter Event: DNS-SD Initialized
Matter Fabric not commissioned yet. Waiting for commissioning.
...
Matter Node is commissioned and connected to Wi-Fi.
====> Decommissioning in 60 seconds. <====
===> Got a Matter Event: Fabric Will Be Removed
===> Got a Matter Event: Fabric Removed
===> Got a Matter Event: Commissioning Window Opened
Matter Node is decommissioned. Commissioning widget shall start over.
Using the Device
Event Monitoring
The example continuously monitors and displays Matter events to the Serial Monitor. This includes:
- Connectivity Events: Wi-Fi, Thread, Internet connectivity changes, IP address assignments
- Commissioning Events: Commissioning session start/stop, commissioning window open/close, commissioning complete
- Fabric Events: Fabric committed, updated, removed
- BLE Events: CHIPoBLE connection established/closed, advertising changes
- Network Events: Operational network started/enabled, interface IP address changes
- Service Events: Service connectivity changes, provisioning changes, DNS-SD events
- System Events: Server ready, OTA state changes, time sync changes, fail-safe timer expiration
Test Cycle
The device operates in a continuous test cycle:
- Commissioning Phase: The device waits for Matter commissioning and displays all related events.
- Commissioned Phase: Once commissioned, the device is connected to the Matter network and ready for use. All network and service events are displayed.
- Automatic Decommissioning: After 60 seconds, the device automatically decommissions itself.
- Repeat: The cycle repeats, allowing you to test the commissioning process multiple times and observe all events.
Smart Home Integration
Use a Matter-compatible hub (like an Apple HomePod, Google Nest Hub, or Amazon Echo) to commission the device during each test cycle. Monitor the Serial Monitor to see all events that occur during the commissioning process.
Apple Home
- Open the Home app on your iOS device
- Tap the "+" button > Add Accessory
- Scan the QR code displayed in the Serial Monitor, or
- Tap "I Don't Have a Code or Cannot Scan" and enter the manual pairing code
- Follow the prompts to complete setup
- Monitor the Serial Monitor to see all Matter events during commissioning
- The device will appear as an on/off light in your Home app
- After 60 seconds, the device will automatically decommission and the cycle will repeat
Amazon Alexa
- Open the Alexa app
- Tap More > Add Device > Matter
- Select "Scan QR code" or "Enter code manually"
- Complete the setup process
- Monitor the Serial Monitor to see all Matter events during commissioning
- The light will appear in your Alexa app
- After 60 seconds, the device will automatically decommission and the cycle will repeat
Google Home
- Open the Google Home app
- Tap "+" > Set up device > New device
- Choose "Matter device"
- Scan the QR code or enter the manual pairing code
- Follow the prompts to complete setup
- Monitor the Serial Monitor to see all Matter events during commissioning
- After 60 seconds, the device will automatically decommission and the cycle will repeat
Code Structure
The MatterEvents example consists of the following main components:
setup(): Initializes Serial communication, configures Wi-Fi (if needed), sets up the Matter On/Off Light endpoint, registers the Matter event callback handler, and starts the Matter stack.loop(): Checks the Matter commissioning state, displays pairing information when not commissioned, waits for commissioning, and then automatically decommissions after 60 seconds to repeat the cycle.onMatterEvent(): Comprehensive event callback handler that processes and displays all Matter events, including connectivity changes, commissioning events, fabric management, BLE events, and system events.
Troubleshooting
- Device not visible during commissioning: Ensure Wi-Fi or Thread connectivity is properly configured
- No events displayed: Verify that the event callback is properly registered using
Matter.onEvent() - Failed to commission: Try waiting for the next cycle after decommissioning. Other option would be to erase the SoC Flash Memory by using
Arduino IDE Menu->Tools->Erase All Flash Before Sketch Upload: "Enabled"or directly withesptool.py --port <PORT> erase_flash - No serial output: Check baudrate (115200) and USB connection
- Device keeps decommissioning: This is expected behavior - the device automatically decommissions after 60 seconds to allow continuous testing and event monitoring
Related Documentation
License
This example is licensed under the Apache License, Version 2.0.