Connectivity
Command Ack Timeout
Configure Command Ack Timeout in HPzenAi Smart. Detects when a device does not confirm a command.
What it does
Notify when a device does not confirm a command.
Detects when a device does not confirm a command. Use this automation when the selected field devices should work together without repeated manual setup.
Automation Logic
Trigger
A command is sent to a valve, relay, motor, or controller.
Command acknowledgement is missing for 30 sec
Example: choose "Command acknowledgement is missing for" and keep the default 30 sec, select another preset, or enter another value.
Condition
The device does not confirm the expected result within the timeout.
No condition
Example: leave No condition selected when the trigger alone should run the workflow.
Action
Send an acknowledgement timeout alert.
Notify me (warning)
Example: choose "Notify me (warning)" for the default then behavior.
Allowed Time
Use All day for commanded devices.
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
Valves, relays, pumps, and controllers where command confirmation matters.
Gateways, Water Meters, Level Sensors, Valves
Send an acknowledgement timeout alert.
Do not assume the field device changed state if acknowledgement is missing.
Send a supervised command and confirm acknowledgement timing in normal operation.
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 Command Ack Timeout
Open the HPzenAi app.
Commissioning Checks
- Confirm the notification or failsafe action happens when device communication changes.
- Send a supervised command and confirm acknowledgement timing in normal operation.
- 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.