Description
The "Low Battery" rule acts as a safeguard against power-related issues in tracking devices. Some devices may be powered by internal or external batteries (or both). It is designed to respond to specific low-power events, depending on the beacon's capabilities and software. When a device is equipped with a hardware event indicating low primary power or low battery charge, this rule is activated to address the situation. If such a hardware event is absent but the device transmits its battery charge level, the "Low Battery" rule may still function in an emulated mode (depending on the model).
This rule is particularly useful in scenarios where the status of the tracking device's power source is critical for uninterrupted operations. For example, logistics and supply chain businesses rely on this rule to ensure that they are alerted when a tracking device's power source is running low. This allows them to take immediate action, such as replacing batteries or recharging devices, to avoid disruptions in tracking valuable shipments. Additionally, in fleet management, the rule assists in maintaining constant visibility into the locations of vehicles, even during extended missions.
In addition to the aforementioned rule for monitoring external power or backup battery, there is another rule called "Backup battery low". These rules serve distinct purposes in device management.
The "Low battery" rule can be applied as either an external power/internal battery low level hardware event or an emulated one, offering broader utility even if a given model does not support such kind of rule type by its hardware.
On the other hand, the "Backup battery low" rule is mainly for devices with two batteries or those that solely rely on an internal battery when external power isn't available.
The choice between these two rules depends on the specific device being used and integration. Please, refer to the list of devices for the availability of each rule type.
Settings
As this rule is based on hardware configurations, there is not much to configure in the rule itself.
Bind zone to rule:
Enables geofence rule binding.
Geofence:
Fill out the section if the rule needs to work only inside/outside of the selected geofences.
Map button:
Shows bound geofences on the map.
Notifications
Emergency notification:
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.
Push notifications:
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.
SMS notifications:
List of recipients for SMS notifications when the event occurs.
Email notifications:
List of recipients for email notifications when the event occurs.
Schedule
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 "Low battery" alert has a 30-minute reset timer, meaning the alert event will not occur more often than once every 30 minutes. 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.
- In this rule type, users have the flexibility to select multiple trackers which they wish to receive notifications from. The only requirement is that the selected trackers must support Low battery events and the feature must be integrated on the platform for given trackers. This means that users can choose multiple compatible trackers to receive notifications from, allowing them to monitor harsh driving events across various vehicles or devices in a convenient way.
- Whenever the platform identifies a hardware event of this type 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
Event reports
To view the dates when the events were received, you can build the "Report on all events" report.
