jay (support) wrote:We make the assumption that the user wants the schedule to run regardless of leap year, so we move it to the next day.
Exactly, I expected it to run regardless of leap year. But when there is no February 29, I would assume it would skip past that date. Why would it run the next day, which is March? That logic escapes me. What is the point of having monthly parameters?
Example of what happened today:
6:00am Turn on IRRIGATION Zone 2 for 10 min [Feb]
6:00am Turn on IRRIGATION Zone 1 for 28 min [March]
8:00am Turn on HEAT and set to 72º [Feb]
8:00am Turn on COOL and set to 80º [March]
Then when you factor in the Lighting, Windows, and every other February schedule getting multiple conflicting commands.
jay (support) wrote:If you want a schedule that only runs specifically on Feb 29th every 4 years, I'm afraid you'll need to take a different approach...
I'm not looking for anything unusual or special solution pertaining to leap year. Just expected a February schedule to run in February.