I have same issue - the file from the backup is homeassistant.tar.gz but when applying your script:
Extracting homeassistant.tar.gz...
Traceback (most recent call last):
File "/Users/papio/tmp/decrypt.py", line 145, in <module>
main()
File "/Users/papio/tmp/decrypt.py", line 137, in main
_dirname = _extract_tar(_inputfile)
File "/Users/papio/tmp/decrypt.py", line 89, in _extract_tar
_tar = tarfile.open(name=filename, mode="r")
File "/opt/homebrew/Cellar/[email protected]/3.9.13_1/Frameworks/Python.framework/Versions/3.9/lib/python3.9/tarfile.py", line 1625, in open
raise ReadError("file could not be opened successfully")
tarfile.ReadError: file could not be opened successfully
however the file homeassistant.tar.gz cannot be extracted from gz file as MacOS is not able to deal with that - what am I missing?
Yes, there have been changes on how the files are handled. The file format is now available as library.
The previous tar.py thus has been removed from the supervisor repo and the securetar files are now handled by the backup.py using the securetar dependency.
This is INCREDIBLY frustrating. I appreciate they are trying to protect our data but all this is doing is forcing me to not want to use encryption because I cannot just unzip anything with my password. I don’t want to have to restore a massive backup over 2 hours so I can get a hold of a SINGLE file to restore some mangled dashboard. The whole “you own your data” is kind of great in principle but in practice it’s so messy if you enable encryption with ZERO native tooling from HA. Why can we not browse our own backups easily damn it :*(. Ok sorry about the rant. I’m just waisting hours of my Sunday without really getting anything done.
