HA Yellow (PoE) restarts after shutdown is initiated upon upgrading to CM5 Lite

[Lemon-Doctor10]

Describe the issue you are experiencing

After swapping out my CM4 Lite for a new CM5 Lite, my HA Yellow reboots whenever a graceful shutdown is triggered. The boot process itself seems to finish properly and the system runs normally otherwise with no hiccups, so I am hesitant to say this is a hardware-related issue with respect to the CM5. To cover all bases, however, I tried wiping my NVMe and reinstalling the OS, but to no avail - the issue persists.

Prior to the upgrade, I would simply see a solid red light indicating power could be safely removed once the shutdown process completed. I assume this is the expected behavior, as I believe this is considered the norm for the CM4 Lite?

As the Yellow prepares to shutdown, I notice the following sequence:

1. Approximately 1 minute into shutdown, the red indicator light flashes once.
2. All indicator lights then shut off.
3. About 2-3 seconds later, all indicator lights return.
4. A solid green indicator appears, followed by the boot sequence.

Based on the indicator lights alone, I would assume this was a problem related to the system's power (PoE-related)? Although, considering it only occurs specifically on shutdown, perhaps this warrants further investigation.

I should also note that the PoE+ port I am using on my switch to power the Yellow is functioning normally.

What operating system image do you use?

yellow (Home Assistant Yellow)

What version of Home Assistant Operating System is installed?

16.2 (also attempted on 16.3 beta with same results)

Did the problem occur after upgrading the Operating System?

No

Hardware details

PoE variant of Home Assistant Yellow with CM4/CM5 Lite and Z-Wave GPIO attachment

Steps to reproduce the issue

1. Go to Developer Options tab in sidebar.
2. Navigate to Restart > Advanced options > Shut down system (alternatively, trigger hassio.host_shutdown command in an automation).
3. System shuts down and restarts within a few minutes without intervention.

Anything in the Supervisor logs that might be useful for us?

Nothing useful in supervisor logs (perhaps due to the system restarting).  Reading logs with journalctl also appears to show nothing of note.

Anything in the Host logs that might be useful for us?

Nothing useful in host logs (perhaps due to the system restarting).  Reading logs with journalctl also appears to show nothing of note.

System information

No response

Additional information

No response

[sairon]

I have only tested with CM5 (non-lite version; though there should not be any difference in this regard) but I am not able to reproduce it - I shut down the Yellow about two hours back and it's still staying off with the red LED steadily lit. Can you check what bootloader version you're running (with rpi-eeprom-update) and eventually update it with rpi-eeprom-update -a and power-cycle the device afterwards? You'll need to access the HAOS shell directly, easiest on Yellow would be using the USB-serial console.

[Lemon-Doctor10]

So, I managed to login to the shell and check the version with rpi-eeprom-update. I was indeed running an older version and updated with the -a option. After a power cycle, however, the same issue occurred. For reference, the version displayed originally was as follows:

CURRENT: Mon Mar 10 17:10:37 UTC 2025 (1741626637)
LATEST: Thu May 8 14:37:17 UTC 2025 (1746713597)

Post-update, the latest version appeared under "CURRENT" as well, indicating I updated successfully. As a side note, I also cannot seem to access the config info aside from viewing its boot order as I am running the lite version of CM5. This one's definitely a head-scratcher. Anything else I can try on my end?

[Lemon-Doctor10]

Upon further research, the most plausible explanation I found is that some PoE implementations can cause the power line to reset upon shutdown, thus rebooting the system moments later. One instance of this was found in a specific PoE hat for the RPi 5. I wonder if this behavior carries over to some CM5s, too.

Apparently, there are some settings in the EEPROM that can change this (POWER_OFF_ON_HALT, or WAKE_ON_GPIO maybe?), but the default settings might be allowing the Yellow to briefly lose power regardless. Unfortunately, I cannot seem to modify these settings in HA OS to test that theory. I assume this is either because I am using the lite version of CM5, or the command "rpi-eeprom-config --edit" does not exist. Maybe you are able to test some of these settings with your CM5, sairon?

Take this info with a grain of salt since I have no way of confirming any of it myself, but it is the only lead I could find that would explain the behavior I am seeing. I also re-seated the CM5 to ensure it was indeed installed properly. Still experienced the same "power cut" issue after doing so.

Can a workaround be implemented for this in the OS, assuming the prior info holds true, or is this purely hardware/firmware in nature and I should exchange my CM5 for a non-lite version or different solution?