Hi there, complete novice here where I’ve seemingly given myself a bigger problem than the one I was trying to fix…
First the issue was that I couldn’t install a couple of updates and it wasn’t allowing me to install add-ons due to a ‘no host internet connection’ (despite the device clearly being online and working)
I was then poking around in network settings. I tried changing the auto ipv4 to static following a youtube tutorial but the setting change wouldn’t save (just had a spinning wheel for 5 minutes). I then clicked it back to auto and hit save and after a few moments it lost connection.
Now when trying http://homeassistant.local:8123/ I get ‘This site can’t be reached’ and the HA is greyed and showing as not connected under my router settings. It’s connected directly via an ethernet cable.
I’ve tried turning it off and on again but no joy. How on earth might I go about getting the connection back? Any help would be hugely appreciated!
As others have pointed out it is likely your IP address changed. Log into your home router and see what IP it currently has.
I only access my HA over TLS using the IP address. I use a SAN certificate which validates the TLS with the IP address instead of a domain name. By relying on IP address you guarantee you can access HA even if the DNS is not working.
Static IP
After you discover the IP of your home assistant assign a pre-allocated IP address in your router DHCP settings. Reboot your HA device so that it gets the pre-allocated IP.
Once you have access to home assistant from the pre-allocated IP you should set a static IP from within home assistant itself. Visit Settings > System > Network, under IPv4 set a static IP in HA to be the same IP address as your pre-allocated IP.
With a pre-allocated IP you guarantee your router will not assign the IP address by mistake. With the HA static IP you guarantee your HA instance does not rely on router DHCP.
In my experience this is a very stable setup.
Other thoughts
One of these days I’ll develop a guide and a sane add-on which supports securing HA with TLS that doesn’t rely on external services (e.g. not let’s encrypt or anything). When securing personal services with TLS there’s no more trustworthy party than yourself. I don’t like relying on 3rd parties for offline services (e.g. let’s encrypt is great for public facing services but not good for personal services).
Thanks for all the pointers so far guys. Here’s where I’ve got to…
With a HDMI cable connected into the HA Green, I can see that it’s assigned IP is 192.168.100.43/32. HOWEVER, I’ve tried navigating to http://192.168.100.43:8123/ with no joy and my router still can’t see it. http://homeassistant.local:8123/ also still doesn’t work.
Through the HA CLI, I’ve also found the HA MAC address and tried adding it to my network manually (in router settings) but the router rejects/won’t save it.
I’ve then tried changing my IP address on the HA in CLI by typing: nmcli> set ipv4.addresses 192.168.1.10/24 but I’m returned with ‘can’t create set: read only file system’. Any thoughts?
My HA is clearly alive and has an IP but for some reason my router can’t see it! I’ve got an activity light on the ethernet port of the HA Green but it’s not picking up. Thanks again!
Update. I’ve managed to get it back onto auto assigned IP with the router now picking it up. I ran the following via a HDMI into the HA device on the CLI:
network info to find the correct network adapter and see your current IP address set for HAOS
network update end0 --ipv4-method auto --ipv6-method disabled (“end0” being my network adapter)
Back online and the core update even installed properly! Thanks all!