Help to Better understand HA config

Configuration
1

My question is to better understand this process, and best practice.
Current running info:
Core 2023.11.3
Supervisor 2023.11.6
Operating System 11.1
Frontend 20231030.2

Here is a base scenario:
I use HACS to add a repository and install the “MOD”. The JS files any other needed resources are then stored in:
/homeassistant/www/community/ADD-ON NAME/FILES

Now for the discrepancies, when visiting GITHUB Read.me file, it states that the files should be stored in the config/www and that I should manually add the resources to the “Configuration.yaml” file.

My issue with this is that I am not sure how the HA is dealing with the information.
For example, when using NAGIOS, there is a command that says look in a folder and find any files that end with *.cfg

Is there something like that in HA that says store all data in config/www and look for JS files?
Should the data reside at the root of the www or can it sit further in to better organize and will HA recursively check?

The next question is about the manually adding the info to the YAML file.
In my experience in applications, you do not write to the main config file, you create a secondary file to better organize as well as protect the original configurations. Could I create a second Config file, call it “addons.yaml” and have HA pull from that?

2

That’s not a mod, and it’s not an add-on, it’s a custom card.

Add-ons are “other software”, and HACS doesn’t support those (the docs tell you that, and the install process gets you to confirm that you understand that).

Because the docs for that card assume you’re doing this manually. HACS doesn’t care what the ReadMe says.

For the frontend cards, that’s the resources.

Sure, HA won’t even care you’re confusing the terms :wink: Splitting your config is well documented, here’s what I do.

3

This is exactly what I was looking for, this is perfect.
Thank you so much, your example for splitting the config is perfect. Thank you

1 Like