Home Assistant Yellow gets CM5 support in HAOS 14

[xstrex]

Sticking with the original topic, I’ve got myself into a bind.

Running a Yellow, with a CM5 w/eMMC & a NVMe. As @ogiewon mentioned, I initially installed the HAOS on the eMMC, then installed the NVMe and performed a ‘move-data-disk’, which as you illustrated caused the install to be split. HAOS is still installed on the eMMC, and the data disk is on the NVMe, which has caused some odd performance issues…

I already have backups of everything, so I’m not worried there.

I’d like to wipe both the eMMC & NVMe and just install HAOS on the NVMe only, and bypass the eMMC altogether. But I’m not seeing a guide on the nabucasa site on exactly how to-do that? Would anyone have any suggestions?

Here’s the output of my current lsblk, it’s gross.

# lsblk
NAME         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
mmcblk0      179:0    0  58.2G  0 disk
|-mmcblk0p1  179:1    0    32M  0 part /mnt/boot
|-mmcblk0p2  179:2    0    24M  0 part
|-mmcblk0p3  179:3    0   256M  0 part /
|-mmcblk0p4  179:4    0    24M  0 part
|-mmcblk0p5  179:5    0   256M  0 part
|-mmcblk0p6  179:6    0     8M  0 part
|-mmcblk0p7  179:7    0    96M  0 part /var/lib/systemd
|                                      /var/lib/bluetooth
|                                      /var/lib/NetworkManager
|                                      /etc/systemd/timesyncd.conf
|                                      /etc/hosts
|                                      /etc/hostname
|                                      /etc/NetworkManager/system-connections
|                                      /root/.ssh
|                                      /root/.docker
|                                      /etc/usb_modeswitch.d
|                                      /etc/udev/rules.d
|                                      /etc/sysctl.d
|                                      /etc/modules-load.d
|                                      /etc/modprobe.d
|                                      /etc/dropbear
|                                      /etc/default
|                                      /mnt/overlay
`-mmcblk0p8  179:8    0  57.6G  0 part
mmcblk0boot0 179:32   0     4M  1 disk
mmcblk0boot1 179:64   0     4M  1 disk
zram0        254:0    0     0B  0 disk
zram1        254:1    0    32M  0 disk
zram2        254:2    0    16M  0 disk /tmp
nvme0n1      259:0    0 465.8G  0 disk
`-nvme0n1p1  259:1    0 465.8G  0 part /var/log/journal
                                       /var/lib/docker
                                       /mnt/data

Ideally mmcblk0 would be empty/blank, and nvme0n1 would contain both the HAOS & data.
Looking for suggestions on how to get there…

[xstrex]

As usual, once I ask for help, I manage to solve my own problem…

I gave it one last ditch effort, and followed this guide, performing the rpiboot steps, and getting into the Raspberry Pi Flasher… To my surprise, after choosing RPi5 / Yellow, I was presented with two options… Install on the mmcblk0 or ‘nvme0n1’!!! I chose the nvme0n1, erased all data, flashed the OS, rebooted…

After getting back into the serial console, I was greeted with the following lsblk!

# lsblk
NAME         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
mmcblk0      179:0    0  58.2G  0 disk
|-mmcblk0p1  179:1    0    32M  0 part
|-mmcblk0p2  179:2    0    24M  0 part
|-mmcblk0p3  179:3    0   256M  0 part
|-mmcblk0p4  179:4    0    24M  0 part
|-mmcblk0p5  179:5    0   256M  0 part
|-mmcblk0p6  179:6    0     8M  0 part
|-mmcblk0p7  179:7    0    96M  0 part
`-mmcblk0p8  179:8    0  57.6G  0 part
mmcblk0boot0 179:32   0     4M  1 disk
mmcblk0boot1 179:64   0     4M  1 disk
zram0        254:0    0     0B  0 disk
zram1        254:1    0    32M  0 disk
zram2        254:2    0    16M  0 disk /tmp
nvme0n1      259:0    0 465.8G  0 disk
|-nvme0n1p1  259:1    0    32M  0 part /mnt/boot
|-nvme0n1p3  259:3    0   256M  0 part /
|-nvme0n1p7  259:7    0    96M  0 part /var/lib/systemd
|                                      /var/lib/bluetooth
|                                      /var/lib/NetworkManager
|                                      /etc/systemd/timesyncd.conf
|                                      /etc/hosts
|                                      /etc/hostname
|                                      /etc/NetworkManager/system-connections
|                                      /root/.ssh
|                                      /root/.docker
|                                      /etc/usb_modeswitch.d
|                                      /etc/udev/rules.d
|                                      /etc/sysctl.d
|                                      /etc/modules-load.d
|                                      /etc/modprobe.d
|                                      /etc/dropbear
|                                      /etc/default
|                                      /mnt/overlay
|-nvme0n1p2  259:9    0    24M  0 part
|-nvme0n1p4  259:10   0    24M  0 part
|-nvme0n1p5  259:11   0   256M  0 part
|-nvme0n1p6  259:12   0     8M  0 part
`-nvme0n1p8  259:13   0 465.1G  0 part /var/log/journal
                                       /var/lib/docker
                                       /mnt/data

So it worked!

Now I’ll just clean up the old partitions on the eMMC and call it done… Thanks for this thread, it lead me down the path to figure out this was possible!

[ogiewon]

@xstrex

So it worked!

Awesome to hear! Nice work!

[VeloSteve (Steve)]

Recommended CM5 version?

I have ordered the Yellow system with no compute module and a 1 TB NVMe drive. I will be starting with just a few devices, but I want powerful hardware in case I end up using some combination of many devices, local voice processing, or AI. I can afford to get the most expensive CM5, but that is partly because I don’t like to throw money away .

Do I want WiFi? The device will be wired to my network, which of course has wireless.
Is “Storage” (eMMC) useful even if I am using the 1 TB NVMe drive?
Is there an amount of RAM beyond which there is little benefit, or should I just get 16 GB?

Background: I have looked around yellow.home-assistant.io and other places, but so far no answer has appeared. I’m reasonably fluent with computing in general, but I’m totally new to Home Assistant and haven’t used a Raspberry Pi in years.

Thanks!

[francisp (Francis)]

You can’t add memory to a Raspberry Pi, so I would buy the version with most ram. You might not need it now, but it is most future proof.

[Juggler (SR)]

Just got my yellow and CM5 (WiFi, lite). I also purchased the “official” raspberryPi heatsink. Reading through this thread, I do not see any consensus on whether it is better to use the heatsink that came with the yellow, the official raspberryPi one, or it doesn’t matter.

Can anyone comment on this?

[francisp (Francis)]

Do NOT use the HA yellow kit screws on a CM5 module

The heads on the four screws that come with the HA Yellow kit are too large and one of them will break off a small component next to the screw. [broke HA yellow] When I plugged in PoE I just got one flash of all the LEDs. While taking it apart to check for fitment I noticed the component circled in the picture. I soldered the part back on and now when I plug in I get a red light for about 1 second, then a solid green light, but no yellow light. It seems online this is a pretty common proble…

[Juggler (SR)]

Thanks for this… I used the raspberryPi custom CM5 heatsink. No spacers necessary, simply put the included (from RPi) in.