1) Give a description of the problem
Not a problem, but I was wondering what the behavior of the time statement “Time is before X seconds to Y” is regarding subsequent piston scheduling.
2) What is the expected behavior?
I don’t know, hence the question:grin:.
3) What is happening/not happening?
I created the piston below, using that form of statement in line #27. I noticed that after initial test run, the next run was scheduled for 12:00 am that night. I had the statement set to “always subscribe” (on automatic there was no event scheduled). So I was wondering if the behavior is that the piston was scheduled for the earliest possible time that would be “before” the test condition, and then would again be rescheduled at some small incremental time until the condition was no longer possibly true (i.e. before time was passed). Worried about excessive scheduling, I changed the statement to an absolute time check (happens daily at…) - but am still curious if anyone knows the answer to my question about the resulting (re)scheduling behavior. Hopefully the question is sufficiently clear.
4) Post a Green Snapshot of the piston
(UPLOAD YOUR IMAGE HERE)
5) Attach any logs (From ST IDE and by turning logging level to Full)
(PASTE YOUR LOGS HERE BETWEEN THE MARKS THEN HIGHLIGHT ALL OF THE LOGS SND CLICK ON THE </> ICON TO FORMAT THEM)
REMOVE BELOW AFTER READING
If a solution is found for your question then please mark the post as the solution.