About Device Health Alert Rules – Knowledge Base

Device Health Alert Rules tell your team when Kontakt.io devices need attention. An Alert Rule is what turns a Portal Light going offline, or a device's battery level dropping below a level you set, into an alert that notifies the right people.

When an Alert Rule is configured and enabled, Device Health triggers the alert, sends notifications by email, text message, or to a third-party system through a Webhook, and lists the alert in the Alerts list. If no enabled rule covers a device and its location, or the rule that covers it is disabled, no alert is triggered and no one is notified. That's why careful setup and review of Alert Rules are essential.

Device Health offers two alert types: Portal Light Offline and Battery Level.

Alerts from either type can also escalate, notifying an additional Group if the alert still needs attention after a set amount of time. See About escalation alerts.

The steps of creating a Device Health Alert Rule, started from Settings, Alert Rules, Create Alert Rule, and Portal Light Offline or Battery Level Alerts. 1 General: Alert Name, Alert Severity, and Description. 2 Applies To, for Battery Level only: all devices or device types. 3 Locations: all locations, a campus and its buildings, or a building. 4 Conditions: for Portal Light Offline, offline for a set time, a number offline, or a percentage offline; for Battery Level, a battery below a set percentage. 5 Actions: Emails, Text Messages, or Webhooks to Recipients, Users, or User groups, with optional Reminders and Escalations. 6 Summary: review, Enable after saving, save, and confirm with Create new rule. A rule triggers alerts only while it is enabled; when it is disabled, no alerts trigger for that rule and no one is notified, and it is changed with the toggle in the Alert Rules list. Every alert is in the Alerts list. Escalation Alert Rules are a separate rule type with only General, Actions, and Summary, used by other rules to notify a different group.

Enabled and disabled rules

An Alert Rule is either enabled or disabled, and this status decides whether the rule does anything at all.

Enabled: The rule is monitoring. When its conditions are met, it triggers an alert and sends its notifications.
Disabled: Monitoring stops immediately. No alerts trigger for that rule, and no one is notified, until it is enabled again. Device Health keeps showing device status, but an offline Portal Light or low battery that rule covers does not trigger an alert.

A new rule is enabled as soon as it's saved, unless Enable after saving is cleared at the top of the page. To enable or disable an existing rule, use its toggle in the Status column of the Alert Rules list, then confirm. Each rule shows Enabled or Disabled under its toggle, and disabled rules are grayed out. Editing a rule does not change its status.

Disabling an Escalation Alert Rule affects every Alert Rule that uses it. Before it's disabled, the list shows those rules and asks you to confirm.

Important: Check a rule's status after you set it up and after every change. A disabled rule still appears in the Alert Rules list with all its settings, but it triggers no alerts.

Alert type: Portal Light Offline

The Portal Light Offline alert rule monitors a Portal Light's connection to Kio Cloud, confirming it is connecting to the local Wi-Fi network and sending data to Kio Cloud.

This alert helps keep data flowing between Portal Lights and Kio Cloud, including the data received from Kontakt.io BLE devices within range of Portal Lights.

An Offline status is commonly caused by a network or power issue, or by no BLE devices being within range of a Portal Light (so no data is received by Kio Cloud).

The following is required when creating a Portal Light Offline Alert Rule.

Setting	Information required
General	Alert Name: uniquely identifies the rule. Alert Severity: Critical, High, Medium, Low, or Info. Description: optional. Enable after saving: in the page header, for new rules only; selected by default, so the rule monitors the condition as soon as it's created. Clear it to create the rule disabled, then enable it later with the Status toggle in the Alert Rules list.
Locations	All locations, a specific campus and its buildings, or a specific building.
Conditions	When the condition is reached, an alert is triggered. Options: when any Portal Light is offline for a specified amount of time; when a specified quantity of Portal Lights are offline; when a specified percentage of Portal Lights are offline.
Actions	Set how and who is notified when an alert is triggered. Notifications: Emails: sends alerts to specified email addresses. Text Messages: sends alerts to specified mobile phone numbers. Webhooks: sends alerts to an external system using a webhook created and managed in Company Settings. Reminders: optionally send alert notifications again (Resend configured notifications) if an alert is not resolved within a set window of time (days, hours, or minutes). Escalations: optionally notify an additional Group if the alert still needs attention after a set amount of time. See About escalation alerts.
Summary	Review every section before you save. Each section has its own card; select the edit (pencil) icon on a card to change that section.

Alert type: Battery Level

Monitors the battery levels of battery-powered BLE devices.

This alert is useful when you want to know when a device's remaining battery life is getting low, so you can schedule a battery or device replacement.

Under Applies To, choose all devices or pick specific device types. Device types are grouped into Infrastructure, Tags, and Monitors, covering your battery-powered devices across every Kio App: Portal Beams, Beam Minis, Anchor Beacons, and all three Dispenser Beacon models under Infrastructure; Asset Tags, Nano Tags, and Smart Badges under Tags; and the Temperature Monitors under Monitors.

The following is required when creating a Battery Level Alert Rule.

Setting	Information required
General	Alert Name: uniquely identifies the rule. Alert Severity: Critical, High, Medium, Low, or Info. Description: optional. Enable after saving: in the page header, for new rules only; selected by default, so the rule monitors the condition as soon as it's created. Clear it to create the rule disabled, then enable it later with the Status toggle in the Alert Rules list.
Applies To	The devices the rule monitors: all devices, or specific device types.
Locations	All locations, a specific campus and its buildings, or a specific building.
Conditions	When the condition is reached, an alert is triggered. Options: when any device has a battery level below a specified percentage; when a specified quantity of devices have a battery level below a specified percentage.
Actions	Set how and who is notified when an alert is triggered. Notifications: Emails: sends alerts to specified email addresses. Text Messages: sends alerts to specified mobile phone numbers. Webhooks: sends alerts to an external system using a webhook created and managed in Company Settings. Reminders: optionally send alert notifications again (Resend configured notifications) if an alert is not resolved within a set window of time (days, hours, or minutes). Escalations: optionally notify an additional Group if the alert still needs attention after a set amount of time. See About escalation alerts.
Summary	Review every section before you save. Each section has its own card; select the edit (pencil) icon on a card to change that section.

Alert Rule examples by use case

For examples of how to set up Alert Rules for different deployments, see Alert Rule examples by use case.