Connectivity
Sensor-Loss Failsafe
Configure Sensor-Loss Failsafe in HPzenAi Smart. Prevents control decisions when a required sensor is unavailable.
What it does
Never pump blind when the sensor is gone.
Prevents control decisions when a required sensor is unavailable. Use this automation when the selected field devices should work together without repeated manual setup.
Automation Logic
Trigger
A required sensor stops reporting or goes offline.
Level sensor goes offline
Example: choose "Level sensor goes offline" for the default when behavior.
Condition
An automation depends on that sensor for safe operation.
Pump is running
Example: choose "Pump is running" for the default if behavior.
Action
Stop or block the controlled pump, valve, or relay until sensor data returns.
Stop the pump and alert me
Example: choose "Stop the pump and alert me" for the default then behavior.
Allowed Time
Use All day for sensor-dependent protection.
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
Tank fill, dry-run protection, and level-based pump control.
Gateways, Water Meters, Level Sensors, Valves
Stop or block the controlled pump, valve, or relay until sensor data returns.
Choose a conservative safe state for each controlled device.
Simulate sensor loss and confirm the controlled 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 Sensor-Loss Failsafe
Open the HPzenAi app.
Commissioning Checks
- Confirm the notification or failsafe action happens when device communication changes.
- Simulate sensor loss and confirm the controlled 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.