Witty Pi4 - Scheduler not executed from time to time - no shutdown

You need to look into the wittyPi.log file. The log you provided is from the schedule.log file, which only tells what happened/not happened, but does not give any hint about why.

The content of the logfile is posted below. It contains the log from the last succesful run and the last, where the pi won't shut down due to the not updated alarms.

For me it gives no real hint why the Scheduler is not run. 

[xxxx-xx-xx xx:xx:xx] Witty Pi daemon (v4.21) is started.

[xxxx-xx-xx xx:xx:xx] System: Raspbian GNU/Linux 11 (bullseye), Kernel: Linux 6.1.21+, Architecture: armhf

[xxxx-xx-xx xx:xx:xx] Running on Raspberry Pi Zero W Rev 1.1

[xxxx-xx-xx xx:xx:xx] Witty Pi is not detected, retry in one second...

[xxxx-xx-xx xx:xx:xx] RTC offset register has value 0x79

[xxxx-xx-xx xx:xx:xx] Seems RTC has good time, write RTC time into system

[xxxx-xx-xx xx:xx:xx] Writing RTC time to system...

[2025-08-28 10:45:46] Done 🙂

[2025-08-28 10:45:46] Firmware ID: 0x26

[2025-08-28 10:45:46] Firmware Revison: 0x06

[2025-08-28 10:45:46] Current Vout=4.1V, Iout=0.17A

[2025-08-28 10:45:46] System starts up because scheduled startup is due.

[2025-08-28 10:45:52] Send out the SYS_UP signal via GPIO-17 pin.

[2025-08-28 10:45:53] Pending for incoming shutdown command...

[2025-08-28 10:46:12] Schedule next shutdown at: 2025-08-28 10:48:00

[2025-08-28 10:46:13] Schedule next startup at: 2025-08-28 11:00:00

[2025-08-28 10:45:59] TIME-LAPSE LOW-COST SYSTEM

[2025-08-28 10:46:01] USB Drive mounted

now: 10:46:02 +04

Sunrise: 05:52:46 +04

Sunset: 18:33:49 +04

capturing image/videos

[2025-08-28 10:46:03] Camera V2 detected. Resolution: 3280x2464

[2025-08-28 10:46:05] Image: 20250828_1046_1 successfully captured

[2025-08-28 10:46:15] Video: 20250828_1046_ successfully captured

[2025-08-28 10:46:16] WittyPi log files copied to USB

[2025-08-28 10:47:55] Shutting down system because scheduled shutdown is due.

[2025-08-28 10:47:56] Halting all processes and then shutdown Raspberry Pi...

[xxxx-xx-xx xx:xx:xx] Witty Pi daemon (v4.21) is started.

[xxxx-xx-xx xx:xx:xx] System: Raspbian GNU/Linux 11 (bullseye), Kernel: Linux 6.1.21+, Architecture: armhf

[xxxx-xx-xx xx:xx:xx] Running on Raspberry Pi Zero W Rev 1.1

[xxxx-xx-xx xx:xx:xx] Witty Pi is not detected, retry in one second...

[xxxx-xx-xx xx:xx:xx] RTC offset register has value 0x79

[xxxx-xx-xx xx:xx:xx] Seems RTC has good time, write RTC time into system

[xxxx-xx-xx xx:xx:xx] Writing RTC time to system...

[2025-08-28 11:00:46] Done 🙂

[2025-08-28 11:00:46] Firmware ID: 0x26

[2025-08-28 11:00:46] Firmware Revison: 0x06

[2025-08-28 11:00:46] Current Vout=4.36V, Iout=0.17A

[2025-08-28 11:00:46] System starts up because scheduled startup is due.

[2025-08-28 11:00:52] Send out the SYS_UP signal via GPIO-17 pin.

[2025-08-28 11:00:53] Pending for incoming shutdown command...

[2025-08-28 11:01:00] TIME-LAPSE LOW-COST SYSTEM

[2025-08-28 11:01:01] USB Drive mounted

now: 11:01:02 +04

Sunrise: 05:52:46 +04

Sunset: 18:33:49 +04

capturing image/videos

[2025-08-28 11:01:03] Camera V2 detected. Resolution: 3280x2464

[2025-08-28 11:01:05] Image: 20250828_1101_1 successfully captured

[2025-08-28 11:01:16] Video: 20250828_1101_ successfully captured

[2025-08-28 11:01:16] WittyPi log files copied to USB

The runScript.sh should be run after the "Pending for incoming shutdown command..." line got printed in the log, which will schedule the next shutdown and startup.

However this didn't happen after this line:

[2025-08-28 11:00:53] Pending for incoming shutdown command...

Indeed there was no more information about why. However you may modify the runScript.sh and let it output more verbose log. For now we can not confirm if this script was executed.