force encryption without decryption tool is very stupid
True. This (an offline, standalone decryption tool) is actually something that we do need, and we need it soon. Some people were mentioning a python tool already exists, but I am not sure what tool they were referring to.
And in this context (forced encryption without a dedicated decryption tool) I will even agree with the “stupid” term 
Reading the announcement I assumed that I could at least specify a network location (e.g. samba share).
But there does not seem to be an “add location” button anywhere?
Settings / System / Storage / Add network storage. Once you add your network storage location, you will be able to reference it for the backups.
Sorry, typo on my part - should be Settings / System / Storage. Typed too quickly
I will edit the post to fix it.
Maybe it’s because of the containerized environment…
True, the external storage feature is only for HAssOS . But as the comments there say, if you are in containers, you can just mount any remote directory anywhere you wish inside the container - the sky is the limit
I am backing up with Add-on: Home Assistant Google Drive Backup will that continue to work as it has done until now?
And will the content of the backup stay the way it used to be unencrypted and with filenames that tell what component it comes from?
From my side all was said in other topic already. Just a conclusion: from 2025 version “backup” function is dead for me until “stupid” mandatory encryption is removed. I’ll find another way for this.
Just one light at the end of the tunnel: samba backup addon still works (so far…).
On my testsystem Google Drive backup is unencrypted and working as before and also backup from the commandline is possible to do unencrypted.
Automatic backups in HA and to Nabucasa is encrypted.
So if only an official statement that the old api will stay there is no problem as I see it.
The stupid encryption is the next step to leave HA for something else.
Why can’t you change the scheduled backup time?
04:45 seems a bit restrictive.
I configured the new Backup to only go to Cloud yesterday (10d retention, approx 300MB each) and am grateful for this valuable addition. Currently, as said in the ReleaseParty, the Nabu Cloud is the Backup of last resort and in my HA the existing SMB backup/purge Automation stays in place with 30d retention (good 10GB currently).
Super valuable extensions in my view would be the ability to
With SMB (unencrypted) I can browse and use the “Select what to restore”, I do not understand why browsing Cloud Backup from the HA GUI thows an “Unknown error”, shouldn’t it have the key …
Anyway - Rome wasn’t been built in a day - a very good start and as all existing Backup arrangements still work unchanged nothing should be broken.
I’ve not had that issue. My ‘Backup to keep’ custom setting is set at 10.
Do you have it set to days or number of backups?
I just wrote up an issue against number of backups.
Set to number of backups.
Interesting, maybe my issue is related to updating then.
Same idea from my side, automatic backup is a good idea, but the timing must be flexible, for example I made my backup on a NAS that is shut off for the night!
In this way I can’t use automatic backup
Do we have the ability to browse encrypted backups and only restores say a single file (assuming you have the key of course)? That’s by far my biggest issue with the current system as I’ve had the Google drive backup addon forever and it is incredibly good (in fact I think still might be better than this new builtin offering though it’s def a good thing new users won’t need a special addon).
I do agree, with may others.
The encryption on all backups is really daft, not being able to have the option to extract the contents is a step too far.
Just as an idea why not give the MANUAL setting an option to discard the encryption, this would then give you at least an option to check and see the content.
The way it is now feels incredible uncomfortable and vulnerable if I can’t be sure I can check the content and replace small portions and it would be useful if this addition was at least reversible in the core update.
The question is now, what should I do?
I think the answer is to reject this update until the Backup has been altered with options based on a user preference as I feel handcuffed with this version.
My proposal would be to do the update and either not use the new Backup config, all your existing Automations will be unchanged - or, as I did - only use the new Config for Cloud, as an additional in the 321 concept. If the Cloud Backup works fine in an emergency you won, if it doesn’t you are not worse of, as you are now.
