The Missing Link to simple UI-configurable Scheduling

[5iver (Scott Rushworth)]

@Zeto

Lets take a look at this from another angle, let’s say i want to utilize a UI based rule engine like the Next Generation Rule Engine for Scheduling (setting aside that it is experimental), that engine needs access to a time item it can use because it likely doesnt have access to cron, and this is where the concept of an event based time item comes in.

This is a completely inaccurate depiction of the new rule engine, the current UI rule editor, and of what their capabilities are. They absolutely have access to cron ! The issue you appear to be addressing is merely a limitation of the old rule engine, which does not exist in the new rule engine. Here is an example of a rule that triggers on Item change and creates/updates another rule that uses a cron trigger… and yes, this could also be created through the REST API or UI rule editor…

Dynamic set days and time for rules, instead of hard-coded cron?

How about a rule that triggers on an Item change, where the action creates/modifies another rule that triggers on the time from the Item in the first rule? This is not possible in the old rule engine, but with scripted automation, you could do something like this… from core.rules import rule from core.triggers import when @rule("Adjust rule trigger") @when("Item Virtual_DateTime_1 changed") @when("System started") def adjust_rule_trigger(event): adjust_rule_trigger.log.warn("Cron Item chan…