High Threshold Condition

High Threshold Condition: Value-Based Workflow Triggers

The High Threshold Condition monitors data point values and triggers workflows when values exceed a specified threshold. This is essential for automated alerting, safety systems, and responsive automation based on real-time sensor data.

Info: This is a Trigger node type that can be used to trigger workflows based on data value conditions. When a monitored data point exceeds the threshold, this trigger executes all of its child executor nodes.

Overview

High Threshold triggers provide automated monitoring and response capabilities. By continuously watching data point values, they enable your system to react immediately when readings exceed safe or normal operating ranges.

Key Features

• Automatic Monitoring: Continuously evaluates data point values
• Configurable Threshold: Set the exact value that triggers the alarm
• Immediate Response: Triggers child executors instantly when exceeded
• Integration Ready: Works with any numeric data point
• Visual Feedback: Clear indication when threshold is exceeded
• Multiple Thresholds: Create multiple triggers for different levels

Threshold Monitoring Flow

graph TD
    A[Data Point Updates] --> B[Threshold Monitor Checks]
    B --> C{Value > Threshold?}
    C -->|No| D[Continue Monitoring]
    C -->|Yes| E[Set Trigger to EXECUTED]
    E --> F[Execute Child Executors]
    F --> G[Perform Actions]
    G --> H[Send Alerts/Take Actions]
    H --> D

How It Works

The High Threshold trigger operates through continuous monitoring:

1. Setup: Configure threshold value and link to a data point
2. Monitoring: System continuously evaluates the data point’s value
3. Comparison: Each update checks if current value > threshold
4. Trigger: When condition is met, trigger transitions to EXECUTED state
5. Execution: All child executor nodes are activated
6. Actions: Perform configured responses (alerts, logging, control actions)

Configuration

Field	Description	Required
threshold	Numeric value that triggers the alarm	Yes
dataPointId	ID of data point to monitor	Yes

Use Cases

• Temperature Alarms: Alert when temperature exceeds safe limits
• Pressure Monitoring: Trigger safety shutdown at high pressure
• Flow Rate Alerts: Detect excessive flow conditions
• Level Monitoring: Alert when tank levels get too high
• Power Consumption: Monitor for overcurrent conditions
• Speed Control: Detect over-speed conditions in motors
• Environmental Monitoring: Alert on high humidity, CO2, etc.

Example Workflows

High Temperature Safety Shutdown:

1. Data Point: Temperature sensor (updating continuously)
2. Trigger: High Threshold (> 80°C)
3. Executor: Logic Gate (safety check)
4. Executor: Pin Control (disable heater)
5. Executor: OutgoingWebHook (send alert notification)

Pressure Relief Activation:

1. Data Point: Pressure sensor
2. Trigger: High Threshold (> 100 PSI)
3. Executor: Pin Control (open relief valve)
4. Executor: Lambda (log event)

Overcurrent Protection:

1. Data Point: Current sensor
2. Trigger: High Threshold (> 10 A)
3. Executor: Logic Gate (confirm condition)
4. Executor: Pin Control (trip circuit breaker)
5. Executor: OutgoingWebHook (emergency notification)

High Water Level Alert:

1. Data Point: Water level sensor
2. Trigger: High Threshold (> 95% full)
3. Executor: Pin Control (close inlet valve)
4. Executor: OutgoingWebHook (SMS alert)

Combining with Other Features

Multi-Level Alarms: Create cascading alarms by using multiple threshold triggers:

• Low threshold: Warning notification
• Medium threshold: Email alert
• High threshold: Emergency shutdown

Logic-Based Responses: Combine with Logic Gates for complex conditions:

High Temperature AND High Pressure → Emergency Stop

Time-Delayed Actions: Use with SilentAlarm for delayed responses:

High Threshold → SilentAlarm (5 min) → Action

Integration Points

• Data Points: Monitor any numeric data point
• Executors: Trigger calculations, webhooks, or Lambda scripts
• Pins: Control hardware in response to threshold violations
• Logic Gates: Combine with other conditions for smart responses
• MQTT: Publish threshold events to message queues

Best Practices

• Set Appropriate Margins: Don’t set thresholds too close to normal operating values
• Hysteresis: Consider using both high and low thresholds to prevent oscillation
• Response Time: Ensure child executors can respond quickly enough
• Testing: Test threshold triggers during commissioning
• Logging: Always log threshold events for analysis
• Redundancy: Consider multiple sensors for critical safety applications

Comparison with Low Threshold

Feature	High Threshold	Low Threshold
Trigger Condition	Value > Threshold	Value < Threshold
Common Use	Over-limit detection	Under-limit detection
Example	Overheat alarm	Low battery warning

High Threshold Conditions are essential for building responsive, safe automation systems that react to changing conditions in real-time.