Alarms | Wildeye Support

What are Alarms?

The Wildeye Alarm system is a mechanism where emails and/or text messages can be sent when your data matches predefined thresholds. You can send to individual recipients, or to pre-configured groups of recipients.

Wildeye supports a range of Alarm types. The alarm types available for an individual input depend on the input type, and the inputs configuration. Our most common alarm type is the High/Low threshold alarm, perfect for frost alerts, tank level alerts, etc.

Alarms can be configured to trigger “immediately”, or with a delay/buffer to ensure the value read has crossed the threshold for a number of readings or a particular time period. When configuring alarms it’s important to consider the immediacy of the notification required.

Most of these features can only be accessed by Client Admin users. Your Wildeye devices may be managed by a third party as a service. Jump to Client User features here.

How they work behind the scenes

While some alarms can be evaluated on the logger itself and then trigger the logger to upload the latest readings to our servers to send the notifications, other inputs values are only calculated on the server. The alarm notifications for these alarms will only be sent after the logging interval of the logger, plus a period of server processing time. A common input type where this occurs is the Calculated Input, as these are all computed on our servers.

Server-controlled Alarm Example

Upload frequency: 1 day
Input logging frequency: 15 minutes
Calculated input: <RawInputReading> * 0.5
We now set up an alarm on the calculated input to trigger when it passes a threshold. The calculated input is computed on the server when the raw data readings of each input is uploaded. Once a day our server will calculate the calculated input on the uploaded readings for our input. After this calculation we test the alarm trigger against the data just calculated.
The greatest delay we can see before an alarm is triggered is 1 day, plus upload and processing time on the server.

Where to find Alarms

Input Settings

Alarm configuration for an input is accessed by clicking on the input’s alarm count link, on the Input Settings page.

The Input Alarm List shows the alarms associated with just this input. This is where you can create a new alarm for an input, enable or disable an alarm, access an alarm to edit the threshold value or the notification recipients, and access the history. Some of these features are only available for Admin logins.

Alarms list for the Office Temperate input.

Previously (before Oct 2025) you could access an Alarms tab when editing the configuration of an input. We have removed access from this screen as part of our future plan for updating the inputs page and configuration of inputs updates.

Graph View of Alarms

For administrators (and recipients of associated alarms) we display a blue bell icon on any graphs which include a series with alarms configured. Clicking on the bell icon in the top right corner of the graph will open the list of alarms. From here you can edit the alarm, or enable or disable the alarm(s).

**Office - Air Temperate** graph showing the bell icon for Alarms

Graph alarm page, showing the alarms linked to the series on the **Office - Air Temperature** graph

On a graph you can choose to show the alarm thresholds for an individual series. Edit the series by clicking on it in the legend, and then choose the option “Show Alarm Thresholds” to get the named horizontal threshold lines included on the graph.

Editing the Temperature data series with the Show Alarm Thresholds option checked.

Client View of Alarms

The client’s view of alarms allows you to see all the alarms configured across the client, by clicking on the Alarms tab. From this table, you can filter and search for known alarms, then edit or enable and disable the alarm. This is very useful when needing to disable a selection of alarms at the end of a harvest.

Client alarms showing alarms from Wildeye Auckland

Types of Alarms

High/Low - Alarm by a specific high or low input value. Eg:
- Irrigation events to detect burst pipes
- Frost alarms at a certain wind and temperature thresholds
Daily Total Volume - Total flow today greater than X
Minimum Night Flow - Minimum flow between time A and time B measures greater than X. A useful alarm to monitor for leaks from water consumption systems.
Weekly Minimum Night Flow - When the minimum night flow consistently measure above the threshold for over a week; useful if some nights are expected to have data coming through.
Yesterday's Total Volume - similar to Daily Total Volume but for the previous day; useful for loggers that only upload once a day to ensure the alarm measures the total data received from the day before.
Last X Days' Volume - similar to Total Volume but for a specified number of days.

Alarm Configuration

When you create a new alarm, you are presented with a popup window with 2 tabs: Conditions and Recipients.

Conditions

This tab defines the triggering conditions for an alarm, specifying when it should activate, how often it should repeat, and any additional automation to run. The tab is different for each alarm type.

High / Low

Name field
- Default: Will match the input name and type of alarm. e.g. Temperature High alarm.
- You may rename this alarm to a descriptive title (e.g., “Reactor Cooling High Temp” or “Freezer Low Temp Warning”).
- Helps distinguish multiple alarms within the same project.
High / Low toggle
- High – Alarm triggers when the input value rises above the defined threshold.
- Low – Alarm triggers when the input value falls below the defined threshold.
Threshold input
- Defines the numeric value at which the alarm will trigger.
- The unit of measure selected could force the alarm to convert the rate to a different time scale. i.e. Measured in Litres/Sec at the sensor, in the alarm choosing Litres/Hour will cause a rate conversion. This conversion can only happen on the server, and therefore this alarm will not be evaluated on the logger.
- Example: “Trigger when Temperature is above 35°C”.
And (extra condition)
- This option is only visible to clients with this feature enabled.
- Drop-down selection of an output valve or relay value and its current status, On/Off.
- Used to create conditional alarms based on the state of output. e.g. Alert when water flow is low but the valve is open.
Immediate / Wait
- Immediate – The alarm triggers the moment the threshold is crossed on one reading.
- Wait – The alarm triggers only if the condition is met continuously for a specified time window, as indicated by the number of readings at the input’s logging interval.
Reset Time / Value
- Time – Condition is based on duration (e.g., temperature above 35°C for 10 minutes).
  - Don’t repeat alarms for [dropdown]
    - Prevents recipients from being spammed with repeated alerts.
    - Options include time intervals (e.g., 1 hour, 6 hours, 1 day, custom).
    - Example: If set to “1 day,” once triggered, the alarm will not send again until 24 hours have passed (even if the conditions are still met).
- Value – Condition is based on the reading crossing a threshold.
Dial at reset
- If enabled, the logger will upload its data when the alarm reset period/value is complete.
- Helpful in managing battery consumption on loggers.
Automation dropdown
- Allows linking this alarm to make changes to control systems or the logger upload interval.
- Default: None.
- Example: An alarm could trigger an automation that shuts down equipment, starts backup pumps, or closes a valve.
- Example: An alarm could adjust the upload frequency of the logger to get data onto the server faster.

Daily Total Volume

This alarm works best when the Wildeye uploads data multiple times per day. If data is only uploaded once daily, use the Yesterday’s Total Volume alarm instead.

Name field
- Default: Will match the input name and type of alarm. e.g. Water flow Today’s total alarm.
- You may rename this alarm to a descriptive title (e.g., “Excessive water consumption”).
- Helps distinguish multiple alarms within the same project.
Trigger if today’s total volume exceeds:
- Input a threshold value for the total of the unit of measure.
- e.g. 3,000 Litres
Automation dropdown
- Allows linking this alarm to make changes to control systems or the logger upload interval.
- Default: None.
- Example: An alarm could trigger an automation that shuts down equipment, starts backup pumps, or closes a valve.
- Example: An alarm could adjust the upload frequency of the logger to get data onto the server faster.

Minimum Night Flow

Name field
- Default: Will match the input name and type of alarm. e.g. Water flow minim night flow alarm.
- You may rename this alarm to a descriptive title (e.g., “Excessive water consumption”).
- Helps distinguish multiple alarms within the same project.
Check for flow between the hours of:
- Enter the start hour and end hour of the period that is considered night for this site.
- e.g. 22:00 to 06:00
When the minimum night flow measures above:
- Enter the threshold value for the minimum flow should go below during the nighttime period.
- e.g. 10 Litres
Automation dropdown
- Allows linking this alarm to make changes to control systems or the logger upload interval.
- Default: None.
- Example: An alarm could trigger an automation that shuts down equipment, starts backup pumps, or closes a valve.
- Example: An alarm could adjust the upload frequency of the logger to get data onto the server faster.

Weekly Minimum Night Flow

Similar to the Minimum Night Flow Alarm but instead it will only trigger the alarm if the minimum night flow is consistently above the threshold for over a week.

Name field
- Default: Will match the input name and type of alarm. e.g. Water flow Weekly minimum night flow alarm.
- You may rename this alarm to a descriptive title (e.g., “Excessive water consumption”).
- Helps distinguish multiple alarms within the same project.
Check for flow between the hours of:
- Enter the start hour and end hour of the period that is considered night for this site.
- e.g. 22:00 to 06:00
When the minimum night flow consistently measures above the threshold for over a week
- Enter the threshold value for the minimum flow should go below during a week in the nighttime period.
- e.g. 10 Litres
Automation dropdown
- Allows linking this alarm to make changes to control systems or the logger upload interval.
- Default: None.
- Example: An alarm could trigger an automation that shuts down equipment, starts backup pumps, or closes a valve.
- Example: An alarm could adjust the upload frequency of the logger to get data onto the server faster.

Yesterday's Total Volume

This alarm will trigger when the total volume from yesterday’s readings is above a threshold.

Name field
- Default: Will match the input name and type of alarm. e.g. Water flow Yesterday total alarm.
- You may rename this alarm to a descriptive title (e.g., “Excessive water consumption”).
- Helps distinguish multiple alarms within the same project.
Threshold
- Enter the threshold value for yesterday’s total volume.
- e.g. 2,500 Litres
Only send this alarm between the hours of:
- The time range for when this alarm will be evaluated on the server.
- e.g. 09:00 to 10:00
Automation dropdown
- Allows linking this alarm to make changes to control systems or the logger upload interval.
- Default: None.
- Example: An alarm could trigger an automation that shuts down equipment, starts backup pumps, or closes a valve.
- Example: An alarm could adjust the upload frequency of the logger to get data onto the server faster.

Last X Days Volume

Name field
- Default: Will match the input name and type of alarm. e.g. Water flow Last X days total.
- You may rename this alarm to a descriptive title (e.g., “Excessive water consumption”).
- Helps distinguish multiple alarms within the same project.
Threshold and days
- Enter the threshold value for the number of previous days.
- e.g. 4,500 Litres for the previous 5 days.
Only send this alarm between the hours of:
- The time range for when this alarm will be evaluated on the server.
- e.g. 09:00 to 10:00
Automation dropdown
- Allows linking this alarm to make changes to control systems or the logger upload interval.
- Default: None.
- Example: An alarm could trigger an automation that shuts down equipment, starts backup pumps, or closes a valve.
- Example: An alarm could adjust the upload frequency of the logger to get data onto the server faster.

Recipients

On this tab you define who will receive notifications when the alarm is triggered, and the message they will receive.

Recipient Type

Dropdown: Recipient
- Custom – Enter specific recipients manually.
- Recipient Lists – Select a predefined group of recipients created for this client. These lists can be reused across multiple alarms for consistency. Read more about Recipient Lists.

It is not possible to use a recipient list and add custom recipients to an alarm.

Add Recipients

You can notify recipients by email and/or SMS. Multiple addresses or numbers may be added.

Add by email
- Enter one or more email addresses.
- You can also search and select registered users from the user directory.
- This field also accepts a pasted list of email addresses.
Add by phone
- Select the country code from the dropdown.
- Enter the phone number in the text box.
- Click Add phone to include the number in the Recipients list.
Recipients list
- Displays all recipients currently added.
- Each entry shows the selected notification methods (Email/SMS).
- For each user, you may choose whether they receive an email, SMS, or both. Click on the icon representing the communication method to toggle it on/off.
Test Alarm Delivery
- Sends a test notification to all listed recipients.
Copy To Clipboard
- Copies the recipient list so it can be pasted into another alarm configuration.

Test Alarm Delivery: This option is disabled until changes are saved with Create/Update.

Alarm Message

Type the message here which you want the recipients to receive. You can customise the wording of the notification. Dynamic tags insert alarm-specific details at runtime.

Default Example:

#sitename #inputname is above #alarmsetvalue #unit

Would produce:

West dam water level is above 2.75 m

Available Tags

Tag	Description
`#sitename`	Name of the site
`#inputname`	Name of the input (sensor/log)
`#projectref`	Project reference ID
`#unit`	Unit of measurement (e.g., °C, m)
`#scadatagid`	SCADA Tag ID
`#alarmdate`	When the alarm occurred
`#alarmvalue`	The actual triggering value
`#alarmsetvalue`	The configured threshold value
`#alarmsentdate`	When the alarm was sent
`#alarmname`	Type of alarm (e.g., “High Temp”)

Users may mix free text and tags.
Example:

Alert: #inputname at #sitename exceeded #alarmsetvalue #unit at #alarmdate

✅ Best Practices

Use Recipient Lists for common groups (e.g., “Operations Team”) to ensure consistent updates across alarms.
Always test alarm delivery after saving, to ensure recipients receive alerts as expected.
Keep alarm messages short but informative — include at least the site, input name, value, and unit.
Always configure a repeat delay to avoid alarm fatigue.