Connection refused with Home Assistant OS

Installation Home Assistant OS
1

I’ve been running Home Assistant OS on my RasPi 4 for quite a while. Now I can’t get to the web interface anymore, the connection’s refused. ping still works, but if I try wget or curl to the device (name or IP with port 8123), I get “connection refused”. The browser just gives some generic error that the connection’s not possible.

The only thing that changed is that I don’t have the previous WLAN router in use anymore, it’s connected via LAN cable to the new one. Maybe it expects to be reached via the previously configured WLAN? If that’s the reason, is there any way to change this?

2
3

The port was not supposed to change for existing users, and there is a mechanism in place to revert back if port changes are not confirmed in time. But it is indeed likely the mechanism isn’t working as expected for everyone. During the beta I also experienced some anomalies, maybe those were not completely fixed.

4

Interesting to know. But no, port 80 refuses the connection as well.

5

Try connecting it to a screen / TV to see what is going on.

6

Sadly, I can’t see anything interesting there. I see the usual Linux boot messages for a few seconds, way too fast to read them, then there’s no monitor signal anymore. Or at least none my TV can handle. It just turns to the blue “no signal” screen.
However, HA does run, the automations still work.

7

Does the supervisor port work? 4357?

8

Nope, also connection refused. Though I don’t know if it ever worked, I just read about it when looking for solutions now.

Almost looks like I have to try how good my backups will work…

9

And you are 100% certain that you are using the correct IP when you try to connect?

10

As certain as I can be. There are just 3 devices connected via cable to the router, and I can connect to the other 2. So unless my router shows the wrong IP for some reason… But then again, ping works.

11

If you changed from having it connected through wifi to ethernet, it is very likely the IP changed. You are not using vlans? What is the ip the router reports that HA has, and what is the IP of the device you are trying to connect to HA with?

12

HA is 192.168.178.21, my PC is 192.168.178.30. As said, I can also reach the other two devices plugged right next to the HA RasPi just fine, so I don’t think it’s related to that.

13

Can you ssh to it?

Can you see the SAMBA shares?

(this is assuming you have those installed…)

…and if it was on WLAN and not LAN the LAN won’t have that IP address/be configured.

14

OK, it does seem to be something in my local network. I just don’t have any idea how and why.

I tried to start with a new HA image (flashed to a different SD). Still the same effect. Then unplugged the device. Now it’s no longer shown on the router, but somehow ping still works (where to?).

ssh never worked via the port, only as app. I assumed that’s some security thing. But it seems I’ve got a more fundamental issue here…

It’s a new router with different SSID, so the configured WLAN wouldn’t have worked anyway. With the fresh image nothing’s configured, but according to the router it got the same IP as before, probably because it’s the same MAC.

Guess I’ll try a different cable next, though I really don’t get how some “half connection” where it shows up in the router but not can be reached via http is possible…

15

Can you change the SSID/Add another SSID with the same password to that of your old router? That would at least let the original HA connect to something again?

16

this is a clear indication that the IP you think is HA actually is something else.

17

Assigned a new IP in the router, now it works. No idea what the hell the router did there. Thanks for your support.