# Recommended scheduling for roller-shutters

**URL:** https://discourse.nodered.org/t/recommended-scheduling-for-roller-shutters/36927
**Category:** General
**Created:** [3 December 2020 05:04 UTC](https://discourse.nodered.org/t/recommended-scheduling-for-roller-shutters/36927 "2020-12-03T05:04:18Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![PizzaProgram](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/pizzaprogram/32/19431_2.png) [@PizzaProgram](https://discourse.nodered.org/u/PizzaProgram)
#### Post date: [3 December 2020 05:33 UTC](https://discourse.nodered.org/t/recommended-scheduling-for-roller-shutters/36927/4 "2020-12-03T05:33:21Z")

</div>

@Trying_to_learn Thanks for the quick answer, but the "simple" way is not working, because it can NOT cancel running delays and triggers.

Currently I'm investigang following methods to decide what would be best to solve this:

- using contexts with unique IDs to remember "current / last state"
- insert switches to decide if the original command has been ovveriden to drop execution of timer-based triggers
- maybe creating timer-arrays as [here](https://discourse.nodered.org/t/multiple-settimeout-cleartimeout-within-same-function-node/25300/2) ?
- how to make more complex JSONATA templates + messages to store multiple infos like:  
{  
name: "livingroom",  
time-to-full-roll: 22,  
half-roll: 5,  
last\_direction: "DW",  
current\_state: "rolling"  
}

# Is it possible, somehow to use "events" to notify [1,2,5] to "go full Up" ?

---

_[View the full topic](https://discourse.nodered.org/t/recommended-scheduling-for-roller-shutters/36927)._