Sensor Stopped Reporting Alarm

Who it’s for

Operators of multi-sensor devices, gateway-connected fleets, and integration owners asking “has one sensor gone silent while the others still report?”, “is a probe unplugged downstream of a working gateway?”, “is a LoRaWAN node stuck or an integration silently dropping one telemetry key?” — when device-level offline alarms won’t catch a single feed going dark inside a device that’s otherwise alive.

What it does

Watches the latest temperature reading and raises a Major alarm when no new reading arrives for several minutes. The rule ships without a clear condition, so the alarm stays active until an operator clears it.

How to set up

The rule has default value for the silenceWindowMinutes threshold argument, so it works as soon as it is installed. Install on a device profile so every device of that type is monitored and any new device added later is picked up automatically. Single-device installs are also supported.

How to customize

• To monitor a different telemetry key for liveness — change the Time series key on the metric argument (e.g. temperature → humidity for a humidity-sensor liveness check).
• To use a different silence-window attribute name — change the Attribute key on the silenceWindowMinutes argument to match what your devices already use (e.g. silenceWindowMinutes → silenceLimit).
• To change the silence tolerance used when no per-entity attribute is set — change the Default value on the silenceWindowMinutes argument.
• To tune the silence tolerance 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. silenceWindowMinutes) 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 silenceWindowMinutes 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 restrict firing to expected reporting hours — in the Trigger condition’s Schedule, choose Active at a specific time range (or Custom schedule for different intervals per day) so the silence check only enforces when the entity is expected to report. For per-entity schedules — devices with different reporting cadences — 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.

See also

When you need to detect that an entire device has gone offline rather than one of its telemetry streams, use the alarm template that reads ThingsBoard’s built-in active attribute instead:

IoT Device Offline Alarm verified Dmytro Shvaika