Hassio - Web interface connection refused after power outage

1

Hi,

I had a power outage today, and since then I’ve been unable to access the web front end on Hassio on my RPi3.

I have the SAMBA add-on enabled and can see the usual shared folders and the HA log, which doesn’t report any significant errors or warning (just what i normally get), which seems to suggest HA is running, but the web UI isn’t allowing connection.

I’ve seen that this seems to be a common error after a power outage usually fixed by a re-install. I’m reluctant to jump straight into that route as I have the ps4wakerbridge installed and that was a pain to get working.

Can anyone off pointers to fix this issue without a full re-install?

2

Do you have ssh access so you can check the error logs?

3

Samba access would work to check the logs too.

4

Do you mean Hassio logs or HA logs?

HA doesn’t show anything out of the ordinary:

2019-03-31 22:31:59 WARNING (Recorder) [homeassistant.components.recorder.migration] Database is about to upgrade. Schema version: None
2019-03-31 22:32:01 WARNING (MainThread) [homeassistant.loader] You are using a custom component for alexa.media_player which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2019-03-31 22:32:01 WARNING (MainThread) [homeassistant.loader] You are using a custom component for ps4.media_player which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2019-03-31 22:32:02 ERROR (SyncWorker_17) [custom_components.ps4.media_player] Failed to call info: HTTPConnectionPool(host='x.x.x.x', port=3031): Max retries exceeded with url: /ps4/x.x.x.x/info (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x72aad1b0>: Failed to establish a new connection: [Errno 111] Connection refused'))
2019-03-31 22:32:06 ERROR (SyncWorker_12) [homeassistant.components.media_player.onkyo] Unable to connect to receiver at x.x.x.x
2019-03-31 22:32:06 ERROR (SyncWorker_4) [pychromecast.socket_client] [x.x.x.x:8009] Failed to connect, retrying in 5.0s
2019-03-31 22:32:11 ERROR (SyncWorker_3) [homeassistant.components.device_tracker.icloud] Multiple devices with name: xxxx
5

Look at your custom components for alexa and ps4.
Also, [homeassistant.components.device_tracker.icloud] Multiple devices with name: xxxx

6

Have you tried restarting home assistant from the ssh access?

7

I can’t get into ssh on HA, but I do have ssh onto hassio fortunately. How do I drill from there as I assume the HA instance is in a docker image?

8

Do you have ssh set up using the add-on, or ssh with shared keys for the dev/debug documentation to port 2222?

9

I only have HassOS all in one install. When you log in via ssh there are a list of commands available. You can restart host and home assistant. I think stop home assistant then reboot host then restart home assistant. That’s usually done it for me in the past.

10

Ssh into hassio.
Enter;

Hassio ha restart

11

I have ssh setup for dev/debug on 22222. I can login to that and managed to workout how to get into the docket containers and check logs.

No errors in either HA or Supervisor logs, but just had a quick review last night so will look closer this evening.

I’ll also give the restart command ago tonight when I get home.

Thanks for all your responses so far.

12

Ok, I tried the restart, but that failed:

hassio > ha restart
Error: Unknown Error, see logs

Checking the logs I fount that the chromecast component was failing to load and crashing out a task. When I removed that the system was able to restart successfully. On further investigation, it transpired that the Google Home Mini hadn’t come back online after power outage and it was that causing the chromecast error.

Many thanks for all the pointers on how to investigate.