Contains YAML files in a form of packages. See here for more details.
The main reason I use packages is to better manage configurations from automations to sensors in a way that makes sense to me. This is at the detriment of being able to maange them from the UI (Lovelace). To help with this, I do move things from packages to UI supported files and back again.
For automations, I use a caret (^) prefix to denote the automations are stored in a package and therefore cannot be editted from the UI.
I tried to split the files into three categories and a corresponding folder in /config/packages/:
- rooms - settings based on a room in the house.
- integrations - settings around an integration. If the integration was removed, then the package would be self contained.
- other - is stored in the root package folder.
The priority where settings reside is in the above order with the top being the highest priority. For example for a new light bulb in the lounge then it will (eventually) go into the /config/packages/rooms/lounge.yaml package rather than in the integrations.
The root folder contains files as a catch all for any files that do not fit the folder structure below.
Configuration organised by rooms in the house. This is probably a bad way of organising files however it makes it easy for me to recall why things sit.
Integration related configuration. It makes it easier to manage especially if the ingegration is added, removed, etc to have all the configuration in one place.
Something that does not naturally fit in any of the above goes into the package root folder.