I reinstalled the CM4 module. I was wondering if maybe it hadn’t been seated properly, but it was.
I have tried both options for reinstalling the os, when I hold on the blue and red buttons, it never starts with only the red light on.
Running rpiboot never goes anywhere (the 2 jumpers are set as specified in the instructions). The HA Yellow is connected directly to the computer with a USB cable, not through a hub.
I now have a very expensive paperweight that I had to wait a year and a half for. 
I was able to get my new HA Yellow PoE up and running just now. I am using the same CM410832 module as you. However, because I did not want to use the onboard eMMC, I had to follow this guide in order to change the default boot order. I wanted my 1TB WD SN750 NVME drive to be both my boot and storage drive. I used another Raspberry PI as the USB boot host for the Yellow, as Windows is not supported when building the new code required to change the boot order.
It should be noted that two jumpers on the Yellow board need to be moved (JP1 to ‘USB’ & JP2 must be bridged) in order for the Yellow to boot off of the USB-C port. Also, one must supply external 12v power to the Yellow in order for it to be seen by the computer one is running ‘rpiboot’ from. For me, my goal in doing this was to update the firmware on the CM4 to make it boot from NVME first.
In order to get the HAOS 9.4 for the Yellow installed on the NVME drive, I simply downloaded haos_yellow-9.4.img.xz from Releases · home-assistant/operating-system · GitHub. I then used the Raspberry Pi Imager (on my Win11 PC) to flash the image I just downloaded to the NVME drive that I had temporarily installed in a USB to NVME enclosure. Once the drive was imaged, I removed it from the USB enclosure and installed it in the HA Yellow PoE board.
Finally, with JP1 and JP2 back in their original positions, I simply plugged in a PoE Ethernet cable. After about 5-10 minutes, I was able to connect to the Yellow board via my web browser.
I know my process is a little non-standard… However, it seemed like the easiest method to me. I have had some prior experience with using CM4 modules in other boards, so this was a little familiar to me.
I hope this helps! Good luck in getting your Yellow PoE up and running!
Thanks for the update.
I tried on 2 different computers, a windows computer and a Mac, and both had the same result running the rpiboot - it never progressed from waiting for the computer. I tried with both the HA Yellow and another CM4 I have mounted to a Piunora board I recently got but hadn’t had a chance to set up yet, so I have no real experience with either. Neither of them worked on either computer.
I’ll see if I can try running it on one of my RPi Zeros when I get a chance.
I may order an SSD to try this out. Does that completely bypass the eMMC? That might be a good solution, as it would also allow me to replace the CM4 board at any time in the future if there are any issues.
I was looking forward to migrating everything over this weekend, looks like it’s going to be a few more weeks at least now. 
Thanks again.
Yes, it does bypass the eMMC as long as the boot order in the CM4 is configured to boot NVME first. I am not sure what would happen if the boot order still looked first to the eMMC, even it it were empty.
Are you 100% sure your CM4 has eMMC on it? The part number you mentioned above does indicate that it has 32GB of eMMC… Just a thought that would explain the behavior you’re seeing… 
Make sure you buy a NVME M.2 SSD. Some users in the other Yellow threads have had issues with some SSD’s - especially those who have tried a M.2 SATA SSD. 
Yes, without taking it apart again, I can see both the eMMC and WiFi modules from the side, as depicted here:
I was also looking at a WD, different model. It is a NVME M.2.
@MarkWalsh I just went through the same process and issues. I wasn’t really paying attention and the install via rpiboot process passed before my eyes. Then when I ran again it just sat looking. I reinstalled rpiboot, rebooted the machine, and reattached the HA. Then rpiboot ran properly and installed ok. I was able to then use the eMMC as the location to install the OS and run everything ok (I think). Now I have to work through my internal network to see the HA and configure. I am not sure my input helped a lot, but I guess it seems like I had a similar issue.
I haven’t had any luck yet. I’ve tried using the reset button, I’ve tried switching the headers to mount via usb, but the rpiboot never recognizes it.
I bought an SSD and have that mounted, but still no luck.
I’ll try again when I have time to devote to it. I’ve also ordered an NVME adapter so I can try installing the system directly on the drive. I also may order a RPi compute development board to see if I can use that to install the system. I have another computer module 4 that I’d like to use for another purpose.
Otherwise, maybe I can see if there’s someone in the Philadelphia area that is more familiar with this that could help me get the system installed.
Last resort, I order another without PoE and wait another 2 months.
I finally had time to get back to this. No luck with anything.
I used a USB Nvme adaptor, successfully installed the Home Assistant OS onto the drive (I didn’t download the file as suggested, just used the RPi imager to install the HA OD (not the Yellow installer) onto the drive. I’m not getting anything. My router briefly showed an extra device in the count (35), but very quickly dropped down to 34 devices and never came back.
I want to verify what is the correct setting for the jumpers to boot off of the ssd. I tried with the jumpers in both positions, in one I only got the red light on solid, the other I got both the red and green lights on solid. The green light never blinked once.
Getting extremely frustrated with this.
EDIT: I think I figured out why I couldn’t get it to mount to my PC as a USB device. I’ve been using the wrong USB ports. I need to use the USB-C port (I had a usb-c cable but can’t find it right now) I missed that part.
I’ll order a new cable and try yet again next weekend if I have time.
I finally got the thing to reset during startup. I’m trying another install of the eMMC OS using the Yellow installer on USB stick.
Edit: SUCCESS! I finally got to the “Preparing Home Assistant screen!
That is good news. I wish I could have been more help, but your sticktooitiveness is on point.
Dear friend. I am having the same issue only red and green lights are on on my POE version. How did you solve the problem?
Sorry for the delay, i haven’t been on the forum for a while.
I went through the reinstall process.
https://yellow.home-assistant.io/guides/reinstall-os/
I don’t remember what happened that finally got it working, or why it wasn’t working the first few times, I just kept trying. I was never able to get it connected to the rpiboot, I don’t know if I had the wrong cable (it said it was a data cable when I bought it), I used option 1 and eventually was able to reinstall.
I believe I also swapped out the Ethernet cable I was using (I wasn’t using PoE) just in case, but I don’t think that was what solved the issue.
I hope you’ve gotten it working.
Just got the full kit with the CM4 included, Status LED is blinking twice (patern) imagine that is the heartbeat for more then an hour, so i tried the Re-install recommanded way, didnt do much more, and now tried the other way still nothing.
any ideas…
If you got the full kit, you shouldn’t have needed to do anything, it was preinstalled.
Hey Mark thanks for the link,
I had also same problem and been trying for several days to install home Assisstant Yellow as well.
I got always flickering yellow led even after 20 minutes and kept flickering. After unplugged everything out of my home assisstant yellow. I plugging the power wire back in and holding blue and red button like that for 5 seconds.As described on the website: Home Assistant Yellow Guide
And applied the process back from beginning:
. I put the usb flash back into the drive with Raspberry Pi software
. Internet cable and power cable back into home assisstant Yellow
. After installation, finally only the red led remained on; installation completed
Hope by now everything is working for you!
My issue is that i had to plug it directly in my switch, even if its not the Poe edition it burned 2 of my keystone ethernet ports…
Once i plugged it in the switch everything worked directly.
Hi folks, I’m new to HA. Received my PoE kit with NVMe, and experienced similar issues described here. For many attempts I never once saw the yellow light. Usually just solid red and green. And some times I would get the 4-5 pattern, which translates to ‘fatal firmware error.’ Factory resets seemed to do nothing.
This statement from Mark basically sums up my experience:
I don’t remember what happened that finally got it working, or why it wasn’t working the first few times, I just kept trying.
I was planning to try and reflash the EEPROM, but it is stretching my knowhow.
What I did do was to remove the NVMe (which had been purchased from Seeed wtih the kit). When I did that, I saw the yellow light for the first time (hurray!). But then it was back to just solid red and green. Then I took of the heat sink and reseated the CM4. And after that, still solid red and green. Along the journey I had tried several different Ethernet cables, and a couple of PoE power supplies.
By this point my spirit was officially broken, and I was about to give up… and then it just worked 
Sorry this isn’t definitive advice on how to solve this issue, but hopefully my experience helps someone navigate any issues they experience. Maybe you just need to be willing to get to the absolute end of your tether before computer says yes! 
As DNS-Sec is used by home-assistant.io domain. Its important that the time on the Yellow is correct, otherwise the install will not work, and you will see the following like errors if you access the yellow’s console:
# ping version.home-assistant.io
ping: bad address 'version.home-assistant.io'
# curl --no-progress-meter -L https://version.home-assistant.io/stable.json
curl: (6) Could not resolve host: version.home-assistant.io
# systemd-resolve version.home-assistant.io
version.home-assistant.io: resolve call failed: DNSSEC validation failed: signature-expired
The above message is misleading, as the signature start time is in the future.
How to confirm its a time error:
# TZ=Australia/Melbourne date
Tue Dec 20 20:09:05 AEDT 2022
I suspect this is the date it was tested, it took 18 months for my CM4 to arrive.
# networkctl stats
State: routable
Online state: online
Address: 192.168.0.10 on end0
2001:4479:6903:7a00:da2a:ddff:fecd:18ab on end0
fe80::da3a:ddff:fecd:18ab on end0
Gateway: 192.168.0.254 on end0
fe80::c225:6ff:fedc:adfc on end0
DNS: 192.168.0.254
8.4.4.4
NTP: 192.168.0.250
# timedatectl show-timesync --all
LinkNTPServers=192.168.0.250
SystemNTPServers=
RuntimeNTPServers=
FallbackNTPServers=time.cloudflare.com
ServerName=192.168.0.10
ServerAddress=192.168.0.10
RootDistanceMaxUSec=5s
PollIntervalMinUSec=32s
PollIntervalMaxUSec=34min 8s
PollIntervalUSec=34min 8s
Frequency=0
The NTP (Time Server information comes from your DHCP server), check IP address indicated is infact running a time service, link ntpd, or chrony or its the same IP address as your modem/router as most run a time service.
Fix your DHCP server so it responds with a valid time server IP address. And then reboot or run the following:
# networkctl forcerenew end0
# systemctl restart systemd-networkd.service
# TZ=Australia/Melbourne date
It would be nice if the yellow installer had a python web server which ran the install, instead of
/usr/bin/haos-flash which is called by systemd service install-autostart
The issue can also happen if you are using https and the date on the system is earlier than the start date of the SSL/TSL certificate.
The cost me a fair about of time to determine the cause was the NTP setting sent by the DHCP server was invalid. I hope posting here saves others some time. You can access the console by plugging a cable into the USB-C, see use-serial-console-windows or use-serial-console-linux-macos for more details.