-
Notifications
You must be signed in to change notification settings - Fork 142
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
Clean install with current tree, Mar27 (CON-375) #285
Comments
Fix.... git submodule update --init --depth 1 |
Next error: Done. Made 6364 targets from 316 files in 365ms |
Fix.... cd connectedhomeip/connectedhomeip When rerunning ./install it stopped on: mkdir: cannot create directory ‘/home/jonsmirl/aosp/esp-matter/.zap’: File exists rm -rf /home/jonsmirl/aosp/esp-matter/.zap |
Next failure:
|
Fix: Previously I built and I was missing ESP openthread. So upgraded from idf 4.3 to idf 4.4. But I had run CHIP bootstrap while idf 4.3 environment was active and it recorded the 4.3 python environment. This run IDF 4.4 was active so the 4.3 python environment was gone. matter_idl had been installed into the 4.3 environment. So whack .environment and run . ./scripts/bootstrap.sh again. |
That was only part of the problem...
|
Fix... to do esp-matter CHIP build these modules need to be installed into the the IDF venv, not the CHIP venv.
|
ESP32S3 booted. Now try commissioning from Google Home. |
Go into light_switch example.... Switch over to my esp32c3
ESP32C3 booted. Now try commissioning from Google Home. Reboot ESP, try again, same thing. Check Android logs, nothing interesting.
|
Factory reset Google Home Hub. No difference. Plug iPad in to charge, maybe Apple will work. |
IOS and chip-tool are able to add the device. |
The Google failure is very early. It is not connecting to the BLE device correctly. I don't think it even gets into the Matter code. I get the new Matter device detected popup on Android phone. And I can use rRF Connect app from Android phone to connect to the ESP BLE devices. |
This build is failing because there are warnings, and this unrecognized command line option is causing warnings to count as errors. |
@jonsmirl I was able to build Could you please give it a try again? |
Is it safe for me to move esp32s3 and esp32c3 onto IDF 5.1 now? |
release/v1.0 branch (a tag should be created in a few days) will support Matter v1.0 with IDF v4.4.x for ESP32-C3/ESP32-S3/ESP32 IDF v5.1 for ESP32-C3/ESP32-S3/ESP32 is supported only on the main branch which will have Matter v1.1 The upstream hasn't officially released v1.1 yet. Also, IDF v5.1 release is scheduled around end of May. |
@jonsmirl Can you close this issue if you are able to compile on the main branch? |
Closing this. Feel free to re-open in case of any issues |
hi, how did you fixed this? |
You need to rerun the install.sh script in esp-matter root |
https://docs.espressif.com/projects/esp-matter/en/latest/esp32/developing.html#getting-the-repositories
This command is failing.
./connectedhomeip/connectedhomeip/scripts/checkout_submodules.py --platform esp32 --shallow
I am starting over from clean tree because I have lost any ability for Google to control my devices. Google is not making BT connection.
The text was updated successfully, but these errors were encountered: