Replies: 1 comment
|
I understand this is for those using the ESPHome Builder integration with Home Assistant? Am I correct in assuming that if base_url is left empty, everything will remain as is? If so, then yes, I like that idea. As for secrets.yaml, things are a bit more complicated, since the !secret directive won't work in that case. Of course, there's a way around this, but for now, the usefulness of this for the general public is debatable, unless you have a compelling argument. Otherwise, I'd be happy to see your PR. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I have the src folder of this repo as /config/guiton in my esphome install.
That is because I have other esphome devices that have their own config (and subdirectories) and would like to keep things organized.
And reuse the package for multiple displays.
In the main directory of ESPHome I have my display.yml file (created via the webUI).
I now try to build, but get an error about the files not being found:
Is it possible to resolve them, for example via a substitution of the base path?
Like this (for image.yml)
substitutions:
display_name: display01
display_friendly_name: Display My Room
base_path: "guition"
ENTITIES
weather_entity: "weather.home"
temperature_entity: "sensor.outside_temperature"
humidity_entity: "sensor.outside_humidity"
climate_entity: "climate.kamer_1"
SETTINGS
secondary_language: "ru"
timezone: "Europe/Moscow"
packages:
guition: !include guition/main.yaml
All reactions