Skip to content

Cookie preferences

We use cookies for our own analytics, to see how our campaigns perform and, if you allow it, to load content from other services such as the Google site search. We never sell your data. Necessary cookies keep the site working and cannot be switched off. See our Cookie Policy for details and our Privacy Policy for how we handle personal data.

Security, load balancing and remembering your cookie choice.

Show us which pages people read and how they find the site, so we can improve it (Google Analytics).

Show us which of our ad campaigns bring visitors to the site and remember the campaign or partner link you arrived from (Google Ads, partner program). We do not use these cookies to build advertising profiles.

Load the site search from Google when you use it. Google sets its own cookies and shows ads in the search results.

© 2026 The ThingsBoard Authors
Try for free

ThingsBoard Cloud

Choose your data region

Your data stays in the region you choose, for residency and compliance. No credit card required.

Rather run it yourself? Install on your own servers

IoT Alarm Rules

Install ready-to-use alarm rules in one click — detect threshold breaches, offline devices, and equipment faults, and start reacting the moment they happen.

Contribute
Alarm Rules illustration

21 results

Items per page:

Share Your Alarm Rule with the Community

Built a reliable alarm rule? Export it as a JSON from ThingsBoard and publish it to the IoT Hub. Share it with thousands of ThingsBoard developers and help the community react to incidents faster.

Frequently Asked Questions

An alarm rule is a reusable condition-to-severity template. Once installed on a device, asset, or profile, it evaluates live telemetry and raises — and clears — alarms whenever its conditions are met, with no rule logic to write.

Click Install and pick the target — a device, an asset, or a device/asset profile — in the install dialog. The rule is created there and starts evaluating live telemetry immediately. A profile-level install covers every entity of that type, including ones added later.

Usually not. Well-built rules read thresholds from server attributes with sensible defaults, so they fire correctly out of the box. You can override the value per entity by setting the attribute — no need to edit the rule.

CRITICAL, MAJOR, MINOR, WARNING, and INDETERMINATE. A single rule can define different trigger conditions for different severities.

A rule can include a clear condition that clears the alarm automatically when telemetry returns to normal. Without one, the alarm stays active until an operator clears it.

The category describes what the rule monitors (Threshold, Connectivity, Equipment Health, Environmental, Energy, Safety, Geofencing, Other). Use Case is the shared IoT domain (Cold Chain, Fleet Tracking, Predictive Maintenance, etc.) used across the whole marketplace.

Check the IoT Alarm Rule Contribution Guide that describes the process of adding alarm rules. You can also contact us or email iothub@thingsboard.io for help.

All community-contributed alarm rules are currently free. Commercial listings may be introduced in a future phase.