Just upgraded to 0.86.4 and Hassio will not run

Hi. Just upgraded from 0.86.3 to 0.86.4, and Hassio will not load, was set up as secure and would load via duckdns, local.hassio and IP address previously (using https) now will not load with any. I can still access IDE and so can see the log:

2019-01-31 20:51:18 WARNING (Recorder) [homeassistant.components.recorder] Ended unfinished session (id=59 from 2019-01-31 20:23:20.592763)
2019-01-31 20:51:20 WARNING (MainThread) [homeassistant.loader] You are using a custom component for custom_updater 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-01-31 20:51:22 WARNING (MainThread) [homeassistant.loader] You are using a custom component for calendar.google 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-01-31 20:51:22 WARNING (SyncWorker_10) [homeassistant.components.sensor.darksky] Monitored condition temperature_max is deprecated
2019-01-31 20:51:22 WARNING (SyncWorker_10) [homeassistant.components.sensor.darksky] Monitored condition temperature_min is deprecated
2019-01-31 20:51:22 WARNING (SyncWorker_10) [homeassistant.components.sensor.darksky] Monitored condition apparent_temperature_max is deprecated
2019-01-31 20:51:22 WARNING (SyncWorker_10) [homeassistant.components.sensor.darksky] Monitored condition apparent_temperature_min is deprecated
2019-01-31 20:51:23 WARNING (SyncWorker_15) [root] Couldn't connect to host: 192.168.1.222:5555, error: Broken pipe
2019-01-31 20:51:23 WARNING (SyncWorker_15) [homeassistant.components.media_player.firetv] Could not connect to Fire TV at 192.168.1.222:5555 using adbkey='/config/android/adbkey'
2019-01-31 20:51:27 ERROR (SyncWorker_2) [pychromecast.socket_client] Failed to connect, retrying in 5.0s

Not made any changes since last boot except the upgrade. Any clues?

It solved itself this morning, Most odd!

Just to inform that today I faced this issue and after 6H of troubleshooting the issue is not solved on 0.86.4

1 Like