I lost access to my HA

Hello everyone,
I hope you’re good

I had HA since january and everything was great

Since 2 weeks my street got strucked by lightning and I lost power and it fried some of my internet boxes
So I had to change everything

My HA is on a raspberry that is plugged with internet cable directly to the new box

I use a tool called “Advanced Ip scanner” to be sure this is the same IP adress

But somehow I don’t have access anymore to my HA dashboard

It says :

" This site can’t be reached

192.168.68.93 took too long to respond.

Try:

ERR_CONNECTION_TIMED_OUT"

What should I do ?

I connected it on a screen to see what is going on and I have a screen

With 2 link to connect

http//homeassistant.local:8123 and
http//homeassistant.local:4357

none of them work

I hope I could solve this :slight_smile:
Thank you so much

“Advanced Ip scanner” would reveal the the IP address is alive, but not to which device actually got the address; it might be something else now.

Your router (new box?) probably gave your Raspberry another DHCP lease.
You should be able to check the DHCP leases on your router, and see what new IP your instance got…
If you know the MAC address, it would narrow your search :wink:

Interesting !

So I don’t really know how to find the DHCP but here is the IP adress and MAC adress :

IP : 192.168.68.93
MAC : E4:5F:01:90:DE:D6

For that to work, your router must have a good working mDNS

Where exactly you’d find your DHCP leases totally depends on the make of the router, but it shouldn’t be too hard to find if you know the MAC :wink:

This is a view from my EdgeRouterX:
image


this ?

No, you need to log on to your new router - it should have a GUI where you can see what is connected to it. That or use FING (an Android APP) as that will at least ID the Raspberry Pi.

Basically go to http://192.168.1.1 in a browser. Should ask for a login - and your new router will have come with a user/pass. Failing that - what is the make of the new router?

EDIT : Also noticed that you are looking for 192.168.68.93 but your router is giving out addresses in the 192.168.1.x range.

I’m guessing you’ve done nothing with the router and it’s running on default settings. Your HA won’t be visible unless it gets a 192.168.1.x address or your router uses the 192.168.68.x range.

1 Like

Hum interesting …

So what should I do to get both of the IP adresses to match ?

If it is a DHCP issue (which i think it is), it is what @Neil_Brownlee said, log on to your router on http://192.168.1.1 and lookup the IP address in your router (by finding your mac address in the dhcp lease list). This will probably be an address in the 192.168.1.x range.

after that you will be able to log on to HA by using http://192.168.1.x:8123.

And not related to your issue, but on that same page on your router you can probably turn the lease into a reservation, which will prevent HA from changing IP while connected to this router.

1 Like

Put a monitor directly on your RPi and see it in its own logs.

1 Like

That screen will also have the ip address of the machine running HA. Like


| |  | |                          /\           (_)   | |            | |
| |__| | ___  _ __ ___   ___     /  \   ___ ___ _ ___| |_ __ _ _ __ | |_
|  __  |/ _ \| '_ \ _ \ / _ \   / /\ \ / __/ __| / __| __/ _\ | '_ \| __|
| |  | | (_) | | | | | |  __/  / ____ \\__ \__ \ \__ \ || (_| | | | | |_
|_|  |_|\___/|_| |_| |_|\___| /_/    \_\___/___/_|___/\__\__,_|_| |_|\__|

Welcome to the Home Assistant command line.

System information
  IPv4 addresses for enp2s0: 192.168.20.254/24
  IPv6 addresses for enp2s0: 2404:4404:1000:1300:4b5c:fcb:c567:2afa/64, fe80::8528:35de:c280:2bda/64

  OS Version:               Debian GNU/Linux 11 (bullseye)
  Home Assistant Core:      2022.11.0b6

  Home Assistant URL:       http://hass.local:8123
  Observer URL:             http://hass.local:4357

this line being the relevant one

IPv4 addresses for enp2s0: 192.168.20.254/24

So that tells you what address to type into your browser to access HA.

1 Like

I’m sorry guys I’m a real noob :frowning:
So I didn’t understand everything

I tried to plug the raspberry, to check the logs so I share with you the picture of what I have

It seems I have a different Ip now (but when I scan my network I still have the old one indicated that I shared with you)

and for some reason on the main dashboard command line I have 0 IP indicated :frowning:(

Thank you for your help !

172.30.x.x and 172.29.x.x are typical IPs on a virtual network.
In this case it is probably the internal virtual network of docker.
Just like you have a network behind your router and then some public IP, so have the docker software. The public IP is just one of the internal IP. The one you can still access HA on.

Try

ha net info

Quite impossible, your old IP address is not reachable from your new IP range…
You can only scan 192.168.1.1-254(/24) so that excludes 192.168.68.93 :wink:

This is what I get

eth0 does not have an ip address. Are you sure it is plugged in to your network? That all cables are OK?

The RPi have to leds at the network cable connector.
When the RPi is powered on, then these should light up. One of them might be blinking, but there should be active still.
If you have no lights, then your connection between the switch/router and your RPi is not working and we are down to hardware fault then, which means cable or network card inside the RPi.

Hum that’s weird, I’m litterally plugged to my router ! :confused:

I have this one :

Does anyone know how could I set up the wifi ?
Maybe when some equipment in my house fried, it frieds also the ethernet part on this ?

Thank you so much y’all for your help !

Verified it is really plugged in well?
Tried another port on the router?
You can also try another cable :face_with_raised_eyebrow:
Does the router show any activity on the led of the port?