Notifications
Clear all
Topic starter
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
Posted : 11/12/2023 11:20 pm
causing4132 reacted
@msage Witty Pi 3's software is now also upgraded to V3.52 with newer gpio-util.sh. Changes can be viewed here.
Posted : 24/01/2024 8:28 am
causing4132 reacted
Topic starter
@admin Thanks, I've upgraded my 3 pi's and none of them appear to be logging the message any more! 🙂
Posted : 24/01/2024 9:02 am
Hi @admin, I gave this issue some time to rest in hope things will get solved with time. Came back now and installed a clean, most up-to-date OS Lite on RPi Zero 2 W. I installed Witty Pi 3 software v3.53 using https://github.com/uugear/Witty-Pi-3/blob/master/Software/install.sh, as it seems the old http://www.uugear.com/repo/WittyPi3/install.sh script is no longer available.
Unfortunately it seems everything is still broken. The shutdown schedule does shutdown the Pi but leaves it in a weird state, where both the red and white leds on WittyPi are lit. During next scheduled startup, instead of booting up it seems to complete the shutdown and then the red led goes off, and the white one blinks, as if the shutdown only completes after scheduled startup. Same thing happens when using the button on WittyPi to shutdown (and in this case it is impossible to boot it back up with the button by pressing it, only holding it down for 5 seconds shuts it down and then I can start it up again).
Please let me know if I'm doing something wrong, and what data I should provide to help debug this issue. The device stays useless as it is. Thanks in advance.
This post was modified 2 months ago 3 times by causing4132
Posted : 29/12/2024 6:55 pm
@causing4132 The installation script is still there, but you will need to replace "http" with "https" in the URL. Documents may be out-of-date, and we do not actively update it because Witty Pi 3 has been discontinued for more than 2 years. The way you installed the software also worked.
If white and red LEDs stayed on after shutdown, it seems your Pi's system crashed during shutdown. Witty Pi 3 doesn't have the ability to deal with such scenario (Witty Pi 4 has it since firmware revision 0x03).
Posted : 30/12/2024 11:39 am
@admin I see. Ok do you know if there's a plan for WittyPi 4 Mini version (I'm using it on Pi Zero 2 W). Or is there some ancient Raspbian version I can install and not update where things were still working? At this point I think I may have to revert to using a garden (mechanical) timer :), though that's probably not very healthy for the SD card.
Posted : 31/12/2024 12:16 pm
@causing4132 Witty Pi 4 Mini has been released when Witty Pi 3 Mini was discontinued.
You can find all old versions of Raspbian here: https://downloads.raspberrypi.org/raspbian/images/
Posted : 31/12/2024 12:22 pm
causing4132 reacted
Page 3 / 3
Prev