# Scheduler for Dashboard 2

**URL:** <https://discourse.nodered.org/t/scheduler-for-dashboard-2/90253>\
**Category:** Dashboard\
**Tags:** dashboard-2\
**Created:** [18 August 2024 15:11 UTC](https://discourse.nodered.org/t/scheduler-for-dashboard-2/90253 "2024-08-18T15:11:29Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![RB1](https://avatars.discourse-cdn.com/v4/letter/r/48db29/32.png) [@RB1](https://discourse.nodered.org/u/RB1)\
**Post date:** [18 August 2024 15:11 UTC](https://discourse.nodered.org/t/scheduler-for-dashboard-2/90253/1 "2024-08-18T15:11:29Z")

</div>

I have written a small home automation system with Node Red and Dashboard 1.  
I use the ui\_scheduler to control shutters, for example. I could not find a corresponding alternative for Dashboard 2. Is something like this planned, and if so, by when?  
What would be a good way to implement the function differently?

---

<div class="post-metadata">

**Author:** ![xx\_Nexus\_xx](https://avatars.discourse-cdn.com/v4/letter/x/54ee81/32.png) [@xx\_Nexus\_xx](https://discourse.nodered.org/u/xx_Nexus_xx)\
**Post date:** [19 August 2024 07:50 UTC](https://discourse.nodered.org/t/scheduler-for-dashboard-2/90253/2 "2024-08-19T07:50:39Z")

</div>

I moved away from these internal scheduler ... and using my normal Outlook calendar to schedule things .. example below...ROBBY is my vacuum cleaner and I schedule him to clean areas  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/1/e/1e46b0cfa694ad7199dba5f487ad0c3422341512.png)

or I use it send reminders via a MSG code which will be announced in my house via TTS (here it is a reminder to put the bins out

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/f/d/fdcd205aa367fc287e5fc3bbd2e0738910087123.png)

I use this node for the [calendar events](https://flows.nodered.org/node/node-red-contrib-ical-events)

The benefit is that I can re/schedule tasks when I'm away

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [19 August 2024 09:03 UTC](https://discourse.nodered.org/t/scheduler-for-dashboard-2/90253/3 "2024-08-19T09:03:13Z")

</div>

Many would say that the UI operation should not be tied closely to the logic of the system. In other words the UI should supply the fields for entering the schedule, but the same nodes should not implement the schedule. Using that strategy you can use regular ui nodes for inputting the data and something like the cron plus node for the actual scheduling.

---

<div class="post-metadata">

**Author:** ![RB1](https://avatars.discourse-cdn.com/v4/letter/r/48db29/32.png) [@RB1](https://discourse.nodered.org/u/RB1)\
**Post date:** [22 August 2024 17:43 UTC](https://discourse.nodered.org/t/scheduler-for-dashboard-2/90253/4 "2024-08-22T17:43:57Z")

</div>

A separation of logic and visualization sounds good.  
I have looked at “cron-plus” and think this will be the easiest solution for me.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [5 September 2024 17:44 UTC](https://discourse.nodered.org/t/scheduler-for-dashboard-2/90253/5 "2024-09-05T17:44:26Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.