FleetControl now offers the option to create and manage credentials for your OneAPI message queues (RabbitMQ). It also allows you to subscribe or unsubscribe to specific event topics so that you only consume the event data you actually need to support your booking application’s workflows or supplement data you otherwise collect.
If you are interested in integrating INVERS OneAPI or experimenting with it, simulated vehicles are a great way to get started. They behave like real vehicles, except they are purely virtual. Not only can they provide realistic data like vehicle states and entire trips, you can also interact with them using FleetControl and OneAPI.
We have added the option to choose the unit FleetControl displays distances and speeds in. You can now select either metric (kilometers) or imperial (miles) units.
Users with the full Fleet Settings permission can adjust the units displayed by default for the entire fleet. This fleet-wide setting is located under Administration > Base Fleet Settings. Additionally, every user can set a personal preference by navigating to My Profile > Settings.
Customers exceeding the legal speed limit during rentals cannot only lead to fines but also to crashes, putting your vehicles in danger of falling out of service. Until now, speeding events were only accessible in FleetControl, making their rich data easy to access manually but difficult to harness in your applications. As of today, you can consume speeding events from our API.
The Trips feature can provide you with rich aggregated data on your fleet’s usage. It allows you to easily track the movement of your vehicles, identify the intricate patterns of your rentals, and quickly spot problematic trips. Trip Viewer not only makes the collected data accessible, it also offers a range of visualizations. Additionally, Trips data is accessible through the API.
Trips is a paid feature. Find out more on our website.
CloudBoxxes equipped with two SIMs can now perform an automatic switch of the SIM whenever a disruption of service is detected for the current SIM.
The feature can only be configured by INVERS.
The synchronization of the Real Time Clock (RTC) is performed more regularly. Under normal conditions, this leads to a typical maximum time drift of about 6 seconds, whereas previously the drift could reach up to 20 seconds.
The mileage value is now additionally stored in non-volatile flash memory so that it can be restored after most failure scenarios. If the backup battery of the CloudBoxx ran out and in other rare scenarios, the total mileage value got lost which lead to the CloudBoxx reporting unreasonable values.
When the CloudBoxx leaves standby mode, the measurement of the board voltage and the backup battery voltage (CloudBoxx Mini only) is now triggered more quickly. This provides more accurate board voltage values in the power-fail and power-recovered events.
We have reworked our user permission system to allow for more customization and control over what fleet users can and can’t do. You can now fine-tune each user’s access to data and configurations by choosing between read & write and read-only permissions.
This way, you can make sure your fleet users can only see and use what they actually need. Check out the updated permissions under Administration > Users within FleetControl.
SmartControl is now available on the App Store. In addition to Android devices, you can now configure, test, and control connected vehicles with iPhones as well. Both app versions offer all functionalities, so your choice of operating system is not going to limit you in any way.
CloudBoxx Mini now supports switching to survival mode to save power. The device enters this mode automatically when the following entry conditions are met:
In this mode, the CloudBoxx is not sharing ready and unaccessible via server. Once in survival mode, the CloudBoxx will wake up in a specific time intervals and perform the following survival mode tasks:
The API routes to access the Alarm Input status and configuration were extended to provide a more generic method to get and update the configuration of the Alarm Inputs and to get the state of the Alarm Inputs. The old methods are still available, but only support Alarm Input 1 and Alarm Input 2.
Warning
Unavailable Alarm Inputs are not displayed in the status anymore. Previously, they were displayed as off. This change currently only affects the CloudBoxx Mini.
The event was added as a generic event for Alarm Input changes, including Alarm Input 1 and Alarm Input 2. The existing events ALARM_INPUT_CHANGED for Alarm Input 1 and ALARM_INPUT_2_CHANGED for Alarm Input 2 are still generated.
The Scooter Input of the CloudBoxx Mini can be used as Alarm Input 5. If the Scooter Input is used to control the vehicle, Alarm Input 5 is unavailable. Alarm Input 3 is available when certain extenders are connected. The current states of Alarm Input 3 and Alarm Input 5 are also accessible over BLE.
The shock, motion, and crash detection internal triggering accuracy has been improved.
A previous limitation has been resolved, so that now the tilt angle is also measured while a shock or motion is active and TILT_STATUS_CHANGED events are generated accordingly. The tilt measurement may fail during active shocks or motion if a measurement is impossible due to external circumstances.
The power consumption of the BLE module has been reduced while the BLE Beacon feature is not configured.
Added support for legacy Eddystone BLE Beacons and support for iBeacons with Extra Byte feature (the Extra Byte is ignored).
The DELETE method has been added to the /status-config and /event-config API routes to allow resetting existing configurations.
The can_values field in the /status route can now show up to 20 values. Previously, it was limited to 16.
The can_description_to_create_events_for field under the /event-config route can now hold up to 32 entries. Previously, it was limited to 16.
The mobile connectivity of the CloudBoxx has been improved. Especially the reconnection speed after a connection loss has been sped up.
Congestion of event and tracking messages, caused by temporary loss of cellular connectivity, is now resolved faster. This reduces the latency of server-side reception of these messages.
The vehicle can now be closed by presenting an RFID tag or card to the card reader even if the access grant for this tag/card has expired. According to the options of the access grant (parameter switch_immobilizer false or true) either only the central lock or both, i.e. central lock and immobilizer, are locked. Such locking of the vehicle with the expired access grant is no longer possible once the next immobilizer or central lock command is triggered, e.g. by API command, by BLE command, or by a different RFID tag with a valid access grant.
The default value for the configuration parameter tracking_heading_change_minimum_threshold has been changed from 60° to 45°.
With Fleet Log, we created a new and upgraded analytics tool, so you always stay on top of your fleet.
Detailed information on your vehicle’s events and states is at your team’s fingertips. Reconstruct what happened by searching for events in certain time frames and comparing vehicle event histories. Enhance your customer support by understanding crashes and reviewing vehicle states. Access information from all your vehicles, regardless of whether they are using a CloudBoxx or OEM telematics.