Hello,
Is there a fix in the works for the firmware / software to fix the handover between standard time and saving time, e.g. USA Eastern Time Zone?
My WP4 turned off and stopped at 2:00 AM at the time of the switch back to standard time. I had to push the button to turn on the RPi and then run sync time two or three times to get the times synched. I also had to reselect the Schedule Script to get it to reflect local time not DST. Log attached.
Bruce
[xxxx-xx-xx xx:xx:xx] Witty Pi daemon (v4.23) is started. [xxxx-xx-xx xx:xx:xx] System: Debian GNU/Linux 13 (trixie), Kernel: Linux 6.18.59-v8+, Architecture: arm64 [xxxx-xx-xx xx:xx:xx] Running on Raspberry Pi Zero 2 W Rev 1.0 [xxxx-xx-xx xx:xx:xx] RTC offset register has value 0x77 [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... [2026-11-01 01:40:29] Done :-) [2026-11-01 01:40:29] Firmware ID: 0x36 [2026-11-01 01:40:29] Firmware Revison: 0x07 [2026-11-01 01:40:29] Current Vout=5.08V, Iout=0.25A [2026-11-01 01:40:29] System starts up because scheduled startup is due. [2026-11-01 01:40:34] Send out the SYS_UP signal via GPIO-17 pin. [2026-11-01 01:40:34] Pending for incoming shutdown command... [2026-11-01 01:40:34] Schedule next shutdown at: 2026-11-01 01:55:00 [2026-11-01 01:40:35] Schedule next startup at: 2026-11-01 01:00:00 [2026-11-01 01:55:01] Shutting down system because scheduled shutdown is due. [2026-11-01 01:55:01] Halting all processes and then shutdown Raspberry Pi... [xxxx-xx-xx xx:xx:xx] Witty Pi daemon (v4.23) is started. [xxxx-xx-xx xx:xx:xx] System: Debian GNU/Linux 13 (trixie), Kernel: Linux 6.18.59-v8+, Architecture: arm64 [xxxx-xx-xx xx:xx:xx] Running on Raspberry Pi Zero 2 W Rev 1.0 [xxxx-xx-xx xx:xx:xx] RTC offset register has value 0x77 [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... [2026-11-01 11:46:22] Done :-) [2026-11-01 11:46:22] Firmware ID: 0x36 [2026-11-01 11:46:22] Firmware Revison: 0x07 [2026-11-01 11:46:22] Current Vout=5.08V, Iout=0.34A [2026-11-01 11:46:22] System starts up because the button is clicked. [2026-11-01 11:46:27] Send out the SYS_UP signal via GPIO-17 pin. [2026-11-01 11:46:27] Pending for incoming shutdown command... [2026-11-01 11:46:27] Schedule next shutdown at: 2026-11-01 11:55:00 [2026-11-01 11:46:28] Schedule next startup at: 2026-11-01 12:00:00 [2026-11-01 10:50:31] Internet detected, apply network time to system and Witty Pi... [2026-11-01 10:50:31] Applying network time to system... [2026-11-01 10:50:31] Done :-) [2026-11-01 10:50:31] Writing system time to RTC... <2026-11-01 10:50:31> Done :-) <2026-11-01 10:51:18> Copying "on_15m_every_20m.wpi" to "schedule.wpi"... <2026-11-01 10:51:18> Running the script... <2026-11-01 10:51:19> Schedule next shutdown at: 2026-11-01 10:55:00 <2026-11-01 10:51:19> Schedule next startup at: 2026-11-01 11:00:00 <2026-11-01 10:51:19> Done :-) [2026-11-01 10:54:59] Shutting down system because scheduled shutdown is due. [2026-11-01 10:54:59] Halting all processes and then shutdown Raspberry Pi... [xxxx-xx-xx xx:xx:xx] Witty Pi daemon (v4.23) is started. [xxxx-xx-xx xx:xx:xx] System: Debian GNU/Linux 13 (trixie), Kernel: Linux 6.18.59-v8+, Architecture: arm64 [xxxx-xx-xx xx:xx:xx] Running on Raspberry Pi Zero 2 W Rev 1.0 [xxxx-xx-xx xx:xx:xx] RTC offset register has value 0x77 [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... [2026-11-01 11:00:29] Done :-) [2026-11-01 11:00:29] Firmware ID: 0x36 [2026-11-01 11:00:29] Firmware Revison: 0x07 [2026-11-01 11:00:29] Current Vout=5.09V, Iout=0.27A [2026-11-01 11:00:29] System starts up because scheduled startup is due. [2026-11-01 11:00:34] Send out the SYS_UP signal via GPIO-17 pin. [2026-11-01 11:00:34] Pending for incoming shutdown command... [2026-11-01 11:00:34] Schedule next shutdown at: 2026-11-01 11:15:00 [2026-11-01 11:00:35] Schedule next startup at: 2026-11-01 11:20:00 pi@RPi-Zero-W-72:~/wittypi $
The behavior shown in your log is consistent with the known DST limitation of Witty Pi 4.
At 01:40, the software scheduled the next shutdown for 01:55 and the next startup for 01:00. The latter was intended to occur after the EDT-to-EST transition. However, Witty Pi 4 does not automatically adjust its RTC for DST, so the scheduled startup was missed.
We have explained this limitation in an earlier forum topic:
https://www.uugear.com/forums/technial-support-discussion/witty-pi-4-about-daylight-saving-time-dst/
Implementing reliable DST handling across different regions, especially when the Raspberry Pi may be powered off during the transition, would require substantial changes and testing.
We do not have a plan to implement automatic DST handling for Witty Pi 4.