Hi everybody,
I am currently (once again 
) trying to get a more sensible structure to my configuration yaml files. I’d like to create a file containing yaml anchors that I need in multiple different files in that folder. Can you please help me figure out how to do this?
Example folder structure; the anchors.yaml file is the one I’d like to include in both packages/radiators/bedroom.yaml and packages/radiators/bathroom.yaml.
root_folder/
|- packages/
|- lights/
|- kitchen.yaml
|- livingroom.yaml
| (etc.)
|- radiators/
|- bedroom.yaml
|- bathroom.yaml
|- ==> anchors.yaml
This is an example for the current radiators configuration; it contains all radiators (so it is not -as in the example above- split into one file per room. This is fine, but since I have different things I want to happen in different rooms, I’d like to split it up in one config per room. But when I do, the current solution (below) that I am using will not work.
input_number:
az_morgens:
name: "AZ 08:30"
initial: 16.5
<<: &input_template
min: 5
max: 30
step: 0.5
icon: mdi:radiator
unit_of_measurement: "°C"
wz_morgens:
name: "WZ 07:45"
initial: 19.5
<<: *input_template
az being study and wz being livingroom; as per definition above, these two entities, that are currently in the same .yaml file would be in two separate files; so wz_morgens would not be able to access *input_template; my solution would be an anchors.yam file something like this (not sure about indentation here…)
<<: &input_template
min: 5
max: 30
step: 0.5
icon: mdi:radiator
unit_of_measurement: "°C"
Then in both wz.yaml and az.yaml I’d somehow have to integrate this file
az.yaml
!include `anchors.yaml`
az_morgens:
name: "AZ 08:30"
initial: 16.5
<<: *input_template
and
wz.yaml
!include `anchors.yaml`
wz_morgens:
name: "WZ 07:45"
initial: 19.5
<<: *input_template
However, if I understand yaml correctly, you can only !include something when it is behind a colon, for example sensor: !include_dir_merge_named sensor/… in my case, I’d somehow have to be able to just have !include anchors.yaml…
Can this be done somehow? Or is there another solution for what I’d like to do?
I am doing this because my packages/ folder alone is getting out of hand! I have too many subdirectories for things that don’t need them on one hand, and some files I was “forced” to combine because of this issue that should rather be separate files.
.
├── haus
│ ├── bad_oben_test.yaml
│ ├── gewitter.yaml
│ ├── grandfather_clock.yaml
│ ├── grocy.yaml
│ ├── neato.yaml
│ ├── notify_changes.yaml
│ ├── notify_jonna_trinken.yaml
│ ├── notify_script.yaml
│ ├── podcasts_gpodder.yaml
│ ├── r_arbeitszimmer.yaml
│ ├── r_draussen.yaml
│ ├── r_dusche.yaml
│ ├── r_kueche.yaml
│ ├── r_schlafzimmer.yaml
│ ├── routine_guten_morgen.yaml
│ ├── routine_tv.yaml
│ ├── spezialtage_sensor.yaml
│ ├── tasmota_schalter.yaml
│ ├── timer.yaml
│ ├── wecker.yaml
│ └── zeitsteuerung.yaml
├── heizungen
│ ├── baeder.yaml
│ ├── flur.yaml
│ ├── fritzbox.yaml
│ ├── heizungen_mit_template.yaml
│ ├── wohnzimmer.yaml
│ └── zeitsteuerung_heizungen.yaml
├── homeassistant
│ ├── anzahlen.yaml
│ ├── batterien.yaml
│ ├── browser_mod.yaml
│ ├── conversation.yaml
│ ├── customize.yaml
│ ├── customize.yaml.backup
│ ├── devices_im_netzwerk.yaml
│ ├── discovery.yaml
│ ├── downloader.yaml
│ ├── feiertage.yaml
│ ├── groups.yaml
│ ├── hacs.yaml
│ ├── influxdb.yaml
│ ├── locations_usw.yaml
│ ├── logbook.yaml
│ ├── logger.yaml
│ ├── mqtt.yaml
│ ├── neato.yaml
│ ├── notify.yaml
│ ├── panel_iframe.yaml
│ ├── recorder.yaml
│ ├── shellies_discovery.yaml
│ ├── shopping_list.yaml
│ ├── synology.yaml
│ ├── tankerkoenig.yaml
│ ├── tts.yaml
│ ├── unifi.yaml
│ ├── wetter.yaml
│ └── zones.yaml
├── licht
│ ├── bad_oben.yaml
│ ├── festlegen.yaml
│ ├── flur.yaml
│ ├── flux.yaml
│ ├── haustuer.yaml
│ ├── kueche.yaml
│ ├── licht.yaml
│ ├── scenes.yaml
│ ├── sonnensensor.yaml
│ ├── wohnzimmer.yaml
│ ├── xmas.yaml
│ ├── zwischenzimmer.yaml
│ └── zwischenzimmer_led.yaml
├── media
│ ├── alexa.yaml
│ ├── chromecast.yaml
│ ├── firetv.yaml
│ ├── firetv_tor.yaml
│ ├── kodi.yaml
│ ├── licht_media.yaml
│ ├── media_extractor.yaml
│ ├── mpd.yaml
│ ├── nvidia_shieldtv.yaml
│ ├── plex.yaml
│ ├── sonos.yaml
│ └── tv.yaml
├── misc
│ ├── caldav.yaml
│ ├── calendar.yaml
│ ├── day_of_week.yaml
│ ├── hundefutter.yaml
│ ├── jahreszeit.yaml
│ ├── mond.yaml
│ ├── sabnzbd.yaml
│ ├── sonarr.yaml
│ ├── soziale_netzwerke.yaml
│ ├── time.yaml
│ └── unifi.yaml
├── remotes
│ ├── broadlink.yaml
│ ├── button_schlafzimmer.yaml
│ ├── espurna.yaml
│ ├── zigbee2mqtt.yaml
│ └── zigbee2mqtt_networkmap.yaml
├── security
│ ├── alert.test_funktioniert
│ ├── cams_alle.yaml
│ ├── cams_dafang.yaml
│ ├── rauchmelder.yaml
│ ├── security_tor.yaml
│ └── security_unterstand.yaml
├── tasmota
│ ├── energyreset_total.yaml
│ └── tasmota_startup.yaml
├── telegram
│ ├── abfragen.yaml
│ ├── callback.yaml
│ ├── cameras_telegram.yaml
│ ├── jonna_trinken.yaml
│ ├── klingel.yaml
│ ├── telegram_bot.yaml
│ ├── tor.yaml
│ └── wuff.yaml
├── testing
│ ├── test_wled.yaml
│ └── zeittest.yaml
└── 00.yaml
Instead of all this, I could instead have one package per room (plus one for things that do not have a location, or work in multiple locations); but that’d require me to import the template somehow, as az.yaml would be in packages/az (containing all things related to the study) and wz.yaml would be in packages/wz with everything related to the livingroom…
THank you for your ideas 