Coming in cron-plus v3: a "Cron Filter" node with natural language conditions

General
21

TBF, "last day of the week" is the same as saying "on sunday" (or "on saturday" if you are from a crazy part of the world :wink: ) so a tick box is probably just adding complication.

I think it makes sense to leave "of the week" ISO standard.

But I have noted you comment and not 100% ruled it out just yet.

And thank you for the feedback.

22

I would prefer 'Time Gate' to 'Cron Filter' as it is not necessarily tied to cron-plus

23

Though it would forever remind me of the superb Stargate Si-Fi series. :smiley: No bad thing though.

24

Changing my preference re node name from Time Gate to Cron Plus Gate :grinning_face:

"Cron Plus" because it's part of the Cron Plus group and also to reflect that it's not limited to cron related triggers.

"Gate" because of Simple Gate and Queue Gate

25

I'm thinking of naming the node simply "when" :thinking:

(note the underlying distinction between packages will still be "cron-filter", "when" would be a display name!)

26

Just about sums up 'it all', like it!

27

The only downside of that is that it is such a short name and might easily end up with a name clash? Shouldn't such short, generic names be reserved for core features rather than contributed nodes?

And actually, I am not convinced that it gives enough meaning to be able to pick it out from the crowd. Having the "gate" postfix accurately describes its effect.

So maybe when-gate?

28

I like - top of the list!

29

Sounds good to me.

30

Forgot to mention, v3.0.0 is now live.

Hopefully I didn't break anything (or too much)

I have zero doubt that some of the most obvious when gate phrase support has been overlooked and you will all hopefully be kind in pointing that out.

Anyhoo, happy Friday.

31

Altitude and Azimuth are important solar (and lunar) properties. eg the sun shines into Newgrange when it's azimuth is between 134 and 138 degrees and it's altitude is greater than 0.5 degrees.

The node seems not to understand an input including the words altitude or azimuth, though "sun above 30" is accepted and explained as "Allow when: sun altitude is above 30 degrees"

image

32

Coming soon

image
image716×116 4.23 KB

33

Looks interesting.

4
Chrono-logic
or
Crono-logic

34

Awesome concept, especially text based instructions feature

here are few suggestions for names

cron-guard, cron-sieve, chronogate, cron-if

35

I tried this as the input to the Node. Any use to you?

daily between civilDawn to 2130h

Screenshot from 2026-09-15 13-43-16
Screenshot from 2026-09-15 13-43-16919×230 21.8 KB

DOesn't seem to like a mix of named times and HHMMSS

36

Thanks for the feedback. "daily" is a synonym i missed (will add) (you could already enter "every day" or "always" or just leave it out tbh!)

civilDawn is effectively "dawn" but I will add explicit support for "civil dawn/dusk" so it avoids ambiguity.

As for 2130h, 21:30 works but i think I will add support for the military nnnnh version too.

37

I wanted to use something similar as @mudwalker.
I wanted to control the output every hour on the hour, but only between sunrise and sunset.
So e.g. 08:00, 09:00, 10:00, but not 02:00.

I don't think it is very unusual or complicated, but maybe I'm missing the proper English phrase.

Cronplus-When-Gate1

38

"on the hour" is something i could add, but for now:

image
image647×632 52.3 KB

39

This looks like another example where the node's stated understanding "every hour" is not accepted as an input to the node. This does not make sense to me!

Of course "On the hour" quickly gets more complicated: "At 2, 6, 10, ...58 minutes, between morning nautical twilight and sunrise".

Once you go down the rabbit hole ...
:rabbit: :new_moon:

40

It’s always 6 o’clock at the mad hatters tea party…