I had tried from Arch update and it has failed. Reverting to 0.96.1 I got things going again.
My matter is to find what are the broken dependencies, which are not satisfied.
Perhaps I should update from pip, rather than pacman or AUR-helper.
Last solution was
sudo CFLAGS=$(pkg-config --cflags libffi) LDFLAGS=$(pkg-config --libs libffi) pip install --upgrade homeassistant --ignore-installed PyYAML
But PyYAML has changed recently. Other archer here ?
You should be using a venv and pip. Are you?
I’m using the way that I set a special user, “hass”, which has few privileges, so this will ensure a good protection. But the system is installed over an Archlinux, because I prefer to have certain control about packages and or scripts which cannot fit into HA.
Perhaps I started in such way, because I knew nothing about the way to add components into HA, so I managed to add my own directly into python site-packages.
The Arch rolling system ensure newer package to be passed in, but I’d like to find the way which give me the package dependencies.
$ pacman -Qi home-assistant
Name : home-assistant
Version : 0.96.0-1
Description : Open source home automation that puts local control and privacy first
Architecture : any
URL : https://home-assistant.io/
Licenses : APACHE
Groups : None
Provides : None
Depends On : python-aiohttp python-astral python-async-timeout python-attrs
python-bcrypt python-certifi python-cryptography
python-importlib-metadata python-jinja python-pyjwt python-pip
python-pytz python-requests python-ruamel-yaml python-slugify
python-voluptuous python-voluptuous-serialize python-yaml
Optional Deps : net-tools: Nmap host discovery [installed]
openzwave: Z-Wave integration
python-lxml: Meteo France integration
Required By : None
Optional For : None
Conflicts With : None
Replaces : None
Installed Size : 37.93 MiB
Packager : Arch Linux ARM Build System <[email protected]>
Build Date : Thu Jul 18 20:57:42 2019
Install Date : Tue Jul 23 14:28:02 2019
Install Reason : Explicitly installed
Install Script : No
Validated By : None
Theoretically it seems that all dependencies are satisfied, but during the HA restart it shows that is not true.
I know what arch is, and I do love it. I am also a gentoo user, so I know all about systems which have a lot more control than debian/ubuntu and their ilk.
However, even if I was using gentoo or arch, I would follow the recommended install method. Up to you, but don’t come here with some non recommended set up and ask people to fix it. That is what the arch forums are for.
OK, I’m not asking a fix.
I’d like to know what HA has to complain about unsatisfied dependencies. Perhaps I have to dig into the journal to find if HA tells all about that.
About the other options, I’m aware that is rather a risk to go out of the recommendations 
Updated to 0.96.4, doesn’t shows lovelace, 404 
Jul 25 15:11:40 alarm hass[2464]: 2019-07-25 15:11:40 INFO (MainThread) [homeassistant.setup] Setup of domain device_tracker took 21.4 seconds.
Jul 25 15:11:40 alarm hass[2464]: 2019-07-25 15:11:40 INFO (SyncWorker_3) [homeassistant.loader] Loaded ffmpeg from homeassistant.components.ffmpeg
Jul 25 15:11:40 alarm hass[2464]: 2019-07-25 15:11:40 INFO (MainThread) [homeassistant.setup] Setting up camera
Jul 25 15:11:40 alarm hass[2464]: 2019-07-25 15:11:40 INFO (MainThread) [homeassistant.setup] Setting up ffmpeg
Jul 25 15:11:40 alarm hass[2464]: 2019-07-25 15:11:40 INFO (MainThread) [homeassistant.setup] Setup of domain ffmpeg took 0.3 seconds.
Jul 25 15:11:40 alarm hass[2464]: 2019-07-25 15:11:40 INFO (MainThread) [homeassistant.components.camera] Setting up camera.ffmpeg
Jul 25 15:11:40 alarm hass[2464]: 2019-07-25 15:11:40 INFO (MainThread) [homeassistant.components.camera] Setting up camera.ffmpeg
Jul 25 15:11:40 alarm hass[2464]: 2019-07-25 15:11:40 INFO (MainThread) [homeassistant.setup] Setup of domain camera took 0.3 seconds.
Jul 25 15:11:40 alarm hass[2464]: 2019-07-25 15:11:40 INFO (MainThread) [homeassistant.bootstrap] Home Assistant initialized in 25.72s
Jul 25 15:11:40 alarm hass[2464]: 2019-07-25 15:11:40 INFO (MainThread) [homeassistant.core] Starting Home Assistant
Jul 25 15:11:40 alarm hass[2464]: 2019-07-25 15:11:40 INFO (MainThread) [homeassistant.core] Timer:starting
Jul 25 15:11:40 alarm hass[2464]: 2019-07-25 15:11:40 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.2829502704] Received invalid command: get_panels
Jul 25 15:11:40 alarm hass[2464]: 2019-07-25 15:11:40 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.2829502704] Received invalid command: frontend/get_themes
Jul 25 15:11:40 alarm hass[2464]: 2019-07-25 15:11:40 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.2829502704] Received invalid command: frontend/get_translations
What dependencies???
clear your browser cache.
I downgrade HA, for this time. That didn’t required to clear the cache.
I’ll try again, when I’ll find the way to get a step back.
So I need to understand what I should backup, in order to be on feet in few minutes when the case is not solvable.
To whom don’t know my setup is on ALarm, I tried the pacman upgrade and I repeated with pip install to get the things in sync. No errors came out.
I’m expecting to finalize my setup in a box, so any intervention should warrant that I won’t need to open the box for anything. Even wired connection might not be acceptable, so I suppose that at the least the OS and SSH to be working. That would allow me to have the system working , even the HA will not come alive.
For the worst situation, I think I’ll get a SD card with a recovery system installed and open the box. But I face currently that I can’t access the eMMC.
I’m thinking about to backup the entire /usr/lib/python3.7/site-packages/. Will it suffice ?