Skip to content

Mastering Automation with JEDI's Rules and Actions

JEDI's powerful rules engine enables you to define sophisticated logic that automatically monitors your real-time data and triggers the appropriate actions. Design your rules using the intuitive drag-and-drop interface for streamlined setup.

Getting Started

  1. Rules Dashboard: Access the "Rules" section from JEDI's navigation panel. Here you'll see a list of existing rules, each with toggle controls to enable/disable, edit, or delete.
  2. ADD RULE Button: Click this to start configuring a new rule.
Rules Management
Rules Management

Rule Configuration

Name and Type

Rules Types
Rules Types

Rule Name: A name for easy identification.

Rule Type: Choose from the following core types:

  • Condition: Triggers actions when a data expression evaluates as true.
  • Schedule: Triggers actions at set intervals or specific times.
  • Schedule with Condition: Combines scheduling with a conditional check for refined control.

Trigger Settings (Based on Rule Type)

Condition

  • Expression Builder: Drag-and-drop to construct your rule logic.
  • Trigger if condition true for...: Ensures the condition persists for the specified duration (seconds/minutes) before actions are triggered.
  • Once Per Interval: (Optional) Triggers actions only once, even if the condition remains true within the interval.
  • Time Window Validation: (Optional) Restricts rule execution to a specified start and end time for quiet periods.
Conditions Settings
Condition Settings

Schedule

  • EVERY: Defines actions based on a recurring interval (seconds, minutes, hours, days).
  • DAILY: Triggers actions each day at a specific 24-hour time.
Schedule Settings
Schedule Settings

Schedule with Condition

  • Combines the settings from Schedule with a conditional expression for finer control.
Schedule With Condition Settings
Schedule With Condition Settings

Actions

Use the "+" button to incorporate one or more actions to execute when a rule fires.

Supported Actions

Notification Action

LabJack Client Action

LabJack Client Action

Modbus Client Action

Send To Telegram Action

Custom Plugin Action

Count Nodes Action

Count Events Action

Supported Actions
Supported Actions

Tip

Testing: Thoroughly test your actions after configuration to ensure they trigger as intended and deliver the correct information.
Clarity: Choose descriptive metric names and clear messaging to make it easy to understand what the actions report when they are triggered.

Real-World Examples

  • Temperature Thresholds

    "If temperature exceeds 30°C for 5 minutes, send an email alert and trigger a custom script to activate a fan."

  • Offline Device Detection

    "If device hasn't reported data in 1 hour, send an SMS notification."

  • Scheduled Reports

    "Every Monday at 8 AM, generate a CSV report of the previous week's performance data and email it to stakeholders."

  • Motion Detection

    "If motion is detected in a specific area between 9 PM and 6 AM, trigger a notification to the security team and start recording video footage."

Need help? Contact our support team support@machinechat.io