# About Light Scheduler node output frequency

**URL:** <https://discourse.nodered.org/t/about-light-scheduler-node-output-frequency/8694>\
**Category:** General\
**Created:** [7 March 2019 09:06 UTC](https://discourse.nodered.org/t/about-light-scheduler-node-output-frequency/8694 "2019-03-07T09:06:14Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![pictux](https://avatars.discourse-cdn.com/v4/letter/p/7993a0/32.png) [@pictux](https://discourse.nodered.org/u/pictux)\
**Post date:** [7 March 2019 09:06 UTC](https://discourse.nodered.org/t/about-light-scheduler-node-output-frequency/8694/1 "2019-03-07T09:06:14Z")

</div>

Hi guys,  
i'm using the LightScheduler node (node-red-contrib-light-scheduler).  
It's possible to define the output frequency:  
" The output setting can be either of:

- "when state changes" - Will only output a `msg` when the state changes. The state is evaluated on a minutely basis, so it can take up to a minute after deploy of a new configu before the output it triggered.
- "when state changes + startup" - Will only output a `msg` when the state changes and directly after a deploy and a restart of node-red.
- "minutely" - Will only output a `msg` on a minutely basis even if the state have not changed."

but even if i've choose "when state changes + startup" it continues to generate output every minute.  
Does anyone have encountered the same behaviour?

Thanks  
M

---

<div class="post-metadata">

**Author:** ![pictux](https://avatars.discourse-cdn.com/v4/letter/p/7993a0/32.png) [@pictux](https://discourse.nodered.org/u/pictux)\
**Post date:** [7 March 2019 09:29 UTC](https://discourse.nodered.org/t/about-light-scheduler-node-output-frequency/8694/2 "2019-03-07T09:29:03Z")

</div>

> [@pictux](#):
>
> node-red-contrib-light-scheduler

hi guys, sorry i've checked the github issues and there's already a workaround (even if it's not already addressed).

The workaround is:  
"To anyone having the same issue - the `rbe` node can filter out messages unless the payload changes and helps to circumvent this problem."

cheers  
M

---

<div class="post-metadata">

**Author:** ![niklaswall](https://avatars.discourse-cdn.com/v4/letter/n/bb73d2/32.png) [@niklaswall](https://discourse.nodered.org/u/niklaswall)\
**Post date:** [3 May 2019 08:27 UTC](https://discourse.nodered.org/t/about-light-scheduler-node-output-frequency/8694/3 "2019-05-03T08:27:11Z")

</div>

Hi,

This is solved in the latest versions of node-red-contrib-light-scheduler

Changelog can be found here:

> **[Node-RED Light Scheduler](https://faulty.cloud/projects/node-red-contrib-light-scheduler/)**
>
> The faulty cloud

/Niklas Wall