I have update the Ha All-In-One installation to the letest version, but after reboot my raspberry pi, the HA doesn’t work…
If I scan the IP, there is no service on port 8123. The log file is no updated after update process…
If I check the service status this is the output:
pi@raspberrypi:~ $ sudo systemctl status home-assistant.service
* home-assistant.service - Home Assistant
Loaded: loaded (/etc/systemd/system/home-assistant.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2017-11-07 17:46:29 CET; 4min 12s ago
Main PID: 29227 (hass)
CGroup: /system.slice/home-assistant.service
`-29227 /srv/homeassistant/homeassistant_venv/bin/python3 /srv/homeassistant/homeassistant_venv/bin/hass -c /home/homeassistant/.homeassistant
nov 07 17:46:29 raspberrypi systemd[1]: Started Home Assistant.
nov 07 17:46:35 raspberrypi hass[29227]: 2017-11-07 17:46:35 INFO (Thread-2) [homeassistant.config] Upgrading configuration directory from 0.56.2 to 0.57.2
nov 07 17:46:35 raspberrypi hass[29227]: Config directory: /home/homeassistant/.homeassistant
But it doesn’t work… his is very strange…
If I downgrade to 0.56.2 and everything is ok…
same here - webinterface is not avaiable after upgrade to 0.57.2
furthermore some modules doesn’t seem to be correctly installed. _sqlite3 is missing so the recoder, history and logbook could not be initalized (i’m using a sql database on my synology)
some custom componentes (pylacrosse) don’t work either.
irqnet
try deleting home-assistant_v2 and reboot… sometimes corrupt home-assistant_v2 causes recording issue…
as for updating… I updated the other 2 days ago… everything seems to work fine… it could be some configuration settings… try running it with default configuration.yaml
Ok thanks, i will try. I think can be relativi to https or acme.sh or somthing like this… But the strane think is ste service is activated but the 8123 is offline.
I’ve started hass right now with default config and moved step by step every config item to the new file. everything works like charme, except the recorder, history, logbook and the custom components.
going to figure out whats the recording issue now.
updated hass with pip3 upgrade homeassistant (that uninstalls 0.56.2 automaticaly)
running hass with pi user results in the case i described before (no recorder, history, webinterface)
running hass with sudo results in a new config (/root/.homeassistang) -> webinterface working
renamed configuration.yaml to configuration.old (in /home/pi/.homeassistant) -> empty config -> webinterface working
Then i transfered the configured components step by step from the old to the new config file to be sure i can figure out which componentent might be cause the failure. result = transfered all components and webinterface is still up and running and accessable by browser.
Only the recoder did not work, i guess that was an pyhton3 sql issue. So i had to compile and install pyhton3.6 manually and reinstall the needed sql client to connect to my maria database on my synology.
I think this weekend I reinstall all the Raspberry with new stretch image i update the last version of python and I make a new All-In-One installation of homeassistant… I think this is the best way.
Because the Last time i try to update only the python but i wasn’t able to restart the homeassistant like this time… I don’t know where is the problem.
In the Raspberry i install homeassistant, duck dns script, acme.sh script, influxdb, grafana and dnsmasq. Maybe some of this software create this issue…
I think 3.5.3 is enough right now (til 01/2018), but it causes the sqlclient error with my config, because I’m using an maria sql db for the log instead of the db file in the hassio dir.
