Seems a nice solution. I will try that!
FYI: I’m migrating from x86 to VM on Synology
Same issue here and I am running 8.5
I was in the same situation, but after reading your messages I just tried restoring only the add-ons again. I mean, they were not working but they were restored from the landing page. When restoring them for the second time everything is working.
I hope it helps. Regards.
Thank you guys for all the tips.
Ii actually managed to get a clean working install after many tries (and reproduced iit, thanks to the inputs of @factorial, @sme79 , @Protechtedd , @overkill32 )
So the process is quite easy 'even if i still think that it should be working directly and this is a workaround). Actually for some reasons, the restore does not manage to install the addons properly. They are then fully functional (once started) but supervisor does not see them as up. So if they have an UI you cant access it (ex. Deconz, tasmota etc…)
Prerequisite: a full backup your instance
- Get yur new syste ready (eg. Burn the new sd or whatever) and let it start
- Do a partial restore, with everything (configuration) but the add ons. Note the addons you have
- Install all the add ons from the addons stores (you may have to reimport custom repositories if you use community addons). No need to configure them at all.
- Then restore the backup again, but jus the add ons this time,
Voila
PS I am really used to HA working so well that i think this should be fixed. the issue is restoring an addon without installing it. As a developer myself (not contributing to HA because i am not a python fan, i a pretty confident this is easy to fix)
Thanks everyone for the great job
10 Likes
I had the same issues and was about to follow your steps.
However I did a complete shutdown and reboot of the hardware - restarting via the UI doesn’t solve the problem. And when it booted up, all the addons were back and running. Not sure if this is the solution, but in my case it seems it a hard reboot fixed it.
29 Likes
Upgraded from Rpi 2 → Rpi 4 can confirm hard reboot fixed the problem.
3 Likes
I had the same issue, but hard reset (unplugging RPi from power) did the trick! Hopefully this will help others.
5 Likes
Great many thanks. Exactly this solution is working!!. How easy 
I had the same issue upgrading from pi3 to x86 (both hass os). Add-ons displayed as not started despite supervisor logs showing a lot of “XXX already started!” warnings. Did a partial restore (add-ons only) from the same snapshot used for the initial restore followed by a host reboot and everything is working now. I’m not sure if the partial restore was necessary. Thanks to this thread to help me resolve w/o rebuilding from scratch!
I had the same problem, that after the snapshot restore the addons no longer worked. For me, the solution was quite simple.
I restarted the host, after everything had booted up I only restarted the Pi via “Restart”, then everything worked again.
Homematic also found the devices again.
System Respberry Pi 3, second system Raspberry Pi 4 with 4GB
2 Likes
++ migrated to a new eMMC Module this morning and the hard reboot (and some patience) resulted in not having to do anything crazy
1 Like
Migrated from HAOS VM to Pi 4 - hard reboot solved the issue. Migrated HACS as well.
2 Likes
Hard reboot solved the issue in 2022.9.5. I had to restore from a snapshot and the add ons couldn’t be started. Thanks!
4 Likes
For anyone that cannot find the hard reboot, its under Settings > System > Hardware > 3 dots at the top > Reboot Host
(Restart from the Developer options page did not fix the add-ons not starting, Reboot Host did)
This resolved the Add-ons not starting after restore. Many thanks for all of the suggestions!!
Not sure why this option is hidden under 2000 clicks, took me 10 minutes to find a simple reboot, but there we are, better option to just tanking the power to RPi.
4 Likes
Thank you!
I just restored from backup and had the add on issue. Power cycling fixed it.
Z wave network is incredibly slow but I am hoping a heal + waiting overnight will improve things
Absolutely, it worked for me. 
Can confirm, was in the same boat.
Migrated from RPi3 to RPi4 and did a full restore - add ons showed they were working in the logs but would not actually turn on.
Instead of wiping everything and going through the restore process with partial backups, I just did a hard restart (not through UI) and everything was back!
Thanks for the great advice everyone who suggested it!
When in doubt… Turn it off and back on again…
1 Like
Thank you very much, this helped me a lot!
This worked for me too. Thanks.
Simply reboot the os solve the problem