Hi,
Hoping someone can assist me, as im having a total facepalm moment.
I am wanting to properly deploy split configuration in my HAS instance, and what I thought I had done previously being right, however, it appears not to be
What I had done was, created a folder called “includes” and then created sensors.yaml, media-players.yaml, switches.yaml etc
I then called each of these from the main configuration file
However, what I found when I recently attempted to add things to sensors.yaml (thinking all sensors go in the one file) and things wouldn’t work!
I have read and read the splitting configuration documentation, but I don’t know why I cant fully comprehend it – sorry!
I am thinking, that each item needs its own yaml file? So for example, I would have a directory called components say, then inside that have subfolders called
Media Players
Sensors
Lights
Climate
Switches
Then inside those folders, have the yaml files, dependent on the component type, so hue would go into the lights folder, efergy and speedtest in the sensors folder and so on
Octoprint.yaml - for my ocoprint instances
hue.yaml - for all things hue
wemo.yaml – for my wemos
efergy.yaml – energy gateway
spotify.yaml – spotify
speedtest.yaml
Yamaha.yaml – for my Yamaha AVR
kodi.yaml – for my kodi instances
evovac.yaml – for my robot vac
and so on and so on…
Then, in configuration.yaml, I would add the line
sensor: !include_dir_merge_list components/sensors
switch: !include_dir_merge_list components/switches
light: !include_dir_merge_list components/lights