Event-based Automation

How to Create a Conditional Rule

1. Click Create rule, set Name and Scope — just like for a scheduled rule
2. Select trigger type Condition
3. Set the condition:
   • Metric: Miner Status, Chip Temperature, Hashrate Efficiency, Fan Duty
   • Operator: for numerical metrics — >, <, ≥, ≤; for Miner Status — only = and ≠
   • Value: numerical (with metric unit) or device status (Mining, Stopped, Error, Idle) — depending on the metric
4. Set Condition holds for — how long the condition must continuously be met before the action triggers (1–30 minutes, default 3 minutes)
5. Set Cooldown between triggers — the minimum pause before re-triggering on the same device (5 minutes – 24 hours, default 30 minutes)
6. Select an action — the same as for Schedule rules, plus Boards config (available only for Condition rules)
7. Save the rule

Metrics

The condition for Chip Temperature, Hashrate Efficiency, and Fan Duty is evaluated only on devices with Connectivity status = Online. An Offline device is unavailable for any rule action.

Cooldown and Condition Hold — Independent per Device

The condition is evaluated for each device within the scope independently. The action is applied only to those devices where the condition continuously held for the specified duration. Cooldown after triggering is also counted separately for each device — other devices within the scope may trigger earlier or later.

Loss of connection with a device during the condition hold resets the duration count for that device.

Rule Card

Instead of Next run / Last run, the Condition rule card shows the cooldown status (Ready or remaining time) and Last triggered. The Run Now option is absent from the card menu — a conditional rule cannot be triggered manually.

Boards config for Conditional Rules

The Boards config action is available only for Condition rules — applying board configuration reboots the device, and a disabled board does not automatically turn on. Therefore, this operation makes no sense and carries risk when scheduled. The configuration form is identical to the group operation Boards config.

For rules with Boards config, it is recommended to set a higher than usual cooldown — applying it entails a device reboot.

Notes

A trigger contains a single condition. Combining multiple conditions with AND/OR logic is being considered for future versions based on operator feedback.