Yesterday I updated my home assistant instance running on a raspberry pi 3b to the latest core. It worked for a while with no problems but now I can’t access it anymore whether from the app, the Duckdns link or the local Connection. But the server still looks like it is running because every switch I imported in the Home App from Apple and my passwordmanager are still working. Does anybody have an idea how I can solve this issue?
It anymore
This happened to me last week too. Unfortunately I had to start over. Although I did have back up file which helped. But still a chew to get everything back to where it was.
I now have no confidence in updating to newer versions of the software… hopefully this is something that can be sorted?
I don’t trust it anymore too. This happened to me a few month ago and I had to start over. But I am not happy now that I need to start over again. Fortunately I backed up my hole system before I updated the core.
Ye, very frustrating! Hopefully, this will be fixed in the near future??
If you don’t mind me asking, how did you back up the whole system? I use the Back up option in ‘Supervisor / Back up’ and select full back up. I then store the file external to the Ras Pi so that I always have access to it.
I thought this was the method I used prior to my ‘rebuild’ but was surprised that none of the Add-Ons etc were available so had to start from scratch with those (Which took me an age!)
Cheers
The same happened here, but I did not even update? It just happened during the night
Any fix?
I use the Google Drive addon. It’s a third party addon. You can make full and parts of an backup which are then stored in your google drive and/or on the raspberry pi.
A little update:
Today I installed proxmox on my old computer to install home assistant on it. I connected to a „new“ pi address (thought this because I am stupid) and locked in with my common credentials. And it worked then I noticed that this was my old instance running on my raspberry pi and everything looks fine. Then I tried it with my iPad and the app(where the duckdns link is stored) and this didn’t worked. So I think there is just a issue with duckdns. Trying to solve this now.
Now my problem is solved. I read that somebody renewed his portforwarding rules. Now I did it too and nw I can access my home assistant instance again.
What port forwarding rules did you need to update to access it locally?
I didn’t do anything to access it locally. I did work after a few hours.
Renew port forward, how did you do this please. Mine works locally but not externally after os update.
@daveco If you are lucky and your HA only has changed IP adres after updating then you can try port forwarding by replacing the old up address in the port forward option in your router.