Few things in webCoRE seem to be as stealthy or unstoppable as a “fade to level” once it has begun. I’ve tried to write a few pistons around it and have been part of many threads in “Piston: Design Help” with the same issue. All the usual suspects have been tried, but come up short when it comes to stopping a fade:
- Cancel all pending tasks
- If $systemVariable is, then Do xxx… all system variables seem to be null, including $currentEventAttribute when the piston wakes up to set the next level. Success using this method would seem to still be limited by item #1. If you can ID a fade command woke up the piston, how could you stop it?
- Piston pause - this CAN work, but requires a separate piston to monitor and resume the offending piston. Since the name of a piston to resume can’t be passed as a variable or argument, the piston doing the monitor/resume function has to be hard-coded with a piston name to resume. This stacks up pistons quickly depending on the number of times you use fade in other lighting applications.
The most common need for this comes about as “if my automation has started a fade, and someone adjusts the light with a switch, I want the automation to stop further adjusting the lights”.
As someone that was travelling for work and 10.5 hours ahead of my home time zone, bored, and playing with the automation… and may have inadvertently started a fade from 0 to 100 command on the Master Bedroom lights at 1:30am… I can speak to how much any kill for Fade to Level would be appreciated.