Back Online and Inactivity Alerts

The Inactivity Rule and Back Online Rules offer some basic but useful function.

For Inactivity:
  • The Rule will trigger if the sensor/gateway does not communicate within the configured "Inactivity Time".
  • If the device does communicate within this time, the Rule will not trigger.
  • If the Rule has triggered, and the device communicates after the Rule has triggered (and it ha Auto-acknowledge enabled), the Rule will Disarm/Rearm and will not trigger again until the sensor does not communicate within the configured "Inactivity Time" again.
  • The minimum "Inactivity Time" recommended is 2x the sensor Heartbeat + 1x the gateway Heartbeat + 1 minute.

For Back Online:
  • If the sensor reports continuously before the "Alert after" time elapses, the Rule will not trigger.
  • If the sensor has not communicated within the configured "Alert after" time, the Rule will trigger on the sensors next communication.
  • If Auto-acknowledge is enabled, the Rule will Disarm/Rearm itself if the sensor communicates a second consecutive time before the configure "Alert after" minutes configuration.
  • The minimum "Alert after" recommended is 2x the sensor Heartbeat + 1x the gateway Heartbeat + 1 minute.

It generally makes sense to make the Inactivity Time and the "Alert after" time the same value since they both start their timer on the sensor's previous Heartbeat (the difference is that the Inactivity Rule sends the alert immediately when the time elapses, and the Back Online alert send on the next Heartbeat recorded after the timer has elapsed).
There is no complex relationship between the different Rules, with the status color shown on the sensor, or with the status value reported by the sensors. They simply trigger within the parameters configured. You may be able to configure System Actions to implement more complex operations. How you do this or the logic required to configure them with the desired action would fall outside of the scope offered here. It may be worth exploring System Actions for advanced functionality.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.