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

Three-Phase Phase Loss Alarm

  • Alarm Rule
  • 0 installs
  • v1.0.1
  • Nov 16, 2026
  • MIT license
  • v4.3+

Raise a critical alarm the moment a phase is lost on a three-phase supply, with the lost phase in the alarm details. Catches phase failure, a blown fuse or a missing phase on motor, pump and compressor feeds, switchboards and energy meters. A separate warning shows a phase that the meter cannot read.

Type
  • Alarm
Category
  • Safety
  • Equipment Health
Use Cases
  • Industrial Automation
  • Predictive Maintenance
  • Smart Energy
  • Smart Metering

Who it’s for

Electricians, maintenance engineers and facility managers asking “has a phase dropped out on this motor feed?”, “did a fuse blow on the pump or compressor supply?”, “is the meter on this switchboard still reading all three phases?” — when a lost phase must reach someone at once, before a machine overheats on two phases or stops.

What it does

Reads the result of the phase loss calculated field: how many phases are lost, how many the meter cannot read, and their names. A lost phase raises a Critical alarm at once, with the lost phases in the alarm details (for example L2). A phase that the meter cannot read, such as one that reports OFF or ERR, raises a Warning alarm when it stays unreadable for 5 minutes. When a phase is lost while the Warning is active, the alarm goes up to Critical. The alarm clears when every phase is back and readable.

phase-loss-alarm

The Critical alarm has no waiting time on purpose: a motor that runs on two phases overheats within minutes. The Warning waits, because a meter can send one bad reading and then recover.

How to set up

The rule has default values for every setting, so it works as soon as it is installed. Install on a device profile so the alarm covers every meter of that type at once and automatically picks up any new meter added later. Single-device installs are also supported.

The rule reads lostPhaseCount, lostPhaseNames, unknownPhaseCount and unknownPhaseNames. Install this calculated field on the same devices first, so these keys exist:

Detect Phase Loss on a Three-Phase Supply Dmytro Shvaika

How to customize

  • To use keys from another source — change the Time series key on the lostCount, lostNames, unknownCount and unknownNames arguments.
  • To use a different hold-time attribute name — change the Attribute key on the unknownHoldMinutes argument (e.g. phaseUnknownHoldMinutes → meterErrorMinutes).
  • To change how long a phase must stay unreadable before the Warning — change the Default value on the unknownHoldMinutes argument.
  • To tune the hold time 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 — set phaseUnknownHoldMinutes on the meter itself. The per-device value overrides the Default value.
    • Per customer (in deployments that use customers) — change Entity type on the unknownHoldMinutes argument to Current owner, then set the attribute on the customer. Every meter that customer owns picks up that value.
  • To make the alarm manual-clear-only — remove the Clear condition. The alarm then stays active until an operator clears it.
  • To raise the alarm only during set hours each week — in the Schedule of both the Warning and Critical trigger conditions, choose Active at a specific time (or Custom for different hours per day). The schedule repeats every week. For different hours per site, add an argument that reads the schedule JSON from a server-side attribute on the device, and set its Default value to {} so a device without the attribute raises the alarm at any time. Then switch the Schedule of both trigger conditions to Dynamic and pick that argument in Argument.
  • To control where the alarm shows up — toggle the propagation flags under Advanced settings.

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.