By looking at your picture you might have disabled the network interface for your virtual machine which is running HA.
Try to check your network setting in Virtual Box.
Managed to sort it don’t know how permit the fix will be I changed the network adapter on the VM saved it then changed it back seems to have solved the issue don’t know how or y. Thank you for pointing me in the right direction
1 Like
Hi, can you explain more detail on how u fix the issue? I am new here, had to do home assistant for my grafana tools
Try to unplug and your network cable and plug in again. You now should get the IP address (You might want to use Fing to discover the IP of HomeAssistant)
1 Like
Hi, I have similar problem. I’m running Home Assistant on Raspberry pi for more the year, but since 2 months ago, when power cutoff and go back, my Home Assistant won’t get IP address. It is wired connection. So I have to hook up a monitor and keyboard and run from Home Assistant CLI command ‘network update’ (or similar) , to get an IP address. Do you have idea what could couse this bug?
1 Like
I also just experienced the same issue. My Home Assistant is running in a VM on Proxmox. Two days ago, there was a power outage and when the power came back, my HA instant came back up and running but without an IP address assigned. I was troubleshooting with the VM and also my IP settings in my Unifi controller and could not resolved the issue. Luckily I found this thread and was able to fix the issue using the CLI command @ayordanov outlined above to have the IP assigned again. Thanks.
You do not need to reinstall anything. Just go to the console and run the command as in below screenshot. Change the “enp0s18” according to your card and also the ipv4 and v6 settings accordingly to your own settings. 
As to why this happens, I believed it is some kind of bug as @ayordanov mentioned too. Hopefully it will be fixed at some point.
5 Likes
Ok, I will remember that. Thanks!
I reinstalled and made sure to have the eth connected before startup which also worked but only ideal for a fresh install.
Hi Skull29,
the first time I used your fix it worked nicely. I then rebooted my PC and it’s back to missing local ip address and I get the following screen. Help?
Your help would be appeciated please. I am a novice of 1 week
Regards
I had to use a few commands to get the eth0 to get an IP Address.
ha network info
ha network eth0 disabled
ha network eth0 auto
Sorry…Just saw the post. I am not an expert as well but merely searching and experimenting. 
Your first attempt is just wrong syntax. As for your second attempt, looks like some processes failed. Googling gives…"the error ‘context deadline exceeded’ means that *we ran into a situation where a given action was not completed in an expected timeframe "
I would suggest that you also try out other network commands to make sure it is working first as mentioned by @s-e-t-h.
If it still does not work, then either someone with more knowledge can chip in or you would have to reinstall. 
1 Like
Thanks worked for me !
1 Like
Is that a bug in the current HA build?
I had a power outage this morning that resulted in my home assistant pi4 not showing up on my network. It’s connected through ethernet and as in the screenshot earlier in this thread, the ipv4 address is showing up empty in the pi 4 display (it seems to be running fine apart from that).
I tried typing in ‘network update’, ‘network update wlan0’ and a few other variations on the commands recommended above, but am getting ‘Unexpected Server Response’ in response.
it’s possible I miskeyed the command. I tried again just now and it worked. My little pi display is so small it’s hard for me to read it 
The command for eth0 to be Disabled / auto makes more sense now I see this panel.
Enabled is not the opposite of disabled as On/Enabled can be DHCP (auto) or Static.
The command is turning IPv4 off and then on. The good old reboot
I hope this helps others, I had to travel 4hrs round trip to fix this in person.
Hi all, I just want to share how I fix it with you and hope may be is solution for some of you.
Little story of my config before:
eth0 was set to DHCP and I use my router settings and reserve by MAC Address of my RaspberryPi some IP address that I use to communicate with my Home Assistant, but like all the stories in this topic, after power shortage I lose access to my HA, I try to do what I ever I can remotely with no success, and only after I manage to connect monitor and keyboard I was able to fix it with the command listed in previous posts, but this fix my problem only to the next power shortage. I spoke with friend and he ask me, do I setup the same IP address that I put in the router, also in my HA.
Well I didn’t at this point it was set to DHCP, so it turns out that for ever reason in some cases on boot HA couldn’t get IP from the router, it didn’t get it later when router is available.
I would like to summarized my present settings that fix my problem and what ever I do now (manually cutting the power to test it), I always get the right IP address.
Go to ‘Settings’ → ‘System’ → ‘Network’ → In tab ’ Configure network interfaces’ → IPv4 → Static → And put your IP Address, Gateway address and DNS address( you can get this info from your router).
Home Assistant Operating System
Installed version 7.6
Home Assistant Core
Installed version 2022.5.2
I hope this will help to some one! Good luck!
1 Like