Home Assistant works fine after reboot but I cann’t reach it anymore in my network. The IP address is still the same, I can ping it. I use a Raspberry Pi4 and have the latest update (3-4-2022). Can anybody help me please? I use a SSD drive for my HA. I cannot reach it by Putty. When I reboot by SD card (without ssd-drive) I can reach the Pi by Putty, but I don’t know what to do next.
Hi TP51,
I am not sure if we have a similar situation here.
I updated ESPHome, and was working on updating my ESP modules wirelessly.
The system appeared to have stalled, eventually I pulled power to the HA Pi3+.
The Pi fully boots, but when I try to go to connect to homeassistant.local:8123 I get a “refused to connect” message.
So far I have confirmed that I can ping and receive a response from the Pi IP of HA.
I plugged in a monitor to the Pi, and I see the HA CLI.
I also see that I have a response from the observer URL indicating “Supervisor: connected, supported and healthy”.
I have been searching for answers, but not find a way to get back on line and working.
I am running HA OS 7.4 with Core 2022.3.7
try to access it over ip:8123
Hi Daniel,
I am thinking I was not pinging the correct IP, as my HA Pi Ip does not look to be replying to the pings.
Is the fact the HA Observer is responding helpful, but maybe my SD card is corupted?
well I dont know if your sd card is corrupted. I dont use PI, I use regular server with debian. If you can ping or ssh to your PI then PI its up. Is home assistant up I dont know.
In HA Cli, type --help … and go from there
I connected a wireless keyboard and mouse to the HA Pi, and I can access the help and other information for HA.
Is there a guide for the HA CLI? I did a brief search, i will try a few of the options to see if I can find anything out.
Thanks for your replies Daniel, it is pointing me in a positive direction.
Hi boheme61,
I see reload, scan and update.
I am leaning towards reload network information.
Does that sound the most logical as oposed to update?
–help … work on all commands, ha os -help etc. etc. etc.
Edit: yes i would start with “network info”
… there you see your ipv4 … ip number … under interfaces
btw, don’t you see that in your router ?
ok, I am going to spend some time going through this as it is all new to me at this point.
I may have to find a larger monitor.
Thanks for the direction and advice thus far; it is appreciated.
ok, im properly around a few hours more … but do you see an IP number in cli , just type " network info "
I think that you are on to something here.
I have:
type: ethernet
wlan: null
wifi: null
connected: false
enabled: false
I do not see an IP at all here?
I will continue to look
i see:
ipv4
address: []
gateway: null
netlod: disabled
nameservers: []
Try to reboor pi. You don’t have network. If you don’t have network after reboot and pi is connected to network than you have some more seriously problem.
ok, I am connecting a larger monitor to see the CLI better.
Then I will do a reboot and let you know what I see.
then tell your network “interface-name” (over ipv4:) … or type
network update “name” -e
(if it’s still “false”)
I am trying to search for a list of CLI commands to do the reboot.
Not finding it, I am still missing the left most 2 letters of each line.
Can you provide the reboot command for the CLI?
sure
ho reboot
ok, I wrote that down along with the other commands.
Unit is rebooting now.