Tank & Pump
Sump Recovery Cycle
Configure Sump Recovery Cycle in HPzenAi Smart. Lets the sump recover before another transfer attempt.
What it does
Pause the pump, wait for recovery, then try again.
Lets the sump recover before another transfer attempt. Use this automation when the selected field devices should work together without repeated manual setup.
Automation Logic
Trigger
Sump level drops below the safe source level during pumping.
Sump level drops below 15%
Example: choose "Sump level drops below" and keep the default 15%, select another preset, or enter another value.
Condition
A recovery delay is configured and the target tank still needs water.
Pump is running
Example: choose "Pump is running" for the default if behavior.
Action
Stop the pump, wait for the sump to recover, then retry within the configured limit.
Pause the pump and retry after 30 min
Example: choose "Pause the pump and retry after" and keep the default 30 min, select another preset, or enter another value.
Allowed Time
Use All day for unattended sump transfer systems.
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
Small sumps, slow recharge sources, and buildings with intermittent water supply.
Level Sensors, Motor Controllers, Gateways
Stop the pump, wait for the sump to recover, then retry within the configured limit.
Use retry limits and a minimum recovery level to protect the pump from short cycling.
Force the low-sump condition and confirm the workflow waits before trying again.
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 Sump Recovery Cycle
Open the HPzenAi app.
Commissioning Checks
- Confirm the pump starts and stops at the expected tank levels.
- Force the low-sump condition and confirm the workflow waits before trying again.
- 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.