Just re-read, yes it is. That's why I deleted my message shortly after posting.
(Sorright.) You saw my reply.
It happens.
Thanks to all.
Steve, I'm still interested in what you said but am waiting a reply to my question.
Um, looking harder and harder and more and more.
This sends a message (daily) at 06:30 and tells me if dawn has/not happened.
That isn't what I want/need.
If dawn happens before 06:30 it is ok for the signal to go out.
Just I want 06:30 to be the latest time it is sent.
Paul, Julian.
Thanks.
I may have to go away and re-think how I am going to do this.
(Waste a few hours to think of a bad way to do it.) 
(See other recent post - making things more difficult than they need to be)
Final offering... using a delay node in rate limit mode.
First msg wins, the second msg is dropped.
2 Likes
That is a very different approach.
Thanks.
Honestly, that looks like the way I will go.
It is simple.
1 Like
of course the 06:30 inject could also be a 2nd schedule entry in the cron+ node too
2 Likes
Haha, yes of course, so really, it only needs a delay node set as rate limit, and let both events be managed by cron+.
Good idea.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
