Base Files and folders duplicated somehow. Why, and how to fix?

Hi Folks!

As you can see in the screenshot below, somehow my file structure has been duplicated. I noticed this after 2024.1.0, but I don’t go into folders that often, so not sure when this happened. Surely after 2023.10.
Anyhow, this is my current file structure, as you can see, there’s a “Homeassistant” folder, that contains the same subfolders and files as the “Config” folder. Including configuration.yaml
I know I didn’t do this willfully, nor do I have any automations that should do this. The only addon that I use that I can think of, that could be the culprit, is the google drive backup utility, but that only copies my entire HA instance to google drive.

Did we have a structural change in how HA stores files and folders, and I just missed the announcement? If so, can I safely delete the duplicates? Which one is the “currently used” part?

Not a complete newbie, but I’m only completing 1 year with HA. I did search and did not get a single hit, so please be kind. :slight_smile:

If relevant:

Running Home Assistant OS on a RPI4, 8Gb, with a 128Gb ssd as storage. Zigbee dongle ConbeeII is the only other thing connected to the RPI. Below are my integrations and addons:

How do you get that list?
I only get the “homeassistant” directory from the File Editor add-on and from SSH add-on.

I assume (but don’t know 100%) that the “config” folder could be deleted

I changed my base folder in VScode to be the root folder for home assistant. Don’t remember how, but I’ll look it up. I think it was because I needed to access some OS files a while back.

The strange thing is I know for sure that this is recent. Before I only had the “config” folder, and the “homeassistant” folder is nested inside the config, so that would be my guess as to which one to delete.

So, doing a little digging, and experimenting, I found this topic:

I also found that, when I changed one config.yaml file and restarted HAOS, the change was reflected in the other file, so my guess is this is just a glitch.
I’ll wait a few days before marking this as a solution as others might have more insight.

It is not a glitch, it is on purpose.
“config” was the old name for it which is (currently) being kept for legacy purposes (many guides still use that name) during a transitional period.
“homeassistant” is the new name, and the one you should start using.

(this applies to this (and some other addons), some add-ons will still only have “config” and some will only have “homeassistant”, and some that does not need access to it will not have any of them, this is up to the add-on author to chose)

These folder names are names inside the add-on you view them from.
On the host they all point to the same place.