Motor & Energy
Load Shedding
Configure Load Shedding in HPzenAi Smart. Turns off non-essential loads during high demand.
What it does
Shed non-essential loads at peak demand.
Turns off non-essential loads during high demand. Use this automation when the selected field devices should work together without repeated manual setup.
Automation Logic
Trigger
Measured demand crosses the selected load-shedding threshold.
Site load rises above 50 kW
Example: choose "Site load rises above" and keep the default 50 kW, select another preset, or enter another value.
Condition
The load is marked as non-essential and can be safely turned off.
No condition
Example: leave No condition selected when the trigger alone should run the workflow.
Action
Switch off the selected relay or load and send a status alert if configured.
Switch off non-essential relay channels
Example: choose "Switch off non-essential relay channels" for the default then behavior.
Allowed Time
Use the peak-demand monitoring window or All day for demand control.
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
Panels with relay-controlled auxiliary loads.
Motor Controllers, Energy Meters, Level Sensors
Switch off the selected relay or load and send a status alert if configured.
Do not include safety-critical loads in load shedding.
Use a temporary threshold and confirm only the intended load switches off.
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 Load Shedding
Open the HPzenAi app.
Commissioning Checks
- Confirm the motor action or alert follows the selected protection condition.
- Use a temporary threshold and confirm only the intended load switches off.
- 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.