[Solved / Archived] WittyPi 3 mini on Pi Zero 2W and WittyPi 4 on Pi 4

Hi,

My wittypi's have been working fine for ages. I recently upgraded to bookworm and it everything was still working. I've just done updates (including a kernel upgrade) on both devices now neither of my wittypi's appear to be working to their schedules and aren't shutting down.

This is the log from one of the pis

[2023-12-08 05:30:31] Pending for incoming shutdown command...
[2023-12-08 05:30:31] Schedule next shutdown at: 2023-12-08 17:30:00
[2023-12-08 05:30:32] Schedule next startup at: 2023-12-11 05:30:00
[xxxx-xx-xx xx:xx:xx] Witty Pi daemon (v4.13) is started.
[xxxx-xx-xx xx:xx:xx] Running on Raspberry Pi 4 Model B Rev 1.4
[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...
[2023-12-08 08:26:25] Done :-)
[2023-12-08 08:26:25] Firmware ID: 0x26
[2023-12-08 08:26:25] Firmware Revison: 0x01
[2023-12-08 08:26:25] Current Vout=5.02V, Iout=1.56A
[2023-12-08 08:26:25] System starts up because scheduled startup is due.
[xxxx-xx-xx xx:xx:xx] Witty Pi daemon (v4.13) is started.
[xxxx-xx-xx xx:xx:xx] Running on Raspberry Pi 4 Model B Rev 1.4
[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...
[2023-12-08 12:13:15] Done :-)
[2023-12-08 12:13:15] Firmware ID: 0x26
[2023-12-08 12:13:15] Firmware Revison: 0x01
[2023-12-08 12:13:15] Current Vout=5.02V, Iout=1.72A
[2023-12-08 12:13:15] System starts up because scheduled startup is due.
[xxxx-xx-xx xx:xx:xx] Witty Pi daemon (v4.13) is started.
[xxxx-xx-xx xx:xx:xx] Running on Raspberry Pi 4 Model B Rev 1.4
[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...
[2023-12-11 05:30:26] Done :-)
[2023-12-11 05:30:26] Firmware ID: 0x26
[2023-12-11 05:30:26] Firmware Revison: 0x01
[2023-12-11 05:30:26] Current Vout=5.03V, Iout=1.63A
[2023-12-11 05:30:26] System starts up because scheduled startup is due.
[2023-12-11 09:20:56] Copying "studypi.wpi" to "schedule.wpi"...
[2023-12-11 09:20:56] Running the script...
[2023-12-11 09:20:56] Schedule next shutdown at: 2023-12-11 17:30:00
[2023-12-11 09:20:56] Schedule next startup at: 2023-12-12 05:30:00
[2023-12-11 09:20:57] Done :-)
[xxxx-xx-xx xx:xx:xx] Witty Pi daemon (v4.13) is started.
[xxxx-xx-xx xx:xx:xx] Running on Raspberry Pi 4 Model B Rev 1.4
[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...
[2023-12-11 09:29:16] Done :-)
[2023-12-11 09:29:16] Firmware ID: 0x26
[2023-12-11 09:29:16] Firmware Revison: 0x01
[2023-12-11 09:29:16] Current Vout=5.01V, Iout=1.61A
[2023-12-11 09:29:16] System starts up because scheduled startup is due.
[xxxx-xx-xx xx:xx:xx] Witty Pi daemon (v4.13) is started.
[xxxx-xx-xx xx:xx:xx] Running on Raspberry Pi 4 Model B Rev 1.4
[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...
[2023-12-11 13:18:34] Done :-)
[2023-12-11 13:18:34] Firmware ID: 0x26
[2023-12-11 13:18:34] Firmware Revison: 0x01
[2023-12-11 13:18:34] Current Vout=5.02V, Iout=1.72A
[2023-12-11 13:18:34] System starts up because scheduled startup is due.

Interestingly if I look at the wittypi menu, I get the following:

>>> Current temperature: 44.625°C / 112.325°F
>>> Your system time is: 2023-12-11 22:18:49 GMT
>>> Your RTC time is:    2023-12-11 22:18:51 GMT
>>> Vout=5.10V, Iout=1.22A
Now you can:
  1. Write system time to RTC
  2. Write RTC time to system
  3. Synchronize with network time
  4. Schedule next shutdown [11 17:30:00]
  5. Schedule next startup  [12 05:30:00]
  6. Choose schedule script [in use]
  7. Set low voltage threshold
  8. Set recovery voltage threshold
  9. Set over temperature action
 10. Set below temperature action
 11. View/change other settings...
 12. Reset data...
 13. Exit
What do you want to do? (1~13)

As you can see the shutdown time is well past and the device hasn't shutdown. 

I am guessing this is a problem with a recent raspberry pi bookworm OS update as it's happening on both devices across two different types of pi.

Any advice?

Thanks