Notifications
Clear all
Technial Support / Discussion
6
Posts
2
Users
0
Likes
212
Views
Topic starter
I have about 140 witty pi's!!! and I use this shedule on all witty pi 4's:
BEGIN 2022-10-11 06:30:00
END 2033-09-30 22:30:00
ON H16
OFF H8
however I now have 10 that have started to not do this:
They will start correctly the next day but then will set the shutdown time as a minute before the startup time on that date, so they will not shutdown and will not restart, it seems to be spreading!!! Any ideas
Posted : 22/09/2024 10:36 am
set the shutdown time as a minute before the startup time on that date
That seems to be the behavior of "schedule revising", as described here: https://www.uugear.com/forums/technial-support-discussion/witty-pi-4-about-schedule-revising/#post-8
It is designed to avoid breaking the schedule, when the schedule is interrupted.
Like you said, it set the shutdown time as a minute before the startup time on that date. That means it should shutdown and then startup at the scheduled time. If it was not what happened, you need to check the wittyPi.log and find out why.
Why the schedule was interruptted is also a question that needs to find out the answer. I have no clue with the provided information.
Posted : 23/09/2024 12:54 pm
Topic starter
@admin thanks for replying, this is the log data:
[2024-09-22 20:36:26] Done 🙂
[2024-09-22 20:36:26] Firmware ID: 0xd0
[2024-09-22 20:36:26] Current Vout=5.36V, Iout=0.86A
[2024-09-22 20:36:26] System starts up because the input voltage reaches the restore voltage.
[2024-09-22 20:36:31] Send out the SYS_UP signal via GPIO-17 pin.
[2024-09-22 20:36:31] Pending for incoming shutdown command...
[2024-09-22 20:36:31] Schedule next shutdown at: 2024-09-22 23:30:00
[2024-09-22 20:36:32] Schedule next startup at: 2024-09-23 06:30:00
[2024-09-22 23:29:59] Shutting down system because scheduled shutdown is due.
[2024-09-22 23:29:59] Halting all processes and then shutdown Raspberry Pi...
[xxxx-xx-xx xx:xx:xx] Witty Pi daemon (v4.00) is started.
[xxxx-xx-xx xx:xx:xx] Running on Raspberry Pi 4 Model B Rev 1.5
[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...
[2024-09-22 23:30:31] Done 🙂
[2024-09-22 23:30:31] Firmware ID: 0xd0
[2024-09-22 23:30:31] Current Vout=5.37V, Iout=0.68A
[2024-09-22 23:30:31] System starts up because the input voltage reaches the restore voltage.
[2024-09-22 23:30:36] Send out the SYS_UP signal via GPIO-17 pin.
[2024-09-22 23:30:36] Pending for incoming shutdown command...
[2024-09-22 23:30:36] Schedule script is interrupted, revising the schedule...
[2024-09-22 23:30:36] Schedule next shutdown at: 2024-09-23 06:29:00
[2024-09-22 23:30:37] Schedule next startup at: 2024-09-23 06:30:00
[2024-09-23 06:28:59] Shutting down system because scheduled shutdown is due.
[2024-09-23 06:28:59] Halting all processes and then shutdown Raspberry Pi...
[xxxx-xx-xx xx:xx:xx] Witty Pi daemon (v4.00) is started.
[xxxx-xx-xx xx:xx:xx] Running on Raspberry Pi 4 Model B Rev 1.5
[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...
[2024-09-23 06:29:32] Done 🙂
[2024-09-23 06:29:32] Firmware ID: 0xd0
[2024-09-23 06:29:32] Current Vout=5.35V, Iout=0.77A
[2024-09-23 06:29:32] System starts up because the input voltage reaches the restore voltage.
[2024-09-23 06:29:37] Send out the SYS_UP signal via GPIO-17 pin.
[2024-09-23 06:29:37] Pending for incoming shutdown command...
[2024-09-23 06:29:37] Schedule script is interrupted, revising the schedule...
[2024-09-23 06:29:37] Schedule next shutdown at: 2024-09-23 06:29:00
[2024-09-23 06:29:38] Schedule next startup at: 2024-09-23 06:30:00
[2024-09-24 09:36:19] Writing system time to RTC...
<2024-09-24 09:36:20> Done 🙂
<2024-09-24 09:36:21> Writing RTC time to system...
[2024-09-24 09:36:20] Done 🙂
[2024-09-24 09:36:21] Internet detected, apply network time to system and Witty Pi...
[2024-09-24 09:36:21] Applying network time to system...
[2024-09-24 09:36:23] Done 🙂
[2024-09-24 09:36:23] Writing system time to RTC...
<2024-09-24 09:36:23> Done 🙂
<2024-09-24 09:36:28> Copying "DTBNormalShedule.wpi" to "schedule.wpi"...
<2024-09-24 09:36:28> Running the script...
<2024-09-24 09:36:28> Schedule next shutdown at: 2024-09-24 23:30:00
<2024-09-24 09:36:28> Schedule next startup at: 2024-09-25 06:30:00
<2024-09-24 09:36:29> Done 🙂
<2024-09-24 09:36:34> Set to "Default ON"!
Posted : 24/09/2024 9:39 am
Topic starter
and this is a screen shot:
Posted : 24/09/2024 9:40 am
System starts up because the input voltage reaches the restore voltage.
If you are powering the device via USB-C connector, you need to clear the low voltage threshold and the restore voltage threshold. They are not useful for your use case, and they might cause unexpected startup, which interrupts the schedule.
If the interruption happens very close to expected startup time, the schedule revising will not work as expected and it could set the shutdown time in the pass. You can see it actually happened in the log you provided.
Posted : 24/09/2024 10:07 am
Topic starter
It looks like removing the recovery voltage worked, one of the systems has started behaving itself, I'll change the others and report back if they don't start working properly again
Posted : 27/09/2024 9:21 am