I’ve been running DietPi on a RaspberryPi3 for a while now, only utilizing Pi-Hole.
Yesterday I upgraded to 7.7 and tried installing Home Assistant. Install seemed to go okay, but I couldn’t get the web front end to load. Stumbled around and figured out what I think is the problem, but I can’t figure out a solution: Looks like a library is missing or not linked properly (sorry I’m super rusty with Linux, I’m a .Net guy)
root@HammerPi:~# systemctl restart home-assistant
root@HammerPijournalctl -f -u home-assistant.service
-- Logs begin at Thu 2019-02-14 10:11:58 GMT. --
Oct 19 21:23:54 HammerPi systemd[1]: Stopped Home Assistant (DietPi).
Oct 19 21:23:54 HammerPi systemd[1]: Started Home Assistant (DietPi).
Oct 19 21:23:58 HammerPi homeassistant[14319]: 2021-10-19 21:23:58 ERROR (MainThread) [b][homeassistant.auth.providers] Unable to load auth provider homeassistant: libffi.so.7[/b]: cannot open shared object file: No such file or directory
Oct 19 21:23:58 HammerPi homeassistant[14319]: 2021-10-19 21:23:58 ERROR (MainThread) [homeassistant.bootstrap] Home Assistant core failed to initialize. Further initialization aborted
Oct 19 21:23:58 HammerPi homeassistant[14319]: 2021-10-19 21:23:58 WARNING (MainThread) [homeassistant.bootstrap] Unable to set up core integrations. Activating safe mode
Oct 19 21:23:58 HammerPi homeassistant[14319]: 2021-10-19 21:23:58 ERROR (MainThread) [homeassistant.auth.providers] Unable to load auth provider homeassistant: libffi.so.7: cannot open shared object file: No such file or directory
Oct 19 21:23:58 HammerPi homeassistant[14319]: 2021-10-19 21:23:58 ERROR (MainThread) [homeassistant.bootstrap] Home Assistant core failed to initialize. Further initialization aborted
Any tips on what to try to resolve this issue?
Thanks,
Chris
could you share some more system details
Required Information
- DietPi version | cat /boot/dietpi/.version
- Distro version | echo $G_DISTRO_NAME $G_RASPBIAN
- Kernel version | uname -a
- SBC model | echo $G_HW_MODEL_NAME or (EG: RPi3)
G_DIETPI_VERSION_CORE=7
G_DIETPI_VERSION_SUB=7
G_DIETPI_VERSION_RC=3
G_GITBRANCH='master'
G_GITOWNER='MichaIng'
buster 1
Linux HammerPi 5.10.63-v7+ #1459 SMP Wed Oct 6 16:41:10 BST 2021 armv7l GNU/Linux
RPi 3 Model B (armv7l)
Installed Software:
LLSP: Lighttpd | SQLite | PHP
Lighttpd: Extremely lightweight webserver
SQLite: Persistent single-file database system
PHP: Hypertext Preprocessor for dynamic web content
Pi-hole: block adverts for any device on your network
DietPi-RAMlog: Makes /var/log a RAM disk, preserves file structure on reboot
Dropbear: Lightweight SSH server
Home Assistant: open-source home automation platform
Unbound: validating, recursive, caching DNS resolver
I’ve tried removing HA and reinstalling it. whenever I run htop as the instructions call for, CPU always appears to be 0, so I ran
systemctl restart home-assistant
Results of that with journalctl →
Oct 19 22:50:44 HammerPi systemd[1]: Stopped Home Assistant (DietPi).
Oct 19 22:50:44 HammerPi systemd[1]: Started Home Assistant (DietPi).
Oct 19 22:50:48 HammerPi homeassistant[29279]: 2021-10-19 22:50:48 ERROR (MainThread) [homeassistant.auth.providers] Unable to load auth provider homeassistant: libffi.so.7: cannot open shared object file: No such file or directory
Oct 19 22:50:48 HammerPi homeassistant[29279]: 2021-10-19 22:50:48 ERROR (MainThread) [homeassistant.bootstrap] Home Assistant core failed to initialize. Further initialization aborted
Oct 19 22:50:48 HammerPi homeassistant[29279]: 2021-10-19 22:50:48 WARNING (MainThread) [homeassistant.bootstrap] Unable to set up core integrations. Activating safe mode
Oct 19 22:50:48 HammerPi homeassistant[29279]: 2021-10-19 22:50:48 ERROR (MainThread) [homeassistant.auth.providers] Unable to load auth provider homeassistant: libffi.so.7: cannot open shared object file: No such file or directory
Oct 19 22:50:48 HammerPi homeassistant[29279]: 2021-10-19 22:50:48 ERROR (MainThread) [homeassistant.bootstrap] Home Assistant core failed to initialize. Further initialization aborted
hmm issue could be that we switched to latest Python 3.9 but this is available on Bullseye only. Probably it is now causing issues on Buster systems. Something we would need to investigate with our developer. Let me ping him.
I don’t know the difference between buster and bullseye, is that something I can choose with a fresh install of DietPI on my RPI3?
Did you just target the MOTD To me? 
I’ll give that a try tonight
Nope it’s posted to all user. We are not able to assign dedicated MOTD 
Following up on this: I was able to get things working, did the following:
Follow the steps in this blog post to manually upgrade to Bullseye
Reinstalled Home Assistant (this time around I could see the CPU usage post install and post restart of the service)
Still was getting errors with Home Assistant and Diet PI had quit working too, saw a message about Lighttpd not starting up.
Uninstalled Lighttpd and changed the default web server to NIGX
Installed NGIX
Both Pi-Hole and Home Assistant now respond in a web browser.
Usually there is no relating between a web browser like Lighttpd/Nginx and HA because HA is using it’s own port 8123. You should be able to connect to HA even without a web server installed. BTW, the issues with Lighttpd could have been fixed 
I did “Fix” them, I replaced
Thank you for all your help, super please with how well all this works even with a few bumps which is mostly from me learning!
I cannot seem to get Home Automation to work properly - I get the 404 error when i try access it, I attempted to follow the buster update instructions and they didnt appear to work properly - plus i run SONARR so i’m unsure if this will be an issue.
could you share the log
journalctl -u home-assistant.service