Rule Engines Overview

Available pages

• Rule Engines — /rule-engines
• Editor — /rule-engines/new or /rule-engines/:id

Verified user flows

• Create / edit / delete a rule engine
• Add nodes from the palette; connect with relation handles
• Apply job templates (forward, alarm, notify, Slack/Teams, inactivity, RPC, blank)
• Dry-run preview with sample JSON + path highlight on the canvas
• Start / pause; live debug traces + metrics when active
• Bind a Started engine on a device profile (Automations)
• Optional tenant default rule engine when a profile has none
• Action nodes: set attributes, send command, integration downlink, notify, webhook, act on a related device
• Compare a reading with the previous one, measure the change, average a window, notice a key gone quiet, and test a geofence
• Restore an earlier saved graph

Key concepts

• Graph automation — not a linear pipeline editor
• Primary ingest path: rule engine → persist / realtime / profile Alarm Rules
• Legacy data/attribute pipelines redirect to Rule Engines
• Fail-open on unexpected errors (ingest continues unless a drop node runs)
• Preview is dry-run (no alarms / attributes / commands / downlinks written)
• Webhooks are async by default (off the ingest critical path)

Related

• Rule Engines (full guide)
• Alarm notification settings — Telegram ops group for alarms
• Scheduler — timed control jobs
• Integrations — ChirpStack / TTN / MQTT bridge