Closed f0rdprefect closed 3 years ago
I can reproduce the issue here, so looking into it now.
Found it already. The substitutions:
component doesn't like being in the config file on its own.
When you provide one or more keys, or comment out the substitutions:
line, then it will work.
I will update my example yaml to not have this error, and I will check if an improvement can be made for ESPHome on this.
I updated the example.yaml
file in the dev
and release/2021.10.0
branches.
As a quick fix, I included the name
and friendly_name
keys by default, so an unmodified compile from the example.yaml
will now work.
Thanks for the issue report, @f0rdprefect
Yes, I can confirm this helps. However looks like something is still missing:
***** [.pioenvs/bedside-lamp/.pioenvs/bedside-lamp/x509_crt_bundle.o] Source `.pioenvs/bedside-lamp/x509_crt_bundle.S' not found, needed by target `.pioenvs/bedside-lamp/.pioenvs/bedside-lamp/x509_crt_bundle.o'.
**
Will double check the release branch now! Thanks for the prompt response @mmakaay
Same error.
Generating assembly for certificate bundle...
CMake Error at /home/matt/.platformio/packages/framework-espidf/tools/cmake/scripts/data_file_embed_asm.cmake:26 (file):
file failed to open for reading (No such file or directory):
/home/matt/src/esphome/bslamp-guest/bedside-lamp/.pioenvs/bedside-lamp/x509_crt_bundle
even tried to update platformio and clean the cache. platformio is no version 5.2.2 ...
I compiled the firmware using an unmodified example.yaml file.
That worked, without the error that you saw.
I do see the file .pioenvs/bedside-lamp/x509_crt_bundle.S
in the build output.
Can you try a clean build? I don't think that should matter in this case, but I have seen some strange compile issues with ESP-IDF that were resolved by a clean build.
clean build does not solve this. I believe this will haunt us some more time. See https://github.com/espressif/esp-idf/issues/7631#issuecomment-934212224 for details. Anyhow the initial issue is solved and I will look into how to apply the workaround...
And this is the workaround (for now...) https://github.com/espressif/esp-idf/issues/7621#issuecomment-950135638 at least for the command line
Thanks again!
Great! Thanks for sharing the pointer to the work-around. I hope to never need it :-)
just took the example.yaml and supplied a secrets.yaml
when I do a
esphome config example.yaml
I get
not sure who is to blame. However I successfully compiled a new project created with
esphome wizard
to confirm my installation is working in principle. Any idea what to check or try? Thanks for this awesome project!