Missing power-down feature under all circumstances

[jonnyns]

I am operating a set of LiFePO4WEREDPi+ devices in remote locations. For maximum uptime I use AUTO_BOOT=1 (AUTO_BOOT_VBAT).
The reason I do not use AUTO_BOOT=2 (AUTO_BOOT_VBAT_SMART) is that "sudo reboot now" will NOT reboot the device, it just halts the device, which is not ideal in the remote case.
Using AUTO_BOOT=1 for the unit will safely allow rebooting the unit while remote.
When visiting remote locations I usually change to AUTO_BOOT=0 before powering down a device for service. However, what I miss is a VERY LONG button PRESS (say 30 sec) on the LiFePO4WEREDPi+ unit which will bring the unit back to AUTO_BOOT=0 and safely power it down. Think of it as an "emergency shutdown".
Maybe it is just me missing this feature, but I thought I would mention it anyway.

[xorbit]

Hi Jonny,

I did a bit of investigating and I believe I know why this is happening. The problem is that the modern Raspberry Pi's keep spending more and more time in the bootloader, versus older Pi's (and it seems to be getting worse with updates). When the Raspberry Pi is shutting down, the LiFePO4wered/Pi+ monitors the TX line to see when it goes low, to detect when the Pi is done shutting down. It then waits a while before removing power, because it might have been a reboot and it is waiting to see if the TX and then the run flag is coming back.

The preprogrammed delay SHDN_DELAY is currently set to 64 (about 8 s) from the factory, but that doesn't seem to be enough any more, at least for the Pi5 which I just tested. It looks like currently, on my test device, SHDN_DELAY needs to be set to 80 (10 s) to correctly go through a reboot. I would recommend you set your delay to 12 s or so to give it some margin with:

$ lifepo4wered-cli set shdn_delay 96

Then see if that helps the situation to make AUTO_BOOT=2 reboot correctly.

I should increase the factory value to accommodate the ever bloating bootloader delay, thank you for reporting this!