Evaluates the rules in order against the payload. In first_match mode the first matching rule decides, in all_matches mode every matching case output fires. No match goes to Default. Stateless.
Waits for a message on both A and B with the same key within window_seconds and emits them joined. Unmatched messages go to Timeout when emit_timeout is set.
Writes one line per incoming message to the node log of the deployment and to the log of the device or cloud process, with the configured prefix and the message payload. The message continues on the Passed output when it is connected.
Passes a message and drops all messages with the same key during cooldown_seconds. With key_paths set it deduplicates; without, it is a global cooldown.
Evaluates conditions on named signals (classification scores or mapped payload values) with hysteresis, minimum duration, gap tolerance, combination (all/any/at least) and inhibit conditions. Emits Fired (and Cleared in state mode) with the contributing signal values; events dropped by cooldown or inhibit go to Suppressed. Keeps a ring buffer for timeline and dry run.
SIGNAL_COMBINE_ALL (All required conditions must be met (default).); SIGNAL_COMBINE_ANY (At least one required condition must be met.); SIGNAL_COMBINE_AT_LEAST (At least at_least required conditions must be met.)
At least
Number of required conditions that must be met. Only used with AT_LEAST.
number
No
at least 1
Window s
Memory time in seconds within which required conditions may be met at different times.
number
No
at least 0
Inhibit hold s
Seconds an inhibit keeps blocking after it ended. Unset = window_s.
number
No
at least 0
Mode
Output behaviour: single events or state with clear.
choice
No
SIGNAL_RULE_MODE_EVENT (Emit one Fired event per occurrence (default).); SIGNAL_RULE_MODE_STATE (Emit Fired when the state begins and Cleared when it ends.)
Cooldown s
Seconds after a fire during which further fires are suppressed.
number
No
at least 0
Clear after s
Seconds without a met rule before Cleared is emitted. Only used in STATE mode.
number
No
at least 0
Stale after s
Seconds without a sample until a level signal counts as no data. 0 = automatic (5 x sample interval, at least 5 s).
number
No
at least 0
Mappings
Mappings for non-classification messages.
list of group of fields
No
Key paths
Payload paths forming the key (state is kept per key). Empty = global.
list of text
No
Max keys
Maximum tracked keys; oldest are evicted beyond it.
number
No
at least 1
1000
Buffer minutes
Ring buffer length in minutes for the timeline and dry run.
Passes up to max_events messages per window_seconds and key; further messages go to the Dropped output. Keys are built from key_paths (empty = global).
Emits the agent's current system timestamp as a formatted string on every tick of the configured interval. The format is defined using Go's reference time layout (Mon Jan 2 15:04:05 MST 2006). Use this node whenever you need to inject a periodic timestamp signal into a flow — for example, to timestamp each processing cycle, to provide a time reference for time-based comparisons downstream, or to trigger other nodes at regular intervals with a current-time label attached. The ticker interval is shared with the IntervalTriggerConfig configuration. Example 1: emit an ISO 8601 timestamp every 10 seconds and pass it to a JsonProcessor that assembles a heartbeat payload for an external monitoring system. Example 2: emit the current date string (format '2006-01-02') once per minute as a key for daily database partitioning.
Window end in HH:MM (24h). An end before the start wraps over midnight.
text
No
5 to 5 characters
Weekdays
Active weekdays (mon, tue, wed, thu, fri, sat, sun). Empty = all days. For a window that wraps over midnight, the weekday of the start counts (fri with 22:00-06:00 covers Fri 22:00 to Sat 06:00).
list of text
No
Timezone
IANA timezone name, e.g. Europe/Berlin. Empty = device timezone.
Constructs a typed protobuf message from arbitrary input by walking configured JSONPath mappings and defaults. Supports percent / uuid / now / level / cardinal-direction transforms. Target type is resolved at runtime from the global proto registry, so any message compiled into the agent binary (DroneEvent, ClickEvent, Vektri, …) is a valid target. Missing source paths are skipped silently — only fully invalid configuration errors out.
Fully-qualified protobuf message name (without the package), e.g. DroneEvent, ClickEvent, Vektri. Resolved at runtime via protoregistry.GlobalTypes. Anything registered in the binary is a valid target.
text
Yes
1 to 200 characters
Target package
Optional protobuf package prefix used when resolving target_type. If empty, the registry is scanned by short name and the lookup fails when more than one message matches across packages. Set this to disambiguate (e.g. dronesensor, clicksensor, ares).
text
No
at most 200 characters
Mappings
Field mappings from input to output. Applied in order — later mappings overwrite earlier ones for the same to path.
list of group of fields
No
Defaults
Default values applied after all mappings. Use these for fields the source does not provide (timestamps, UUIDs, sensor IDs, confidence-derived levels).