--- title: "Alarm Actions" canonical: "https://farmconnect.docs.rubiconwater.com/space/FCD/2022113344/Alarm%20Actions" format: markdown --- > Macro (toc) # Alarm Actions List > ℹ️ **Note** > ℹ️ > ℹ️ The alarm actions list only shows alarm actions that you have configured yourself. There may also be default alarm actions. You can set up alarm actions to notify you when device datapoints reach a certain value and when there are event-related errors with event-based irrigation programs. When a device has an alarmed status it will appear on the [https://rubiconwater.atlassian.net/wiki/spaces/FCD/pages/2022342699](https://rubiconwater.atlassian.net/wiki/spaces/FCD/pages/2022342699) list and it may trigger a notification to be sent by email or SMS. Use the **Alarm Actions** screen to view and manage the alarms you have configured for your devices and to create new alarm configurations. # Default Alarm Actions The Alarm Actions list only shows alarm actions that you have configured yourself. However, there are some critical tags that are pre-configured with alarms and alarm actions so you will also see these alarms on your [https://rubiconwater.atlassian.net/wiki/spaces/FCD/pages/2022342699](https://rubiconwater.atlassian.net/wiki/spaces/FCD/pages/2022342699)list and you will receive notifications if any default alarm actions are configured. These tags are alarmed by default (but note that these defaults may be modified for you as appropriate when your farm is set up): | **Tag Description** | ** Devices** | **SMS Notification?** | **Email Notification?** | | --- | --- | --- | --- | | Battery voltage | Advanced Stop Gate, BladeValve, RiserDrive, Smart Stop Gate | | Y | | Comms Fail or Device Comms Fail | Advanced Stop Gate, BladeValve, RiserDrive, Smart Stop Gate, Standard Stop Gate, Variable Speed Pump, Standard SmartMeter, Standard FloodTech Sensor, Standard Relay Controller. | | Y | | Comms Fail or Device Comms Fail
(with no default alarm action) | Rubicon Water Level Sensor, Senix Water Level Sensor, Water Level Sensor | | | | Current Flow | Standard Smart Meter | | | | Device Measurement Error | Infrared Sensor | | Y | | Failed to reach setpoint | Advanced Stop Gate, BladeValve, RiserDrive, Smart Stop Gate, Standard Stop Gate, Variable Speed Pump | Y | Y | | Gate open mm | Standard Smart Meter | | | | Gate overtorque | Advanced Stop Gate, BladeValve, RiserDrive, Smart Stop Gate, Standard Stop Gate | Y | Y | | IO board open batt voltage | iBee Coordinator | | Y | | No movement alarm | Advanced Stop Gate, BladeValve, RiserDrive, Smart Stop Gate | Y | Y | | Plant Temperature High | Infrared Sensor | | Y | | Plant Temperature Low | Infrared Sensor | | Y | | Power module hardware fault | FerIT Solar Node | | | | Sensor Temperature High | Infrared Sensor | | Y | | Sensor Temperature Low | Infrared Sensor | | Y | | Summated Soil Moisture | Rubicon Water Level Sensor, Sentex Probe | | | | Summated Soil Moisture (VSM) | Sentex Probe | | | | Water leak alarm | Advanced Stop Gate, BladeValve, RiserDrive, Smart Stop Gate | Y | Y | # Creating and Configuring a New Alarm Action There are two steps to creating a new alarm action: - [Create an alarm action](https://rubiconwater.atlassian.net/wiki/spaces/FCD/pages/2022113344/Alarm+Actions#Create-an-Alarm) and specify the devices and datapoints to which it will apply and the type of notification sent for the alarm. - [Configure the tag settings](https://rubiconwater.atlassian.net/wiki/spaces/FCD/pages/2022113344/Alarm+Actions#Configure-Tag-Settings) including the exact tag values that will trigger the alarm. If your alarm is for a group of devices you can also enable or disable alarms for specific devices. ## Create an Alarm Action **Step 1** Click the :createAlarmAction: **Add Alarm** button at the top-right of the alarm actions list to start creating an alarm. **Step 2 ** Enter the following details on the **Create Alarm** screen: | **Field** | **Description** | | --- | --- | | Device Type | Pick the device type for this alarm from the drop-down list or choose *All device types* to create an alarm for all device types.
**Note:** This will create an alarm action for all devices that have the selected datapoint (tag). | | Device | Pick the specific device for which you want to create an alarm or choose *All devices* to create an alarm for all the devices of the Device Type you have chosen.
**Tip:** If you pick *All devices* you can still configure or enable/disable the settings for individual devices by [Configuring Tag Settings](https://rubiconwater.atlassian.net/wiki/spaces/FCD/pages/2022113344/Alarm+Actions#Configuring-Tag-Settings). | | Datapoint | Pick the datapoint (that is, the tag or property) of the device for which you want to create the alarm.
**Note:** If you have picked a Device Type this list will only show datapoints for that device type. Otherwise, it will show all possible datapoints prefixed by the device type they apply to. | | Alarm State | Specify the alarm states for which you want to trigger an alarm - or you can choose all to trigger an alarm on any state. The alarm states available depend on whether the datapoint you chose is an analogue or a binary value. For example, binary datapoints can only be ON or OFF, but analogue datapoints can take a range of high and low values. See [Alarm State Triggers](https://rubiconwater.atlassian.net/wiki/spaces/FCD/pages/2022113344/Alarm+Actions#Alarm-State-Triggers) for a list of the possible options.
**Note:** You will specify the datapoint values that will trigger an alarm by [Configuring Tag Settings](https://rubiconwater.atlassian.net/wiki/spaces/FCD/pages/2022113344/Alarm+Actions#Configuring-Tag-Settings) after the alarm is created. | | User | This will be populated for you. | | Email | This is your email address by default but you can set a different alarm notification email address if you choose. Click the **Edit Details** button if you need to set or update the contact details. | | SMS | This is your phone number by default but you can set a different alarm notification phone number if you choose. Click the **Edit Details** button if you need to set or update the contact details. | > ℹ️ **Note** > ℹ️ > ℹ️ You can also change the default alarm notification contact details in the [https://rubiconwater.atlassian.net/wiki/spaces/FCD/pages/2242379780](https://rubiconwater.atlassian.net/wiki/spaces/FCD/pages/2242379780). **Step 3** Click **Submit** to save your alarm details. > ℹ️ **Note** > ℹ️ > ℹ️ You can edit these settings at any time by clicking the :AlarmSettingsIcon: **Alarm Settings** option for this alarm in the Alarm Actions list. ### Alarm State Triggers Alarm state triggers are thresholds that you can set on tag values that will trigger alarms. These are the types of triggers available for analog and binary datapoints: | **Type** | **Triggers on:** | **Analog/Binary** | **Explanation** | | --- | --- | --- | --- | | HH | High-high alarm limit | Analogue only | Tag value is greater than the HH alarm limit. | | H | High alarm limit | Analogue only | Tag value is greater than the H alarm limit. | | L | Low alarm limit | Analogue only | Tag value is less than the L alarm limit. | | LL | Low-low alarm limit | Analogue only | Tag is less than the LL alarm limit. | | SET | The tag is not in its normal state. | Both | Any alarm state is set. | | N | Alarm cleared and in a normal state | Both | A previous alarm state has been cleared. | | ACK | Alarm acknowledged | Both | An alarm has been acknowledged. | | ANY | Any of the above | Both | Any of the above. | ## Configure Tag Settings Once you have created your alarm you can edit the tag settings for the alarm. > ℹ️ **Note** > ℹ️ > ℹ️ You can also manage the tag alarm settings for individual devices by using the :editTagConfig: **Edit Tag Configuration** option in the device popup in the [https://rubiconwater.atlassian.net/wiki/spaces/FCD/pages/2022342671](https://rubiconwater.atlassian.net/wiki/spaces/FCD/pages/2022342671) module. **Step 1** On the **Alarm Actions** list, choose the alarm that you want to configure and click the :tagSettingsIcon: **Tag Settings** icon for that Alarm. The **Tag Configuration** screen will pop up. **Step 2** Make any configuration changes that you need. Your changes will be saved as you make them. For example: - Set an alarm limit value for the whole column by entering it in the column header and clicking the :tick: **Update All Tags** icon or set individual values by changing the appropriate cell. - Enable or disable the alarm for all devices or for specific devices. > ℹ️ **Note** > ℹ️ > ℹ️ Alarms will be enabled by default when you create them, you don’t need to explicitly enable all the alarms you create. You can also use the :TrendIcon: **Trend** tool to view a chart of the alarm history for each tag. > ℹ️ **Example** > ℹ️ > ℹ️ This can be useful when you are deciding where to set the alarm limits. # Creating Alarm Actions for Program Events You can be notified of event timeouts and event error timeouts during an event-based program by creating [https://rubiconwater.atlassian.net/wiki/spaces/FCD/pages/2022113344](https://rubiconwater.atlassian.net/wiki/spaces/FCD/pages/2022113344) for the program. These alarms will trigger if the action for an event times out or if the event error timeout included *Abort Group*. To do this, [create an alarm action](https://rubiconwater.atlassian.net/wiki/spaces/FCD/pages/2022113344/Alarm+Actions#Creating-and-Configuring-a-New-Alarm) in the usual way but choose the following settings: | **Field** | **Setting** | | --- | --- | | Device Type | eventBasedProgramExecution | | Device | Select the (synchronised) program for which the alarm will trigger. | | Datapoint | Event Control Alarm | | Alarm State | SET | > ℹ️ **Note** > ℹ️ > ℹ️ Any active alarms are cleared when a new program is synchronized.