The image which was available on Raspberry Pi Imager so far was mainly meant to be flashed on a USB flash drive and only contains an installer. This installer is not compatible with the CM5 on Yellow.
Since today the Raspberry Pi Imager offers the HAOS image which can be directly flashed onto the CM5 eMMC (or NVMe for the light variant) when using rpiboot:
Hi all,
I think it would be beneficial for all Yellow users if the next revision for CM5 Modules will accommodate holes pattern for standard CM5 Cooling fan from Raspberry itself!
@agners My current system is a cm4 with eMMC and HAOS installed on the NVMe.
Is it possible to install a CM5016000 “16GB RAM – 0GB Storage (Lite)” and then do an install of HAOS via rpiboot directly on the NVMe?
After that can i restore the full backup image?
I had assumed that “yellow support for cm5” also meant “generic cm5” support but that does not seem to be the case.
Neither the generic raspberry release nor the yellow specific one work on a cm5 (using eMMC) when using a Compute Module 5 IO Board instead of a yellow.
I’m having network issues with my current setup and I bought the CM5 Dev kit for HAOS. I hope there will be a working release for the “generic CM5”, since I’ve spent too much money for the dev kit to just replace it with Yellow.
So there are issues using the new Home Assistant OS 14 on Raspberry Pi’s official Compute Module 5 Development Kit with their Raspberry Pi Compute Module 5 IO board?
Raspberry Pi Development Kit for Compute Module 5 == Raspberry Pi Compute Module 5 with their reference Raspberry Pi Compute Module 5 IO board?
Well at least with my limited knowledge I couldn’t get it to boot. I tried both eMMC and NVME and both images on Pi imager. The image for the Yellow just loop restart w/ u-boot icon appearing on the screen and the RPI 5 image does load somewhat, but it halts when there is a High Speed DDR5 recognize or something.
Does that mean you are using RPIBOOT method described in the “Option 2: Reinstall Home Assistant OS using rpiboot” + “Using Windows Installer…” there? → How to reinstall the operating system – Home Assistant Yellow and if so have you also tried to the even more complicated “From source code…” way too?
I haven’t spent the time to troubleshoot but I’m going from a CM4 (4GB RAM, No eMMC, with WiFi, booting from M.2 SSD) to a CM5 (4GB RAM, 32 GB eMMC, WiFi, boot from M.2 SSD) and sadly my HA Yellow will not boot. Looks like I may need to re-image and restore from backup like others have done.
Hi, I installed RPIBOOT and Pi Imager on W11, disabled the eMMC boot w/ jumper on a J2 from IO board, connected the IO board to PC w/ USB-C, ran the RPIBOOT, ran the Pi Imager and then the Pi Imager detected the eMMC and NVME. There were two image options in the Pi Imager under RPI5->Home Assistant and neither worked.
Just upgraded my HA Yellow from a CM4 lite to a CM5 lite which changed my fixed IP address as the CM5 has a different network MAC address. That was relatively easy to solve and have access to my HA now on the original IP but lots of things don’t work, the worst of which is that ZHA doesn’t load so none of my Zigbee or Thread devices work any more. Anyone come across this?
Update: also tried it on a spare HA Yellow POE where I installed HAOS 14.1 via rpiboot which went fine and then restored from backup but has the identical issue - ZHA won’t load so none of my Zigbee or Thread devices are working. I’m going to assume this is a genuine issue/bug as I’ve reproduced it on 2 completely separate HA Yellow’s. Fingers crossed for a speedy resolution.
I’m not sure anymore what I actually did, but somehow I got this to work. I first installed the Raspberry PI OS to eMMC. I’m quite sure that then I just used the PI Imager from RPI OS to install the Home Assistant OS (RPI5 image) to NVME. Finally I found some setting from the RPI OS to change the boot order and CM5+IO Board booted to HAOS. I used full back up and everything works now very well. I’m not sure what was the issue w/ HAOS installed to eMMC via Windows & PI Imager.
Was able to simply swap my CM4108032 for a new CM5108032 on my HA Yellow PoE. I have HAOS on my 1TB NVME drive, so no need to worry about the eMMC at all in my situation.
Nice upgrade. Really like how much quicker ESPHome build times are now.
Thank you @agners and the entire Home Assistant/Nabu Casa team for making the HA Yellow upgradable!
Spent a day tinkering with the CM4 → CM5 upgrade on the HA Yellow w/ PoE, and it did not go flawlessly.
I went from the CM4108032 + to CM5108032. The HA Yellow data was moved to a 1TB NVMe on the CM4 installation.
Following the guide to use rpiboot and then the RPi Imager, the experience was not great:
after flashing the HA OS Yellow on the CM5 eMMC, when the device restarts, it goes into a bootloop.
Apart from the device LEDs telling you it is booting over and over, and the device being pingable for a few seconds, there were no other clues what is happening.
What was actually happening is that it was still booting off the NVMe disk. After removing the NVMe disk, the device actually booted and I could restore my full back-up.
As a sanity check, I put in the NVMe disk in and yes, it would still boot from the NVMe disk and have a boot loop. I had to wipe the NVMe disk.
The problem here is that there is no progress bar of any sorts, so it was not possible to know what was happening in the background, after letting it run for a long time, I decided to SSH into the device to check the logs, but I was none the wiser. (at this point the Web UI would still not load)
As mentioned above the MAC address actually changed; this meant it would no longer be assigned the static IP if you had mapped it in your router. After addressing that and restarting both the router and HA Yellow, the Web UI became accessible.
At this point I installed the wiped NVMe disk, and moved the data there; that was nice and smooth!
However as @roelof1 mentioned, ZHA is effectively dead. It looks like /dev/ttyAMA1 is unresponsive, as the Silicon Labs Multiprotocol keeps spamming
[01:36:12:551163] Info : Failed to connect, secondary seems unresponsive
[01:36:12:551176] Info : Connecting to Secondary...
I cant even get rpiboot to work windows or linx , waiting for device… 2 days uggggg
I can confirm ZHA is not working with a 8Gb CM5 lite module.
Haven’t got any logs at the moment probably won’t have for a few days yet
I have bought an SONOFF Zigbee 3.0 USB Dongle Plus and migrated to Zigbee2MQTT.
ZHA not working is due to the Zigbee controller not being configured properly so the OS is not aware that it is there.
I installed my old conbee 2 stick on another pi I’m using as a media server and zigbee2mqtt. As a workaround it’s fine and unnoticeable in day to day usage
I am having no issues whatsoever using the HA Yellow’s built-in Zigbee radio via Zigbee2MQTT with my CM5. Not sure why others are having issues. 
Same prolem