Either I don’t understand the meaning of search, or I don’t understand your question. Decryption was discussed in posts #41, 65, 103, 134, 156, 185, 225, 227, 240, 243, 253, 306, 323, 361, 365, 414, 471, 486 … I could go on, but you get the point?
4 Likes
totally agree…
also could make a default disabled auto backup option (because of running out of space?! seriously?) (wich you could enable by a settings or something)
whole backup thing now is working not good…
try delete a backed up file… its still being there in home assistant as a backup. But you cant remove it becease file is gone…
Restore unencrypted by uploading also not working…
Yeah but no solution up until now!
Or did i missed it?
You missed it.
1 Like
See the below post:
2 Likes
For future reference:
-
It wasn’t “prematurely” closed. It was closed when the work was completed. There’s no obligation to keep the PR open after the work is done.
-
Since Home Assistant’s inception, Paulus has always had final say in all matters. Opposing views were aired and a decision was made.
If you disagree with this age-old arrangement, you are free to petition for changes (by starting a topic in the community forum, not in Github).
2 Likes
compiled version: Release v0.1 · sdotter/ha-backup-decrypt · GitHub
2 Likes
TBH he cannot been serious unless disconnected from reality.
If running out of space is the problem, the solution should be backup file retention. Not removal of the widely used backup feature.
Then I mention it again: backups should be located on a separate volume than the main system (to secure system stability in case backups eat all space).
For me, the only reason for auto-update removal was to fill the gap in achieving the goal: “all backups must be encrypted for any cost”. Then his answer was made up just to close users mouths.
3 Likes
Has anyone already tested whether the automatic backups with the “great new backup system” are recognized and listed after decryption by HA and can then be used immediately for a possible recovery?
If so, it would be great if someone with more knowledge could package the decryption tool as an add-on for HA that automatically decrypts all the backups that HA created…
1 Like
As for me, I will only change version if the google drive option is defined…
No 
Restoring an unecnrypted backup is not possible
Unless json in backup is also modified and changed etc…
1 Like
OMG. I didn’t know that. Thank you for the tip. It’s getting worse and worse 
2 Likes
Yes, I’m commenting on this very answer.
If auto-backup was causing piles of backup files stored infinitely (hence running out of space), then auto-backup should be responsible for the removal of older backups (backup retention). It shouldn’t be a big deal to implement that, should it?
Also, this auto backup was always triggered by user action. So what is the deal to inform a user that space on disk is running out?
There are dozens of ways how to cope with backups that make disks run out of space issue. This is why I don’t believe the reasoning he provided. It just doesn’t make sense.
It’s like: HA causes a lot of problems to thousands of users, thus let’s close the project.
3 Likes
The world has searched for sustainable resources… nuclear fusion… the perpetual motion machine…
This thread is the perpetual motion machine of HA.
It will outlive us all… the Earth… the sun.
It’ll be on the menu at The Restaurant At The End Of The Universe as reading material in between courses.
6 Likes
thx a lot for this!!!
I have added the support for extracting the whole .tar and decrypting all .tar.gz files in it in batch.
Here is the PR: Support extracting of .tar & decrypt multiple .tar.gz files by popy2k14 · Pull Request #1 · sdotter/ha-backup-decrypt · GitHub
My branch in my fork: GitHub - popy2k14/ha-backup-decrypt at popy2k14-multi-extract-decrypt
And compiled one for Windows here: ha-backup-decrypt/bin/Debug/net8.0 at popy2k14-multi-extract-decrypt-with-binarys · popy2k14/ha-backup-decrypt · GitHub
Usage is:
Usage: ha-backup-decrypt <input> <output> <key>
<input> encypted single tar.gz file or complete .tar backup with multiple encrypted tar.gz files
<output> output filename or destination directory
Have fun
3 Likes
Sorry, but this is what we are asking everyone to be patient on. Which is why I said:
1 Like
I want to thank everyone for the feedback so far, however it seems this thread has started to circle the same topics again with no net gain for the situation.
With that being said, the thread will be closing until Tuesday next week. It is a US holiday on Monday, so Missy will not return to work until Tuesday morning. Missy will be reopening the thread when she has the information everyone is seeking. Sorry for the inconvenience.
22 Likes
Thanks to everyone for your patience and understanding - locking down this thread was a last resort in order to maintain order, but always intended to be temporary this round. Since yesterday was a US holiday, I had to spend some time talking with everyone to ensure I knew where we stood after my last update. I’ll jump into the details for my update, though, with less fluff ahead of it to get to the point for y’all. 
A big caveat to this post is that I have no specific timelines yet
Here is where we are right now:
- We will re-introduce the option to backup on/before update for both core & add-ons.
- We’re going to introduce the ability to customize the time and days your system will backup on.
- We will also introduce an action to allow for any custom schedule and conditional in automations.
- Works in progress:
- We will implement turning off encryption with a per location basis.
- Except for Home Assistant Cloud - we will require it.
- We want to improve filenames to be more easily read and sensible.
- We will implement turning off encryption with a per location basis.
- As of 2025.1.3 - SSL information missing in backups has been fixed.
Lastly, we are approaching the next release - for my side of things this means that this thread will no longer be the appropriate place to leave feedback for this feature. I don’t want to lose y’all’s valuable feedback, so next Wednesday when Beta is live I will be locking down this thread and creating a Beta-specific backup feature thread to continue this conversation. When the next release goes live, we will be able to move the convo further into that blog post’s thread. I will point to those threads in the previous thread’s last comment when this happens - I won’t leave y’all digging for this because I want to have an active convo here but still need to maintain the organization of this forum.
That laid out now, this thread is reopened for discussion. A couple reminders: there is no need to discuss moderator actions on this thread - those are best left to DMs with the moderator and staff teams (review the Code of Conduct if you haven’t while you’re here); let’s keep the topic at the current statuses I mention in this post - I have no information on anything else at this time. Any replies moving forward not following these reminders will be removed without warning - this is the warning.
/statusUpdate
121 Likes