-
Notifications
You must be signed in to change notification settings - Fork 659
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't restore addons from a backup in Supervisor 2022.03.2 #3497
Comments
I am getting this too, after installing supervisor 2022.03.2 and losing access to my supervisor page, I prepared a new rpi3 with 64bit image. I restored my full snapshot and everything restored except all the add-ons. I thought this was because I moved from 32 to 64bit but maybe not? |
No. I have the same problem from 64 to 64. It's a supervisor problem |
Same here. Can I somehow install an older supervisor version? Bad timing, I wanted to re-install due to issues with my storage :( |
I found that, if you install the addon on the new system, without starting and configuring anything on the addon, you can restore the addon from a backup to import your previous configuration and it works. The problem is restoring an addon when it doesn't exist on your system (that is a normal behaviour when you try to restore a full backup) |
Does this work around restore the folders? |
No. For the folders you have to unzip the backup file and copy the folders manually to your home assistant instance :-( |
I am having this issue with a 2022.03.3 to a 2022.03.3 transfer. https://discord.com/channels/330944238910963714/944337294389805056/951492809033138247 |
Can confirm that for me atleast installing the add-ons then rerunning the restore works. |
The error seems clear. Try to find some data of the installed addons (I think the slug). Since the addon is not installed, it throws an unhandled exception. The question is: Is not there a beta program for the supervisor releases? Was not this error detected before releasing the new supervisor version? (Especially when we talk about a component that you have no choice to install, not install, doing a rollback...). Many people have suffered this problem without being able to restore backups, in some cases with serious consequences |
Indeed, though it might be nice to point the user in the direction of "Have you installed the add-on?" |
I don't think this is the right direction. The addon should install itself automatically, as it has always worked. Just they have had a coding error, something very common in programming. The problem is not having detected it in the testing phase, especially when it is a component that autoupdates itself without user permission |
Looks like @ludeeus is on it :D |
After upgrading the supervisor and restoring all my Zigbee devices are gone in the Zigbee2mqtt add in. I guess that is related to this somehow. Got no lights in the house now :( |
It may be related to this one: home-assistant/core#67780 I hope not because I'm planning to install Zigbee2mqtt to see if it works around the ZHA problem. |
@mdegat01 please, don't forget to do a release as soon as possible. Backup and restore is not still possible for us with the actual release... |
Describe the issue you are experiencing
Cannot restore any addon from a backup when the addon is not installed on the system
What is the used version of the Supervisor?
2022.03.2
What type of installation are you running?
Home Assistant Supervised
Which operating system are you running on?
Debian
What is the version of your installed operating system?
Debian Bullseye (aarch64)
What version of Home Assistant Core is installed?
2022.3.3
Steps to reproduce the issue
...
Anything in the Supervisor logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: