Motor & Energy
Overload Protection
Configure Overload Protection in HPzenAi Smart. Stops the motor before overload damage occurs.
What it does
Cut power before the motor burns out.
Stops the motor before overload damage occurs. Use this automation when the selected field devices should work together without repeated manual setup.
Automation Logic
Trigger
Motor current exceeds the selected overload threshold.
Motor current rises above 20 A
Example: choose "Motor current rises above" and keep the default 20 A, select another preset, or enter another value.
Condition
The overload condition lasts longer than the configured delay.
No condition
Example: leave No condition selected when the trigger alone should run the workflow.
Action
Stop the motor and send a fault alert.
Stop the motor and alert me
Example: choose "Stop the motor and alert me" for the default then behavior.
Allowed Time
Use All day for motor protection.
All day
Example: keep All day for protection workflows, or choose Day or Night when operation should stay inside site hours.
Automation Details
Recommended use
Pumps, fans, compressors, and motor loads monitored by HPzenAi controllers.
Motor Controllers, Energy Meters, Level Sensors
Stop the motor and send a fault alert.
Do not replace required electrical protection devices with app automation alone.
Set thresholds from rated current and verify alerts without forcing unsafe overloads.
Before You Start
Device Readiness
Link every device used by this workflow and confirm each one is online.
Device Selection
Choose the exact tank, pump, valve, relay, or meter that should be controlled.
Safe Test
Test with safe thresholds or manual observation before leaving the workflow enabled.
Guided Setup
Set Up Overload Protection
Open the HPzenAi app.
Commissioning Checks
- Confirm the motor action or alert follows the selected protection condition.
- Set thresholds from rated current and verify alerts without forcing unsafe overloads.
- Confirm the saved card shows the correct workflow, devices, schedule, and enabled state.
- Review the event history after testing so the action is recorded as expected.
- Keep safety-critical workflows active all day unless the site needs a specific time window.
Troubleshooting
- If the Save button is disabled, complete every required trigger, condition, action, and timing field.
- If the workflow does not run, confirm the devices are online and the active time allows it to run now.
- If the action does not complete, check whether the target device is already in that state or cannot accept commands.
- If notification behavior is missing, confirm phone notification permission and recent device data.