Polar Cloud
- Action Buttons
- Adding Alerts
- Adding Users
- Adding Users to Alerts
- Alert Action Triggers
- Alert Types
- Calculated Fields
- Can I change my login details ?
- Configure a 4–20mA sensor reading
- Configure a pulse water meter
- Create a conditional alert with several thresholds
- Device Dashboard
- Download Polar App on your phone
- Editing Users
- First Time Setup
- Groups
- Home Screen Navigation
- How do I get my login details?
- How to edit a users account details
- Poll Rates
- Read connection status and Site licence usage
- Remote Programming
- Removing A User
- Schedulers
- Sites
- Software License
- User Roles
- Viewing Active Alerts
- Viewing Historical Alerts
- What happens during an internet or power outage?
- What happens to schedules and alerts during an outage?
- Show all articles (16) Collapse Articles
Create and manage device alerts
Find the alert settings and history
- Open the relevant device dashboard and choose Alerts.
- Review the configured alerts in the left panel. The right panel shows triggered alert history with timestamps and resolved/active information.
- Use the history navigation to review earlier events. An integrated controller fault can include its mapped fault code.
- Choose Add Alert to create an alert, or open an existing alert to edit it.
- Select the alert type, give it a clear Alert Name and add an optional Alert Description.
Available types include Device in Fault, Gateway Offline, maintenance counters, minimum/maximum thresholds and the separate Condition alert.
Configure the alert currently labelled Gateway Offline
Select Gateway Offline for the intended device. This alert reads the database and triggers when no new data from that device has been inserted for the configured period. It can indicate a device communication failure while the gateway itself remains connected. In Settings, choose the missing-data duration before triggering and the restoration duration before resolving. In Advanced, set Check Every, Enabled and Notifications Enabled.
A 30-minute check interval is one example; five-minute checks are available. These are configurable examples, not a confirmed platform default. The check interval and offline/restore durations are separate settings; do not promise an immediate message simply because the connection has dropped.
Configure a minimum or maximum reading alert
- Choose the minimum/less-than or maximum/greater-than alert type.
- In Settings, select the correct Site, gateway, device and measurement tag.
- Choose Aggregation Type, set Threshold Value in the selected tag’s units, and configure the applicable Lookback Period.
- For the demonstrated All configuration, set Trigger Percentage and Restoral Percentage.
- Check the preview graph against the threshold and the intended behaviour.
- Configure the advanced options, save the alert and verify its saved settings.
| Aggregation Type | Meaning explained in the recording |
|---|---|
| Average | Compare the average of stored readings in the selected period against the threshold. |
| All | Evaluate the readings in the lookback period. With Trigger Percentage 100, all must meet the trigger condition; 50 means half. |
| Live Read | The alert engine requests a current device reading rather than evaluating the stored history dataset. It still cannot poll faster than once every five minutes. |
In the example, a generator fuel-level alert uses a 30% minimum threshold, a 30-minute lookback, 100% trigger percentage and 25% restoral percentage. The restoral percentage is the proportion of readings that have returned to the normal side of the threshold; it is not a new fuel-level threshold of 25%.
Be aware that a live analogue reading hovering around a threshold can repeatedly trigger and resolve, producing repeated messages. Choose the aggregation and timing to suit the application.
Enable the alert and its notifications separately
Enabled controls the alert itself. Notifications Enabled separately controls its notifications. Check both for an alert that must run and notify users. Customize Alert Text allows distinct trigger and resolve messages, such as “Generator communication lost” and “Generator communication restored.”
Check Every is the evaluation interval. For a tag-based alert, the conditional-alert recording confirms that the interval cannot be shorter than the tag’s polling interval. To allow five-minute checks on a tag currently polled every 15 minutes, first change that tag’s polling to five minutes on the device’s Live page, then edit the alert.
The demonstrated alert execution location is Cloud. Cloud measurement alerts need new device data and cloud connectivity. Glacier also supports locally enabled alerts: evaluation and event timestamps can be local, while delivery waits for cloud reconnection. To select it on a Glacier alert, open Advanced and change the execution dropdown from Cloud to Edge. Save the alert.
Choose which controller faults notify
A Device in Fault alert uses the controller’s integrated fault state and mapped fault codes. In its Settings, enable the relevant faults and disable notifications for faults that do not apply to the installation. This selection changes Polar’s alert handling; it does not remove or repair a fault in the controller. Review the history to identify the reported fault code.
Optional action on trigger or resolve
If an appropriate control button is already enabled/configured on a device, the alert’s Trigger section can perform an action when the alert triggers, and Resolve can perform another when it resolves. The target can be a different device or gateway. For example, a tank-level alert can act on a pump at another gateway.
See Create control buttons for the configuration walkthrough and automation recovery for missed-schedule and reconnect rules.
Live Read is not unlimited-speed polling
Five minutes is the fastest permitted Live Read alert polling interval. Users cannot configure faster polling. Live describes the reading source, not continuous or sub-five-minute monitoring.
When notifications are sent
Polar sends one notification when an alert triggers and one when it resolves. If a tank remains below its threshold for six hours, recipients receive the original trigger notification, with no recurring reminder merely because the alert remains active. Separate conditional thresholds can produce their own trigger/resolve notifications as described in the conditional-alert guide.
There is currently no user acknowledgement feature. A user cannot mark an alert as acknowledged to silence or resolve it. Resolution follows the configured recovery condition.
Maintenance alerts and multiple recipient groups
For maintenance-counter alerts, ask Polar support for the procedure supported by your device, including counter units, reset scope and interval behaviour. See alert types and their intended use.
The recipient guide covers users and channel choices in an existing notification group. For additional notification groups or routing requirements, contact Polar support for the current supported setup. Do not assume editing an existing group creates a separate group.
If you searched for an alarm, Polar’s alert rules are the starting point. Continue to missing-alert troubleshooting when a notification has not arrived.