emonPi shutting down ~1hr after boot after updating to latest version

emonSD
1

I recently updated my emonPi v1 (and applied this fix: FIXED: Failed to fetch https://packages.sury.org, signatures were invalid ) to 11.16.8. It works fine for about an hour after boot but then dies, could be shutting itself down?

It was very stable before the update. I can’t see anything obvious in the logs. Any idea of where to look? Sometimes the screen shows the wait 30s message. The button has always been a bit unresponsive/dodgy.

I could rebuild off the latest image (no guarantee it will fix it) or use an old version (but I’d like the security updates). Any other ideas?

emonpiRelease: emonSD-01Feb24

Model: Raspberry Pi 4 Model B Rev 1.5 - 2GB (Sony UK)

2

Hello James, could it be that the button is triggering the shutdown?

You could try:

sudo systemctl stop emonPiLCD
sudo systemctl disable emonPiLCD

and see if that makes any difference..

3

Thanks, I’ll give this a go.

I think there is something up with the LCD/button. It cycles through the screens very quickly on its own sometimes and the button is unresponsive mostly. Not sure why the update would trigger this though.

4

I’ve disabled the service and it shows as emonPiLCD: Inactive Dead in the admin web interface and via sudo systemctl status emonPiLCD. The LCD shows the Pi is booting... message (as expected) after a restart.

The rest is all working and data is being logged. Hopefully this fixes it, will let you know if not. I can live without the LCD. :slight_smile:

5

@TrystanLea I had the same problem for a while - until the button failed completely. This was one of the very first emonPis - probably pre-production. I’ve retired this emonPi front end & case, now using the RPi with the emonPi3 front end (uncased!).

6

This appears to have resolved the issue and it isn’t shutting down now. Thanks.

FYI this can be disabled via the web interface if SSH is not already enabled (tricky if the button is dodgy).

I’m not sure if it’s literally the button (easy replacement) or an issue with the LCD.

7

In my case, very definitely the button.

8

Unfortunately, while this has fixed the shutdown issue, after a few days data stops being logged. The pi stays up and responsive but readings stop being recorded and the graphs abruptly end until a reboot, leading to gaps. I could schedule a regular reboot but it’s not ideal. I think something more fundamental than a button may be wrong with it. Or maybe it is the button and I should try disconnecting it.