Support of Arduino Matter library

[Humancell]

Related area

Arduino Library

Hardware specification

All Boards

Is your feature request related to a problem?

The Matter specification has been released, and there has been IDF support for quite some time. At one level is would be good to see examples of using these APIs from the Arduino environment. At another level it would be great if there was a higher level Arduino library created that leveraged these APIs and provided examples for both implementing and controlling a Matter device.

Describe the solution you'd like

It would be great if there was a higher level Arduino library created that leveraged the IDF Matter APIs and provided examples for both implementing and controlling a Matter device.

Describe alternatives you've considered

There are some other people outside of this project starting to experiment with this, but they are not fully open source nor sponsored by Espressif.

Additional context

For the Espressif platform to dominate in the market for Matter devices it could be engaging the Arduino developers better.

I have checked existing list of Feature requests and the Contribution Guide

• I confirm I have checked existing list of Feature requests and Contribution Guide.

[lbernstone]

Why does this need to be part of the core? It can be handled in a 3rd party library.

[VojtechBartoska]

Hello @Humancell,

thanks for opening this feature Request.

I'm adding this to next major milestone 3.0.0 and we will evaluate it.

[Humancell]

Hello,

Thank you for considering this!

@lbernstone I can understand your question, but I see this no differently from all of the other libraries that are already a part of core. We already have Bluetooth, HTTP, DNS, Webserver, NetBIOS, RainMaker and many more. Just as many of these are built on the esp-protocols, this - it seems - would be built on https://github.com/espressif/esp-matter .

It is a protocol layer provided by Espressif in the IDF, and besides the technical reasons I believe by exposing it to Arduino developers it could assist the ESP32 in becoming an even more powerful platform for the development of Matter controllers and devices.

[Yacubane]

You can try library I have created few days ago https://github.com/jakubdybczak/esp32-arduino-matter

[Humancell]

Hello,

You can try library I have created few days ago https://github.com/jakubdybczak/esp32-arduino-matter

I did see this library, but from my understanding you have not made this 100% open source, which is a problem for us. We can not use any closed source code in our projects.

If I am incorrect, and this really is 100% open source then we could take a look.

[Yacubane]

@Humancell
Why do you think that this one is not open-source?
arduino-esp32 also contains precompiled libraries and scripts that do this are in esp32-arduino-lib-builder repo.
Same with esp32-arduino-matter, you can find scripts used to build it there esp32-arduino-matter-builder.

[SuGlider]

We will consider this request for next releases in 2023... please be patient.

[SuGlider]

I have done an initial effort to build Matter and Arduino as Component.
The steps are here:

espressif/esp-matter#116 (comment)

[HamzaHajeir]

Hi all

Is there any progress for supporting Matter to the Arduino core?

[SuGlider]

@HamzaHajeir - We are currently working to release OpenThread as an Arduino Library. This shall be done later this month.
Next step is to work on releasing Matter as an Arduino Library.
I believe that it will be done by the end of this year.

[SuGlider]

About Matter Library implementation for Arduino Core 3.0.x:

• We will initially implement it to be supported within WiFi. In the future also within Thread Protocol.
• WiFi Matter will be supported for ESP32, ESP32-C3, ESP32-S3, ESP32-S2 and ESP32-C6. No support for ESP32-H2 and ESP32-P4, which have no WiFi radio. ESP32-S2 has no BLE, it won't have Matter Device BLE advertising service.
• Thread Network Protocol will be supported for the ESP32-C6 and ESP32-H2. Both have also BLE, therefore, BLE Commissionable discovery is also available.
• Commissionable discovery will be done through BLE (whenever available in the SoC), WiFi SoftAP (future feature), DNS-SD for Thread Border Routers (future feature).
• Commissioning will follow Matter standard, including QR Code generated from a URL printed in the log output.
• ESP32 Matter implementation for BLE Commissionable discovery is based on NimBLE. Therefore, it won't be compatible with ESP32 BLE Arduino Library that uses Bluedroid instead. This means that there may be issues when using both together in the same Arduino Sketch. This will be a limitation. We are planning to move ESP32 Arduino BLE Library to use NimBLE as well in the future, which may solve this incompatibility problem.
• ESP32 Matter Arduino implementation will make available all possible Matter 1.0 device types as Arduino Classes: Lighting, Smart Plugs, Switches and Controls, Sensors, Closures and HVACs. Each Device Type Class will have necessary implementation of the device data model, endpoints, roles, clusters, commands and events.
• The current implementation is only for Matter Device. No plans for Matter Controllers or Matter Commissioner library.
• This implementation will use testing and development Matter Vendor ID (0xFFF1..4), therefore valid for CSA for testing purpose only. In case you need your own VID, please follow CSA processes and add certificates as necessary to your code, on your own.

[HamzaHajeir]

About Matter Library implementation for Arduino Core 3.0.x:

• We will initially implement it to be supported within WiFi. In the future also within Thread Protocol.
• WiFi Matter will be supported for ESP32, ESP32-C3, ESP32-S3, ESP32-S2 and ESP32-C6. No support for ESP32-H2 and ESP32-P4, which have no WiFi radio. ESP32-S2 has no BLE, it won't have Matter Device BLE advertising service.
• Thread Network Protocol will be supported for the ESP32-C6 and ESP32-H2. Both have also BLE, therefore, BLE Commissionable discovery is also available.
• Commissionable discovery will be done through BLE (whenever available in the SoC), WiFi SoftAP (future feature), DNS-SD for Thread Border Routers (future feature).
• Commissioning will follow Matter standard, including QR Code generated from a URL printed in the log output.
• ESP32 Matter implementation for BLE Commissionable discovery is based on NimBLE. Therefore, it won't be compatible with ESP32 BLE Arduino Library that uses Bluedroid instead. This means that there may be issues when using both together in the same Arduino Sketch. This will be a limitation. We are planning to move ESP32 Arduino BLE Library to use NimBLE as well in the future, which may solve this incompatibility problem.
• ESP32 Matter Arduino implementation will make available all possible Matter 1.0 device types as Arduino Classes: Lighting, Smart Plugs, Switches and Controls, Sensors, Closures and HVACs. Each Device Type Class will have necessary implementation of the device data model, endpoints, roles, clusters, commands and events.
• The current implementation is only for Matter Device. No plans for Matter Controllers or Matter Commissioner library.
• This implementation will use testing and development Matter Vendor ID (0xFFF1..4), therefore valid for CSA for testing purpose only. In case you need your own VID, please follow CSA processes and add certificates as necessary to your code, on your own.

Glad to hear that's coming support of Matter in the Arduino core. I have just some questions and comments:

• ESP-IDF identifies several tools related to setup Matter device (as esp-matter-mfg-tool), are these included also?
• Per Commissioning, please consider On-Network commisioning method, in which some could have his own device on the network previously, by either Ethernet or custom implementation of WiFi-AP.
• Therefore, I think it's okay to have ESP32-S2 supported with respect to such user responsibility (or even with the feature of WiFiAP commissioning).
• Is it available for some to build a custom device using matter data and interaction model?

With thanks,
Hamza Hajeir

[SuGlider]

@HamzaHajeir - Thanks for the comments.

ESP-IDF identifies several tools related to setup Matter device (as esp-matter-mfg-tool), are these included also?

Not as part of the tools that ESP32 Arduino would provide.
These tools, as the CHIP tools, or any other Python tools, can be used independently of the ESP32 SDK used to build Matter Applications. These tools can be used while using IDF, Rust or Arduino Frameworks for Matter development.

Per Commissioning, please consider On-Network commisioning method, in which some could have his own device on the network previously, by either Ethernet or custom implementation of WiFi-AP.

Commissioning will always be done on-network.
The device must be already on the network and WiFi/Thread credentials shall be already in place.
Ethernet must have the cable connected.
In all cases, the device must have a valid IP address (DHCP or Static IP).

Therefore, On-Network Commissioning method will be included.

Therefore, I think it's okay to have ESP32-S2 supported with respect to such user responsibility (or even with the feature of WiFiAP commissioning).

Yes, correct.

Is it available for some to build a custom device using matter data and interaction model?

We may consider it for future feature. At first, we'll focus on the Matter 1.0 device types as described above.
But given that ESP32 Arduino is based on IDF and ESP-Matter, it is always possible to add code from those two to an Arduino Sketch and We may consider it for future feature. At first, we'll focus on the Matter 1.0 device types as described above.
But given that ESP32 Arduino is based on IDF and ESP-Matter, it is always possible to add code from those two to an Arduino Sketch and create custom devices, as well as custom interaction models.

[HamzaHajeir]

@SuGlider Nice, that explains all, I was mixing between commissioning discovery and commissioning process, seems two different operations.

However, it seems that all Factory Data Providers would be 'custom' in Arduino, correct?

[SuGlider]

However, it seems that all Factory Data Providers would be 'custom' in Arduino, correct?

Arduino will set the Matter Device as a Testing unit using a VIDs allocated by the CSA for testing purposes.
https://developers.home.google.com/matter/get-started#vendor_id
No Real Provider information would be used within Arduino.

Commissioning will happen as defined in the description from https://developers.home.google.com/matter/primer/commissioning

Discovery may be done using BLE and/or WiFi AP, as described here: https://developers.home.google.com/matter/primer/commissionable-and-operational-discovery

[Fideus]

Hi, I created my own Matter RGBWW LED Spot. It works fine, but I'm not able to find any easy solution to give a device a unique code to setup multiple devices. Did I missed something?

[me-no-dev]

@Fideus the library is using development license, which can provide only one code. To get your own code, you need to have a device and apply for and buy certificatation from the appropriate authorities: https://matter-smarthome.de/en/development/how-the-matter-certification-works/

[me-no-dev]

You can setup the devices one by one using the same code and it will be OK

[SuGlider]

Hi, I created my own Matter RGBWW LED Spot. It works fine, but I'm not able to find any easy solution to give a device a unique code to setup multiple devices. Did I missed something?

As @me-no-dev said, the setup code for commissioning (34970112332) can be used for all the devices you may need in the same Matter network. Just commission one by one and each will have its own ID in the Matter environment.

Each device will be added to the Matter Controller with an Unique IPv6 address and each Matter RGBWW will be controlled individually by the APP (smartphone) or by an Automation.

Scenes and Groups can also be created for each Matter RGBWW light.

[Fideus]

Unfortunately this does not work with my google nest hub. As soon I try to add another device compiled with the same code, It will remove the old one, and the new one also isn't connected.

[Jason2866]

In general this approach is possible. In project Tasmota we use the development key for all devices which are setup as Matter device. It is no problem to set up more devices. So it is not an issue in general. Cant speak for this Matter implementation since the one in Tasmota is completely written from scratch (based on the espressif IDF Matter implementation) but Tasmota is written with actual Arduino Core.

[Fideus]

I can't find a way to connect more than 1 device to my google home nest hub.
Isn't it possible to generate different test devices (with same test vendor)?
Or is there any other idea to solve this?

[SuGlider]

Unfortunately this does not work with my google nest hub. As soon I try to add another device compiled with the same code, It will remove the old one, and the new one also isn't connected.

It sounds like Google has updated their APP and their device Matter firmware in 2025.

I'd suggest trying to update the firmware of your Google Nest Hub.

[Fideus]

The google Nest Hub is always up to date. II created a support ticket for that to google. Maybe they can solve that.
For the Arduino Matter library there isn't any chance to generate multiple different device ID's?

[SuGlider]

The google Nest Hub is always up to date. II created a support ticket for that to google. Maybe they can solve that.

I have an Alexa 5th gen here. It works fine. I have already added up to 8 endpoints using the same commissioning code, VID and PID.

For the Arduino Matter library there isn't any chance to generate multiple different device ID's?

We will consider that, for sure.
I will add this request to the feature list.