Many GPS trackers come equipped with inputs that can be connected to different tools, such as a car tracker opening sensor, ignition status or an SOS button. By configuring the system accordingly, users can receive notifications for input triggers through the user interface, push notifications, SMS, or email.
The rule is designed to monitor specific discrete inputs and notify users whenever there is a change in their status. These discrete inputs can only have two values: 0 or 1, hence the term "discrete." The rule waits for the specified input to transition from true (1) to false (0), or vice versa, and generates notifications for each change detected.
This functionality enables users to stay informed about the status of connected tools or sensors, providing real-time updates on various events, for example, activation of an SOS button. The ability to receive timely notifications enhances monitoring capabilities and facilitates quick responses to critical situations or events detected by discrete inputs.
The input number field should set the utilized hardware or virtual hardware number of input. The best way to determine which input is responsible for which functionality is to refer to the tracker manufacturer's documentation. The input number should be taken from the needed discrete sensor that is created in the "Device and settings" -> "Sensors and buttons" portlet.
Fill out the section if the rule needs to work only inside/outside of the selected geofences.
Bind zone to rule:
Enables geofence rule binding.
Shows bound geofences on the map.
is used for important events. A message on the screen and the sound signal can only be disabled by clicking on the notification. Please note, some browsers can block notification sound until user activity is recorded on the page.
Receive push notifications on the mobile app and web interface.
Add geofence name to the notification:
Adds names of the specified geofences to the notification text. This option is available only when the "Inside" geofence binding radio button is selected on the "Settings" tab.
List of recipients for SMS notifications when the event occurs.
List of recipients for email notifications when the event occurs.
Set a schedule for when the rule will run. If your schedule indicates that the event should not run some day or time period, it will not appear as a notification in the user interface, and notifications via SMS or email will not be sent. Additionally, you can choose a default template for quick scheduling.
The platform specifics:
- The "Inputs triggering" alert has a 10 seconds reset timer, meaning the alert event will not occur more often than once every 10 seconds. If this type of event occurs in time the rule has been waiting for the reset, this event will be omitted by the platform, including the reports.
- There can be multiple trackers assigned to the rule, meaning the same number of input that is specified in the rule settings is utilised as data sources for each tracker. For example, if you have chosen the 2d input and multiple trackers are selected, the rule will notify the user whenever any of the selected trackers send a change in its input #2.
- Whenever the platform identifies an input event (1 true/high level or 0 false/low level) from a packet of tracker data with no valid coordinates in it, the platform counts the event as a valid one and displays it regardless of whether the event occurred within or outside the bound geofences. The logic of the Inside/Outside radio buttons is also ignored in this case. This behaviour is due to the fact that showing a controversial event once more is better than omitting it.
- If a user only wants to receive an input-triggering alert when there is a change in input from 1 to 0 or from 0 to 1, they can achieve this by clearing the notification text for the respective field if they do not want to receive alerts for. For instance, the screenshot below illustrates how users can receive alerts only for changes from "ON to OFF " while ignoring events from "OFF to ON".
The notification text #1 field is empty in this example.
To view the dates when the events were received, you can build the "Report on all events" report.