flespi now works with Assistant Telematics devices. The list of supported models: ATL100 AVT110 AVT111 AVT131 AVT20 AVT50 ABT110

Assistant Telematics protocol updated: fixed parsing of can.fuel.level parameter

Added Electric CAN Data parsing

The OBDII DTC codes registration is planned to be changed. Currently, error codes are stored in the can.dtc parameter as an array of strings. To unify with other diagnostic protocol types, errors will be stored as an array of objects. The changes will be applied in 2 weeks, on May 8, 2025 . For reference, two additional parameters have been added: can.dtc.strings - contains errors in the current format (will be removed in 1 month, on May 24, 2025 ) can.dtc.objects - contains errors in the new format (will be removed in 2 weeks, on May 8, 2025 ) can.dtc.strings example: ["P0020","U0001"] can.dtc.objects example: [{"standard":"OBDII","code":"P0020"},{"standard":"OBDII","code":"U001"}]

Added BLE data parsing from AVT20 devices

YuryAheichyk changes applied, can.dtc array contain objects now. For reference, two additional parameters added: can.dtc.strings - contains errors in the old format (will be removed on May 24, 2025 ) can.dtc.objects - contains errors in the new format (will be removed on May 24, 2025 ) can.dtc.strings example: ["P0020","U0001"] can.dtc.objects example: [{"standard":"OBDII","code":"P0020"},{"standard":"OBDII","code":"U001"}]

YuryAheichyk changes applied, can.dtc.strings and can.dtc.objects parameters removed

timestamp parameter is now taken from the Generated time field. position.timestamp - from the GNSS UTC time . send.timestamp parameter removed.

Bugfix: parameter position.timestamp now stored in timestamp. Using position.timestamp instead of timestamp broker the consistency of the track build using messages that came in a batch in one packet.

Added BLE Ranging Distance parameter parsing from ATL100

Assistant-telematics protocol is updated: Bits 26-20 of CAN information Mask 2 ( RPT report) are supported.

[Changelog] assistant-telematics protocol

bird

+DFI (Device Full Information) report is now supported for AVT110 and AVT111 devices. New parameter: can.controller.hardware.version.

bird

Bugfix: AVT110/AVT111 devices with CAN bus sync enabled (firmware v5.03+) no longer crash-loop on connection
New parameter vehicle.model.id added to +RPT messages for AVT110/AVT111 devices (CAN Bus Sync ID)

bird

Fixed parsing of tachograph string fields (driver names, card codes, model) in RPT reports for AVT110 and AVT111 devices. Non-ASCII characters (e.g., European names with umlauts) are now correctly decoded.

bird

Fixed parsing of +DFI tachograph driver fields for AVT111 (firmware 000421+): corrected field order to tacho.driver.card.code.1 / tacho.driver.name.1 / tacho.driver.card.code.2 / tacho.driver.name.2, and added ISO-8859-1 charset decoding for driver name fields (supports Latin-1 characters such as umlauts).

bird

New device type added: Assistant Telematics AVT80.
Added parsing of BLE iBeacon info (ble.beacons), PEO fence and PEO fence overspeed alarm events, and PEO geofence status (geofences.ids.bitmask) for AVT80.

baja

Fixed CAN total-time parameters that were stored in the wrong unit. can.total.engine.idle.time and can.total.engine.cold.time now report hours (corrected values previewed in can.total.engine.idle.time.hours and can.total.engine.cold.time.hours); the originals switch over on June 17, 2026. can.total.cruise.control.time corrected to hours immediately.

EvgenyShatilo

Tacho update AVT110:

The ability to use a command to download tachograph data has been added.
- The full tacho file loading mechanism is supported.
- The format, file name, extension and all file metadata are determined automatically.
Authorization with a company card via TBA.

Note: The automatic download mechanism is currently unavailable (still under development).

namo

Assistant-telematics protocol is updated: Bit 21 of Data mask - RS485 Information Mask is supported.

EvgenyShatilo

Tacho update:

Added automatic download scheduler mechanism.
Bugs fixed.
Improved protocol compliance.

EvgenyShatilo

Tacho update:

fixed a problem where a command could be sent earlier than required.
improved work of the scheduler.

bird

Major auto-upload scheduler changes

The tachograph auto-upload scheduler has been substantially reworked to fix duplicate commands and retry timing.

Fixed duplicate request_tachograph_file commands. Because command enqueueing is asynchronous, a device could receive several copies of the same request in quick succession (up to 3 within one second on production) before the first was registered. Each scheduled request is now stamped the moment it's enqueued, so subsequent packets in that window no longer enqueue duplicates.
Unified retry-by-timeout. Lost commands, expired sessions and offline company cards now all recover through a single retry timeout rather than separate stuck-state handling. Requests also self-expire from the device queue, so stale copies don't pile up across reconnects.
Smarter scheduling. While one file type is being uploaded, other due types wait their turn instead of triggering extra requests, and the company-card availability check runs once per attempt instead of on every packet.
Fixed a scheduler stall. A missing card-in-slot status parameter no longer blocks retries (it previously stalled scheduling on devices that don't report that parameter).

Significant under-the-hood improvements accompany these changes. No configuration changes are required, and scheduler behavior is now more correct without affecting normal protocol operation.

EvgenyShatilo

Tacho update:

The DDD file download session timeout has been increased from 60 to 300 seconds (AVT devices sometimes pause for long periods between packets).
The settings tab has been renamed from "Tachograph" to "Tacho."
Operation 2 ("Send authorization APDU packet") has been removed from the tco setting for internal use.
Operation 2 ("Cancel DDD file request") has been removed from the tco setting ("Tachograph Common Operation").
A separate setting, tacho_cancel_process ("Cancel tacho file request"), has been added to cancel the current DDD file request. It sends the command AT@TCO=...,2,,,0001#, taking into account the sms_password, if set.
When requesting driver data (driver1 and driver2), the start of the period is now explicitly set to activity_from = file_info_timestamp - 28 days, meaning the download depth for a driver card is limited to 28 days.

bird

New parameter ecl.trigger.bitmask added for AVT50 - reports which trigger conditions fired the ECL alarm.
Fixed parsing of PEO polygon fence status (Event Data Mask bits 21/23) for AVT50.

bird

assistant-telematics ABT110:

New setting commands: AT@SSI (Second Server Information) and AT@EDS (External Distance Setting, BLE distance sensor).
AT@GCS Button Working Mode: added power-on with SOS-only-trigger option.
AT@SIS: added Connection Life parameter.

bird

assistant-telematics: Output Alarm Event (Event Type 27) is now decoded for AVT50, AVT80 and AVT110. The output state is reported as dout.1 / dout.2 and, for AVT50 BLE relays, as ble.dout.1…ble.dout.5, together with a descriptive event.name ("Output 1 ON", "BLE Output 3 OFF", etc.). New parameter ble.dout added.

bird

Fixed parsing of neighboring cell information for AVT131 devices. New parameters gsm.mcc and gsm.mnc added for neighbor cells.

bird

Tachograph Information bitfield parsing for AVT110 & AVT111. The Tachograph Information field is now decoded into individual parameters in both +RPT and +DFI reports: tacho.driver.work.state, tacho.driver.work.state.enum, tacho.driver.card.presence, tacho.driver.card.status, tacho.driver.time.state, tacho.driver.time.state.enum, tacho.out.of.scope.condition.status, tacho.motion.status, tacho.driving.direction, tacho.overspeed.status (driver fields indexed [1]/[2]). The raw tacho.performance parameter is removed in favor of these decoded fields. Values outside the documented ranges are reported as protocol warnings.