Lesson 4. Alarm Management

Alarms trigger when telemetry crosses defined thresholds. This lesson configures alarm rules on the air-sensor device, adds an Alarms table widget to each dashboard state, and enables propagation so alarms bubble up the building hierarchy.

---

Define Alarm rules at the device profile level to detect abnormal telemetry (e.g., temperature thresholds). These rules specify severity levels, trigger conditions, and automatic clearing logic, forming the foundation for alarm generation and monitoring.

1. Go to the Alarms ⇾ Alarm rules.
2. Click + Add alarm rule ⇾ Create new alarm rule.
3. In the General section set:
   • Alarm type: High temperature
   • Entity type: Device profile
   • Device profile: air-sensor
4. In the Arguments section click Add argument and fill in:
   • Entity type: Current entity
   • Argument type: Latest telemetry
   • Time series key: temperature
   • Argument name: temperature
   • Click Add.
5. In Create conditions click Add create condition:
   • Severity: Critical
   • Click Add condition ⇾ Add argument filter:
     • Argument: temperature, Value type: Numeric
     • Filter: operation greater than, value 26
   • Click Add, then Save.
6. Click Add create condition again:
   • Severity: Major
   • Click Add condition ⇾ Add argument filter:
     • Argument: temperature, Value type: Numeric
     • Filter 1: greater than 24
     • Filter 2: less or equal 26
   • Click Add, then Save.
7. In Clear conditions click Add clearing condition:
   • Click Add condition ⇾ Add argument filter:
     • Argument: temperature, Value type: Numeric
     • Filter: less or equal 24
   • Click Add, then Save.
8. Expand Advanced settings, enable Propagate alarm to related entities, set Relation type to Contains.
9. Click Add to save the rule.

Create the following rules for the air-sensor profile using the same steps. Enable Propagate alarm to related entities (Relation type: Contains) for each.

Alarm type	Major condition	Critical condition	Clear condition
Low temperature	temperature < 20 AND temperature ≥ 18	temperature < 18	temperature ≥ 20
High humidity	humidity > 60 AND humidity ≤ 65	humidity > 65	humidity ≤ 60
Low humidity	humidity < 40 AND humidity ≥ 35	humidity < 35	humidity ≥ 40
High CO₂	co2 ≥ 490 AND co2 < 500	co2 > 500	co2 < 490

---

Add an Alarms table widget to the dashboard state to visualize active and historical alarms generated by devices. This allows users to monitor issues in real time directly from the dashboard.

1. Open Indoor Air Quality Sensor from Office sensors list to navigate it state.
2. Click + Add widget in edit mode.
3. Select Alarm widgets ⇾ Alarms table.
4. Set the datasource to the Selected entity alias.
5. Filter section: check Active in the alarm status list (show only active alarms).
6. Remove the Assignee column from the columns list.
7. Card title: Air sensor alarms
8. Table buttons: leave only Allow alarms acknowledgment and Allow alarms clear enabled.
9. Disable Data export in the Card appearance section.
10. Click Add.
11. Place the widget, resize, and save the dashboard.

---

Simulate telemetry data that exceeds defined thresholds to verify that alarms are triggered, displayed correctly in the widget, and follow the configured severity levels.

1. Go to Entities ⇾ Devices and open SD-001 (Indoor Air Quality Sensor).
2. Click Check connectivity in the Device details panel.
3. Select your messaging protocol and operating system. Copy the provided curl command.
4. In the command, change the temperature value to 25 (triggers Major) or 27 (triggers Critical).
5. Paste and execute the command in your terminal.
6. Return to the dashboard — the alarm should appear in the Air sensor alarms widget within a few seconds.

Once an operator has seen the alarm and is handling it, they can acknowledge it to signal that the event is known — the alarm remains active but is marked as acknowledged.

1. In the Air sensor alarms widget, click the Acknowledge (check) icon in the alarm row.
2. Confirm the action in the dialog.

Alarms auto-clear when the condition is met (temperature ≤ 24 °C). You can also clear manually.

1. Click the Clear (X) icon in the alarm row.
2. Confirm the action.

---

Ensure consistent alarm visibility across the dashboard by adding the alarms widget to all relevant states, enabling centralized monitoring regardless of the selected entity level. Enable Search propagated alarms so parent-level widgets show alarms from all child entities in the hierarchy.

1. In the air_sensor state (edit mode), right-click the Air sensor alarms widget and select Copy.
2. Navigate to the office state, right-click an empty area, and select Paste.
3. Place and resize the widget.
4. Click the pencil icon on the pasted widget to edit it.
5. Change the alarm source alias to Office sensors (the Device search query alias created in Lesson 2).
6. Enable Search propagated alarms.
7. Change the widget title to Office alarms.
8. Click Apply, then save the dashboard.

1. In the office state (edit mode), right-click the Office alarms widget and select Copy.
2. Navigate to the building state, right-click, and select Paste.
3. Place and resize the widget, then click the pencil icon.
4. Change the alarm source alias to Building offices.
5. Verify Search propagated alarms is still enabled.
6. Change the title to Building alarms.
7. Click Apply, then save the dashboard.

1. In the office state (edit mode), copy the alarm widget again.
2. Navigate to the default Buildings state and paste it.
3. Place and resize, then click the pencil icon.
4. Change the alarm source alias to Buildings.
5. Verify Search propagated alarms is enabled.
6. Change the title to All alarms.
7. Click Apply, then save the dashboard.

---

---

Alarm Rule Hierarchies — Configure rules at the device profile level so they apply automatically to all devices of that type. Use severity levels (Major, Critical) to express urgency, not just on/off triggers.

Propagation Strategy — Enable Propagate alarm to related entities with the correct Relation type (usually Contains) so alarms bubble up to parent entities (office → building → default). This eliminates the need for separate monitoring at each level.

Search Propagated Alarms — This widget setting shows alarms from all child entities, not just the entity directly selected. Use it at parent levels (building, office) so operators get a complete view without drilling into every device state.

Alarm Filtering — Use the Active filter in widgets to show only unresolved alarms. Provide table buttons for Acknowledge (signals handling has begun) and Clear (manual resolution). Disable Assignee column if not using the assignment workflow.

Clear Conditions — Always define clear conditions matching your real-world recovery criteria (e.g., temperature ≤ 24 °C to resolve a high-temp alarm). Alarms cleared manually remain in history with “Cleared” status for audit trails.

Widget Reuse Across States — Copy-paste the same Alarms table widget to different states, then change the datasource alias and title. This pattern ensures consistent behavior and appearance across the hierarchy while adapting to the context of each state level.

---