Huh. Uh…lemme check in on this. You’re using Supervisor, yes?
Thanks for the confirmation. 
Although I would prefer to have more control of its deletion behavior, I can work with that arrangement; I will continue to create a manual backup (for any add-on that I wish to maintain a history of two or more backups).
BTW, I appreciate the team’s time and effort to improve the new backup system. This second iteration appears to include almost everything missing from the initial one.
It’s almost like the development team read our minds. 
No seriously, thanks for incorporating our feedback so quickly.
10 Likes
I am using Smart Recycle also on my NAS. Agreed, would be a nice feature (request) to have some kind of smart retention on HA natively somewhere in the future. Here a screenshot how Smart recycle is defined in Synology Hyper Backup world:
Hourly is of course too much 
But what about last 3 days and last 3 weeks or whatever as standard…
PS: again a feature, not beta related… Personally still very happy with 2025.2b changes.
2 Likes
Well, from my side I’m going to say: thanks for listening! Pretty much all that we wanted is back. Only thing i can’t see (yet?) is possibility to create a (hacs addon) backup before each addon update.
And option to turn off encryption is perhaps a bit too hidden, it took me a while to find it. At start when i set up backups it seems that nothing has changed, encryption is still mandatory, i can turn it off only at a later stage, so it’s a bit confusing. But it’s there, that’s most important.
At the end: my humble suggestion is that when such big changes are planned, please do public research before you implement them. All bad words, hot heads,… could have been avoided this way, don’t you agree?
HACS has nothing to do with Add-Ons. HACS are Custom Components and should be backupped together with your HA Core Backup, as they are in a subfolder of your /config folder.
The Add-Ons backup feature has been brought back and improved upon:
- Return of the backup toggle
- Now turned off by default
- Shows when you last backed up below it
- Syncs before updating
- Separate add-ons toggle specific to them
2 Likes
Oh… now you made me confused… i was under impression that hacs addons were also creating backups when updated… now i’m not that sure anymore… it could be that this was only on HA store’s addons…
But, i can easily install earlier version of hacs addon, that’s true.
I’m not using HACS anymore, but in the past HACS itself had no backup feature, but you can always easily select the specific version you want in HACS if you have a “broken” update of a HACS component.
And the HA Automatic Backup contains the /config/ folder which should also include the /config/custom_components/ folder where most HACS Components are stored.
So you could also download and extract one of those backups and restore a specific folder to your custom_components folder.
HA Add-Ons are just repackaged Docker containers, so are completely different from HACS Custom Components.
1 Like
There are no addons in HACS. It says so repeatedly when you install it.
3 Likes
Sorry for the missing system information, it is now:
- Core 2025.2.0b1 (yesterday 2025.2.0b0)
- Supervisor 2025.01.1
- Operating System 14.2
- Frontend 20250129.0
RaspberryPi 4B with USB-SATA-SSD.
Only local storage for the backups configured.
It was late yesterday so instead of a screenshot I just copied the cli output.
Even today I still don’t get “readable” filenames.
The backups from January 29th and 30th were all created with the beta and “automatic backup”.
Access to the backup directory of HA via the Samba-Share AddOn:
No need to be picky. We all know (except from you, perhaps?) what means “addon from HACS”… and we all know where they are actually stored… 
this issue might still is an issue,
But if you need a fix now, just install HA and restore the backup afterwards, that really doesn’t matter.
I know i can do it manually, but it does not work as of the documentation and i think it might fit to fix in this release.
I have the same with the b1 release. Did you already report it on Github?
Thank you! Turns out we’re still working on getting filenames adjusted in beta - you’re seeing the expected result for now. I’ll edit my OP for that line.
+1 Been there, done that and I totally agree! WOW was my first thought too. I was shocked at how quickly these changes were implemented. Very impressive.
To @MissyQ and the entire HA team, thank you for listening to the feedback and acting upon it. Kudos!
6 Likes
Oh, this sounds great – thanks for listening and taking positive action! 
When I’m on the other side of this nasty flu, I’ll try finding time to getting a beta running on a test RasPi 
Small suggestion: if you’re not already doing so, consider adding a bit of variance to the default nightly backup time – spreading it out over a random 30-60min time range, to reduce the Thundering Herd impact on your cloud servers. (Probably something that should only be done for Nabu Casa destination, and user-controllable if the user sets their own specific time).
lost the overview of requests tbh, so let me ask here:
did someone already mention/request configurable time slots for backup per location?
Asking because I am fine with the default settings, except for my local Synology location, which is down during those hours.
Id love to be able to customize that time, and did just now, but then it uses that for all configured locations.
I believe this situation is why the automation action was implemented - but even then, as I understand it, it is still triggering the whole configuration and not a targeted destination. Let me verify.