How to Manage Gateway Alarms
You can create alarms for gateways if they are disconnected from permanent power, if the battery is low (for applicable models), or if they miss a report, which results in an incident being created in SmartSense. Use these instructions to set up alarms and user notifications.
Note: If your account already has Missed Report and/or Low Battery asset alarms set up at the account (or above site level), without utilizing tags, any assigned gateways will automatically inherit the alarm without the need to create additional gateway specific alarms.
- To begin, hover over the ADMIN tab, select ORGANIZATION MANAGEMENT, then select the GATEWAY ALARMS tab.
- From here you can view and edit any existing alarms set up within your selected site. You can also create new gateway alarms by selecting + GATEWAY ALARMS.
Note: Gateways must be assigned in your account hierarchy to add alarms. If you do not see any gateways under the GATEWAY ALARMS tab check to make sure that they have been assigned to a LOCATION or DEPARTMENT.
- You will now be on the alarm configuration page. Under the APPLY ALARM TO field, select the location within the account hierarchy where the alarm should be applied.
- The GATEWAY field is optional. If no selection is made the alarm will be applied to all gateways in the selected location.
-
The fields under ALARM SETTINGS are all required fields. Choose a unique ALARM NAME and then select one of the following for the ALARM TYPE:
- External Power Loss: your gateway loses permanent power
- Low Battery: your gateway reaches a low battery level (for applicable models)
- Missed Report: your gateway missed a reporting interval to the SmartSense Cloud
-
Set a THRESHOLD if you selected MISSED REPORT in the previous field (this number will determine how many missed reports must transpire before an incident is created in SmartSense). Select the appropriate SEVERITY label.
- The next section you will need to complete is NOTIFICATION SETTINGS. Notification settings determine how frequently incident notifications should be sent and who should receive them after an incident is created.
In the NOTIFICATION FREQUENCY field, select from the dropdown menu. Notifications will only be sent after exceeding the alarm type threshold and the alarm delay duration.
For example, if you set an alarm delay of 3 consecutive readings, notifications will only be sent if the alarm condition is true for more than 3 gateway reports. Reading/Reporting time intervals vary between gateway models but they are approximately every 15 minutes.
-
In the ALARM DELAY field, enter a digit for the number of consecutive readings that will occur.
-
Under RECIPIENT ROLE, select an existing role from the dropdown menu (new recipient roles can be created under the ADMIN tab).
-
Under DELAY INTERVAL, enter a number. This feature allows you to have an escalation of your notifications by setting a longer delay for more senior team members.
-
Under CONTACT METHOD, choose one of the options from the dropdown menu.
-
SEND NOTIFICATION allows you to set the parameters for when notifications are allowed to be sent.
The SELECT DAYS option allows you to set the days of the week and the time of day that the recipient should receive notifications.
By default, an incident generated by an alarm will remain open and continue to produce notifications until closed by a user. ADDITIONAL SETTINGS allow you to customize the actions that occur once an incident is acknowledged.
- STOP NOTIFICATIONS AFTER INCIDENTS HAVE BEEN ACKNOWLEDGED allow notifications to stop as soon as a user acknowledges the alarm in the system.
- AUTOMATICALLY CLOSE INCIDENTS AFTER RESOLVING closes an incident after a user acknowledges the incident in the system.
Don't forget to select SAVE or SAVE + CREATE ANOTHER to finalize your new gateway alarm.