I need a rule that runs every 2 weeks. Yes i seached and still not understanding why this isnt work or even why this is so difficult.
CRON doesnt have 2 week or 14 day support.
We should be able to run automation without learning programming. If i want to run a rule every 18 days or 23 days or whatever we should have drop down or selections.
The solution offered above by @ogiewon won't work, as Cron doesn't work that way.
To get every other week you need to use an every week schedule, and a Boolean variable or Private Boolean. Flip the variable each week, and only when true do whatever it is. That will cause it to skip every other week.
You can also use a community app called Event Engine, which allows you to create cogs (similar to rules in RM) that you can set to run at any interval. Below I've set a cog to run every two weeks (which is many, many minutes)...
Event Engine is available in Hubitat Package Manager. Very functional and flexible, easy to configure via drop-down selections, and is well supported by it's developer, @bptworld:
For more "unusual" intervals (like 23 days) i would run the rule daily and do something like this...
Create a local variable called DayCount or similar.
Trigger daily at preferred time.
Action:
Increment DayCount by +1
IF DayCount = 23 THEN
Do actions.
Set DayCount = 0
END-IF
Thanks for the explanation, Bruce. I can see to this leading to some amount of confusion amongst users, as cron scheduling is not all that intuitive to the vast majority of users.
That's what i need but you might as well told me i need a boggy boggy and a thing....and i have programmed in Java and C+ .... but not sure about this.
I have the same setup; a reminder set for every other Friday. I use the Google Calendar App, it switches a virtual switch whenever a matching event is in your Google calendar. Once you have the app up and running you can leverage all of Google's calendar features to create your event(s).
You can find details here... [RELEASE] Google Calendar, Task, and Reminder Search
This rule would run on the first Tuesday after it was setup, and then every two weeks thereafter. It actually wakes up every week, but only does whatever you want it to every two weeks, because the Else just flips the Private Boolean back to true.