New set up: HA Green - changed IP settings no longer accessible

Hello,

Oh dear, not a good start to my HA journey - I’ve only had my new HA Green for 5 minutes before I broke it and I would be grateful for any assistance…

I have a reasonable grasp on what I’m doing but after hours of research on similar topics and switching everything off and on again(!), none of this has enabled me to resolve it, so I am obviously missing something.

The initial set up worked fine and was accessible until I set a static IP address, now I just get error messages, I have attached a couple of screenshots below.

The HA Green has the white light steady, green light single blinking and yellow double blinking.
I have a Deco x60 with address reservation for HA. (192.168.68.76) I noted from other posts that DCHP may be an issue…?
I am able to ping the static IP (Image below)

I have tried multiple address combinations to access HA in desktop and mobile web browsers including:

homeassistant.local:8123
homeassistant:8123
192.168.68.76:8123
192.168.68.76/24

But they all return error messages. The Android app shows the HA in the selection list but I still get an error message.

I’d be very grateful for any assistance form anyone who can point me in the right direction.

Thank you, Paul

Where exactly are you assigning the static ip? Router? HA Green?
It may be worth while using a tool like angry ip scanner to scan your ip range to see if home assistant shows up on an unexpected ip, maybe. As well as checking any reserved ip’s in your router config.
I would note that with my router, I have to do a reboot after changing any ip reservations or changes to security for changes to take effect. If you have any switches in the mix, maybe reboot those also, so all your network hardware comes online fresh, then up scan, see what’s getting what ip’s from your dhcp, then you can start whittling down errors/conflicts.

It would be helpful to know your network topology briefly and which devices your changing which settings on to be able to identify possible conflicts.

He sort of said it was reserved in the router. (I had to Google “Deco X60” to determine that).

Paul, what is the IP address of the browser and of the router? Did you specify the IP address that you reserved in the router or did you reserve the address selected by the router?

Thanks for your help, sorry yes the Deco x60 is a TP Link mesh network router.

It’s all very confusing, seeing as I’ve not got into HA for more than 5 minutes would if be easier to just factory reset the unit and start again? Not that I can find a way to reset it without going through the UI - Arghh Catch 22!

Anyway, I’m not 100% up on all the terminology so I hope the following answers the questions you raised.

The Deco X60 takes it’s feed direct from the Network Providers router and has a dedicated IoT Network where the HA Green is connected via ethernet cable. I connected my desktop and mobile to the IoT network to set up HA. (nothing apart form the Deco x60 is connected to the Network operators router).

When I first started up HA, the router assigned the IP address 192.168.68.76. (A number of the many You Tube videos I researched recommended setting a static IP for HA.) My router has an Address Reservation option and I selected the the Home Assistant IP from the client list and now it shows in the reserved list ( I am assuming the Address Reservation is the static IP).

I then went into the HA Network settings and set IPv4 to static and entered the reserved IP from my router settings. That’s where it all went wrong and I have rebooted everything a few times but to no avail.

I have not changed any other settings that I am consciously aware of, but it’s always possible I clicked or hit an erroneous key without realising…

I’ve ran an IP scan and it shows as Home Assistant on IP 192.168.68.76 which is the static IP as set on my router.

What I can’t get my head around is that the IP address is recognised and shows up on everything, ie IP scans, router settings, pings, even the HA app, but when I try to connect on the web browser and the HA app it just returns error messages.

IP address isn’t the only thing needed for connection.itnalsobhas to know what network it’s attached to and how to find it’s upstream router. I’d any of those are borked no connection. Usually dhcp takes care of that but if you ALSO set static on the machine (and if they don’t EXACTLY match…)

You haven’t shown us what the HA box thinks it has. (your pictures above none show the actual screen view from the HA box so I only know the IP address from what you tell me.) I suspect a busted setting there.

Plug in a monitor show us what the HA box thinks it has on ip settings.

Id bet the subnet mask on the HA box is wrong and he doesn’t think he’s on the right subnet…

Thanks Nathan, not sure I understand half what you wrote :smile: But I did a bit of digging and managed to get a screen shot of HA box.

Does this help shed any light on what I’ve done or not done?

1 Like

It certainly does. Your subnet address is wrong (that /32 at the end)

It basically says you are in a network of one device…it can’t talk to anyone else…

It should probably be /24 (guessing, /24 ie a standard class c and what routers usually issue in home networks)

Find the commands to change your ip address through the command line (im away from my desk or if look them up - someone help find the command.) but change that subnet mask I your ip config to /24 or pull the stativ assignment out of HA entirely - that’s what the router reservation did you really don’t need the reserved ip And the static assignment)

Also this means this machine is completely unaccessible from the network. You will HAVE TO make these changes on the terminal command line there at that console. (read get a USB keyboard too)

Thanks again for taking the time to help.

I found the following CLI command in this post on May 22.
set ipv4.addresses 192.168.1.10/24
https://community.home-assistant.io/t/how-to-change-ip-adresse-in-cli/332205/22

I just want to check the following is correct for my set up, before I go and do something that makes it worse…
set ipv4.addresses 192.168.68.76/24

I’m Back in!!!
Big THANK YOU to Nathan, tvns and stevemann for your help.

I also found this post
https://community.home-assistant.io/t/how-to-change-ip-adresse-in-cli/332205/44


NeavcenJohannes Schwalbach
May 12
Thanks for this advice!

I managed to change my IP address via CLI using the following commands:

  1. network info to find the correct network adapter and see your current IP address set for HAOS

  2. network update eno1 --ipv4-method auto --ipv6-method disabled (“eno1” needs to be replaced by your network adapter)

  3. network update eno1 --ipv4-gateway 192.168.x.x (“eno1” needs to be replaced by your network adapter, “x” needs to be replaced by your IP gateway, probably router IP)

I couldn’t get step 3 to work as not sure what my network adapter is.

But I got back in after step 2, although this set my to 192.168.68.76/22.
Will the /22 an issue down the line or is it ok as is?

1 Like

/22 or anything it is NOT. is not ok.

Honestly I’d just set the green back to DHCP -and stop banging your head around.

With the reservation in the router your (this is the important part) ip won’t change and that’s what you’re trying to prevent setting a manual ip on your green without understanding the requirements will only continue to lead you to pain.

You’re changing a bunch of settings without the context to change them correctly and you’ve already seen how well that works.

Agreed! Had enough of banging my head around, I’ll let it do its thing and just leave the reservation in the router. Athough, I’m sure there’ll be more headaches ahead…

Thanks again.

1 Like