Cold Chain Temperature Alarm

Who it’s for

Cold-chain operators, lab managers, and facility engineers asking “is this pharma fridge or vaccine freezer drifting up toward spoilage?”, “is a server-room or industrial oven climbing past its safe range?”, “is the wine cellar, blood-bank fridge, or engine-coolant reading exceeding its limits?” — when temperature should trigger an early warning before it stays above the safe limit long enough to escalate.

What it does

Reads the device’s temperature telemetry and raises a Major alarm when temperature rises above a safe limit, escalating to Critical when it stays well past that limit. The alarm auto-clears once temperature drops back to normal.

How to set up

The rule has default values for every threshold, so it works as soon as it is installed. Install on a device or asset profile so the alarm covers every entity of that type at once and automatically picks up any new entity added later. Single-device or single-asset installs are also supported.

How to customize

• To monitor a different telemetry — change the Time series key on the metric argument (e.g. temperature → bodyTemp for medical wearables, or coolantTemp for engines).
• To use different threshold attribute names — change the Attribute key on the threshold arguments to match what your devices or assets already use (e.g. temperatureWarningThreshold → tempLimit).
• To change the warning, danger, and clear thresholds used when no per-entity attribute is set — change the Default value on the warningThreshold, criticalThreshold, and clearThreshold arguments.
• To change how long the reading must stay above the danger threshold before Critical fires — change the Default value on the holdMinutes argument.
• To tune thresholds and hold duration at runtime without editing the rule — set the value on the entity as a regular server-side attribute. It can be edited directly from a dashboard using Update Multiple Attributes input widget:
  • Per device or asset — set the attribute (e.g. temperatureWarningThreshold, temperatureHoldMinutes) on the device or asset itself. The per-entity value overrides the Default value.
  • Per customer (in deployments that use customers) — change Entity type on the relevant argument to Current owner, then set the attribute on the customer. Every device that customer owns picks up that value.
  • Tenant-wide — change Entity type to Current tenant, then set the attribute on the tenant. The value applies across every device.
• To make the alarm manual-clear-only — remove the Clear condition. The alarm then stays active until an operator clears it.
• To restrict firing to specific hours or days — in the Trigger condition’s Schedule, choose Active at a specific time range (or Custom schedule for different intervals per day). For per-entity schedules — different freezers with different defrost cycles — switch to Dynamic mode and source the schedule JSON from an attribute on the entity.
• To control where the alarm shows up — toggle the propagation flags under Advanced settings.