Skip to content
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

Closed
amroncz opened this issue Jun 6, 2024 · 8 comments
Closed

Unable to add ESP32-C6 to an existing Thread network (CON-1189) #953

amroncz opened this issue Jun 6, 2024 · 8 comments

Comments

@amroncz
Copy link

amroncz commented Jun 6, 2024

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)

ESP32-C6 supports both the Wi-Fi and IEEE 802.15.4 radio, so you can run Wi-Fi or Thread matter example on it.

To enable Thread, you should change the menuconfig options to CONFIG_OPENTHREAD_ENABLED=y, CONFIG_ENABLE_WIFI_STATION=n, and CONFIG_USE_MINIMAL_MDNS=n.

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.

@github-actions github-actions bot changed the title Unable to add ESP32-C6 to an existing Thread network Unable to add ESP32-C6 to an existing Thread network (CON-1189) Jun 6, 2024
@shripad621git
Copy link
Contributor

@amroncz , can you please provide the below details
ESP-Matter Commit Id:
ESP-IDF Commit Id:
SoC (eg: ESP32 or ESP32-C3): ESP32s3
Device Logs (Please attach the log file):
Host Machine OS:
Commissioner app and versions if present:
Commissioner's logs if present:

@dhrishi
Copy link
Collaborator

dhrishi commented Jun 6, 2024

@amroncz If you want to quickly try the light example with ESP32-C6 Thread enabled, you can choose ESP32C6 in the thread_light option in ESP Matter Launchpad

@amroncz
Copy link
Author

amroncz commented Jun 12, 2024

@amroncz , can you please provide the below details

ESP-Matter Commit Id: cd83d63
ESP-IDF Commit Id: 3b8741b172dc951e18509698dee938304bcf1523
SoC (eg: ESP32 or ESP32-C3): ESP32s3
Device Logs (Please attach the log file): esp32-c6_logs.txt (the logs say something about wifi everywhere, although i have followed the steps to switch to thread as described above. is that my problem yet?)
Host Machine OS: Microsoft Windows (Version 10.0.19045.4412) with WSL (Ubuntu 22.04.4 LTS)
Commissioner app and versions if present: Amazon Alexa (Version: 2.2.567992.0), Home Assistant Companion App (2024.6.1-full)
Commissioner's logs if present: -

@amroncz If you want to quickly try the light example with ESP32-C6 Thread enabled, you can choose ESP32C6 in the thread_light option in ESP Matter Launchpad

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.

@shripad621git
Copy link
Contributor

Can you share your sdkconfig in the above case where you want to commission esp32c6 over thread. From the logs, it seems that the options you had set are not enabled in the sdkconfig.

@amroncz
Copy link
Author

amroncz commented Jun 17, 2024

Can you share your sdkconfig in the above case where you want to commission esp32c6 over thread. From the logs, it seems that the options you had set are not enabled in the sdkconfig.

Here is my sdkconfig file. I use the Visual Studio esp-idf extension for the configuration.

sdkconfig.txt

@shripad621git
Copy link
Contributor

@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 idf v5.2.2. I have tested the things with the idf v5.2.2 setup as well. The device gets commissioned successfully over thread without any wifi logs.
You can try the steps below and get back:
i) Please do a clean build using rm -rf build sdkconfig sdkconfig.old managed_components dependencies.lock.
ii) set the target as esp32c6 using idf.py set-target esp32c6.
iii) Enable the thread related options you mentioned above.
iv) Flash the app using idf.py erase-flash flash monitor and commission the device using alexa or apple.

@shripad621git
Copy link
Contributor

@amroncz , any update on the issue? Please close the issue if it has been addressed.

@amroncz
Copy link
Author

amroncz commented Jun 20, 2024

@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 idf v5.2.2. I have tested the things with the idf v5.2.2 setup as well. The device gets commissioned successfully over thread without any wifi logs. You can try the steps below and get back: i) Please do a clean build using rm -rf build sdkconfig sdkconfig.old managed_components dependencies.lock. ii) set the target as esp32c6 using idf.py set-target esp32c6. iii) Enable the thread related options you mentioned above. iv) Flash the app using idf.py erase-flash flash monitor and commission the device using alexa or apple.

That worked for me. I was able to control the device via Matter over Thread with both Alexa and Home Assistant.
Alexa indicated that it was not a valid Matter device, but I had that with Matter over Wifi too and the configuration still worked.

Probably the clean build or erase-flash did it...

Many thanks for your help @shripad621git

@amroncz amroncz closed this as completed Jun 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants