Installed on rpi 5 os or Debian?
Is it stable?
I used Raspberry Pi OS and haven’t had any issues once I actually got it installed.
Observer reports:
| Supervisor: | Connected |
|---|---|
| Supported: | Supported |
| Healthy: | Healthy |
I’ve had it running since December and Core (and some addons) have upgraded several times without any issue. Currently running version 2024.1.5
Supervised? Cause the topic says supervised.
Yep, Supervised. All addons and updates available via the UI.
how did you manage that 
I am getting OS-Agent bot modul is loaded and OS-Agent installed.
[supervisor.host.sound] Can’t update PulseAudio data: Failed to connect to pulseaudio server
[supervisor.dbus.rauc] Host has no rauc support. OTA updates have been disabled.
[supervisor.dbus.agent] No OS-Agent support on the host. Some Host functions have been disabled.
could you share any insights how to fix it? thank you
I followed this guide using a fresh install of raspbian.
I initially had some problems with memory allocation which I resolved by booting kernel8.img and manually edited the /var/lib/dpkg/info/homeassistant-supervised.templates file to add the pi5 to the options.
‘rauc’ is for updating embedded linux (HA-OS) but you are using raspbian, which you have to update yourself, so you can ignore the supervisor.dbus… messages.
I don’t know about the pulseaudio since I’m not using any audio and don’t get that message.
1 Like
Hey I made a tutorial about the installation process on my Github. It may help you.
1 Like
I’ve managed to install HA Supervised on Ubuntu 23.10 @ RPi 5 simply by setting system variable BYPASS_OS_CHECK to true and then installing the homeassistant-supervised.deb. The preinstall check allows using this variable to bypass the OS Check. It will still complain that the system is not supported, but will continue in installation.
If you are not root, you need to sudo -s first, then set the variable:
export BYPASS_OS_CHECK=true
and then continue with step 4 of the HA-Supervised install guide:
wget -O homeassistant-supervised.deb https://github.com/home-assistant/supervised-installer/releases/latest/download/homeassistant-supervised.deb
apt install ./homeassistant-supervised.deb
After the installation has completed HA complained about NetworkManager not working. I had to follow the steps on the link HA provided (and set chmod 600 to all created config files) and rebooted the RPi. After reboot everything worked fine.
To folks landing on this thread now that HA is supported for Raspberry Pi 5, here are the install steps:
# Ensure up-to-date.
sudo apt update && sudo apt upgrade -y && sudo apt --fix-broken install && sudo apt autoremove -y
# Install dependencies.
sudo apt install apparmor cifs-utils curl dbus jq libglib2.0-bin lsb-release network-manager nfs-common systemd-journal-remote systemd-resolved udisks2 wget -y
sudo systemctl restart systemd-resolved
# Install Docker.
curl -fsSL get.docker.com -o install-docker.sh && sh install-docker.sh
# sh install-docker.sh --dry-run
# sudo docker run hello-world
# Install OS Agent.
wget https://github.com/home-assistant/os-agent/releases/download/1.6.0/os-agent_1.6.0_linux_aarch64.deb
sudo dpkg -i os-agent_1.6.0_linux_aarch64.deb
# Verify that the OS agent has been successfully installed:
# gdbus introspect --system --dest io.hass.os --object-path /io/hass/os
# Install Home Assistant
wget https://github.com/home-assistant/supervised-installer/releases/latest/download/homeassistant-supervised.deb
sudo dpkg -i ./homeassistant-supervised.deb
# sudo BYPASS_OS_CHECK=true dpkg -i ./homeassistant-supervised.deb
# sudo dpkg --configure -a
# sudo dpkg --purge homeassistant-supervised
# To fix "Unsupported system - AppArmor issues: System is unsupported because
# AppArmor is working incorrectly and add-ons are running in an unprotected and
# insecure way. https://www.home-assistant.io/more-info/unsupported/apparmor
cp /boot/firmware/cmdline.txt cmdline.txt.bak
cp /boot/firmware/config.txt config.txt.bak
sudo sed -i '${s/$/ apparmor=1 security=apparmor/}' /boot/firmware/cmdline.txt
# If something's going wrong, use journalctl -f to get your system logs. If you
# are not familiar with Linux and how you can fix issues, we recommend to use
# our Home Assistant OS.
printf "Navigate to http://%s:8123 after rebooting ('sudo reboot')\n" $(hostname -I | awk '{print $1}')
If your audio stops working (e.g., Device or resource busy) install the Alsa & PulseAudio Fix add-on.
5 Likes
hi,
it happens to me that in few days it just become unhealthy, and I have to restart whole pi.
is there any solution to that?
thank you
Got HA started on raspberry OS (RPI5) following this. Just need to wait little bit till HA starts before going to IP:8123 page!
same thing happening to me.
system shows “healthy, supported, etc” but after couple of days i get the unhealthy warning
If you click on the ‘unhealthy’ warning, you should see the reason. Always interesting to know.
can’t remember what it said off the top of my head . will report back once it pops up again.
it’s just weird that after rebooting host everything is back to normal
After each update of Supervisor you get not healthy, nothing you can do about it, has been since the change from bullseye to bookworm.
You just need to restart the docker server: ‘systemctl restart docker’
A little less radical that rebooting the entire box.
1 Like
even less
docker restart hassio_supervisor
No need to restart all docker containers.
2 Likes
I get the following issue:
Don’t know about Pi 5, but on my Pi 4 I had to add
lsm="apparmor"
to cmdline.txt (in the boot partition)
and of cause
apt-get install apparmor
1 Like
did that, didnt help ((
UPDATE: Thanks for help, but on latest raspberry OS cmdline.txt has moved. So in order for that to work: ssh to rpi, then
sudo nano /boot/firmware/cmdline.txt
then at the end of the line to add lsm=“apparmor”
same and reboot