YuryAheichyk Fixed lock.state parameter registration in 0x02 Position message, 0x04 Alarm message for 0x2727 protocol devices.
baja New packet types 0x62 and 0x64 supported. They contain extended FMS and CAN data parameters used in new device models.
baja New packet type 0x44 supported: it is responsible for Manual CAN parameters. Indexed parameters manual.can.hex.<INDEX> are now stored for this report type
baja Added support for Escort DU BLE sensors. The protocol now parses Escort angle/RPM sensor data transmitted via BLE ELA tags, extracting engine RPM, tilt angle, temperature, roll/pitch angles, and other sensor parameters.
bird Fixed GOOGLE command response handling for cases when GPS is not fixed — now returns proper command failure result instead of parsing error.
bird New parameter timestamp.key added for all device types to prevent message merging when multiple packets share the same device timestamp.
bird Fixed alarm code mapping for 0x25, 0x26, and 0x27 protocol families — alarm codes were incorrectly treated as decimal values instead of hexadecimal, causing wrong parameter assignments for codes ≥ 0x0A. Alarm codes are now unified to appropriate parameters. Standard position packets (0x02) now include alarm type in parsed output.
bird Bugfix: fixed double comma in all SMS commands (e.g., LOCK,0000,,password# → LOCK,0000,password#) Bugfix: fixed CURR_POS command name in locate setting
