# \[ANNOUNCE\] node-red-contrib-ui-time-scheduler

**URL:** <https://discourse.nodered.org/t/announce-node-red-contrib-ui-time-scheduler/36288>\
**Category:** Share Your Nodes\
**Created:** [21 November 2020 13:43 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-ui-time-scheduler/36288 "2020-11-21T13:43:23Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![gojk](https://avatars.discourse-cdn.com/v4/letter/g/41988e/32.png) [@gojk](https://discourse.nodered.org/u/gojk)\
**Post date:** [23 November 2020 21:24 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-ui-time-scheduler/36288/21 "2020-11-23T21:24:54Z")

</div>

Works like a charm. Thanks a bunch! ✅

---

<div class="post-metadata">

**Author:** ![davidz](https://avatars.discourse-cdn.com/v4/letter/d/a88e57/32.png) [@davidz](https://discourse.nodered.org/u/davidz)\
**Post date:** [23 November 2020 23:14 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-ui-time-scheduler/36288/22 "2020-11-23T23:14:31Z")

</div>

Yes confirmed fixed now! 😍

---

<div class="post-metadata">

**Author:** ![SonoraTechnical](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sonoratechnical/32/20033_2.png) [@SonoraTechnical](https://discourse.nodered.org/u/SonoraTechnical)\
**Post date:** [24 November 2020 03:50 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-ui-time-scheduler/36288/23 "2020-11-24T03:50:42Z")

</div>

Thank you for writing this. RIght away I have two use cases for it in one of my projects! Awesome. I'll add feedback as I use it.

---

<div class="post-metadata">

**Author:** ![Dave](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dave/32/10827_2.png) [@Dave](https://discourse.nodered.org/u/Dave)\
**Post date:** [24 November 2020 10:58 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-ui-time-scheduler/36288/24 "2020-11-24T10:58:28Z")

</div>

This is a useful addition to the palette, I like it but just a couple of small feedback points, on the dark theme, black writing on dark background isn't great, also the plus button appears to be a cutoff 2x1 button see attached,

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/0/0/00de3355cf67e6bcacedf96a9f0b008d90aaeb70.png)

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [24 November 2020 11:14 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-ui-time-scheduler/36288/25 "2020-11-24T11:14:32Z")

</div>

the ui module exports a function isDark() that the module can use to decide how to set colours. though if the existing classes are used they are set automatically to match the theme.

---

<div class="post-metadata">

**Author:** ![hotNipi](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hotnipi/32/383_2.png) [@hotNipi](https://discourse.nodered.org/u/hotNipi)\
**Post date:** [24 November 2020 11:19 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-ui-time-scheduler/36288/26 "2020-11-24T11:19:05Z")

</div>

Works for me even with pretty hard CSS override for dashboard defaults. (Nothing modified from this widget perspective)

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/b/4/b4affbf939948bbdfcd868f6366f1d2cbfd6f7d9.png)

---

<div class="post-metadata">

**Author:** ![fellinga](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/fellinga/32/30631_2.png) [@fellinga](https://discourse.nodered.org/u/fellinga)\
**Post date:** [24 November 2020 11:24 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-ui-time-scheduler/36288/27 "2020-11-24T11:24:00Z")

</div>

@Dave I just noticed this yesterday as well 😅.. I am going to address this today after work.

@hotNipi I noticed that the button is cutoff if "Angular Theme in ui\_template" is enabled. That is probably also what Dave is using. Anyway I am going to take a look at different themes later today.

Thanks everybody for the great feedback and help (@dceejay 😉 )

---

<div class="post-metadata">

**Author:** ![fellinga](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/fellinga/32/30631_2.png) [@fellinga](https://discourse.nodered.org/u/fellinga)\
**Post date:** [24 November 2020 18:32 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-ui-time-scheduler/36288/28 "2020-11-24T18:32:52Z")

</div>

Another day, another update - v0.4.4 is now available 🎉  
It should fix CSS problems and also improve readability for dark theme users.

@Dave Is it better now?  
@hotNipi Could you check if its still good for you as well?

---

<div class="post-metadata">

**Author:** ![hotNipi](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hotnipi/32/383_2.png) [@hotNipi](https://discourse.nodered.org/u/hotNipi)\
**Post date:** [24 November 2020 19:05 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-ui-time-scheduler/36288/29 "2020-11-24T19:05:42Z")

</div>

No hard problems found by quick look.  
There may be some better choices of cursor for those elements in this view.  
The hovering over text elements makes a bit misleading result.  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/a/e/aeef42dd8ac15f2528348cdad10240c642e38089.png)

---

<div class="post-metadata">

**Author:** ![Dave](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dave/32/10827_2.png) [@Dave](https://discourse.nodered.org/u/Dave)\
**Post date:** [26 November 2020 13:10 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-ui-time-scheduler/36288/30 "2020-11-26T13:10:05Z")

</div>

Sorry for late reply, YES v0.4.4 fixes my CSS problems, thanks.

---

<div class="post-metadata">

**Author:** ![Spinky](https://avatars.discourse-cdn.com/v4/letter/s/59ef9b/32.png) [@Spinky](https://discourse.nodered.org/u/Spinky)\
**Post date:** [26 November 2020 13:50 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-ui-time-scheduler/36288/31 "2020-11-26T13:50:54Z")

</div>

This looks like something I've been looking at for some time for my irrigation system - many thanks for your efforts!  
Will give it a go - any chance of multiple on/off times during the day?

---

<div class="post-metadata">

**Author:** ![fellinga](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/fellinga/32/30631_2.png) [@fellinga](https://discourse.nodered.org/u/fellinga)\
**Post date:** [26 November 2020 14:00 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-ui-time-scheduler/36288/32 "2020-11-26T14:00:16Z")

</div>

@Spinky Sure, you can create as many as you need. Here is an example:

 ![Screenshot 2020-11-26 145720](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/5/e/5e497aca7dcaadbc93a8bd2a32511aee28c6800c.jpeg) : ![Screenshot 2020-11-26 145441](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/c/2/c2ee11683cce2009deb2551456658b7143f03f45.jpeg)

Both, the default mode (left-hand side) and the event mode (right-hand side), support multiple entries.

---

<div class="post-metadata">

**Author:** ![sonntam](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sonntam/32/19423_2.png) [@sonntam](https://discourse.nodered.org/u/sonntam)\
**Post date:** [27 November 2020 08:01 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-ui-time-scheduler/36288/33 "2020-11-27T08:01:03Z")

</div>

Good job, I will check it out.

Have you thought about including a geo location based astro function that allows you to set time triggers relative to sunrise and sunset times?

---

<div class="post-metadata">

**Author:** ![fellinga](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/fellinga/32/30631_2.png) [@fellinga](https://discourse.nodered.org/u/fellinga)\
**Post date:** [27 November 2020 17:07 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-ui-time-scheduler/36288/34 "2020-11-27T17:07:16Z")

</div>

Thanks @sonntam

I thought about it today, I am not sure if it's something that should go into this UI node. I think if someone wants to put a device on/off at sunrise/sunset then this person would define that once and leave it like this - and that's already possible with many nodes (that do not have a dashboard UI).

But I am open to discussions. Maybe you, or someone else has a good reason why it's a good idea to add this function to this particular node as well.

---

<div class="post-metadata">

**Author:** ![drmibell](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/drmibell/32/8424_2.png) [@drmibell](https://discourse.nodered.org/u/drmibell)\
**Post date:** [27 November 2020 18:55 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-ui-time-scheduler/36288/35 "2020-11-27T18:55:29Z")

</div>

> [@fellinga](#):
>
> a good reason why it's a good idea to add this function to this particular node as well

You may have answered this question yourself:

> [@fellinga](#):
>
> t any person without any technical background (and without access to the node-red flow editor)

I think this feature would be particularly useful for users on mobile devices. Obviously, it would call for some effort to implement. The existing nodes that are most widely used for lighting control in home automation also provide for random offsets to sunrise/sunset times and the ability to temporarily suspend an event. If your node has many happy users, you will be kept busy 🙂

---

<div class="post-metadata">

**Author:** ![fellinga](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/fellinga/32/30631_2.png) [@fellinga](https://discourse.nodered.org/u/fellinga)\
**Post date:** [28 November 2020 10:55 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-ui-time-scheduler/36288/36 "2020-11-28T10:55:43Z")

</div>

I see what you mean @drmibell... My initial thought was that the person who would set things up for you, can activate the sunset/sunrise timer for you in the flow-editor, and then it's very unlikely that you would ever want to change that again...but sure there is a possibility and it makes even more sense now with the offset.

* * *

> [@dceejay](#):
>
> though if the existing classes are used they are set automatically to match the theme.

I've raised an [issue](https://github.com/node-red/node-red-dashboard/issues/640) at the dashboards GitHub site, it seems to me that this doesn't work with Angular Theme enabled.

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [28 November 2020 13:56 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-ui-time-scheduler/36288/37 "2020-11-28T13:56:33Z")

</div>

Ok will look at the issue. But when you select angular theme then we try to get out of the way so it should be whatever they provide.

---

<div class="post-metadata">

**Author:** ![fellinga](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/fellinga/32/30631_2.png) [@fellinga](https://discourse.nodered.org/u/fellinga)\
**Post date:** [19 December 2020 09:46 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-ui-time-scheduler/36288/38 "2020-12-19T09:46:46Z")

</div>

Hey everyone,

I just wanted to mention what has happened in the past weeks.

1. v0.4.5  
fixed a minor migration bug
2. v0.4.6  
added the possibility to change the first day of the week
3. v0.4.7  
added a overview site that is shown if multiple devices are configured so that you can see all the timers for all devices at a glance (I am open to styling suggestions 😅)  
adjusted the pointer like @hotNipi suggested.

The latest update to the node-red-dashboard (v2.25.0 [#646](https://github.com/node-red/node-red-dashboard/pull/646)) also improves the nodes styling for everyone who uses the Angular Theme (like @Dave).

---

<div class="post-metadata">

**Author:** ![fellinga](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/fellinga/32/30631_2.png) [@fellinga](https://discourse.nodered.org/u/fellinga)\
**Post date:** [18 January 2021 20:29 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-ui-time-scheduler/36288/39 "2021-01-18T20:29:47Z")

</div>

Quick update... I fixed a few bugs and improved the UI during the last few weeks.. Here is the summary on what has changed:

Functionality:

- you can now add a msg topic to the outputs

User interface:

- the overview and device view now have sticky headers to improve usability
- the overview page does no longer show devices without timers
- improved time input for firefox&safari

Fixed:

- days in overview were displayed as UTC
- filter for timers didn't filter correctly

[Latest version as of today is: 1.5.2](https://flows.nodered.org/node/node-red-contrib-ui-time-scheduler) 🎉.  
Feedback is welcome!

---

<div class="post-metadata">

**Author:** ![gerry](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gerry/32/21604_2.png) [@gerry](https://discourse.nodered.org/u/gerry)\
**Post date:** [19 January 2021 01:08 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-ui-time-scheduler/36288/40 "2021-01-19T01:08:57Z")

</div>

Just in case you hadn't heard, updated to your new level and now the display is broke on my phone, android running firefox. Display says "invalid or no payload provided" sorry but can't screen shot. Worked before updating to 1.5.2  
[EDIT]  
still works on my laptop and other devices.

[Previous page](https://discourse.nodered.org/t/announce-node-red-contrib-ui-time-scheduler/36288.md?page=1)

[Next page](https://discourse.nodered.org/t/announce-node-red-contrib-ui-time-scheduler/36288.md?page=3)