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, how they find the site and where they get stuck, so we can improve it (Google Analytics, Microsoft Clarity).

Show us which of our ad campaigns bring visitors to the site and remember the campaign or partner link you arrived from (Google Ads, LinkedIn, Meta, 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

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

Alarm feed

  • Widget
  • 18 installs
  • v1.0.0
  • Nov 17, 2026
  • MIT license
  • v4.2+

What needs attention, and since when? Active alarms arrive as a calm feed: each row carries a severity stripe and icon, the alarm type, the device and how long ago it started, with acknowledge and clear buttons right on it. Chips on top count each severity and filter the list in one click, unacknowledged alarms keep a small dot, and a new critical pulses softly until someone takes it. A row click can open the device page.

Widget Type
  • Alarm
Category
  • Tables & Lists

Who it’s for

Alarm feed is for operators and dashboard authors who need to see at a glance which alarms are open right now, how serious each one is and how long it has been waiting. The question behind it is usually “what needs my attention first, and can I acknowledge it without opening another page?”

What it does

For example, a street lighting dashboard with five active alarms shows chips reading All 5 · Critical 1 · Major 2 · Minor 2. The top row is Lamp failure on LS-Lamp-02, started 12 min ago, with a red stripe, a pulsing red icon and a check button. Below it Voltage out of range on LS-Lamp-04 waits in orange, and two acknowledged rows sit dimmed further down.

  • Every active alarm becomes a row with a severity stripe and icon, the alarm type, the device and how long ago it started; the full date and time appear on hover.
  • Acknowledge and clear buttons sit on each row, so an operator handles an alarm without leaving the dashboard. A cleared alarm leaves the list right away.
  • Chips above the list count each severity and filter the list to one severity with a single click.
  • Unacknowledged alarms keep a small colored dot, and an unacknowledged critical alarm pulses softly until someone acknowledges it.
  • A row click can open a device page or any other dashboard state, with the alarm’s device passed along.
  • On a narrow card the severity label drops out and the stripe and icon carry the severity, so the alarm type and device stay readable.
  • Alarm feed lists active alarms only; it does not chart alarm history or keep cleared alarms on screen.

How to set up

Data keys

Alarm feed takes an alarm source rather than telemetry keys: choose the entity, alias or filter whose alarms it lists in the widget’s Data tab. The status, severity and type filters set there decide which alarms are fetched; by default the widget asks for active alarms, including alarms propagated from child entities. When no alarm matches, the card shows No active alarms with a green check.

  • Alarm source — Entity alias or Entity. The entities whose alarms are listed. The device name on each row comes from the alarm’s originator label, falling back to its name.
  • Alarm filter — status, severity and type lists. Narrows what is fetched; an empty list means any value.

List

  • Acknowledge button — on by default. Shows a check button on every unacknowledged row; a click acknowledges that alarm. A failed request shows an error message and leaves the row as it was.
  • Clear button — on by default. Shows a cross button that clears the alarm; the row then leaves the list.

Actions

  • On row click — not set by default. Bind it on the Actions tab to open a dashboard state, a popup or a custom action. The alarm’s device is passed as the entity, so a device details state opens on the right device. Rows show a pointer only once this action is set.

How to customize

  • To hide the severity chips — turn off Severity filter.
  • To put the most severe alarms on top — set Sort by to Severity, then newest; the default is Newest first.
  • To show clock times instead of “12 min ago” — set Time format to Time (21:38) or Date and time; Relative (5 min ago) is the default.
  • To stop the pulse on new critical alarms — turn off Pulse new critical.
  • To change the row background — set Row color; it defaults to a faint gray.
  • To change the text color — set Text color; the device and time use it at lower opacity.
  • To match your own severity palette — edit Critical, Major, Minor, Warning and Indeterminate under Severity colors. The stripe, icon, label, dot and chip of each row follow them.

Tips

  • Put Alarm feed on a dashboard state of its own and bind On row click to the device page, so an operator moves from the alarm straight to the device that raised it.
  • Pair it with a severity summary card on the overview page and keep the full feed one click away.
  • Acknowledging and clearing need a user allowed to change alarms; a customer user without that permission sees the request fail with an error message.

Share Your Widget with the Community

Built a custom widget? Export it as a JSON from ThingsBoard and publish it to the IoT Hub through a simple 4-step wizard (Upload, Listing, Readme, Review & Submit). Share it with thousands of ThingsBoard developers worldwide and get featured in the catalog.