NotificationsYou must be signed in to change notification settings
Fork7.8k
Star15.9k

feature(matter): New ESP32 Arduino as idf component Matter WiFi Only Example#12158

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Jump to bottom

Draft

SuGlider wants to merge3 commits intomaster

base:master

Choose a base branch

fromfeature/matter_wifi_example

Draft

feature(matter): New ESP32 Arduino as idf component Matter WiFi Only Example#12158

SuGlider wants to merge3 commits intomasterfromfeature/matter_wifi_example

+325 −0

Conversation

Copy link

Collaborator

SuGlider commentedDec 19, 2025

Description of Change

This is a sdkconfig example for Matter over WiFi only targeting mainly ESP32-C5, ESP32-C61 and ESP32-C6 SoC.
This project shall be built using Arduino as an IDF Component project.

Test Scenarios

Tested with ESP32-C5, Arduino 3.3.5 and IDF 5.5

Related links

Lib builder issueespressif/esp32-arduino-lib-builder#336

feature(matter): new arduino as idf component example

5e050d2

SuGlider added this to the3.4.0 milestone

Dec 19, 2025

SuGlider self-assigned this

Dec 19, 2025

SuGlider requested a review fromlucasssvaz as acode owner

December 19, 2025 19:23

SuGlider added this toArduino ESP32 Core Project Roadmap

Dec 19, 2025

SuGlider added the Area: MatterIssues and Feature Request about Matter Protocol label

Dec 19, 2025

github-project-automationbot moved this toTodo inArduino ESP32 Core Project Roadmap

Dec 19, 2025

SuGlider commented

Dec 19, 2025

View reviewed changes

idf_component_examples/Arduino_ESP_Matter_over_Wifi/ci.yml OutdatedShow resolvedHide resolved

Copy link

Contributor

github-actionsbot commentedDec 19, 2025•
edited
Loading

	Warnings
⚠️	Some issues found for the commit messages in this PR: the commit message`"feature(matter): new arduino as idf component example"`: type/action should be one of [`change`,`ci`,`docs`,`feat`,`fix`,`refactor`,`remove`,`revert`,`test`] Please fix these commit messages - here are some basic tips: followConventional Commits style correct format of commit message should be:`<type/action>(<scope/component>): <summary>`, for example`fix(esp32): Fixed startup timeout issue` allowed types are:`change,ci,docs,feat,fix,refactor,remove,revert,test` sufficiently descriptive message summary should be between 10 to 72 characters and start with upper case letter avoid Jira references in commit messages (unavailable/irrelevant for our customers) `TIP:` Install pre-commit hooks and run this check when committing (uses theConventional Precommit Linter).

👋Hello SuGlider, we appreciate your contribution to this project!

📘 Please review the project'sContributions Guide for key guidelines on code, documentation, testing, and more.

🖊️ Please also make sure you haveread and signed theContributor License Agreement for this project.

Click to see more instructions ...

This automated output is generated by thePR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with eachpush event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger isnot a substitute for human code reviews; it's still important to request a code review from your colleagues.
-Resolve all warnings (⚠️ ) before requesting a review from human reviewers - they will appreciate it.
- To manuallyretry these Danger checks, please navigate to theActions tab and re-run last Danger workflow.

Review and merge process you can expect ...

We do welcome contributions in the form of bug reports, feature requests and pull requests.

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by 🚫dangerJS againstdc45459