CoRE and Piston Rules Engine, first design steps

[elf]

@kraig109

Also, I wrote this piston originally in 2016 in December. Then it DID say the ‘next scheduled’ was May 2017

@kraig109

However today I was playing with the CoRE dashboard and I noticed it was telling me the next scheduled run was 475 days later - which is May 2018. (It seemed that as the year changed), it MOVED OUT my next schedule another year

Hmmm … I have a piston that I created last year that also has yearly schedules and worked correctly. I need to check it to see if anything has changed. But first, I need a data network connection out here where I work (can’t open the ST app)!!! Gonna have to wait til I get home.

EDIT:
Just remembered that I posted part of it over here:

[SHARE] CoRE - show & tell all about Pistons

HAPPY NEW YEAR!! [image] Special Event Lighting Overview: Part of a special event lighting piston. This section is for the New Year. Implementation: Uses @krlaframboise 's handler for playing MP3 files on the Aeotec Doorbell; standard ST Hue(Connect) for the Hue lights, Bloom in this case. Feature(s): Track 28 is a MP3 soundbite of fireworks, while track 26 is a Chipmunks version of Auld Lang Syne (the Doorbell is limited to a max of ~20 secs. of play-time and this fit the bill, LOL). Note(s): High WAF – the Chipmunk version of Auld Lang Syne was unexpected and she found it funny. Next event is 364 days away. I think I’ll add more lights for next year

It showed the correct ‘next event’ as of the 1st of January. Gonna check again to make sure, though.

FOLLOW UP:
Everything is fine with the piston. Pending future events are correct.