-
Notifications
You must be signed in to change notification settings - Fork 179
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to add ESP32-C6 to an existing Thread network (CON-1189) #953
Comments
@amroncz , can you please provide the below details |
@amroncz If you want to quickly try the light example with ESP32-C6 Thread enabled, you can choose |
ESP-Matter Commit Id: cd83d63
Unfortunately, that won't help me any further. I'm trying to learn how to use ESP devices and Matter using the example. So I'm trying to understand step by step what I need to do. |
Can you share your sdkconfig in the above case where you want to commission |
Here is my sdkconfig file. I use the Visual Studio esp-idf extension for the configuration. |
@amroncz , I have tried to reproduce the issue with esp32c6 and thread options enabled and my device got successfully commissioned over thread. You seem to be using |
@amroncz , any update on the issue? Please close the issue if it has been addressed. |
That worked for me. I was able to control the device via Matter over Thread with both Alexa and Home Assistant. Probably the clean build or erase-flash did it... Many thanks for your help @shripad621git |
Hello,
I have an ESP32-C6 and flashed it with the “light” example.
I used the exact example and didn't change anything. I was able to integrate my device with the example QR code (https://docs.espressif.com/projects/esp-matter/en/latest/esp32c6/developing.html#commissioning-and-control) into both Home Assistant and Alexa.
After I adjusted the values for the device for Thread as described here (https://docs.espressif.com/projects/esp-matter/en/latest/esp32c6/developing.html#flashing-the-firmware)
and flashed it again, I can neither integrate it into Home Assistant nor directly into Alexa via my Echo, which acts as a Thread border router.
The text was updated successfully, but these errors were encountered: