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!
3 Likes
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...
2 Likes
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
2 Likes
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 problem
Today i swapped the CM4 for a CM5 in my HA Yellow. Installed a new NVME via RPI Imager with HASS OS and restored everything from a Backup. I could log in etc etc. But it seems that my UPS isn’t detected anymore via the USB-A Ports. When I use ‘lsusb’ via Terminal it only shows:
Bus 003 Device 001: ID 1d6b:0002 Linux 6.6.62-haos-raspi xhci-hcd xHCI Host Controller
Bus 001 Device 001: ID 1d6b:0002 Linux 6.6.62-haos-raspi xhci-hcd xHCI Host Controller
Bus 004 Device 001: ID 1d6b:0003 Linux 6.6.62-haos-raspi xhci-hcd xHCI Host Controller
Bus 002 Device 001: ID 1d6b:0003 Linux 6.6.62-haos-raspi xhci-hcd xHCI Host Controller
Is there a Problem known with the USB Ports after the swap to a CM5? I even tried my old HA SkyConnect and that is also not recognized…
I am using NUT to monitor my CyberPower UPS via USB on my HA Yellow with a CM5 running the latest version of HAOS and HA. This system was upgraded from a CM4 to a CM5 with no issues observed.
So, it can work. Not sure why your system is behaving differently… 
how did you restore HAOS for the CM5 ? RpiBoot or RPIImage on a new NVME? Or did you just swap?
Also not working on Compute module 5 4GB with yellow POE.
I simply did a swap, as I was already booting off of an NVME M.2 SSD. I was pretty pleased with how smoothly it went. I swapped a CM4 8G RAM, 32GB eMMC with Wireless for a CM5 with the same configuration.
Very strange… After a swap from my CM4 to CM5 (both eMMC) it would not boot of the NVME. Therefore I reinstalled HAOS via RPI Imager and restored via a Backup. Very strange behaviour.
Hello, do you mean the USB Ports?
I reflashed the NVME with RPI Imager (again Homeassistant Yellow Image for RPi5) , restored from backup and everything is backup and running 
USB Ports working…
I have also just switched to CM5 (reinstallation and restore) and found that the video performance is significantly worse. In my case with the Unifi Protect integration. With a CM4 no problem and smooth, with the CM5 the streams are jerky and delayed. Has anyone ever had this?
It also makes a difference whether I use Chrome or Firefox, Chrome runs a little better.
1 Like
CM5 doesn’t support hardware h264 decoding
1 Like