Open Goodwillson opened 10 months ago
Yes, the build directory was moved inside the add-on so it wouldn't cause unnecessary bloat in config backups. What is the benefit of using that particular board file?
I wasnt able to convert all options from json file into platformio_options without some warnings during compilation. When I use the provided json file it goes smooth and I can reuse it in other devices without copying code, I guess thats main advantage. In the end I have solved it by copying the json file into docker image (docker cp /config/esphome/boards/lilygo-t5-47-plus.json addon_5c53de3b_esphome:/data/build/weather-epaper-display/boards/) Would be handy if there would be a way how to include board files like other includes, which are fetched from place where yaml configuration file is or even better from location outside of specific project folder, so it could be reused/shared between projects.
People seem to have success with setting esphome.build_path
back to /config/...
, per these instructions: https://github.com/Januznl/esphome-lilygo-t5-s3-plus
There's also https://github.com/esphome/feature-requests/issues/2370 requesting custom board support in esphome.
The problem
In previous versions was possible to save custom board configuration into /config/esphome/.esphome/build/[your-esphome-device]/boards directory. This location does not exist anymore. I didnt find path where I could access location which platformio looks for the configuration files by default. I guess it all happens inside plugin container now, which is not accessible from HassOS. I tried to set full path like boards_dir: /config/esphome/boards, but that doesnt work either. How I could make it working again while keeping the boards condiguration outside of yaml file?
Which version of ESPHome has the issue?
2023.9.3
What type of installation are you using?
Home Assistant Add-on
Which version of Home Assistant has the issue?
Home Assistant 2023.6.1
What platform are you using?
ESP32
Board
No response
Component causing the issue
No response
Example YAML snippet
Anything in the logs that might be useful for us?
No response
Additional information
No response