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
Hi everyone,
I finally have my Rasberry Pi5 4GB and I’m trying to install Home Assistant Supervised.
I’ve already had a perfectly working installation on pi4 for several years and wanted to test the differences.
However, I noticed that even on a clean installation, without restoring from backup, it is very slow and every now and then all navigation freezes (both WEB and ssh terminal)
has this happened to any of you?
obviously already tried changing wifi, SD, etc. but it doesn’t change.
UPDATE:
what slows down is the network itself.
This is a test of a generic apt install where you can see the very low speed. same test on a clean version without homeassistant run at 2MB/s
Hey guys, any idea how to control GPIOs running HA Supervised in Docker container? I have successfully installed it on PI5 and restored my backup, but faced with just one problem - controlling my relays, which are hooked to GPIOs.
Thanks.
Hey folks, just about to give this a shot… As I understand it, this will after a few days show as unhealthy and simply rebooting resolves the issue? Any changes since March?
Not sure why you continue to persist with Supervised on a Pi, just install HA OS.
This. Keep anything else on the old Pi.
This is a hobby and I like the Raspberry PI platform and teaching myself linux etc.
Previously I had on the RPI4 in the photo on the left running Supervised on Debian.
Although Debian 5 does not support the RPI5, there is a good workaround that I have used here. Raspbian (based on Debian) does. For those of you who insist on Supervised - and in order to have the ability to access the host - for my purposes since I still want to access ths host - to use it for other purposes - but not to alter HA - so this works for me - switching over to HAOS with a twist.
I have finally moved from HA Supervised on the RPI4 (8 Gig) with Weewx on the host (left in picture below) - to Weewx only my RPI4 host and HAOS on the RPI5 (8 GIg) (right in the picture below, in an Pironman5 case with a 1TB nmve) - but in a VM (utilizing only 2 cores, and 4 GB) so that I can stil access the host on the RPI5 (one reason is to run the daemon on the host for the display on the front of the Pironman5 case). Both little CPU’s are still underutilized (even with half the cores and half the memory for HAOS in the VM) so I plan on adding more to them - on either RPI I can send sensor data into HA of course via REST.
I really like the Pironman5 case, in addition to the NVME hat it also includes a cpu fan, two case fans, and adapters that automatically convert the micro HDMI to regular HDMI, moves all the connections to the back, and even includes an infrared receiver (which I am not using).
The fans are pretty much off all the time in the Prionman5 case as they only go on when the CPU temp is above 60 degrees C which never happens (I turned them on temporarily for effect in the photo).
Also, the weewx processes on the RPI4 that monitor status of transmissions to external wensites from my weather station now send that data via REST into the HAOS front end as well so I had only minor work for that change…
If there are continuous transmission receipt error messages from any one of the websites I can fix the issue or reach out to them (occassionally something like this happens but usually resolves itself):
I was fully expecting to be able to do snapshots with the simple QEMU VMM I was using on the RPI5 - but I run into this error unfortunately: “Error creating snapshot: Operation not supported: internal snapshots of a VM with pflash based firmware are not supported”
I do have Google Drive backup running automatically but as that covers only HA - for now I will back both up from time to time to external portable SDD’s (cloning their drives each time) so I have a full copy of each entire drive’s contents. It’s nice to get back using a GUI to access them as well however (Supervised was problematic adding a desktop so I was stuck using on SSH on it which was no big deal):
So I have Raspbian on the RPI5 - with HAOS in a VM (!) and Debian on my RPI4 -
@kanga_who thanks for your help over the years on the supervised (and other) stuff…
Adding extra and unnecessary layers to what could be a very simple setup.
Whatever floats your boat.