Motor & Energy
Motor Cooldown
Configure Motor Cooldown in HPzenAi Smart. Forces a rest period after long motor runtime.
What it does
Force a rest period after long runtime.
Forces a rest period after long motor runtime. Use this automation when the selected field devices should work together without repeated manual setup.
Automation Logic
Trigger
Motor runtime exceeds the configured continuous runtime limit.
Motor runs continuously for 60 min
Example: choose "Motor runs continuously for" and keep the default 60 min, select another preset, or enter another value.
Condition
The cooldown period is enabled for the selected motor.
No condition
Example: leave No condition selected when the trigger alone should run the workflow.
Action
Stop or block the motor until the cooldown period ends.
Stop motor and cool down for 20 min
Example: choose "Stop motor and cool down for" and keep the default 20 min, select another preset, or enter another value.
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
Motors that heat up during long pumping or process cycles.
Motor Controllers, Energy Meters, Level Sensors
Stop or block the motor until the cooldown period ends.
Set cooldown values according to motor duty rating.
Use short commissioning values and confirm restart is blocked during cooldown.
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 Motor Cooldown
Open the HPzenAi app.
Commissioning Checks
- Confirm the motor action or alert follows the selected protection condition.
- Use short commissioning values and confirm restart is blocked during cooldown.
- 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.