-
Notifications
You must be signed in to change notification settings - Fork 176
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
Installation of esp-matter failure (CON-1574) #1302
Comments
For more information, I upload the clone log, and cmd that I executed, please help to review any steps is abnormal. check hash log.txt the linux environment is below: |
@emesamwong can you please follow the steps mentioned in the programming guide Since you mentioned that Can you please setup esp-idf or use the existing one and then run You will have to remove the already present environment before starting again. NOTE: |
@shubhamdp Thank you for your reminder, but the problems have not been fixed. esp-matter install fail log (installed esp-idf).txt I checked that the /.environment folder has been removed before running ./install.sh
For more information, I tried to run ./install.sh in esp-matter release/v1.2, which was successful to install the environment, and switch back to release/v1.1 ((#548ef58 for esp-matter & #83f4163 for Submodule connectedhomeip) but failed to build the project with the below error: |
Sorry for the missing info of esp-idf for the "esp-matter install fail log (installed esp-idf).txt" |
From my checks on the connectedhomeip sdk side:
|
Describe the bug
A clear and concise description of what the bug is.
When I try to install the esp-matter, there is some abnormal message during Python setup stage. please refer to the esp-matter error log.txt
I checked the esp-matter & connectedhomeip status are clean

How could I do to solve this problem?
Environment
esp-matter error log.txt
Host Machine OS: linux
Host Machine Python version: 3.10
Commissioner app and versions if present: N/a
Home hub app and versions if present:N/a
Commissioner's logs if present:N/a
Any additional details
...
The text was updated successfully, but these errors were encountered: