Cold Storage Door Open Alarm

Who it’s for

Cold-chain operators and facility managers asking “is this freezer door open right now?”, “did a delivery bay gate or emergency exit jam open?”, “is a valve or damper that should be closed still open?” — when door- or valve-state telemetry should drive an alert that escalates from warning to critical if the open state stays too long.

What it does

Reads the device’s doorOpen telemetry and raises a Major alarm when the door has been open for several minutes, escalating to Critical if it stays open even longer. The alarm clears the moment the door closes.

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 boolean state — change the Time series key on the state argument (e.g. doorOpen → valveOpen for stuck valves, or gateOpen for delivery bays).
• To use different duration attribute names — change the Attribute key on the warningMinutes and criticalMinutes arguments to match what your devices already use (e.g. doorOpenWarningMinutes → doorGraceMinutes).
• To change the warning and critical durations used when no per-entity attribute is set — change the Default value on the warningMinutes and criticalMinutes arguments.
• To tune the durations at runtime without editing the rule — set the duration as a regular server-side attribute on the entity. It can be edited directly from a dashboard using Update Multiple Attributes input widget:
  • Per device or asset — set the duration attribute (e.g. doorOpenWarningMinutes) 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 duration argument to Current owner, then set the duration attribute on the customer. Every device that customer owns picks up that value.
  • Tenant-wide — change Entity type to Current tenant, then set the duration 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, even after the door closes.
• To allow the held-open state during operating hours and alarm only overnight — in the Trigger condition’s Schedule, choose Active at a specific time range (or Custom schedule for different intervals per day) — typical for cold-chain and warehouse scenarios where doors are expected to be open during the workday. For per-entity schedules — stores with different operating hours — 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.