Hand-me-down HA Green boots but HA is not accessible

So I received a hand-me-down HA Green because the original owner considers it “doesn’t work”.

He can’t remember what it did to it so I cannot backtrack much here.

I followed these steps and sure enough, the LEDs indicate it booted OK but [LOCAL_IP]:8123 is not accessible.
I ensured a freshly formatted SD card is inserted.
Looking at the debugging instructions here, I gained ssh access to the host system so that seems to be working.

Running journalctl -f -u hassos-supervisor.service doesn’t show much:

homeassistant systemd[1]: Starting HassOS supervisor...
homeassistant docker[838]: hassio_supervisor
homeassistant systemd[1]: Started HassOS supervisor.
homeassistant hassos-supervisor[846]: [INFO] Starting the Supervisor...
homeassistant hassos-supervisor[875]: hassio_supervisor

Similarly, docker logs hassio_supervisor shows no errors, only a warning regarding pulseaudio.

Checking the logs for homeassistant with docker logs homeassistant also only prints a couple of warnings:

WARNING (Recorder) [homeassistant.components.recorder.util] The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly
WARNING (Recorder) [homeassistant.components.recorder.util] Ended unfinished session (id=4)

Still HA is not accessible.

Where else could I look for clues?

Maybe a network issue?

What is the output from:

ha network info 

Can’t see anything weird:

docker:
  address: 172.30.32.0/23
  dns: 172.30.32.3
  gateway: 172.30.32.1
  interface: hassio
host_internet: true
interfaces:
- connected: true
  enabled: true
  interface: end0
  ipv4:
    address:
    - 192.168.0.132/24
    gateway: 192.168.0.1
    method: auto
    nameservers:
    - 192.168.0.1
    ready: true
  ipv6:
    address:
    - fe80::29:92c9:148f:dfdf/64
    gateway: null
    method: auto
    nameservers: []
    ready: false
  mac: 20:F8:3B:00:46:A7
  primary: true
  type: ethernet
  vlan: null
  wifi: null

Just to confirm, from a pc, there is no response when trying to go to 192.168.0.132:8123

Well this is awkward… I’m guessing the reset actually did work, and the IP changed from 137 to 132 without me noticing…
Sure enough, Ha is up and running on http://192.168.0.132:8123 :man_facepalming:

1 Like

Glad it’s working. You might want to read through this to get started: The Home Assistant Cookbook - Index.

1 Like