Low Power Factor Alarm
Raise an alarm when the power factor (PF, cos phi) stays below the tariff limit, before the utility adds a reactive power penalty to the bill. Watches motors, pumps, compressors, plants and buildings through energy meters, power analyzers and smart meters. Reads PF without its sign, so it works with both IEC and IEEE meters. Helps find a failed capacitor bank or motors that run with too little load.
Who it’s for
Energy managers, facility engineers and electricians asking “is the power factor of this plant below the limit in our tariff?”, “is a motor, pump or compressor running with too little load?”, “has a capacitor bank stopped working?” — when a low power factor must be found and fixed before the utility adds a reactive power penalty to the bill.
What it does
Reads the powerFactor telemetry. When the power factor stays below 0.9 for 15 minutes, the rule raises a Minor alarm with the reading in the alarm details. The alarm clears when the power factor stays at 0.92 or above for 15 minutes. The gap between 0.9 and 0.92 stops the alarm from going on and off when the power factor moves around the limit.
The rule looks at the power factor without its sign, because meters sign it in different ways. With the IEC convention, the sign shows the direction of active power, and a minus means power flows to the grid. With the IEEE convention, the sign shows an inductive or a capacitive load. So −0.85 and 0.85 both count as 0.85. A reading that is not a number, such as ERR, does not raise or clear the alarm. A reading of exactly 0 does not raise or clear it either, because many meters send 0 when the load is off. Either reading also starts the hold time again.
When some phases send power to the grid and others take power from it, for example on a site with solar panels, the total power factor can be near 0 even when every phase is fine. On such sites, watch the per-phase keys powerFactorL1, powerFactorL2 and powerFactorL3 instead of the total.
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 the powerFactor key. If your meter does not send powerFactor, install one of these calculated fields on the same devices first. For a single-phase load, or one phase of a three-phase supply, use this field:
For a three-phase meter that sends power, voltage and current for each phase, use this field:
Calculate Three-Phase Power Factor per Phase and TotalHow to customize
- To use a key from another source — change the Time series key on the
metricargument (e.g. powerFactor → cosPhi). - To watch one phase instead of the total — change the Time series key on the
metricargument topowerFactorL1,powerFactorL2orpowerFactorL3. To watch all three phases, install the rule once for each phase and give each copy its own Alarm type (for example Low Power Factor L1), because ThingsBoard does not allow two alarm rules with the same alarm type on one device or profile. - To use different threshold or hold-time attribute names — change the Attribute key on the
threshold,clearThreshold,holdMinutesandclearHoldMinutesarguments (e.g.powerFactorThreshold→ pfLimit). - To change the limits used when no per-device attribute is set — change the Default value on the
thresholdandclearThresholdarguments. Many tariffs put the limit between 0.90 and 0.95. Keep the clear value a little above the trigger value. - To change how long the power factor must stay low before the alarm, or good before it clears — change the Default value on the
holdMinutesandclearHoldMinutesarguments. - To tune the 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.
powerFactorThreshold,powerFactorHoldMinutes) 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.
- Per device — set the attribute (e.g.
- To make the alarm manual-clear-only — remove the Clear condition. The alarm then stays active until an operator clears it.
- To check the power factor only during working hours — in the Trigger conditions’ Schedule, 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 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.