Odd Behavior Using Packages

Configuration
1

So I’d like to start using more packages to organize things better. I currently have a sub-folder called packages, and I am using !include_dir_named packages under homeassistant: to include those YAML files.

When I have just one YAML file in the packages folder, everything works great. As soon as I add a second file into the packages folder, the dark sky sensors in my first file (weather.yaml) won’t load on startup. It is so strange. The second file could be totally empty, and it still will break the configuration. What’s even weirder is that there are some components from the first file that still seem to load properly, such as groups.

I tried manually including the package file names instead of using the include_dir_names, same behavior. Having 2 packages breaks it.

Any ideas?

2

I had a huge problem with (just) that package. Maybe related to the python script?

I have like 5 packages together working fine.

3

Maybe…but it works just fine for me by itself.

4

Maybe a typo in the adress, packages: !include_dir_named packages.
In your example is say names in stead of named

5

Luckily that was just a typo in this post, not my config! Thanks for catching that.

6

Do you have multiple groups in your package.yaml?
I’ve ever had problems with more than two groups in a package.

7

Have you placed it in the top of the configuration file?

time_zone: Europe/Amsterdam
customize: !include configuration/customization.yaml
packages: !include_dir_named packages

8

Yeah, it’s in the right spot. I’m still working through troubleshooting this…doesn’t make any sense.