# Time range node recommendation

**URL:** <https://discourse.nodered.org/t/time-range-node-recommendation/34651>\
**Category:** General\
**Created:** [21 October 2020 20:40 UTC](https://discourse.nodered.org/t/time-range-node-recommendation/34651 "2020-10-21T20:40:40Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![JGKK](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/jgkk/32/18515_2.png) [@JGKK](https://discourse.nodered.org/u/JGKK)\
**Post date:** [22 October 2020 18:09 UTC](https://discourse.nodered.org/t/time-range-node-recommendation/34651/7 "2020-10-22T18:09:55Z")

</div>

Hello,

I think this subflow timerange switch I build a while back would also do this and work across midnight:

> [@Two subflows I made: a timerange switch and a scheduler / dashboard integratable](https://discourse.nodered.org/t/two-subflows-i-made-a-timerange-switch-and-a-scheduler-dashboard-integratable/24586/3):
>
> small update to the time range switch. It now shows weekday abbreviations in the info instead of numbers [{"id":"7cc13ada.b6712c","type":"subflow","name":"timerange","info":"Lets through or blocks a payload\nbased on a time range. This can\neither be configured through the\nenviroment variables in the node ui\nor as described below with a message\nthat has an override topic.\nIf in range the msg will be passed\nto the first output and otherwise\nto the second.\nThe start and stop time needs\nto…

Of course as @Steve-Mcl suggested cron plus would be a lot more flexible and sophisticated.

Johannes

---

_[View the full topic](https://discourse.nodered.org/t/time-range-node-recommendation/34651)._