Tank & Valve
Sump Flood Guard
Configure Sump Flood Guard in HPzenAi Smart. Responds early when a sump level rises toward overflow.
What it does
React before the sump floods over.
Responds early when a sump level rises toward overflow. Use this automation when the selected field devices should work together without repeated manual setup.
Automation Logic
Trigger
Sump level crosses the high flood-warning point.
Sump level reaches 90%
Example: choose "Sump level reaches" and keep the default 90%, select another preset, or enter another value.
Condition
A drain pump, outlet valve, or alert path is available.
No condition
Example: leave No condition selected when the trigger alone should run the workflow.
Action
Start the configured response, such as pumping out, opening a valve, or sending an alert.
Close the inlet valve and alert me
Example: choose "Close the inlet valve and alert me" for the default then behavior.
Allowed Time
Use All day for flood 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
Basement sumps, collection pits, and sites with flooding risk.
Level Sensors, Valves, Relay Controllers
Start the configured response, such as pumping out, opening a valve, or sending an alert.
Set the flood point with enough time for the response device to move water safely.
Simulate the high level and confirm the alert or drain action occurs.
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 Flood Guard
Open the HPzenAi app.
Commissioning Checks
- Confirm the valve opens and closes at the expected tank condition.
- Simulate the high level and confirm the alert or drain action occurs.
- 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.