Hassio Slow Restart

Since Hass.io version 0.105.x I seem to have troubles with slow restarts of my Hassio instance. I just couldn’t figure out what happened to it. I did try everything, different SD cards, different raspberry Pi, different OS and Hassio version, but whatever I did, the restart process hung for exactly 15 minutes (+/- a couple of seconds). This seemed like some bug in Hassio. I used SSH to check out the logs of my Hassio installation.

I found out that for some reason the restart was hanging when it was trying to load to the [homeassistant.cloud] component. The log didn’t show any other activity for a while and then gave an error the [homeassistant.cloud] couldn’t connect to the cloud. Duh! I don’t use the cloud and no credentials are available to hassio. 

I did some google searches and I found that the cloud is part of the

default_config:
. This is a default configuration which enables most basic parts of Home Assistant, like the map, history and zones etc.

Well, next question: what is done by the default_config in Hassio? I looked into the Hassio code available on github and did find some interesting stuff: https://github.com/home-assistant/core/blob/dev/homeassistant/components/default_config/manifest.json

Here I found out what the default config was and to my surprise, there was a cloud dependency.

Since a user doesn’t need to use the default config in Hassio, I figured, I could use all the elements in this file, apart from the cloud dependency.

My new config was:

config:
#cloud:
history:
logbook:
map:
mobile_app:
person:
ssdp:
sun:
system_health:
updater:
zeroconf:
zone:
input_boolean:
input_datetime:
input_text:
input_number:
input_select:

Note that I commented out “cloud” with a hashtag #. I did this to remind me what is not activated at the moment and I can just uncomment it the moment I need it or when I want to do some troubleshooting.

A check of the configuration file learned me that all looked good and when I restarted Hassio, it just took less than 1 minute!

Job well done and problem solved!

I do realize its it temporarily fix, and I guess it should be fixed in any of the next updates, since I’m not the only one with this problem. As a small reminder: Hassio and Home Assistant are still in Beta phase, so bugs are to be expected. I’m sure the Home Assistant team does a great job and works hard to fix all possible bugs and still adding new features in the future.

You may also like...

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.