Tank & Valve
Valve Stuck Alert
Configure Valve Stuck Alert in HPzenAi Smart. Warns when a valve command does not produce the expected state change.
What it does
Warn when a valve command does not change state.
Warns when a valve command does not produce the expected state change. Use this automation when the selected field devices should work together without repeated manual setup.
Automation Logic
Trigger
A valve open or close command is sent.
Valve state does not change within 30 sec
Example: choose "Valve state does not change within" and keep the default 30 sec, select another preset, or enter another value.
Condition
The valve does not report the expected state within the allowed time.
No condition
Example: leave No condition selected when the trigger alone should run the workflow.
Action
Send an alert for inspection or service.
Notify me (critical)
Example: choose "Notify me (critical)" for the default then behavior.
Allowed Time
Use All day for controlled valves.
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
Motorized valves, irrigation valves, and inlet valves with command feedback.
Level Sensors, Valves, Relay Controllers
Send an alert for inspection or service.
Treat repeated stuck alerts as a maintenance issue before relying on the valve for protection.
Use a supervised command and confirm the expected state feedback appears.
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 Valve Stuck Alert
Open the HPzenAi app.
Commissioning Checks
- Confirm the valve opens and closes at the expected tank condition.
- Use a supervised command and confirm the expected state feedback appears.
- 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.