That is correct, I want the test to be "true" if any one of the timeSecs is true. Thanks for confirming that it is correct.
In regards to:
Have you tried printing the value of timeSecs just before the test ?
no, I tested timeSecs in the loop by adding:
I just tested it right before the "if" test as you asked and got a running string that did not directly correspond to the timeSecs variable (at least as far as I could break it down).
Does it work if you set timeSecs explicitly to one of the values just before the test ?
Yes, it does. Thanks for this. I am going to create a function outside of all other functions to set the schedule and call that function from the primary "if" test instead of trying to set it directly inside the schedule function - I think this will solve the problem.
Thanks for your help, I will reply back once done and if that solved the problem.
Thanks for replying aarg,
32,400 seconds is 9 hours. How can the elapsed time ever match that if it's only updated once a day?
timeSecs is elapsed time in seconds added to whatever time it was during the last NPT time sync. So timeSecs should range from 0 to 86399 - unless the network goes down. I don't know why this would not work?