I’m trying to create a piston to trigger 35 minutes before sunset but it ends up firing 45 minutes before sunset, even though webcore shows the right sunset times for my location.
2) What is the expected behavior?
To trigger exactly when I intend it to, without adding minutes.
Sunset on 2/9/2018 will be at 6:45 PM, so it is expected to trigger at 6:10 PM, instead it is scheduled to 5:59 PM
The schedule will always be set for tomorrow, but using today’s sunset time, so it’ll always be a little out.
That said, what part of the world are you in? For a day-to-day variance of 11 minutes you’d need to be in the upper hemisphere (I think).
Scrub that… you’re scheduling today, using today’s sunset time, but for a week ahead. So 11m is about right allowing for a 2 minute change in sunset time each day.
Suggest you schedule a dud-execution every night to force a daily re-schedule.
every day at 00:01
DO
(Leave blank)
end do
end every
That sorted it out. It seems that it was using sunset info from a-month-ago sunset, because I was using 1st friday of the month, 2nd friday, etc. And when it was triggered it also scheduled next month’s event with today’s sunset…
Could you help me understand how is Webcore working here? Just for future. Thanks!
When webCoRE completes an execution, it schedules itself for the next run on the list (actually the next 4 runs I think)
ST only provides us with today’s sunset / sunrise, so that’s all the scheduling can use at that point in time.
The piston then ‘sleeps’ until the next scheduled time.
By scheduling a dud wake up every day at 00:01, the piston wakes up, does nothing, then re-schedules itself using the new days sunset / sunrise times. On the actual day you want the piston to run for real, it will therefore be scheduled correctly.
