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 Motor Overcurrent Alarm

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

Raise an alarm when a three-phase motor draws more current than its rated full-load current, with a major alarm for a long overload and a critical alarm for a heavy one. Catches motor overload, high current and overcurrent on pump, fan, compressor and conveyor motors. Compares the highest phase current with the nameplate current set on each motor, waits through motor starts and skips readings that are not numbers.

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

Who it’s for

Electricians, maintenance engineers and plant operators asking “is this motor overloaded?”, “is the pump, fan or compressor motor drawing more than its full-load current?”, “is a conveyor or mixer motor running hot from a jam or a heavy load?” — when an overload must reach someone before the motor overheats, the insulation ages or the overload relay trips the line.

What it does

Reads the three phase currents and the motor’s rated current, then takes the highest phase. When the highest phase stays above 100 % of the rated current for 5 minutes, the rule raises a Major alarm. When it stays above 120 % for 1 minute, the alarm goes up to Critical. The alarm clears when the highest phase stays below 95 % of the rated current for 2 minutes, so a motor that runs close to its limit does not raise and clear the alarm again and again. A reading that is not a number, such as OFF or ERR, is skipped and the other phases are still checked. When no phase sends a number, the alarm does not change until a phase sends a number again. Without a rated current on the device, the rule raises no alarm. The alarm details show the current of each phase.

overcurrent-alarm

The hold times are there on purpose: a motor draws many times its rated current for a few seconds when it starts, and that must not raise an alarm. The Critical alarm waits less, because a heavy overload heats the motor much faster.

How to set up

Install on a device profile so the alarm covers every motor of that type at once and automatically picks up any new motor added later. Single-device installs are also supported.

The rule has default values for every limit and hold time, but not for the rated current, because it is different for each motor. Set ratedCurrent on each device as a server-side attribute, in amps. Take the full-load current (FLA) from the motor nameplate, for the voltage the motor runs on. Until ratedCurrent is set, the rule raises no alarm for that device.

The rule reads currentL1, currentL2 and currentL3 in amps, as the meter or motor controller sends them.

How to customize

  • To use keys from another source — change the Time series key on the phaseL1, phaseL2 and phaseL3 arguments (e.g. currentL1 → ia).
  • To use different limit or hold-time attribute names — change the Attribute key on the ratedCurrent, percent and hold-time arguments (e.g. ratedCurrent → motorFla).
  • To change the limits used when no per-entity attribute is set — change the Default value on the majorPercent, criticalPercent and clearPercent arguments (e.g. majorPercent 115 for a motor with a 1.15 service factor). Keep the clear limit below the Major limit.
  • To change how long the current must stay high or low — change the Default value on the majorHoldMinutes, criticalHoldMinutes and clearHoldMinutes arguments.
  • To tune limits 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. overcurrentMajorPercent, overcurrentMajorHoldMinutes) on the motor 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 motor that customer owns picks up that value. Keep ratedCurrent on each device, because every motor has its own.
  • 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 operating hours — 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.