Pegasus & Core Release Notes for May 2024

Pegasus Release Notes

Alerts
- Fixed alert dialog that wasn’t displaying the map
- Fixed loading maps not showing in the alert dialog
API
- Core
- - Fixes for Titan devices that were reporting incorrect battery level on certain events
  - Improvements in route deletion
  - Identification of where data comes from when being received via the JSON receiver, there’s a new field in the devices API `protocol.application`
  - Support for track point events more frequently from third-party devices (requires a modification to each device)
  - Queclink GV58LAU – Power indicators were integrated
  - Queclink GV310LAU photo integration
  - Concox JM-VL103 – Added ignition events
  - Heartbeat events are no longer marked as invalid locations in tracking
  - Queclink GV350M – Fixed BLE temperature incorrect parsing
  - Fixed platform freezes when selecting unit grouping on the map
- Third-Party Device
  - Support ibutton persistence for Queclink
- Retransmitters
  - Satcom lite – data now supports speed and heading information and added low battery event
  - Surfsight – fixed gaps in GPS events
  - Surfsight – updated the labels to generate ignition events
  - Surfsight – video processing improvements
  - Updates for Wisetrack BHP webservice, new requirements for RUT and Driver ID
  - Surfsight – Improvements in data received live from multiple groups
- Others
  - Performance improvements and distribution of reports in large sites
  - Added more Polish/Czech translations
Tracking
- Tracking improvements to events with multimedia, highlighting events on the map, media browser, and layout changes
- Fixed online state for devices reporting for’udp’
- Fixed video component that was showing a different hour for the same event
- Fixed display the odometer value in the vehicles download file (.xlsx)
- Added polish translations in the transaction tooltip in Cemex Status Cycle view
- Fixed video component that was showing a different hour for the same event
Geofences
- Fixed error when trying to create a geofence
Geofence (JSON Schema Settings)
- Improvements to property templates to allow default values and validate required fields
- Fixed the creation of a geofence that was returning an error
Organization
- Fixed bug that showed wrong trip criteria for Syrus 4 (“Gateway criterion”, “Ignition Only” and “Event labels” are supported for Syrus 4 devices
Reports
- New Daily Usage Report
- Fuel Report – improvements to fuel loss detection for different sensors
- Trips Report – improvements to the fuel consumption for different sensors
- Activity Details Report – in the CSV the event id was replaced with the trip id
- Speed Report – added a filter to discard millisecond events
- Daily Entity Summary Report – for the odometer columns, the values entered by the user are prioritized if there is no value reported by the ECU or GPS respectively.
- Temperature History – Fixed assets showing in the vehicles column
- Temperature Live – Fixed incorrect temperatures values
- HoS Report – Added name of the entity if at one point it had configured segments
- Trips Report – Fixed data inconsistencies shown when multiple reports were generated on the same day with the same parameters
- Idling Report – Improvements so that the idling values are more similar to the idling events shown in the Activity Details Report
- Daily Entity Summary – Added in the Tab Details the latest odometer values when the entity does not report data in a time range
- Events Report – Supported display of media events with multiple photos and videos
- Speeding Report – Added geofence speed limit option, which allows showing speeding events in the selected geofences
HoS Logbook
- Adjustments and improvements
  - Work events less than 5 minutes will not be shown
  - Work events for the entire selected day are displayed
  - Fixed trips that did not appear on the map
  - Fixed the full screen of the map
  - Fixed events not showing well centered on the map
  - The map will be shown when the entities are not selected
  - Breaks are shown if the entity was resting during the selected dates
  - When the entity exceeded its working time limit, it will show that the cycle is invalid.