Tank & Pump
Pre-Peak Top-Up
Configure Pre-Peak Top-Up in HPzenAi Smart. Fills storage before a known high-demand or high-tariff period.
What it does
Fill before peak hours when storage is not enough.
Fills storage before a known high-demand or high-tariff period. Use this automation when the selected field devices should work together without repeated manual setup.
Automation Logic
Trigger
The selected pre-peak schedule time is reached.
At 6:00 AM daily
Example: run at 6:00 AM every day, or change the time and repeat days in the app.
Condition
The tank is not already full and source water is available.
Tank level is below 60%
Example: choose "Tank level is below" and keep the default 60%, select another preset, or enter another value.
Action
Top up the tank before peak demand begins.
Top up the tank to 90%
Example: choose "Top up the tank to" and keep the default 90%, select another preset, or enter another value.
Allowed Time
Use Day or Night when the operating window needs to match the site demand pattern.
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
Buildings, farms, and sites that need stored water before predictable peak hours.
Level Sensors, Motor Controllers, Gateways
Top up the tank before peak demand begins.
Keep normal full-stop protection active so scheduled top-up cannot overflow the tank.
Set a near-term schedule and confirm top-up starts only when storage is below the target.
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 Pre-Peak Top-Up
Open the HPzenAi app.
Commissioning Checks
- Confirm the pump starts and stops at the expected tank levels.
- Set a near-term schedule and confirm top-up starts only when storage is below the target.
- 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.