I am using a “splitting configuration” way with packages:
homeassistant:
...
packages: !include_dir_named conf
Got this structure in my %config% directory:
where the “conf” directory contains some subdirectories & files dedicated to different parts of HA:
It works fine.
Suppose a have a file “test.yaml” in some “/network/router/asus” directory for storing sensors, helpers etc. This file is made for testing.
When I create another file “test.yaml” in some other location - then this file seems to be just ignored:
- no sensors, helpers etc are created which are specified in this file;
- there are no any warnings & errors in Log.
I was explained that a package’s filename is used as a key. Since keys must be unique then package files should be with unique filenames.
Since files may be located in some subfolders - then probably these “keys” could include these relative paths, so they become unique. I propose to change a way how packages are processed to allow same filenames.