The backup on update incrementals mainly, which no longer exists
2 Likes
How do we get notifications and the status of the revamped backup?
1 Like
True, but the maintainer of the integration should!
I never use a backup for going back versions of core.
ha core update --version
is what I use. It only won’t work if the update you are backing out of has changed the database version.
Ye gods, is this thread still going? 
8 Likes
/rant on
I’ll add my two cents here FWIW. I thought I could live with these different changes, in spite of being in agreement with many of the protests appearing above (forced encryption in particular).
But, I just updated to core 2025.1, and find that when I go to System/Backups, there is no longer a button in any of the pages available from there, to create a manual backup! What the hell! How do I kick off a manual backup now? Please don’t tell me to create a button on my dashboard, or an automation.
Although the idea of automated, encrypted, (free nabu) cloud backups is well intentioned, the developers have emasculated everything we had before to do backups.
If I missed something and there is a button to create a manual backup à la previous versions, somebody please tell me.
/rant off
IIRC I think you have to go through the initial backup setup now (encryption key is generated in this step). After that you will get Manual backups category and also Backup button with a dialog - Automatic backup and Manual backup.
So now you’re forced to do initial backup setup even if you only need Manual backup option. Also creating manual backups takes more clicks now.
And of course your manual backups will be encrypted if you creating them in Backup Setting UI.
2 Likes
Nope. No joy.
See the reply just below yours. One has to set up automatic backups (even if you don’t want them), just to get the backup button. To get manual backups back up and running. But encrypted. Geez.
3 Likes
You are right. I must say, it doesn’t get prettier the longer you look at it.
1 Like
I am fine with initial backup setup, but at least bring back option to disable encryption! 
2 Likes
This exceedingly simple script will give you an unencrypted backup. I just tested it. Of course, it should be improved to ask for a name and perhaps some other parameters. But it works.
1 Like
I want to keep using built-in manual (unencrypted) backup from backups settings UI. No addons, scripts or automations.
3 Likes
Totally agree. But in the meantime…
Meantime I have my good old unencrypted backups from 2024 and I do not plan to make big changes in my HA setup
I have some encrypted backups too and I hope that I would avoid using them 
1 Like
Please…
Do not force encryption (or anything) on an user.
This actually goes against the “Open Home Foundation” Ethos.
Give the USERS the option to select what they want - Mandate nothing.
You don’t mandate what we use it for, how we use, what we connect to it, how we connect to it, what options we select, or what options we avoid.
As soon as you mandate it… it’s no longer an option - and options are what the Open Home Foundation is all about.
Someone could just fork it and put the option back.
Start the “Truly Open Home Assistant” Fork
Ahh… The perils of Open source - you can actually have it both ways.
(I would just prefer to see this fixed… I hate following the fork tree.)
You finally found a way to put in encrypted backups…
GREAT!
Now, put in the option turn it off. Thanks.
16 Likes
Hey @parautenbach - did you find a solution to this? My Shelly HT has disappeared, too, and I’m pretty sure it happened when I upgraded HA.
I posted this in the beta thread since that’s what I originally landed on in my Google search, but for the sake of completeness and being annoying, I’ll repost it here since this seems to be the proverbial watering hole on this topic.
I need to throw my hat in the ring here.
I too work in InfoSec.
Thank you to those with awesome relevant posts outlining practical experience from production environments.The bottom line is that forcing encrypted backups on users is most certainly a disservice to the community and does not increase security in any practical way. Encryption keys will be improperly stored by all but the most savvy users. I GUARANTEE IT.
This just feels like a CYA move more than anything. I’m failing to see how this will provide any real value to the community. To be clear, my argument is NOT to negate the value of encrypted backups, but to challenge the decision to force it. Every environment is different and with the focus on providing customizability and uniqueness in HA, this move really has my head spinning.
Let’s not forget that at its core, security is about reducing the risk of unauthorized disclosure, modification, or denial of access to data. If this solution has the net impact of locking people out of their data down the road for the reasons touched on in this thread, these changes actually increase risk not reduce it.
Nothing is 100% secure.
Nothing is 100% risk free.
If it’s so secure that that no one can use it then it isn’t secure at all.
8 Likes
We do need to understand that this is most likely the first step in the developers setting up a more security-minded system. Yes, right now it’s annoying for users like us that would like to view the contents of our backup files, but I do believe they will provide a tool to decrypt them as well as the option to not encrypt if we prefer.