This document details the meaning of each event notification rule you can configure. Please note that not all rules are available for all device types.
Using the "Match all / any of following events" drop down list you can use mutliple conditions in your event notification rule. Use "all" to require that every condition is true before the notification is triggered. Use "any" to only require that one of the conditions is true before the notification is triggered.
| Rule Name | Description | Notes |
|---|---|---|
| EMERGENCY | ||
| When the device emergency state changes | Raised when the device enters an emergency state (i.e. an emergency message is received whilst the device is not in an emergency state) or when an emergency cancel message is received whilst the device is in an emergency state. | Receiving a man-down alert will also cause a device to enter an emergency state. |
| When the device sends an emergency message | Raised every time an emergency message is received. | |
| When the device sends an emergency cancel message | Raised every time an emergency cancel message is received. | |
| When the device is in emergency mode | Used in conjunction with other criteria (i.e. "When the speed is greater than 60KM/h and the device is in an emergency state...") | |
| When an emergency is unacknowledged | Raised when an emergency hasn't been acknowledged for the specified period | |
| When the device activates man down mode | Raised when the user turns on man down detection. | Only available for devices with man-down support (i.e. Lone Worker app). To raise a notification when a man-down alert occurs, use the "When the device emergency state changes" or "When the device sends an emergency message" conditions. |
| When the device deactivates man down mode | Raised when the user turns off man down detection. | Only available for devices with man-down support (i.e. Lone Worker app). To raise a notification when a man-down alert is cancelled, use the "When the device emergency state changes" or "When the device sends an emergency cancel message" conditions. |
| CHECK-IN | ||
| When the device checks-in | Raised every time a message deemed to constitute a check-in is received. | Every message that requires user interaction on the device is considered to be a check-in. For example, a text message is considered a check in. A position report that required the device user to send via an interaction of their own making would also be considered a check-in. An automated position report that did not require the user to interact with the device would not be considered a check-in. Capabilities vary by device. |
| When the device becomes overdue | Raised when a device enters an overdue state having previously not been overdue. | |
| When the device becomes not overdue | Raised when a device enters a not overdue state having previously been overdue. | |
| When the device is overdue | Used in conjunction with other criteria (i.e. "When the device sends an emergency message and the device is overdue...") | |
| When the device starts monitoring mode | Raised when a device enters the monitored state (having previously been not monitored). | |
| When the device stops monitoring or checks out | Raised when leaves the monitored state (having previously been monitored). | |
| When the device is in monitoring mode | Raised when the device has been in monitoring mode for the specified period. | Can also be in conjunction with other criteria (i.e. "When the device sends a text message and the device is is in monitoring mode...") |
| When the check-in schedule is enabled for the device | Raised when monitoring begins (based on a check-in schedule defined via the Portal). | |
| When the check-in schedule is disabled for the device | Raised when monitoring ends (based on a check-in schedule defined via the Portal). | |
| When a check-in request is sent to the device | Raised when a check-in is requested via the Portal. | |
| MESSAGE | ||
| When the message text | Raised when a message is receivied containing / not containing a particular piece of text. | |
| When the message type | Raised every time a message of a particular type is received. | |
| When the message recipients | Raised when a mesage is receivied addressed to particular recipients. | |
| When the message property | Raised when a message property value meets certain criteria (i.e. "Temperture" > 30 or "Engine RPM" < 4000). | |
| When address | Raised when the address (derived from the location data) matches certain criteria (i.e. "When address contains 101 Main Street, Acme Town") | |
| When speed | Raised when the speed (derived from the location data) matches certain criteria (i.e. "When speed > 35KM/h") | |
| When position accuracy | Raised when the accuracy of the position supplied in the message is either high, medium or low | |
| When altitude | Raised when the altitude (derived from the location data) matches certain criteria (i.e. "When altitude < 50M") | |
| When the device sends a position message | Raised when a position report message is received. | |
| When the device sends a message with no position | Raised when a message is received which does not contain position data. | |
| When the device starts moving | Raised when a "started moving" message is received from a device. | Requires device support for sending a message when motion is detected. This capability is currently limited to the Queclink GL300, GV500, Prime AT, PT and SPOT Trace devices. |
| When the device stops moving | Raised when a "stopped moving" message is received from a device. | Requires device support for sending a message when motion is no longer detected. This capability is currently limited to the Queclink GL300, GV500, Prime AT, PT and SPOT Trace devices. |
| When the device battery becomes low | Raised when the device battery level drops below 20%. | Requires that battery data be included in the message data sent from the device. |
| When the device hasn't sent any message | Raised when the device has not sent any messages within the configured period (i.e. 1 hour, 24 hours, 1 week, etc.) | |
| GEOFENCE | ||
| When the device enters a geofence | Raised when the device's position indicates that it has entered a geofence (i.e. gone from outside it to inside it). | |
| When the device leaves a geofence | Raised when the device's position indicates that it has left a geofence (i.e. gone from inside it to outside it). | |
| When the device crosses a geofence | Raised when the device's position indicates that it has crossed a geofence (i.e. gone from inside it to outside it or vice versa). | Checking the "Including Possible Pass-Through" option will cause the event notification to be raised if a geofence may have been crossed based on a straight line drawn between the current and previous positions (even if no report was received within or without the geofence). |
| When the device is inside geofence | Used in conjunction with other criteria (i.e. "When the speed is greater than 60KM/h and the device is inside the geofence...") | |
| When the device is outside geofence | Used in conjunction with other criteria (i.e. "When the altitude is less than 250M and the device is outside the geofence...") | |
| When the distance from point of interest | Raised when the device is within a specific distance of a point of interest. | In the context of this rule, a point of interest is set up under Options > Points of Interest. |
| When the device crosses country border | Raised when a message arrives with a different "country" value in its address data (requires reverse geocoding to be enabled). | |
| TIME | ||
| When the day is | Used in conjunction with other criteria (i.e. "When the device crosses any geofence and the day is a Saturday or Sunday...") | Ensure you set the appropriate time zone to base this calculation upon via the "Time Zone" drop-down list. |
| When the date is | Used in conjunction with other criteria (i.e. "When the device enters any geofence and the date is 01 January 2017...") | |
| When the date is between | Used in conjunction with other criteria (i.e. "When the device is overdue and the date is between 01 January 2017 and 31 January 2017...") | |
| When the time of day is | Used in conjunction with other criteria to perform a check at a set time (i.e. "When the time of day is 18:00 and the device is in any geofence...") | |
| When the time of day is between | Used in conjunction with other criteria (i.e. "When the devices enters any geofence and the time of day is between 06:00 and 21:00...") | |