There are the main paths: /conf /media /share /backup
/conf store sqlite db of homeassistant but also of other addons (i.e. frigate)
By having both configuration and database storage file, in /conf lead to ambiguous roles of the folder.
I see one major issue to this:
When you backup: the backup files can be enormous (depending on your recorder settings).
It is not easy to get a fresh installation without historical data.
Yes it is. Just restore then delete home-assistant_v2.db
I am stunned by this answer which is worded as a solution but is missing the whole point. Let me rephrase it:
It is not easy to backup an installation without historical data.
You do not have the choice to backup a fresh installation = without historical data.
Therefore backups may be huge without need.
I am sure you can see the inadequacy of your solution now.
Thanks, I was not aware of this way however:
This is not visible through the expected settings->backups.
Either you choose full backup and you have media embedded.
Either you choose partial backup and you have to list all add-ons and folders.
This doesn’t solve the missing path which is leading to add-ons putting database files in /conf (or /media)
Conceptually it does seem wrong to put history in among settings. It’s like mixing /var/log in amongst /etc.
