Set up reading alerts
Create alert rules that notify you when a sensor reading crosses a threshold, including multi-sensor rules for end of run.
An alert rule watches your readings and notifies you when one crosses a line you set — a fermenter overheating, a stalled fermentation, a still coming up to temperature. You choose what to watch, the condition that trips it, and how you want to hear about it.
Alert rules live under Sensor alerts in the left-hand navigation, in the Sensors group.
View your alert rules
- In the navigation, choose Sensor alerts. The list shows each rule with its Name, its Subject (what it watches), its Condition, and a Status badge.
- The Status badge reads Enabled, Disabled, or Firing (the rule's condition is met right now).
- Choose a rule's row or its Edit button to open it; choose Delete to remove it.
A workspace with no rules shows No alert rules yet with a New alert rule button.
Create an alert rule
- From the Sensor alerts list, choose New alert rule.
- In the Rule card, enter a Name — for example Fermenter overheating — and leave Enabled on (or switch it off to save the rule without it firing).
- In the What to watch card, choose a Subject:
- A specific sensor, A vessel, A piece of equipment, A cooperage vessel, or A location — then pick the specific thing from the searchable list that appears.
- A stage type (any batch) — then choose the stage type it applies to.
- The whole workspace — no specific subject; the rule applies everywhere.
- In the Condition card:
- Metric — name the reading to watch (for example temperature), or leave it blank to watch any metric.
- When the value is — choose Above, Below, Equal to, Outside a range, or Inside a range. The range options ask for a Lower bound and an Upper bound; the others ask for a single Threshold.
- Sustained for (seconds) — how long the condition must hold before the rule fires. Set it to 0 to fire immediately.
- In the Notify via card, tick at least one channel. Email is always available on every plan; Webhook, Push notification, and Custom routing require a plan that includes them (a channel your plan doesn't grant is shown disabled with an upgrade hint).
- Choose Create rule.
Create a multi-sensor rule (end of run)
A multi-sensor rule fires on a combination of per-sensor conditions — the classic distilling example is kettle ≥ 200 °F AND column ≥ 185 °F to flag the end of a run.
Plan: multi-sensor (compound) rules are available on higher plans. If your plan doesn't include them, the Rule type control below is shown disabled with an upgrade hint (the same way a notification channel your plan doesn't grant is), and every rule is a single-sensor rule until you upgrade.
- From the Sensor alerts list, choose New alert rule and enter a Name.
- In the Rule card, set Rule type to Multiple sensors (AND/OR).
- In the Conditions card, choose how the rule fires under Fire when:
- ALL of — every condition must hold at once (the kettle AND column case).
- ANY of — any single condition firing trips the rule.
- Fill in each condition row: pick the Condition N sensor, name its Metric, choose When the value is and the Threshold (or bounds). Choose Add condition for more — a multi-sensor rule needs at least two.
- Choose the notification channels in Notify via as above, then choose Create rule.
A rule's type is fixed once it's created — a single-sensor rule can't later become a multi-sensor one, or vice versa.
Edit or delete a rule
- From the Sensor alerts list, choose a rule (or its Edit button).
- Change any field. On an existing rule, re-confirm the condition thresholds and notification channels — they're re-applied when you save.
- Choose Save changes.
To remove a rule, choose Delete on its row and confirm — the rule stops firing notifications and can't be recovered.