Connectivity
Offline Failsafe
Configure Offline Failsafe in HPzenAi Smart. Moves equipment to a safe state when control communication is lost.
What it does
Move actuators to a safe state if control is lost.
Moves equipment to a safe state when control communication is lost. Use this automation when the selected field devices should work together without repeated manual setup.
Automation Logic
Trigger
A selected device or gateway goes offline.
Gateway stays offline for 15 min
Example: choose "Gateway stays offline for" and keep the default 15 min, select another preset, or enter another value.
Condition
The controlled device has a configured safe state.
No condition
Example: leave No condition selected when the trigger alone should run the workflow.
Action
Apply the safe state, such as closing a valve or stopping a relay.
Stop motors, close valves, and turn relays off
Example: choose "Stop motors, close valves, and turn relays off" for the default then behavior.
Allowed Time
Use All day for safety-critical 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
Water shutoff, pump protection, and unattended field systems.
Gateways, Water Meters, Level Sensors, Valves
Apply the safe state, such as closing a valve or stopping a relay.
Choose safe states carefully so loss of communication does not create a new hazard.
Test with non-critical equipment first and verify the device moves to the safe state.
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 Offline Failsafe
Open the HPzenAi app.
Commissioning Checks
- Confirm the notification or failsafe action happens when device communication changes.
- Test with non-critical equipment first and verify the device moves to the safe state.
- 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.