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 Voltage Imbalance Alarm

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

Raise an alarm when the three-phase supply voltage stays unbalanced: a major alarm above 2 % and a critical alarm above 5 %, with the imbalance in the alarm details. Protects motors, pumps, compressors and switchboards from voltage unbalance, phase unbalance and uneven phase voltages that make them overheat. The limits follow NEMA MG 1 and can be set per device.

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

Who it’s for

Maintenance engineers, electricians and energy managers asking “is the supply voltage on this motor too unbalanced?”, “is one phase of the feeder lower than the others for too long?”, “is the voltage unbalance on this pump, compressor or switchboard above 2 %?” — when an unbalanced supply makes motors run hot and wear out long before anyone sees a fault.

What it does

Reads the voltage imbalance in percent that the voltage imbalance calculated field writes. When the imbalance stays above 2 % for 5 minutes, the rule raises a Major alarm. When it stays above 5 % for 1 minute, the rule raises a Critical alarm, or moves an active Major alarm up to Critical. The alarm details show the imbalance and the limit it passed. The alarm clears when the imbalance stays below 1.5 % for 5 minutes. A value between 1.5 % and 2 % keeps the alarm as it is, so a reading near the limit does not open and close the alarm again and again.

voltage-imbalance-alarm

The default limits follow NEMA MG 1 for line-to-line voltages: a motor must run at a lower load when the unbalance grows above 1 %, and it should not run above 5 %. Phase-to-neutral voltages of the same supply give a higher number, often about twice as high, so set the limits for the kind of voltage the field reads.

The alarm opens or clears as soon as the waiting time ends, even if no new reading arrives. A reading that is not a number, such as ERR, does not raise or clear the alarm.

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 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 voltageImbalancePercent. Install this calculated field on the same devices first, so this key exists:

Calculate Three-Phase Voltage Imbalance Percentage Dmytro Shvaika

How to customize

  • To use a key from another source — change the Time series key on the metric argument (e.g. voltageImbalancePercent → voltageUnbalance).
  • To use different threshold or hold-time attribute names — change the Attribute key on the threshold and hold-time arguments (e.g. voltageImbalanceWarningPercent → imbalanceLimit).
  • To change the thresholds used when no per-device attribute is set — change the Default value on the warningThreshold, criticalThreshold and clearThreshold arguments. Keep the clear threshold below the warning threshold. When the field reads phase-to-neutral voltages, about twice the default values fit (e.g. 4, 10 and 3).
  • To change how long the imbalance must last before the alarm opens or clears — change the Default value on the warningHoldMinutes, criticalHoldMinutes and clearHoldMinutes arguments.
  • To tune thresholds and hold times 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 the attribute (e.g. voltageImbalanceWarningPercent, voltageImbalanceWarningHoldMinutes) on the meter itself. The per-device 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 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 Major 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.