it should be, if it had been, I might have tried it on time.
There are links at the bottom of the documentation page to make suggestions or submit edits.
But IMO, if you are running pre-release candidates you should know these commands already.
I am unable to restore the backup. all addon are in this backup and now I can’t restore it.
Supervisor logs
23-03-29 22:56:34 ERROR (MainThread) [supervisor.backups.manager] Backup was made on supervisor version 2023.03.3, can't restore on 2023.03.2. Must update supervisor first.
23-03-29 22:56:47 ERROR (MainThread) [supervisor.backups.manager] Backup was made on supervisor version 2023.03.3, can't restore on 2023.03.2. Must update supervisor first.
and can’t update the supervisor
I fell idiotic here. But I am migraiton from HA docker on a raspberry pi to HA docker on a NUC. How do i actally restore the backup? The backup link is not visible on login page.
I did not spot the option to restore from Backup at the first prompt after re-installation.
How can I restore a downloaded backup when I have created a User/Pass already?
Settings → System → Backups → ⋮ icon top right → Upload Backup. Then reload using the three dots menu again. Then click your backup and select restore at the bottom of the pop-up card.
2 Likes
I am trying to restore a docker HA build but didn’t get any option to restore from backup before creating the account on first boot and I don’t see any dots in the backup page when logged in on the top right to allow me to load a backup? Does anyone have a suggestion on how to upload the backup?
There is no restore for container builds. You have to copy the files from within the backup to your system manually.
Deja Vu?
I just went through almost exactly the same scene… Look at this thread, particularly the last post where I summarized the solution.
Let me know if this helps.
1 Like
Ping “homeassistant.local”. What IP do you get?
There is absolutely no “security” in obfuscating your local IP address. Almost everyone here has a 192.168.1.xxx address (or 10.xxx.xxx.xxx) and even if a hacker knew your Home Assistant local IP address, it would be meaningless to them. Your public IP address, how the rest of the internet sees you, is barely more risky because you are probably receiving your public IP address from a DHCP server and that could change at any time. And you do have a firewall running.
My router and a DOS/CMD nslookup and ping all return the same IP address. I wasn’t trying to hide it as much as show I knew the value, and it’s on my local network.
A quick tip to anyone looking to perform a backup restore on Home Assistant OS: The restore process takes a long time and it will not be obvious how or if it is progressing.
In my case, for a >1GB backup file the process took over an hour on a RPi4, during which HA become unavailable in the browser and all the Supervisor logs said was that “Backup restore started” and “Home Assistant was stopped” for a very long time, which did not make it clear the process was progressing in the background and in fact I thought something has gone wrong and restarted the RPi.
So just be patient, it takes a while…
It depends on your hardware and the size of your backup. My 500Mb backup /restore only takes a few minutes on an Intel NUC i3.
Yes, the “Restore from backup” is no longer there. As in https://www.home-assistant.io/getting-started/onboarding/
Anyone know where it is now?
Same here, restore from Backup is Gone from the Onboarding Screen. How can I migrate to another device?
Ok, I dived into the Docs and found, that the Restore Option is not working, if you ran HA in a container (docker). I switched from RasPi to Docker, so that’s the reason why I have no restore button.
I get that to fix an SD failure will require physical access to the hardware running HA.
Occasionally though, upgrading to a new version of HA Core or HA Operating System, which can be done remotely from the other side of the world, may break something badly enough that the system becomes unaccessible, requiring the steps listed here (flashing HA to an SD card, swapping it into the hardware and restoring). [Example: I ended up in a reboot loop after the upgrade introduced a Linux kernel bug in the USB driver that my Conbee II stick relied on to be working, so it rebooted as soon as ZHA tried to start every time HA started].
It would be nice if there were a safe way to upgrade remotely, without this risk. Perhaps falling back to the original version automatically after a configurable amount of time (default 30 minutes?), unless the user has logged back in and confirmed that the upgrade is fully viable.
Feature requests go here: Feature Requests - Home Assistant Community
Or for this month only, here: Month of "What the heck?!" - Home Assistant Community (please read the pinned FAQ).