Thanks this works!
Same here. Hard reboot helped with that. Thanks!
Hi all, i moved from a Pi to Synology - after doing the resore, i re-started the Pi - backed up the Add ons, shut down the Pi - re-started the VM on the synology and restored the add ons only - worked fine.
I had the exact same issue and it was fixed by the advice of kennethpangky. A restart does not work but shutting down, unplugging and booting back up fixed everything.
Just noticed that the ha supervisor CLI tool has a repair command. Has anyone given this a shot to see if it fixes things?
Tested. Did not do anything for me.
Well.
I tested installing Add-Ons before restoring, did not help for me.
Also tried ha supervisor repair, successfull output but did not help.
However, after some time and multiple shutdown-turn-on half of the addons was colored and working, after one more restart all of them was ok.
Maybe just time is needed?
2 Likes
Complete Shutdown worked 100%
In July 2023 this is still a problem. My Pi3B did not survive an upgrade because of corrupt SD card. I recovered the full backup onto newly flashed SD card and my add-ons refused to load even when tried starting them manually (i.e. File Editor). Others like ESPHome semi-worked until I tried upgading them, then stopped working completely.
I tried Shutdown option, unplug power, boot again and it worked.
This is a very late response, but thanks to all of you guys, I ran in this issue yesterday and after trying everything found this post, I could fixed my HA already. I’m very thankful
System restart worked for me as well. But it is important not only to restart Home Assistant but the whole system. Then it worked again.
Same issue: add-ons greyed out. Hard restart (power-down) worked for me.
Home Assitant Core version: pre migration 2023.8.3, after 2023.9.1
1 Like
Thanks, great solution! For other novices that may need a tiny bit more detail to TL;DR, here are a couple of things I discovered on this and other posts. The version of HA I used was the latest as of early December 2023.
-
Once you have a Full backup of your working system, an easy way to get it off the HA box is double-click the backup to bring up the backup’s dialog, click the three dots, and Download backup (to your PC drive). Finding out how to download almost killed me.
-
Once you have booted your newly formatted Home Assistant, you can click the link to upload your saved backup without having to create a throwaway user. Note however if your backup is large you may need to create a user then immediately repave your new install by using the three dots top right of Backups page to upload then restore the backup saved to your PC. Browse around for those threads.
-
If you haven’t run across this, you may be wondering where the “Reboot system” is. Thanks to @kennethpangky and others, I can also confirm this is the magic that properly restarts the add-ons in the new install after restoring the backup. Here is how to find Reboot from the Settings screen (saver than a power cycle reboot):
I hope this saves at least one other person the hours it took me slogging through various posts to get this down to a very few steps (but thanks to those other posts for eventually getting me here!).
One other note, in my case, the spinner that started at the beginning of the restore never went away. I went to lunch and when I returned switched the browser to http://homeassistant.local:8123/ in order to get to the Reboot button.
3 Likes
Can even do a full restart using the extended options in UI. Same issue still in 2023.12.3 - and same solution. All addons shown as running after full system restart. Thanks for your post!
1 Like
Just to add to this in case it helps. I did a full backup from my TrueNAS HA and then a full restore on new NUC hardware. The restore screen was spinning around for a while but I found I could access the restored version from another window in the meantime. I left the restore window overnight but it was still there in the morning. I could still access the new version but the addons were greyed out and not working. I came across this thread and decided to be brave and do a hardware reboot. I can confirm the hardware reboot worked thank goodness! Also simply moving over the SkyConnect dongle worked flawlessly as well.
This thread helped me, but it is pretty wild that this issue has been known for two years and still exists.
I had this same problem after restoring a backup to a Raspberry Pi 4B, reboot did the trick, this is still a problem on 2024.4.3.
1 Like
Still an issue with 2024.5.4 when moving from a RPi3 to RPi5. Hard reboot seems to have gotten the addons working again.
Still had this issue on 2024.6.3, but hard reboot helped
Yeh wild. After a restore it would probably be a good idea for it to do a hard reboot anyway.