Cool stuff for Raspberry Pi, Arduino and all electronics hobby projects
Notifications
Clear all

[Solved / Archived] Unexpected next startup time in schedule script (Witty Pi)

8 Posts
2 Users
0 Likes
553 Views
(@ejwmac)
Posts: 17
Eminent Member Customer
Topic starter
 

Hello,

 

Please see the image below which is a combined image of 3 images:-

1. Right at the top you will see the output from the RunScript.sh after I loaded up the schedule.wpi file into the wittypi folder.

2. My cropping of the image is a little severe but you can still make out that the scrip is indicating that the next shutdown is at 15:00 on the 16 th (Today) 

3. The mystery is the next line which indicates the next start up is at 23:00 tomorrow the 17th and this is teh the real confusion i have.. how did this happen?

4. The next part of this same image is the actual schedule.wpi input

5 Then finally below is the output of the uwi url as well as showing the same schedule info which I am totally confused with it also shows the current time as reported by the RPI.

 

Finally, this is now running on RPi Zero 2 W.

 

I would really like to know what i am doing wrong here please?

 

Thanks

(PS ) hope the image really is attached..

 

 

 

 

 
Posted : 16/10/2023 3:25 pm
(@admin)
Posts: 512
Member Admin
 

It is because you defined the OFF state with duration "H15 H17", which is taken as 15+17=32 hours. I guess you mean "H15 M17".

There are also other lines in your script have similar problem.

 
Posted : 16/10/2023 3:46 pm
(@ejwmac)
Posts: 17
Eminent Member Customer
Topic starter
 

Ok, thank you for the response, but I stated H15 because I thought that was the correct input to start the OFF period at 15:00. and the period of the off was 17 hours?

 

How should that be input, please?

 
Posted : 17/10/2023 2:29 pm
(@admin)
Posts: 512
Member Admin
 

You can only define the duration for each state.

The beginning of the state is decided by the BEGIN time (at the begining of the schedule script). If the BEGIN time moves, all states will move accordingly.

Please read "Make Your Own Schedule Script" section in the user manual.

 

 
Posted : 17/10/2023 3:32 pm
(@ejwmac)
Posts: 17
Eminent Member Customer
Topic starter
 

Thank You 

I have read your documentation which on this subject i find vague/confusing.......so maybe you can answer why the following does not work either, and it would be helpful nto to advise me to read the documentation again..

See the screenshot of the UWI output... Schedule script on the right of UWI image.

 

The first On and OFf lines executed as i expected, but then i got the update on the UWI URL in response to the next scheduled Off and On which i did not expect.

 

Thank You

This post was modified 1 year ago by ejwmac
 
Posted : 17/10/2023 4:59 pm
(@ejwmac)
Posts: 17
Eminent Member Customer
Topic starter
 

Apologies no image is attached please find it below.

 

1697554906-Screenshot-2023-10-17-at-155527.png
 
Posted : 17/10/2023 5:01 pm
(@ejwmac)
Posts: 17
Eminent Member Customer
Topic starter
 

The previous post has a typo in that the 2nd  On should read shut down at 14:20 ....... I was too late to edit the original....apologies.

 
Posted : 17/10/2023 5:10 pm
(@admin)
Posts: 512
Member Admin
 

In this forum, a topic is for discussing one technical question/issue/idea, the topic title should reflect what is discussed inside.

A topic is not a dedicated support channel for one user. So if you have a different question after the initial question gets answered, you should open a new topic instead of appending your new question in the same topic. Appending new question in old topic reduces the chance for others to see your new question, and it also makes the content of discussion no longer match the topic title.

Your initial question has been answered, and it was due to incorrect schedule script writing. This topic will be marked as solved.

Since you are new to schedule script, I would suggest not to use UWI for schedule script troubleshooting. The better way is to create/edit the schedule script directly on your Pi, via SSH session if you prefer to do it on your PC. There is wittyPi.log file that can tell what actually happened and is helpful for troubleshooting. You don't get any log information from UWI, and the screenshot of UWI doesn't provide the information needed for analysis. It is just a picture version of "something goes wrong" or "it doesn't work".

 

 

 
Posted : 19/10/2023 12:11 pm
Join Waitlist We will inform you when the product arrives in stock. Please leave your valid email address below.