Office HVAC Temperature Alarm

Who it’s for

Building-automation operators, retail facility teams, and server-room admins asking “is this office or retail store getting too warm during business hours?”, “is a controller stuck in heating mode during summer, or in cooling during winter?”, “should the alarm stay silent overnight, on weekends, or outside a server-room’s scheduled cooling window?” — when out-of-range readings only matter during working hours and the rest of the time the building is in energy-saving mode.

What it does

Reads the device’s indoorTemperature telemetry and raises a Major alarm when the room gets too hot or too cold and stays uncomfortable for several minutes. The trigger fires only during business hours (Mon–Fri 08:00–18:00 UTC by default). The alarm auto-clears any time temperature returns to a tighter comfort range, including outside business hours.

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. indoorTemperature → humidity for indoor humidity ranges).
• 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. indoorTemperatureWarningHigh → comfortMaxTemp).
• To change the trigger and clear thresholds used when no per-entity attribute is set — change the Default value on the warningHigh, warningLow, clearHigh, and clearLow arguments.
• To change how long a reading must stay out of range before firing or clearing — 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. indoorTemperatureWarningHigh, indoorTemperatureHoldMinutes) 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 adapt the operating-hours window — edit the Schedule on the Trigger condition to match your local timezone, weekday set, and time-of-day range. Use Custom schedule for different intervals on different days, or switch to Dynamic mode to source per-building schedule JSON from an attribute.
• To control where the alarm shows up — toggle the propagation flags under Advanced settings.