Connectivity
Repeated Offline Alert
Configure Repeated Offline Alert in HPzenAi Smart. Escalates devices that repeatedly drop offline.
What it does
Escalate noisy devices that keep dropping off.
Escalates devices that repeatedly drop offline. Use this automation when the selected field devices should work together without repeated manual setup.
Automation Logic
Trigger
A device has multiple offline events within the selected period.
Device goes offline this many times today 5
Example: choose "Device goes offline this many times today" and keep the default 5, select another preset, or enter another value.
Condition
The repeated count crosses the configured alert threshold.
No condition
Example: leave No condition selected when the trigger alone should run the workflow.
Action
Send an escalation alert for inspection.
Notify me (warning)
Example: choose "Notify me (warning)" for the default then behavior.
Allowed Time
Use All day for reliability monitoring.
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
Sites with unstable power, weak signal, or failing devices.
Gateways, Water Meters, Level Sensors, Valves
Send an escalation alert for inspection.
Investigate repeated offline behavior before relying on the device for control.
Review event history to confirm repeated drops are counted correctly.
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 Repeated Offline Alert
Open the HPzenAi app.
Commissioning Checks
- Confirm the notification or failsafe action happens when device communication changes.
- Review event history to confirm repeated drops are counted correctly.
- 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.