Relay Bank
Channel Interlock
Configure Channel Interlock in HPzenAi Smart. Prevents conflicting relay channels from running together.
What it does
Never let two channels run together.
Prevents conflicting relay channels from running together. Use this automation when the selected field devices should work together without repeated manual setup.
Automation Logic
Trigger
A relay channel is requested to turn on.
A channel turns on
Example: choose "A channel turns on" for the default when behavior.
Condition
A conflicting channel is already on or requested.
No condition
Example: leave No condition selected when the trigger alone should run the workflow.
Action
Block the new command or turn off the conflicting channel based on configuration.
Turn the paired channel off
Example: choose "Turn the paired channel off" for the default then behavior.
Allowed Time
Use All day for relay safety.
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
Forward/reverse control, alternate valves, and loads that must never overlap.
Relay Controllers, Motor Controllers, Valves
Block the new command or turn off the conflicting channel based on configuration.
Review wiring and load behavior before relying on an interlock.
Attempt both conflicting channels under supervision and confirm only the allowed channel runs.
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 Channel Interlock
Open the HPzenAi app.
Commissioning Checks
- Confirm the selected relay channel changes state at the expected time or condition.
- Attempt both conflicting channels under supervision and confirm only the allowed channel runs.
- 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.