Automation

Overview

Most fleet issues - overheating miners, hashrate drops, peak-hour power costs - follow predictable patterns. Automation Rules let you define responses to those patterns once and have Commander handle them continuously, whether you're at your desk or not. Instead of watching dashboards and reacting manually, you set the conditions and actions, and Commander evaluates your fleet on a recurring cycle and executes on your behalf.

There are two types of Automation Rules:

• Trigger Rules continuously evaluate your fleet against conditions you define and fire when those conditions are met. Common use cases include automatically rebooting miners that overheat or sending alerts when hashrate drops below a threshold.
• Schedule Rules execute actions at specific times - either as a one-time future event or on a recurring basis (daily, weekly, or monthly). Common use cases include reducing power during peak pricing hours every evening or running a weekly reboot cycle.

Rules List

The Automation page displays all configured rules in a table with the following columns:

Each row also includes controls to delete, edit, or expand the rule for a quick summary.

Upcoming Schedule

The Automation page includes an Upcoming Schedule panel that displays a calendar view of scheduled rule executions for the current and next day. This gives you a quick overview of what automated actions are coming up across your fleet.

Creating a Rule

Click the + Rule button to open the rule creation flow. At the top of the creation page, select the rule type:

• Trigger - for condition-based rules that evaluate continuously.
• Schedule - for time-based rules that run at specific times.

Both rule types share the same three-step creation flow, but Step 2 differs depending on the type selected.

Step 1: Choose a Filter

Define which miners the rule should apply to. You can use the same filters available in the Miners table to scope the rule to a specific subset of miners - for example, only LuxOS miners, only miners at a specific Site, or only a specific model. You can also check Apply to All Miners to target your entire fleet.

Step 2 (Trigger Rules): Set Trigger Condition

Configure when the Trigger Rule should fire.

Evaluation Frequency

Select how often Commander should check the trigger's conditions. Options include interval-based frequencies such as Every 5 minutes or Every 15 minutes.

Stop Condition (Optional)

Enable the Stop Condition to prevent a trigger from firing repeatedly on the same miners. When enabled, you can configure:

• Max Attempts: The maximum number of times the trigger will execute its actions on a given miner within the Attempts Interval. Once this limit is reached, the trigger stops firing for that miner until the interval resets - regardless of whether the condition clears and returns in the meantime.
• Attempts Interval: The rolling time window for counting attempts (e.g., Every 24 hours). When the interval resets, the attempt counter for each miner resets to zero and the trigger can fire again.

This is useful to avoid situations where a trigger repeatedly reboots a miner that has a persistent hardware issue.

Example: You set Max Attempts to 3 with an Attempts Interval of 24 hours. A miner exceeds your temperature threshold at 10:00 AM and the trigger reboots it. The miner overheats again at 10:30 AM (attempt 2) and again at 11:00 AM (attempt 3). The trigger has now reached its limit for this miner. Even if the miner continues to overheat throughout the day, the trigger will not fire again until 10:00 AM the next day, when the 24-hour window resets.

Conditions

Define the metric conditions that must be met for the trigger to fire. Conditions use the same logic as the Advanced Filter.

You can add multiple conditions within a group and create multiple condition groups. For example: "Max Temperature (°C) Greater Than 70 AND Hashing Status Equals Hashing" ensures the trigger only fires for miners that are both overheating and actively hashing.

You can also make use of events for triggering Automation Rules, specially relevant for machines running LuxOS due to the rich variety of Events available.

Step 2 (Schedule Rules): Set Schedule

Configure when the Schedule Rule should run.

Start Date & Time

Select the date and time for the rule's first execution. The time is displayed in your local timezone (e.g., GMT-3).

Repeat (Optional)

Enable Repeat to make the schedule recurring. When enabled, choose a frequency:

• Daily - runs every day at the specified time.
• Weekly - runs once per week on the specified day and time.
• Monthly - runs once per month on the specified date and time.

If Repeat is not enabled, the rule will execute only once at the specified date and time.

Skip Event Condition (Optional)

By default, Schedule Rules fire unconditionally at the specified time - no condition is required. However, you can optionally add a condition by unchecking Skip Event Condition (Run on schedule only). When a condition is added, the rule will only execute its actions if the condition is met at the scheduled time. This is useful when you want time-based evaluation without unconditional execution - for example, only rebooting miners on a daily schedule if they are reporting errors.

Step 3: Assign Actions

Define what actions the rule should execute when it fires. The available actions are the same as those in the Bulk Actions workflow, plus an additional action exclusive to Automation Rules: sending an email alert to one or multiple recipients.

You can assign multiple actions to a single rule, and they will execute in sequence.

Example Rules

Miner Overheat Alert (Trigger Rule)

A trigger that automatically responds to miners exceeding a safe temperature threshold:

• Type: Trigger
• Filter: All miners at Site "Texas"
• Frequency: Every 15 min
• Condition: Max Temperature (°C) Greater Than 70
• Stop Condition: Max 3 attempts every 24 hours
• Action: Reboot, Send Alert

Scheduled Power Curtailment (Schedule Rule)

A schedule that reduces power consumption during peak electricity pricing hours every day:

• Type: Schedule
• Filter: All miners at Site "Texas"
• Schedule: Daily at 14:00 UTC
• Condition: None (runs unconditionally on schedule)
• Action: Change Power Settings

Weekly Maintenance Reboot (Schedule Rule)

A recurring schedule that reboots all miners once per week for preventive maintenance:

• Type: Schedule
• Filter: All miners at Site "Texas"
• Schedule: Weekly on Monday at 03:00 UTC
• Condition: None
• Action: Reboot

Error Event Alert (Trigger Rule)

A trigger that responds to miners reporting specific error conditions:

• Type: Trigger
• Filter: All LuxOS miners
• Frequency: Every 15 min
• Condition: Any event of type Error
• Action: Reboot, Send Alert

Managing Rules

• Enable/Disable: Use the status toggle on each row to quickly enable or disable a rule without deleting it.
• Edit: Click the edit icon to modify any aspect of an existing rule.
• Delete: Click the delete icon to permanently remove a rule.
• Monitor: Use the "Times Used" and "Last Used" columns to understand how often your rules are firing. Cross-reference with the Actions Log for detailed execution history.