Skip to main content
Version: V3.2

Conditional triggers

Conditional triggers are named conditions that can be referenced in Variable configuration to collect data only when one or more conditions are met.

Use cases include collecting data only when a machine is running, when a mode is active, or when a state value matches a set of allowed values.

Condition list​

The condition list shows all configured conditions for the connection.

Supported actions:

  • Add: create a new condition
  • Duplicate: copy an existing condition
  • Delete: remove a condition
  • Enable/disable: toggle whether a condition is active

Condition evaluation model​

A condition evaluates a value read from the connection at a specific mapping and compares it to one or more configured values using a selected operator.

Multiple values are OR-combined​

If a condition has multiple configured values, they are OR-combined:

  • The condition is true if the value read at the mapping matches any of the configured values (according to the selected operator).
  • The condition is false if it matches none of the configured values.

Example (using =):

  • Mapping value = 2
  • Values = [1, 2, 5]
  • Result: condition is true because 2 equals one of the configured values.

Timeout (debounce behavior)​

If Timeout is set (milliseconds), the condition becomes true only after it has continuously been true for at least the configured timeout duration.

This is useful to prevent short spikes or transient states from triggering data collection.

Condition fields​

Name​

Human-readable identifier for the condition. This is the name you select/reference in variable configuration.

Mapping​

Defines where the value is read from within the connection.

The mapping format depends on the connection type (for example a topic/path for MQTT, an address/node for OPC UA, etc.).

Operator​

Defines how the mapped value is compared to the configured values.

Operators shown in the UI include:

  • <
  • <=
  • =
  • !=
  • >
  • >=

Value(s)​

One or more comparison values.

If multiple values are provided, they are OR-combined (see above).

Timeout (ms)​

Optional minimum time (in milliseconds) the condition must remain true before it is treated as true.

  • Not set / 0: condition becomes true immediately when the comparison is true.
  • Set (e.g., 1000): condition must be true continuously for at least 1000 ms before becoming true.

Using conditions in variable configuration​

Conditional triggers are used in variable configuration to control whether a variable is collected.

Typical behavior:

  • If a variable references one or more conditions, the variable is collected only while the referenced condition logic evaluates to true.

Custom settings (advanced)​

The Custom settings tab is a JSON editor for advanced configuration.

Currently, there are no advanced conditional trigger settings exposed through this JSON editor.