I had a problem with the ihost device and I had to reformat. I had both manual backups and the emergency kit with the key written.
I reinstalled everything, loaded my 2 backup files, when I tried to recover it rightly asked me for the password. I put the password of the emergency kit and it does not recognize it as correct.
I tried with a second backup, same problem.
and yet I had only one key generated in early January and my last backup is from this morning.
I spent 5 days configuring everything, creating maps, I have more than 200 devices between tuya, sonoff, etc, lots of rules and customizations and now I have to do everything again.?
because it does not read the key correctly.
But what is this encryption for? if it cannot recognize the emergency kit.
you are right, I forgot to write that
Yesterday an update of the home Assistant image arrived, to be safe I launched a manual backup and then I ran the automatic update via the ihost/docker utility.
after the reboot my HA was completely reset from scratch.
so everything could have happened via the update.
now I try those scripts to extract the backup file
Thanks
it seems that the password is wrong and yet I have only created one, I only have that one. I don’t know what to say.
I will try the other tools suggested.
result:
root@kubeprx03:/home/kubewall#
root@kubeprx03:/home/kubewall#
root@kubeprx03:/home/kubewall# python3 decrypt.py -i ha_202501090028.tar -p VQA7-83CH-XTC8-SXMB-5UKJ-SZDS-8ZU6
Extracting ha_202501090028.tar…
Extracting secure tar homeassistant.tar.gz…
Unable to extract SecureTar - maybe your password is wrong or the tar is not password encrypted?
root@kubeprx03:/home/kubewall#
Get files from password protected snapshot?, Probably instead of displaying the key I actually recreated it and consequently invalidated the old backups. This is what I remember doing in the past few days.
today I saw that in the HA (backup) panel it is no longer possible to display the BACKUP key… Better this way.
Given the urgency I recreated everything from scratch.
now since Cogneato corrected his script I will try again I will do some tests to decrypt both via HomeAssistant and through the script.
for now thanks to everyone.
ok guys I also tried the backup and restore from one type of hardware and version to another.
made a backup from a sonoff iHost hardware (HA Core version) through the HA interface (Settings/systema/backup) and recovered everything on a PROTECTLI FW4A mini-PC with the HA OS version installed.
Everything worked perfectly, and I’m talking about a complex installation with Tuya, sony, ewelink, synology, onvif, floor plans, automations, infrared, zigbee, zwave, etc… All devices and configurations perfect as on the source device.
good job guys. On some installations I can abandon proxmox because I had practically chosen only to be able to have a full backup of the image perfectly working.
With the new Backup and restore procedure I can rest easy.
Thanks
Hello, I’m sorry for asking here if it’s against forum customs, but I’ve been bashing against this for the last 5 hours.
I’ve managed to DECRYPT the backup file, then I encrypt them (edit: no encryption, just put compress into .tar file format) again (into .tar file format) to then try to upload them on my HA server (HA Green), but each time I try to upload no matter which browser (Firefox, Chrome, Edge, phone app), I’m then getting a Error 500 Internal Server Error.
Is there something wrong with my repacking method through 7zip → .tar?
I can not find anybody else with this issue.
I have also managed to that file ONTO the HA Green, through Samba Share, but it’s not showing up in the backups menu, so I can not initiate the restoring backup procedure.
Thanks guys.
It seems the built in restore still has some issues. I had re-installed HAOS from fresh.
When I tried restore I the key and it would noy work.
But I managed to run this script and it decrypted the backup files.
I am now creating a new tar and hoping it will work.