I have finally managed to fully run Home Assistant Supervised on my Raspberry Pi 5 without encountering any problems so far. Here’s what I did:
I downloaded Home Assistant Supervised via VirtualBox and installed it within VirtualBox. Then I proceeded with the installation, created a backup, and downloaded it.
Next, I downloaded the Raspberry Pi 5 Core from GitHub (the only version available for Pi 5) and used it to create a bootable SSD. Its not needed to go forward after the wifi setup Link:
Once it was booted up, I chose not to go through a new configuration but instead opted to restore the backup I had made from the RB Pi 4.
The system successfully performed this task, and now Home Assistant Supervised starts up smoothly without any issues, with all the supervised features intact. It works flawlessly, including updates.
So far, I haven’t encountered any problems. Perhaps this information will be useful to you! Please let me know if it works well for you too!
I have unrelated processes running on the same host (outside any container) that need to communicate with the HA instance. Is that possible with VirtualBox?
For those who use a microSD card, with the release of Home Assistant OS 11.5 I migrated to a Raspberry Pi 5 using a microSD card and I haven’t had any issues so far.
I have a daemon running on my RPI4 host with fans, a resistor and transistor attached to 3 of the GPIO pins to turn the fan on at 60 degrees C and turn it back off at 50 degrees C. The daemon has specific text it enters into the syslog which I have shown in HA as a sensor.
I got the impression that functionality is now built into the RPI5 with a separate dedicated connector to the RPI for said fans on a case?
Yes - new jumpers for a special RPi5 fan (either big heatsink, or smaller case types, both fit in the RPi case with the lid). The fan auto-throttles and is mostly silent.
Just make sure that you update the RPi 5’s EEPROM Boot Loader settings to boot off of the NVME drive using a normal install of Raspberry Pi Operating System. I used a microSD card flashed with the normal Raspberry Pi OS, then booted off of the microSD, adjusted the boot loader to boot first off of the NVME drive, and saved those settings. I then removed the microSD card, and installed my freshly HAOS imaged NVME drive and the RPi 5 booted right up into HAOS.
Yeah they have gone for a 4 pin fan with a mx header.
To be honest I wish they had continued with the 3pin gpio fans and then also we would of had a blower to go with all Pi’s.
Great, i did not know that, last i checked it was still version 1.84 without it.
Now i just need to wait until my NVME drive arrives, i had one i was sure was NVME but it would not work…And a little googling revealed it was SATA, not NVME…
So now i ordered one of the drives in the “it works” list on pimoroni’s site.
For the most part HA with PI 5 is working as it was on my PI 4, also have it working on and a NVMe drive. There are a few things that have broken though such as the Met office integration, the history graph of my Hive thermostat and the HACS pending update notifier has no graph and constantly spinning
yeah sadly I’ve tried to restore my HA backup from my PI4 to my PI5 but it just hangs… unsure what to check or understand why the web site 8123 doesn’t come up after the restore…
supervisor logs aren’t very clear… wasted to much time on this so will put on the back burner for a bit.
It does take a while to do the initial set-up once installed. Make sure the IP address of the new PI is set as the same as the PI4 in your router or port forward the new IP like the old one. Once you login it will take a while, clicking the restore option and locating the full backup file also takes a while
I tried getting this to work on my RPi 5 with Pimoroni NVME base and it boots fine and lets me flash HA to the drive and then it boots fine off of the drive, but it does not want to complete the setup process, the web interface says there were problems and then it complains it does not have internet connectivity, even though the CLI screen output shows it has got an ip, and it was downloading the image to flash just fine.
Complains there is no internet and “will retry in 30 seconds” but have had it on for 30 minutes without it ever getting past that.
Don’t really know what the deal is, but the installer seems to be broken…Atleast for me.
I thought about that, normally i do DNS myself with another Raspberry Pi with PiHole, normally i have no problems.
I tried changing the DNS offered by DHCP and rebooted, it then pointed to 8.8.8.8 and i confirmed in the CLI that the DNS was indeed set to 8.8.8.8, but it did not change anything sadly.
I dont suppose it would be a problem to have my current HA on x.x.x.250 with a fixed IP, and then the new one i am setting up on DHCP, where it got x.x.x.34
As my Home Assistant proof of concept (which has gone on for a year plus…) Raspberry Pi 3 had started running out of memory, I decided to upgrade to a Raspberry Pi 5, 8GB, rPi case, rPi active cooler, Geekworm x1003 and 240GB Samsung M.2 Nvme SSD. All went way smoother than expected!
Flashed HA onto the SSD, and bookworm onto the SD card via the official rPi imager running on my MacBook. I then assembled everything and booted up the rPi. I was surprised to see the nvme show up on first boot, even though dtparam=pciex1 was not in the config.txt (still perplexed about that one).
Regardless, I updated the rPi firmware to the latest, and added the following to the config.txt anyways:
dtparam=pciex1
dtparam=pciex1_gen=3
I also edited the EEPROM and added:
BOOT_ORDER=0xf416
PCIE_PROBE=1
And rebooted into HA running on the SSD. Restoring from a full backup of the rPi3 took less than a minute and I was up and running. HA, and in particular, Z-Wave devices are SO much more responsive now. It’s a joy to use.
One thing I haven’t figured out, is how to add the device tree pci parameters above to HA. My understanding is those are specific to the OS being booted, and I can’t find the /boot/firmware/config.txt file in HA. I suspect it’s not accessible. Clearly the PCIe bus is enabled, but I’d like to boost it to v3 speeds.
