Since updating the core to 2026.5.2 and the supervisor to 2026.05.0, HA is not loading through the local IP. I copied and pasted the IP http://192.168.1.9:8123/ from the config page, disabled IPv6, and looked through the logs, and couldn't find what's wrong! When I try that link, it just times out! Any help is appreciated!
Is your HomeAssistant server still at that IP Address?
Hint: using a static IP Address in your router DHCP configuration should solve that problem.
More info about your setup please. Have you left your system up long enough for the updates to complete? Often this can take overnight.
Note: This is a commonly reported problem after each and every core update release. The solution is invariably to wait until it finishes, with maybe a nudge with a restart after a few hours have elapsed.
1 Like
Does http://homeassistant.local:8123/ work?
Another option via a PC
What do you see using CMD and ping homeassistant.local -4 ?
It seems my network is acting strange. I have a TP Link Deco and I only see 3 things online on their app, but everything in the house is connected. I am trying to figure out what's wrong!
Network issues? Random dynamic IP Addresses? Restart everything from power off, including your router, HomeAssistant server, and mobile devices should most likely clear the problem.
Was my hint about Static IP Addresses useful? You may find (especially in times of troubleshooting) it saves a lot of grief, and may actually prevent the problem recurring in the future.
Thanks. I should have checked the network settings, and your hint prompted me to do so. Thanks. I am still a bit confused. My HA is connected through Ethernet. It has a static IP. Also, the Deco network visibility issue is a glitch in what you see, not the network, because everything is correctly connected, including this laptop I am typing on right now. Even though it is not visible in the Deco app. So, HA should still connect! 
Are there any error message or what when you access that IP Address, or is it just frozen?
From before you attempted the update?
Does having a browse in Settings / system / network/ and all three options in network discovery yield any useful hints?
How about System / repairs / system information (click the three dots on the right to access)
I have just updated to 2026.5.2 (Supervisor was already up to date) and after HA rebooted, it wouldn't reach my home dasboard: I had the never ending loading spinner.
I had to physically switch off/on my RaspberryPi to regain access.
Not sure you're in the exact same boat but I thought that would be worth mentioning.
1 Like
Sorry, it got too late trying to troubleshoot, but without any success.
No error messages. Just times out!
I copied the link after the update. I rebooted HA after the update (because of a Bluetooth issue). I am at a total loss. I can ping all the connected devices, and they all work fine, except HA. But I can connect to HA using DuckDNS, so it is connected! I checked the IP, and it's correct too, but there is 100% packed loss when I ping HA!
Got it sorted out. It seems to be a network issue with my Deco network. I had to physically reboot the network by powering it down.
Now I have an issue with the Nest integration. That's a different issue
I learnt with Windows to start updates at night or otherwise I could be twiddling my thumbs for several hours waiting to start using my PC. It seems that users should update HA (even the .2 release) when they have a day or two to reconfigure their whole system 
For me 2026.5.2 seemed to loose my configuration, asking me my street address to start the onboarding. Since it was already midnight I decided to just restore to the previous backup and try the update next weekend.
HA then told me my username/password was invalid. I used proxmox VM console to execute the command to reset my password (of the 2 users which HA listed) only to be told that user did not exist !
So restore the proxmox backup from last month. Yes i do know i should backup much more regularly.
I managed to log in to 2026.4.4 and restored the HA backup from 2026.5.1 a couple of days ago ...
... and was again asked to start the onboarding process. It seems that there is a lot of configuration which HA does not backup or restore.
And did i mention that http:192.168.1.97:8123 no longer works, but http://homeassistant.local:8123/config/dashboard does ?
I am OK working through setting up things again. I'm just having a moan and letting others know that they're not alone in having unexpected difficulties with HA upgrades.