#I can either access HA directly via IP

1 messages · Page 1 of 1 (latest)

umbral rock
#

"Destination host unreachable" is network connectivity problem as the name says. Something is preventing your computer/tablet/phone etc. to reach your RPi. It's either because the RPi isn't connecting to your router, or something else in your network is preventing traffic from reaching upto your RPi

#

Don't bother with DuckDNS etc... that's behind a DNS lookup which is one more layer to debug

#

You should be able to ping your RPi directly using IP address on local network from your computer

#

Is the RPi+HA running on the same subnet as your computer behind a simple DHCP server (this is very common out-of-the-box for most routers) ? Or do you have some complex multi-router/multiple-subnets/VLANs based set up?

#

Did you fiddle with your router to prevent devices from accessing each other? Or any firewall settings on your computer?
Try pinging other devices on your network from your computer to see if it's just that RPi you've issues accessing all the devices

#

Try using a different computer or a ping from some phone app or even your router (if it has a terminal) ... and see if ping works. To both the RPi and your original computer.

#

If all other devices can talk to each other over network, only the RPi can't be reached... then it's likely just offline, either because it hasn't booted up or has some broken network configuration. And then you need to go physically access it, connect a keyboard/screen etc. and then figure out what's wrong on it.

neon timber
#

It's on the same subnet as my computer. I can check to see if other devices on that hub/switch are reachable. They are (I just Pinged them). I didn't make any changes to my Router or Firewall settings.

Gotta run now but I'll follow up on what you've suggested and let you know.

neon timber
umbral rock
#

Can your laptop ping your Wifi smart plugs?

#

Do you have another computer handy? Trying connecting to same network and try a ping from that one?

neon timber
# umbral rock Can your laptop ping your Wifi smart plugs?

Finally getting back to you. I have HA connected to a monitor & keyboard. It boots up fine and gets to the Home Assistant banner. Here's the info it shows:
OS Version: 10.3
HA Core: 2023.6.3

The last time I was able to get into HA from my computer was Jan 17th and I ran a full backup at that time. Last backup: 2024-01-17 and it was a full backup.

If I run "net info" at the HA CLI it shows that it's running on 192.168.1.30/24. It's supposed to be on 192.168.1.221 and has been for the last few months. When I try to access it at the .30 address (via Firefox) it says "Connection was reset" and there's a button marked "Try Again". I click that and it gives me the same screen. [Continue reading below].

UPDATE: I just tried it again and now I can get into HA from my computer using the .30 address. I see the Dashboard and all looks good. Your comments welcome....

neon timber
#

UPDATE 2: I have saved the backup file from 1/17/24 to my computer. At least I have that as a 2nd location for the backup file.

neon timber
#

Update 3: Sounds like a router problem. I've rebooted the router several times since the problem started. If I knew where in the router settings I could permanently assign the .221 address (and in HA I assume), that would likely solve the problem. Your thoughts?

umbral rock
#

Typically routers run DHCP servers for local subnet i.e. they're setting up Dynamic Addresses for any devices that connect inside that subnet (192.168.1.xxx). The addresses are handed out first-come-first-serve with no guarantee of it being same after reboots.

#

But most routers should have the ability to set a static address (maybe called "static lease" or something similar in your UI) ... and then the router will always assign that specific IP address for that specific device and no one else. That should achieve what you want to do.

#

An alternative way is to access the device via the hostname instead of IP address. For example, to my knowledge, HA OS broadcasts itself as "homeassistant.local" on the subnet, so you should be able to connect it with http://homeassistant.local:8123/ if your OS set up is default. This is similar to how you type "www.google.com" and DNS lookup mechanism figures out what the exact IP address your packet should go to.
The way this works -- since a typical home network doesn't have a DNS server, this local mechanism works using a mDNS broadcast protocol -- all devices broadcast on your subnet something like "Who is homeassistant.local?" and then your device will respond as "I'm homeassistant.local and my address is 192.168.1.xxx", regardless of whether it gets assigned .30 or .221. And then your computer can start talking to that address and load up your webpage, dashboard etc.

#

I use this method in my network, everything accesses each other via their host names.

#

But note, this depends on how strict the firewall settings are on the client side in the router. If router is blocking mDNS/Bonjour traffic, then this won't work. Although this is very very unlikely, because typical Chromecast or Airplay or Printers use this mechanism to find each other, and most home consumers want this.

umbral rock