Settings

Besides datasets, condition and message, the rule has a couple of additional settings which can be set.

Time-based rule

A standard rule is evaluated each time an event has entered the platform for which the rule has a dataset configured. This can be changed by activating the toggle labeled as "Time-based rule". By activating this toggle, the input field "Time-based trigger" will be enabled and is then required.

A rule with "Time-based trigger" activated will no longer be evaluated each time an event enters the platform for which a dataset is configured. The rule will only be evaluated based on the point in time that is defined via the input field "Time-based trigger".

The field accepts a time definition in cron notation which deines when the rule should be evaluated.

Reset state when matched

On a standard Rule, a configured dataset is a First-in-First-Out Stack. Which means, when the total amount of events is reached (defined by the timespan of the dataset), when a new event enters the platform the oldest event will be thrown off the stack. The Dataset will never be cleared. Even, when a notification is sent the dataset is not emptied.

The toggle "Reset state when matched" forces the dataset to be emptied for the according household each time a Notification is generated. This can be useful, e.g. when having datasets that fill over a certain period of time and should earliest generate another notification after this timeframe has passed again.

Name

The name of the rule. The name is for internal use only (i.e. is not customer-facing), has to be unique, and should give a good understanding what the rule is about.

Description

This field may be used to describe the rule in more detail. This is for internal use only (i.e. is not customer-facing).

Match Threshold

This field defines, how often a condition has to be met, before the message is delivered.

If this value is set to "0" (default), then it will always be delivered.

Time between Notifications

When a message has been delivered, we might want to make sure that the same rule does not trigger another message for the same building for some time. This can be defined in this field.

Messages which would have been sent, but were within this time range, can be seen in the data graph as Dropped Notifications.