# Time Triggered Inject Ussie

**URL:** <https://discourse.nodered.org/t/time-triggered-inject-ussie/52260>\
**Category:** General\
**Created:** [15 October 2021 11:00 UTC](https://discourse.nodered.org/t/time-triggered-inject-ussie/52260 "2021-10-15T11:00:16Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Calendil](https://avatars.discourse-cdn.com/v4/letter/c/fbc32d/32.png) [@Calendil](https://discourse.nodered.org/u/Calendil)\
**Post date:** [15 October 2021 11:00 UTC](https://discourse.nodered.org/t/time-triggered-inject-ussie/52260/1 "2021-10-15T11:00:16Z")

</div>

Hello All,  
I am having an issue with specific time triggered inject node. It triggers may be once out of 20 tries whenever I set it up on upcoming time. It is not triggering on specific time and day.  
I flat out imported from cook book and only changed the time. Worked once or twice that's it.

[https://cookbook.nodered.org/basic/trigger-at-time](https://cookbook.nodered.org/basic/trigger-at-time)

Am I missing something? It does not look that complicated.  
(Node red is on Raspberry Pi Zero) I checked the machine time, it is accurate.  
Thank you for your time.

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [15 October 2021 11:03 UTC](https://discourse.nodered.org/t/time-triggered-inject-ussie/52260/2 "2021-10-15T11:03:45Z")

</div>

What version of node-red are you using?

Earlier versions used a different Cron library under the hood.

You could try Node-red-contrib-cron-plus which contains logic to update schedules should the time on the server change due to ntp.

---

<div class="post-metadata">

**Author:** ![Calendil](https://avatars.discourse-cdn.com/v4/letter/c/fbc32d/32.png) [@Calendil](https://discourse.nodered.org/u/Calendil)\
**Post date:** [15 October 2021 11:07 UTC](https://discourse.nodered.org/t/time-triggered-inject-ussie/52260/3 "2021-10-15T11:07:57Z")

</div>

Thank you for your fast response. I am using 2.0.6.

---

<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:** [15 October 2021 12:09 UTC](https://discourse.nodered.org/t/time-triggered-inject-ussie/52260/4 "2021-10-15T12:09:41Z")

</div>

There is an issue with devices that don't have a hardware clock, particularly if connected via wi-fi. On startup node red may start before the network is connected and the clock synchronised. So it gets the wrong time and never recovered. You can check if it is that by restarting node red and then see if it works. If it is that then there is a line in the systemd startup script that you can uncomment to make it wait for time sync before starting node red. Alternatively (and possibly better) use the cron plus node as suggested, which does not suffer from this problem.

---

<div class="post-metadata">

**Author:** ![Calendil](https://avatars.discourse-cdn.com/v4/letter/c/fbc32d/32.png) [@Calendil](https://discourse.nodered.org/u/Calendil)\
**Post date:** [17 October 2021 14:16 UTC](https://discourse.nodered.org/t/time-triggered-inject-ussie/52260/5 "2021-10-17T14:16:52Z")

</div>

Thank you very much, I switched to cronplus as you suggested. Does what I need.

---

<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:** [31 October 2021 14:17 UTC](https://discourse.nodered.org/t/time-triggered-inject-ussie/52260/6 "2021-10-31T14:17:29Z")

</div>

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