For the complete documentation index, see llms.txt. This page is also available as Markdown.

Timed Rules

Run a rule on a fixed schedule instead of on every new data sample.

A timer runs a rule on a fixed schedule. The rule logic is then evaluated at set times, in addition to when new data arrives.

To add a timer, click Add timer at the bottom of the rule detail view.

The Add timer button at the bottom of the rule detail view
Adding a timer to a rule

Timer modes

The timer configuration offers three modes:

Runs the rule every few minutes, hours, or days. The next run is always the next upcoming interval.

Interval
Aligned to
Example

Minutes

The hour

A 10 minute interval runs at XX:00, XX:10, XX:20, and so on.

Hours

The day

A 6 hour interval runs at 00:00, 06:00, 12:00, and 18:00.

Days

Midnight UTC

Runs every day at 00:00 UTC.

Runs the rule every day at the selected time, starting on the day after the selected start date.

Runs the rule on a Quartz cron expression in UTC. Use it for schedules the other modes cannot express.

Output templating

A timer is not a device, so a timed run has no current data sample. The {{data.*}} property and all other properties of the current sample are not available in the payload templates of the rule actions.

Use {{dataSources.X.*}} instead. Data sources always resolve to the latest stored sample of their device. A data source whose device has not stored any data yet is not resolved.

See Data Source Properties for all available properties.

Last updated

Was this helpful?