I’ve managed to restore my latest snapshot, and reach the files using SAMBA in combination with the static IP adress of the RPI. This opened the file folder with the backup folder and the config folder etc. of the Home Assisstant configuration.
I was able to back up the yaml files here, just in case. And to comment out the Haaska settings in the configuration.yaml file and save it. I was then able to reach the Home Assisstant configuration with the static IP again after restart. So guess something got broken with the Haaska or DuckDNS configuration.
I will save my snapshots without password protection from now on!
It’s like two factor authentication. It’s great when it works but if for some reason you need access without it, sorry, you are shit out of luck. The extra protection ends up working against you, but hey at least your data is secure.
Now I have arrived here, too, and yes, it worked like a charm.
However, why can’t HA Backup offer this decryption natively, i.e. without the need to first download the encrypted archive, then installing pip, then running decrypt-ha-backup?
If it is so complicated, nobody will use encrpytion of backups, which renders encryption useless - unless I’m missing a point. Am I?
But it seems impossible to select what should be restored, or am I missing that, too?
Let’s assume that something breaks, and the user wants to restore, but not simply overwrite an e.g. Lovelace card but just a part of it. Does HA Backup currently support this for encrypted backups?
And here it would be nice if decryption was possible from within the backup/restore function without actually overwriting everything, but instead saving the decrypted snapshot to a place from where the user could do more with it.
