This worked beautifully, @Tamsy - many thanks for this detailed writeup! 
1 Like
Raspberry Pi 5 is not officially supported yet.
noticed today that HA Supervisor wasn’t working (would not initialize). played around a bit with no success, so I thought I would do a fresh install following the above instructions. What worked before now gives the same issue, Supervisor will not initialize. Not sure if it is a recent update to HA/HA Supervisor/ Docker, but as it stand now Supervisor will not work.
well I feel like a butt…
feedback in the link worked, Supervisor back up and running. Thank-you.
Hi,
Have you found a solution to this?
Please read 4 posts above.
Ηι,
It has been a little while since it suddenly won’t let me update any add-on, do you know what might be the cause?
Have you checked whether your installation is still in a “Healthy” and “Supported”-condition?
Settings → System → Repairs → 3 dots upper right → Information about System → Home Assistant Supervisor
“Unhealthy” will also block updating Addons.
You’ll find a possible way to fix the issue HERE (the part near the end telling: "In case you are still seeing the status “Unsupported” and/or “Unhealthy” at this point, re-run the “supervised-installer”).
2 Likes
Works for me every time. 
@Tamsy you think the instruciotns will be the same for supervised when supported on a RPI 5 using debian12?
I can not say for sure but I expect the instructions will be still valid for the RPI 5 
1 Like
I followed the instructions and successfully updated the Home Assistant core, but unfortunately, after that, I can’t access Home Assistant. I see that the Docker service for Home Assistant can’t start. In the logs, I get an error: 'homeassistant exec /init: exec format error
Did you lately upgrade Docker to 25.0.0?
Either downgrade Docker to 24.x.x or upgrade it to 25.0.1.
The issue you are describing could be related to THIS.
1 Like
I had version 25.0.1. I followed the link and downgraded to 24.0.7, but unfortunately, I still encounter the same error. The service refuses to start!
Im on rapberry pi 4
my OS:
Distributor ID: Debian
Description: Debian GNU/Linux 12 (bookworm)
Release: 12
Codename: bookworm
Below are my Docker services:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
a63e3d2fe46c ghcr.io/hassio-addons/uptime-kuma/aarch64:0.9.1 "/init" 6 hours ago Up 6 hours 0.0.0.0:3001->3001/tcp, :::3001->3001/tcp addon_a0d7b954_uptime-kuma
30f3ea11f517 homeassistant/aarch64-addon-configurator:5.6.0 "/init" 6 hours ago Up 6 hours (healthy) addon_core_configurator
8a47b85e3539 sabeechen/hassio-google-drive-backup-aarch64:0.111.1 "python3 -m backup" 6 hours ago Up 6 hours 0.0.0.0:1627->1627/tcp, :::1627->1627/tcp, 8099/tcp addon_cebe7a76_hassio_google_drive_backup
d5d0e3db43e4 ghcr.io/home-assistant/generic-x86-64-homeassistant:2023.10.3 "/init" 6 hours ago Exited (1) 32 seconds ago homeassistant
6a5043abcad0 homeassistant/aarch64-addon-ssh:9.7.1 "/init" 6 hours ago Up 6 hours addon_core_ssh
f457e70a471b ghcr.io/hassio-addons/zerotier/aarch64:0.17.3 "/init" 6 hours ago Up 6 hours addon_a0d7b954_zerotier
77442b7597e8 ghcr.io/hassio-addons/influxdb/aarch64:4.8.0 "/init" 6 hours ago Up 6 hours 0.0.0.0:8086->8086/tcp, :::8086->8086/tcp, 0.0.0.0:8088->8088/tcp, :::8088->8088/tcp addon_a0d7b954_influxdb
3994165ce1ba ghcr.io/hassio-addons/grafana/aarch64:9.1.1 "/init" 6 hours ago Up 6 hours (healthy) addon_a0d7b954_grafana
f8a926fbdafa ghcr.io/hassio-addons/adguard/aarch64:4.8.17 "/init" 6 hours ago Up 6 hours (healthy) addon_a0d7b954_adguard
5e98f89d3307 homeassistant/aarch64-addon-rpc_shutdown:2.4 "/init /run.sh" 6 hours ago Up 6 hours addon_core_rpc_shutdown
fdf17b00da5f homeassistant/aarch64-addon-mosquitto:6.3.1 "/init" 6 hours ago Up 6 hours 0.0.0.0:1883-1884->1883-1884/tcp, :::1883-1884->1883-1884/tcp, 0.0.0.0:8883-8884->8883-8884/tcp, :::8883-8884->8883-8884/tcp addon_core_mosquitto
bfd3351a9fb4 ghcr.io/home-assistant/aarch64-hassio-multicast:2023.06.2 "/init" 6 hours ago Up 6 hours hassio_multicast
1f59b19f95de ghcr.io/home-assistant/aarch64-hassio-audio:2023.12.0 "/init" 6 hours ago Up 6 hours hassio_audio
47318a51c754 ghcr.io/home-assistant/aarch64-hassio-dns:2023.06.2 "/init" 6 hours ago Up 6 hours hassio_dns
195c75f2697b ghcr.io/home-assistant/aarch64-hassio-cli:2023.11.0 "/init" 6 hours ago Up 6 hours hassio_cli
747848fed349 zigbee2mqtt/zigbee2mqtt-aarch64:1.33.1-1 "/sbin/tini -- /dock…" 6 hours ago Exited (1) 6 hours ago addon_45df7312_zigbee2mqtt
d35bd50f429b ghcr.io/home-assistant/aarch64-hassio-supervisor:latest "/init" 21 hours ago Up 6 hours hassio_supervisor
36b56092444f flask_app_new "/bin/bash" 3 months ago Exited (129) 3 months ago awesome_northcutt
86e3df383744 flask_app_new "/bin/bash" 3 months ago Exited (129) 3 months ago affectionate_jemison
6e57eb5cccac pms_pytest:latest "tail -f /dev/null" 3 months ago Exited (137) 3 months ago test_pms_pytest
b1fa62110c45 pms_nginx:latest "/start-nginx.sh" 3 months ago Exited (0) 3 months ago test_nginx_svalidation
40ad8b210207 svalidation:latest "docker-php-entrypoi…" 3 months ago Exited (0) 3 months ago test_svalidation
409e13ec2309 pms_nginx:latest "/start-nginx.sh" 3 months ago Exited (0) 3 months ago test_nginx_sentities
ad84609f0d8b pms_nginx:latest "/start-nginx.sh" 3 months ago Exited (0) 3 months ago test_nginx_sgateway
a32d1b04f6bd sentities:latest "docker-php-entrypoi…" 3 months ago Exited (0) 3 months ago test_sentities
3281d64b71a0 pms_phpmyadmin:latest "/docker-entrypoint.…" 3 months ago Exited (0) 3 months ago test_pms_phpmyadmin
619a9daff9ef pms_mysql:latest "docker-entrypoint.s…" 3 months ago Exited (0) 3 months ago test_sentities_db_slave
b797c2704e4b pms_mysql:latest "docker-entrypoint.s…" 3 months ago Exited (0) 3 months ago test_sgateway_db_slave
442d3b539956 pms_traefik:latest "/entrypoint.sh --ap…" 3 months ago Exited (0) 3 months ago test_pms_traefik
dcecc80f4f3a sgateway:latest "docker-php-entrypoi…" 3 months ago Exited (0) 3 months ago test_sgateway
96c1605adf8d pms_mysql:latest "docker-entrypoint.s…" 3 months ago Exited (0) 3 months ago test_sentities_db_master
70430f19a2d4 pms_mysql:latest "docker-entrypoint.s…" 3 months ago Exited (0) 3 months ago test_sgateway_db_master
e72aa6be55dd ghcr.io/home-assistant/aarch64-hassio-observer:2023.06.0 "/usr/bin/observer" 3 months ago Up 6 hours 0.0.0.0:4357->80/tcp, :::4357->80/tcp hassio_observer
baspax1@Raspi:~$ docker logs homeassistant
exec /init: exec format errorAssuming all containers listed with your above shown Docker services are official HA Addons/Integrations, do you have other containers running beside HA Supervised?
There must be more information regarding why HA refuses to start.
I find the new logging method with Debian 12 confusing. Thus I switched logging back to the good old rsyslog to monitor running daemons on the system.
You can do this by executing:
sudo -i
apt-get install rsyslog
mv /etc/rsyslog.conf /etc/rsyslog.conf.bak
nano /etc/rsyslog.conf
Copy the folowing content into the new empty /etc/rsyslog.conf and save the file:
# /etc/rsyslog.conf configuration file for rsyslog
#
# For more information install rsyslog-doc and see
# /usr/share/doc/rsyslog-doc/html/configuration/index.html
#################
#### MODULES ####
#################
module(load="imuxsock") # provides support for local system logging
module(load="imklog") # provides kernel logging support
#module(load="immark") # provides --MARK-- message capability
# provides UDP syslog reception
#module(load="imudp")
#input(type="imudp" port="514")
# provides TCP syslog reception
#module(load="imtcp")
#input(type="imtcp" port="514")
###########################
#### GLOBAL DIRECTIVES ####
###########################
#
# Use traditional timestamp format.
# To enable high precision timestamps, comment out the following line.
#
$ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat
#
# Set the default permissions for all log files.
#
$FileOwner root
$FileGroup adm
$FileCreateMode 0640
$DirCreateMode 0755
$Umask 0022
#
# Where to place spool and state files
#
$WorkDirectory /var/spool/rsyslog
#
# Include all config files in /etc/rsyslog.d/
#
$IncludeConfig /etc/rsyslog.d/*.conf
###############
#### RULES ####
###############
#
# First some standard log files. Log by facility.
#
auth,authpriv.* /var/log/auth.log
*.*;auth,authpriv.none -/var/log/syslog
#cron.* /var/log/cron.log
daemon.* -/var/log/daemon.log
kern.* -/var/log/kern.log
lpr.* -/var/log/lpr.log
mail.* -/var/log/mail.log
user.* -/var/log/user.log
#
# Logging for the mail system. Split it up so that
# it is easy to write scripts to parse these files.
#
mail.info -/var/log/mail.info
mail.warn -/var/log/mail.warn
mail.err /var/log/mail.err
#
# Some "catch-all" log files.
#
*.=debug;\
auth,authpriv.none;\
mail.none -/var/log/debug
*.=info;*.=notice;*.=warn;\
auth,authpriv.none;\
cron,daemon.none;\
mail.none -/var/log/messages
#
# Emergencies are sent to everybody logged in.
#
*.emerg :omusrmsg:*
Make sure rsyslog.conf is owned by user/group root:root:
sudo chown root:root /etc/rsyslog.conf
Now restart the rsyslog daemon:
sudo systemctl restart rsyslog
Make sure rsyslog has started successfully:
sudo systemctl status rsyslog
Now “tail” daemon.log
sudo tail -f /var/log/daemon.log --lines=100
Open another CLI and start the HA-Daemon there. Then switch back to the CLI showing daemon.log.
Any useful output about the failure to start HA showing up there? 
1 Like
Yes i have some containers that is for development but i didnt have any problem till now,
My containers:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
785985e90f81 ghcr.io/hassio-addons/zerotier/amd64:0.18.0 "/init" 34 hours ago Exited (1) 34 hours ago addon_a0d7b954_zerotier
a63e3d2fe46c ghcr.io/hassio-addons/uptime-kuma/aarch64:0.9.1 "/init" 2 days ago Up 2 days 0.0.0.0:3001->3001/tcp, :::3001->3001/tcp addon_a0d7b954_uptime-kuma
30f3ea11f517 homeassistant/aarch64-addon-configurator:5.6.0 "/init" 2 days ago Up 2 days (healthy) addon_core_configurator
8a47b85e3539 sabeechen/hassio-google-drive-backup-aarch64:0.111.1 "python3 -m backup" 2 days ago Up 2 days 0.0.0.0:1627->1627/tcp, :::1627->1627/tcp, 8099/tcp addon_cebe7a76_hassio_google_drive_backup
d5d0e3db43e4 ghcr.io/home-assistant/generic-x86-64-homeassistant:2023.10.3 "/init" 2 days ago Exited (1) 6 minutes ago homeassistant
6a5043abcad0 homeassistant/aarch64-addon-ssh:9.7.1 "/init" 2 days ago Up 2 days addon_core_ssh
77442b7597e8 ghcr.io/hassio-addons/influxdb/aarch64:4.8.0 "/init" 2 days ago Up 2 days 0.0.0.0:8086->8086/tcp, :::8086->8086/tcp, 0.0.0.0:8088->8088/tcp, :::8088->8088/tcp addon_a0d7b954_influxdb
3994165ce1ba ghcr.io/hassio-addons/grafana/aarch64:9.1.1 "/init" 2 days ago Up 2 days (healthy) addon_a0d7b954_grafana
f8a926fbdafa ghcr.io/hassio-addons/adguard/aarch64:4.8.17 "/init" 2 days ago Up 2 days (healthy) addon_a0d7b954_adguard
5e98f89d3307 homeassistant/aarch64-addon-rpc_shutdown:2.4 "/init /run.sh" 2 days ago Up 2 days addon_core_rpc_shutdown
fdf17b00da5f homeassistant/aarch64-addon-mosquitto:6.3.1 "/init" 2 days ago Up 2 days 0.0.0.0:1883-1884->1883-1884/tcp, :::1883-1884->1883-1884/tcp, 0.0.0.0:8883-8884->8883-8884/tcp, :::8883-8884->8883-8884/tcp addon_core_mosquitto
bfd3351a9fb4 ghcr.io/home-assistant/aarch64-hassio-multicast:2023.06.2 "/init" 2 days ago Up 2 days hassio_multicast
1f59b19f95de ghcr.io/home-assistant/aarch64-hassio-audio:2023.12.0 "/init" 2 days ago Up 2 days hassio_audio
47318a51c754 ghcr.io/home-assistant/aarch64-hassio-dns:2023.06.2 "/init" 2 days ago Up 2 days hassio_dns
195c75f2697b ghcr.io/home-assistant/aarch64-hassio-cli:2023.11.0 "/init" 2 days ago Up 2 days hassio_cli
747848fed349 zigbee2mqtt/zigbee2mqtt-aarch64:1.33.1-1 "/sbin/tini -- /dock…" 2 days ago Exited (1) 2 days ago addon_45df7312_zigbee2mqtt
d35bd50f429b ghcr.io/home-assistant/aarch64-hassio-supervisor:latest "/init" 2 days ago Up 2 days hassio_supervisor
36b56092444f flask_app_new "/bin/bash" 3 months ago Exited (129) 3 months ago awesome_northcutt
86e3df383744 flask_app_new "/bin/bash" 3 months ago Exited (129) 3 months ago affectionate_jemison
6e57eb5cccac pms_pytest:latest "tail -f /dev/null" 3 months ago Exited (137) 3 months ago test_pms_pytest
b1fa62110c45 pms_nginx:latest "/start-nginx.sh" 3 months ago Exited (0) 3 months ago test_nginx_svalidation
40ad8b210207 svalidation:latest "docker-php-entrypoi…" 3 months ago Exited (0) 3 months ago test_svalidation
409e13ec2309 pms_nginx:latest "/start-nginx.sh" 3 months ago Exited (0) 3 months ago test_nginx_sentities
ad84609f0d8b pms_nginx:latest "/start-nginx.sh" 3 months ago Exited (0) 3 months ago test_nginx_sgateway
a32d1b04f6bd sentities:latest "docker-php-entrypoi…" 3 months ago Exited (0) 3 months ago test_sentities
3281d64b71a0 pms_phpmyadmin:latest "/docker-entrypoint.…" 3 months ago Exited (0) 3 months ago test_pms_phpmyadmin
619a9daff9ef pms_mysql:latest "docker-entrypoint.s…" 3 months ago Exited (0) 3 months ago test_sentities_db_slave
b797c2704e4b pms_mysql:latest "docker-entrypoint.s…" 3 months ago Exited (0) 3 months ago test_sgateway_db_slave
442d3b539956 pms_traefik:latest "/entrypoint.sh --ap…" 3 months ago Exited (0) 3 months ago test_pms_traefik
dcecc80f4f3a sgateway:latest "docker-php-entrypoi…" 3 months ago Exited (0) 3 months ago test_sgateway
96c1605adf8d pms_mysql:latest "docker-entrypoint.s…" 3 months ago Exited (0) 3 months ago test_sentities_db_master
70430f19a2d4 pms_mysql:latest "docker-entrypoint.s…" 3 months ago Exited (0) 3 months ago test_sgateway_db_master
e72aa6be55dd ghcr.io/home-assistant/aarch64-hassio-observer:2023.06.0 "/usr/bin/observer" 3 months ago Up 2 days 0.0.0.0:4357->80/tcp, :::4357->80/tcp hassio_observer
I followed all instuctions about rsyslog, started on two seperate cli, tried to run the homeassistant
I recorder this on log:
Feb 3 15:36:09 Raspi containerd[2649]: time="2024-02-03T15:36:09.160074711+02:00" level=info msg="shim disconnected" id=d5d0e3db43e4fbdbc967e6238543015e2a775c53abd4af097e5b67b4da62aa5f
Feb 3 15:36:09 Raspi dockerd[2723]: time="2024-02-03T15:36:09.160223114+02:00" level=info msg="ignoring event" container=d5d0e3db43e4fbdbc967e6238543015e2a775c53abd4af097e5b67b4da62aa5f module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Feb 3 15:36:09 Raspi containerd[2649]: time="2024-02-03T15:36:09.161520267+02:00" level=warning msg="cleaning up after shim disconnected" id=d5d0e3db43e4fbdbc967e6238543015e2a775c53abd4af097e5b67b4da62aa5f namespace=moby
Feb 3 15:36:09 Raspi containerd[2649]: time="2024-02-03T15:36:09.161644301+02:00" level=info msg="cleaning up dead shim"
Feb 3 15:36:09 Raspi containerd[2649]: time="2024-02-03T15:36:09.186905294+02:00" level=warning msg="cleanup warnings time=\"2024-02-03T15:36:09+02:00\" level=info msg=\"starting signal loop\" namespace=moby pid=412076 runtime=io.containerd.runc.v2\n"
Feb 3 15:36:09 Raspi systemd[1]: var-lib-docker-overlay2-443e9827f916448058c143ca72e1eda3443ef5efbd8db7a77e00242e83c536e0-merged.mount: Deactivated successfully.
Feb 3 15:36:14 Raspi containerd[2649]: time="2024-02-03T15:36:14.847198915+02:00" level=info msg="loading plugin \"io.containerd.event.v1.publisher\"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1
Feb 3 15:36:14 Raspi containerd[2649]: time="2024-02-03T15:36:14.847405299+02:00" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1
Feb 3 15:36:14 Raspi containerd[2649]: time="2024-02-03T15:36:14.847442650+02:00" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1
Feb 3 15:36:14 Raspi containerd[2649]: time="2024-02-03T15:36:14.848098818+02:00" level=info msg="starting signal loop" namespace=moby path=/run/containerd/io.containerd.runtime.v2.task/moby/d5d0e3db43e4fbdbc967e6238543015e2a775c53abd4af097e5b67b4da62aa5f pid=412123 runtime=io.containerd.runc.v2
Feb 3 15:36:14 Raspi systemd[1]: run-docker-runtime\x2drunc-moby-d5d0e3db43e4fbdbc967e6238543015e2a775c53abd4af097e5b67b4da62aa5f-runc.x8m11H.mount: Deactivated successfully.
Feb 3 15:36:15 Raspi dockerd[2723]: time="2024-02-03T15:36:15.044746633+02:00" level=info msg="ignoring event" container=d5d0e3db43e4fbdbc967e6238543015e2a775c53abd4af097e5b67b4da62aa5f module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Feb 3 15:36:15 Raspi containerd[2649]: time="2024-02-03T15:36:15.045226398+02:00" level=info msg="shim disconnected" id=d5d0e3db43e4fbdbc967e6238543015e2a775c53abd4af097e5b67b4da62aa5f
Feb 3 15:36:15 Raspi containerd[2649]: time="2024-02-03T15:36:15.045392616+02:00" level=warning msg="cleaning up after shim disconnected" id=d5d0e3db43e4fbdbc967e6238543015e2a775c53abd4af097e5b67b4da62aa5f namespace=moby
Feb 3 15:36:15 Raspi containerd[2649]: time="2024-02-03T15:36:15.045433893+02:00" level=info msg="cleaning up dead shim"
Feb 3 15:36:15 Raspi containerd[2649]: time="2024-02-03T15:36:15.075369196+02:00" level=warning msg="cleanup warnings time=\"2024-02-03T15:36:15+02:00\" level=info msg=\"starting signal loop\" namespace=moby pid=412165 runtime=io.containerd.runc.v2\n"
Feb 3 15:36:15 Raspi systemd[1]: var-lib-docker-overlay2-443e9827f916448058c143ca72e1eda3443ef5efbd8db7a77e00242e83c536e0-merged.mount: Deactivated successfully.Once the Pi5 is officially supported the installation instructions will be updated as/if needed.
Providing work arounds for a beta release may lead to issues that are not within the scope of this guide.
2 Likes
@kanga_who @Tamsy thank you so much for this priceless invaluable thread and your consistent ongoing support - and a question (at the end)!
You guys rock with this. I’ve already purchased a RPI5 and power supply (with no real picture why needed other than the fact I have no hardware backup when I have a failure with the current setup), waiting for better cases and peripherals but that will replace the RPI4 that I have now - eventually (since the RPI4 is running smooth as butter right now off a SSD plugged into a USB3 port). I was thinking of maybe switching over to the RPI 5 and then keeping the RPI4 as backup if the RPI 5 hardware fails. But there may be better options. I know there is more robust hardware out there but the RPI’s are so much fun to play with!
I have pretty much everything in the home automated right now:
Door (open/closed sensors only, not locks (yet!?!)
Window (open/closed sensors)
Smoke/CO2 (Yolink only for 24/7 monitoring)
Leak/Moisture (Yolink only for 24/7 monitoring)
Motion (Shelly & also Yolink for 24/7 monitoring)
Heating/Coling vents (flair)
Nest Thermostat
Ring Doorbell
Lights (shelly all over the place)
Weather station (AmbientWeather WS-2902C)*
The only reason why I went with HA Supervised really is because of this * above, I actually am running Weewx on the RPI4 host outside of HA to transmit weather data to 10 or so weather webesites all around the world, and then in addition to the AmbientWeather integration I have then status of those weather transmissions sent to HA via daemons watching the weewx and syslogs making rest api calls to HA sensors to update them - it was s truggle as a python/linux noob but mouch more elegant than just command line sensors scraping the logs which is what I had before.
I probably will not go with any smart locks as the home is older and has for instance a beautiful very old and huge mortice lock on the front door that we like.
Enough rambling. My next major step (and maybe the last at this point) would be to add a weathercam and security type video cameras.
I was leaning very strongly towards Frigate. What does anyone feel are the next best steps for me with regards to the ‘video’ leg of my HA journey (I do not want to have any hardware near capacity or overutilized - maybe leave the weewx on the RPI4, put HAOS on the RPI5 listening to the RPI4 Weewx, and then different hardware for the cameras like a DVR that can interact with HA)? Thoughts?