Hei guys
I recently bought two of your Witty Pi 4 L3V7 boards (and planning to get 18 more) but im having troubles to wakeup as after shutdown the RPi stay down but with power (power LED stay red) so the Witty board cannot turn it on again. This happens only when using the schedule tool (with ./wittyPi.sh) , meanwhile if i turn it off manually (button) or command (sudo shutdown -h now), LED goes off and next time the hat can turn on the Rpi. The only additional changes that I have done so far is to set "auto-on when usb 5V is connected" to off (as i always have 5V comming from a powersupply as im simulating field conditions) and "set low voltage threshold" to 3.5V due the same reason.
How can this situation be debug? Thanks!
RPi stay down but with power (power LED stay red)
This explains why Witty Pi can not turn it on again: the prevous shutdown procedure didn't complete, and the Pi is still powered. Witty Pi needs to cut Pi's power before turning it on again (by powering the Pi).
However, shutting down via schedule has no difference than doing so manually. When scheduled shutdown is due, the firmware on Witty Pi "click" the button for you, by temporarily pull down GPIO-4.
Does this issue happens randomly? Can you always reproduce it?
@admin Thanks for the fast answer. At the moment im using the schedule once a day with a remote connection so it has been quite annoying to debug. I will try to do a more intense campaign and come back to you AFAP
My RPI should turn on once a day and send a file to my server. After some days I turn on manually the Rpi as I have no files . I also have a look today to the logger
[2025-07-16 13:00:20] Done :-) [2025-07-16 13:00:20] Firmware ID: 0x37 [2025-07-16 13:00:20] Firmware Revison: 0x04 [2025-07-16 13:00:20] Current Vout=5.26V, Iout=0.49A [2025-07-16 13:00:20] System starts up because scheduled startup is due. [2025-07-16 13:00:25] Send out the SYS_UP signal via GPIO-17 pin. [2025-07-16 13:00:25] Schedule next shutdown at: 2025-07-16 13:30:00 [2025-07-16 13:00:25] Pending for incoming shutdown command... [2025-07-16 13:00:25] Schedule next startup at: 2025-07-17 13:00:00 [2025-07-16 13:29:53] Shutting down system because scheduled shutdown is due. [2025-07-16 13:29:53] 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: Debian GNU/Linux 12 (bookworm), Kernel: Linux 6.12.34+rpt-rpi-v8, Architecture: arm64 [xxxx-xx-xx xx:xx:xx] Running on Raspberry Pi 3 Model B Rev 1.2 [xxxx-xx-xx xx:xx:xx] RTC offset register has value 0x76 [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-07-23 15:46:05] Done :-) [2025-07-23 15:46:05] Firmware ID: 0x37 [2025-07-23 15:46:05] Firmware Revison: 0x04 [2025-07-23 15:46:05] Current Vout=5.26V, Iout=0.38A [2025-07-23 15:46:05] System starts up because the button is clicked. [2025-07-23 15:46:10] Send out the SYS_UP signal via GPIO-17 pin. [2025-07-23 15:46:10] Schedule next shutdown at: 2025-07-24 13:30:00
It seems as for a random reason skip the turn on between 2025-07-16 and 2025-07-23. I have change it to every hour to evaluate why this could be happening.
Any recomended reason to debug this?
Thanks!
I just realize that when this happens the D1 led from the witty board it also stay on. Is it possible to have damage the board during transport, high voltage or high current peak? just curious if is maybe a defect board
[2025-08-01 22:00:28] Schedule next startup at: 2025-08-02 06:00:00 [2025-08-01 22:29:59] Shutting down system because scheduled shutdown is due. [2025-08-01 22:29:59] 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: Debian GNU/Linux 12 (bookworm), Kernel: Linux 6.12.34+rpt-rpi-v8, Architecture: arm64 [xxxx-xx-xx xx:xx:xx] Running on Raspberry Pi 3 Model B Rev 1.2 [xxxx-xx-xx xx:xx:xx] RTC offset register has value 0x78 [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-02 06:00:19] Done :-) [2025-08-02 06:00:19] Firmware ID: 0x37 [2025-08-02 06:00:19] Firmware Revison: 0x04 [2025-08-02 06:00:19] Current Vout=5.26V, Iout=0.45A [2025-08-02 06:00:19] System starts up because scheduled startup is due. [2025-08-02 06:00:26] Send out the SYS_UP signal via GPIO-17 pin. [2025-08-02 06:00:27] Schedule next shutdown at: 2025-08-02 06:30:00 [2025-08-02 06:00:27] Pending for incoming shutdown command... [2025-08-02 06:00:27] Schedule next startup at: 2025-08-02 14:00:00 [2025-08-02 06:29:58] Shutting down system because scheduled shutdown is due. [2025-08-02 06:29:58] 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: Debian GNU/Linux 12 (bookworm), Kernel: Linux 6.12.34+rpt-rpi-v8, Architecture: arm64 [xxxx-xx-xx xx:xx:xx] Running on Raspberry Pi 3 Model B Rev 1.2 [xxxx-xx-xx xx:xx:xx] RTC offset register has value 0x78 [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-04 08:47:16] Done :-) [2025-08-04 08:47:16] Firmware ID: 0x37 [2025-08-04 08:47:16] Firmware Revison: 0x04 [2025-08-04 08:47:16] Current Vout=5.19V, Iout=0.12A [2025-08-04 08:47:16] System starts up because the button is clicked. [2025-08-04 08:47:22] Send out the SYS_UP signal via GPIO-17 pin.
After retesting over the weekend the problem persist. As you can see the board stay in "turn off mode" and the witty board did not shutdown the power. This have happened randomly in both of my witty boards . Im also using a relay shield and a 4G usb dongle. Could be related to any of them? the relays have not been actived yet and are normally closed so no magnetif field dischard should have affect the witty board. I also check and is not using the same pins as the witty board.
Thanks for your support!
Witty Pi did not cut the power because the conditions for cutting power had not been satisfied.
Witty Pi needs to receive SYS_UP signal to configure its internal state properly. If GPIO-17 is not properly connected, or it is unintentionally pulled by other hardware, the SYS_UP signal may not arrive and Witty Pi's internal state may be wrong.
Witty Pi detects Raspberry Pi's shutdown by monitoring the TXD pin, which should go LOW after the shutdown. You may measure your TXD voltage when this issue happens.
Problem solved . It seems that the additional shield was intereferint with the SYS_UP signal. Thanks for your support