HA no longer reachable after router switch

So yesterday I switched my main router från a Asus AX92U to Asus ZenWifi BT8. Mostly everything with the switch has been very smooth, all clients have reconnected without any problems.

But… I can no longer connect to my HA. My HA unit is connected via ethernet to the new router, same with the old one. I can see HA in the client list in my router UI. But attemtping to connect to http://homeassistant.local:8123/ or the IP fails. Using the HA app on my phone to search for the server also doesn’t find it. I’ve tried disconnecting and reconnecting both the ethernet and power, but it doesn’t help.

Any ideas what to try next?

Have you also tried it with “https://”?

Yes, also fails unfortunately.
Can also add that both homeassistant.local and IP responds to ping.

Plug ha back into old router and if you can then access ha and perhaps adjust the static ip address to automatic. Shutdown Ha. Connect it to new router and power it up.
You didnt say if old and new router use same address range.
You say you reconnected the power but not sure if you meant ha or router.

  1. new router setting up another subnet? means your ha device uses an ip from e.g. 192.168.1.0/24 while new router uses 192.168.2.0/24
  2. any default port filter on your new router?

Same subnet, even the same IP.
Tried connecting a screen and keyboard.
The IP matches what I see in the new router. But I still cannot connect. Unsure about those errors that are printed after the ha> prompt…

Looks more then a router change. Did you power off your HA by plugging the electricity out?

Yes I did.
Things get even weirder. Got thrown into emergency console.
login just loops back to emergency console.
Tried repair, but said container not running.
Looking at the container logs, that error looks like an image was pulled for the wrong cpu arch? :thinking:

sadly to say but your sd-card is buggy!
I had similar experience with mine until I changed to HAT M.2 SSD
So I suggest you do the same.
Unless this isn’t solved it makes no sense to dig further

Soo, I managed to get in again by manually deleting the latest docker image for supervisor from the emergency console, and then restarting. The weird thing is that I updated my HA from the web ui, which I’ve done a million times before. I probably did this around the same time as I was changing my routers. So probably not related to the router change at all, but rather the fact that HA for some reason decided to pull a new image. More digging before updating again I guess.

This I what I see now

…and this

Yeah, probably this. Looks very shaky