I am not able to reach my home assistent blue after my google mesh wifi had a factory reset (my father did a total factory reset, since he was not able to connect to wifi trough his pc… yes - I got a bit frustrated for that hahah) . As a result of the factory reset on the mesh wifi, I am totally locked out from my Home Assistent dashboard trough the http://homeassistant.local:8123/ in the browser, and I get an error when i try to use the HA app. I think the problem is that i the HA dose not automaticly uppdate to a new IP-address, even though i connect my google internett and HA with a ethernet cable. I have search for a solution on how to edit the IP address, and spent the last hours in CLI without any success. I have considered reinstalling HA, but since I do not have a SD-card reader (or much knowledge on reinstaling HA software) I found it to be something I hope to avoid doing. Is there anything i can do trough CLI or any other thing for getting access to the home assistent interface again? I would really like any help! Been trying to fix this problem for a month now, and it kinda sucks not to be able to use home assistent at all! Any help or tips is highly appreciated
Do you know the IP address and subnet mask that your HA is using?
Can you then access it with the IP followed by :8123?
If not then are your client computer in the same subnet?
If not then try to set a static IP on your client computer that is in the same network as your HA and try to access the Ip followed by :8123 again-
Sadly no, that is the docker internal network.
It’s the IPv4 listed under host_interfaces you need, but it’s disabled.
This could be due to an IP address conflict, so make sure no other devices are using the IP address HA has assigned.
It could also be caused by a defective network cable or a switch port that is shutdown/disabled.
Thanks again, I will first try to switch to a new port, and change to a new ethernet cable. How do I identify a conflict?
The message tells you the problem…
Don’t enter ha
in the command
Tried enabling ipv4-to auto without any success
“no carrier” means that it’s not seeing a cable connected
Try another cable and/or another network port.
After you connect a different ethernet cable, reboot the host using host reboot
in the CLI
Tried with three different ethernet cabels, and on the last one now I got “command completed successfully”! After code:ha network update eth0 --ipv4-method auto --ipv6-method disabled
That must be a good sign
Read the output on the monitor then go back to my first reply.