I have just upgraded to the latest version (0.53.0) and find that my HA never comes back to life, I see the following (this is after only a minute or so, but this state persists seemingly forever):
pi@rpi:~/.homeassistant $ sudo systemctl status home-assistant@pi -l
● [email protected] - Home Assistant
Loaded: loaded (/lib/systemd/system/[email protected]; enabled)
Active: active (running) since Mon 2017-09-11 14:53:25 BST; 1min 15s ago
Main PID: 3754 (hass)
CGroup: /system.slice/system-home\x2dassistant.slice/[email protected]
└─3754 /usr/bin/python3 /usr/local/bin/hass
Sep 11 14:53:25 rpi systemd[1]: Started Home Assistant.
Sep 11 14:53:31 rpi hass[3754]: 2017-09-11 14:53:31 INFO (Thread-2) [homeassistant.config] Upgrading configuration directory from to 0.53.0
Sep 11 14:53:31 rpi hass[3754]: Config directory: /home/pi/.homeassistant
Read through the Release Notes for breaking changes for the current release and for any release that you may have skipped. Every release has breaking changes that can affect your configuration and require changes.
Agreed, however, I skipped five versions or so (coming from 0.47 IIRC) - is there no way to get better logging on what the issue might be? It seems stuck at the first hurdle!
Also - I reverted to an empty config and forced a reinstall ( sudo pip3 install --upgrade --force-reinstall homeassistant ), same issue…
Well, what to do next depends on how you install HA on your Pi. Did you use the AIO, virtual environment, other?
Either way, given that you’re using systemctl, the output of journalctl -u home-assitant@pi -n 200 shared on the likes of hastebin or pastebin (not directly here) will hopefully provide enough information that somebody can identify the problem.
Further, in a more general edit of the journalctl commands, I found that MQTT seems to be broken / stuck in a reboot loop, which may be something, but my config is BLANK right now, hoping to get HA to even start:
homeassistant:
# Name of the location where Home Assistant is running
name: Home
# Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
time_zone: Europe/London
# Enables support for tracking state changes over time.
history:
# Enables the frontend
frontend:
# Discover some devices automatically
discovery:
(I know that with this config the systemctl output also includes a warning about Lat/Long being missing, but nothing else in addition…)
I don’t think I’m the same boat as you but I had the same issue, for me it was the new customize panel. In my configuration.yaml I had it set as a seperate entity instead of under homeassistant which caused it to get stuck as it was trying to load it as a component.
I renamed my configuration.yaml and restart HA to generate a new config so I could work that out. Sounds like you’ve already tried that though?
No worries, Once I’d figured out that, I just went through the configuration.yaml and commented a couple of items out and restarted. Mine turned out to my “customize:” and it was a layout issue. I had too many spaces, it worked in the previous build but didn’t like it on this one!
My HA is laid out with separate files for most config such as groups and scripts etc.