This topic will be used to post changes in topflytech protocol implementation. The list of supported devices: Topflytech T8608D OBDII Topflytech T8808+ Topflytech TLD1-A Topflytech TLD1-DA Topflytech TLW1-10A Topflytech TLW1-4A Topflytech TLW1-8A Topflytech TLW2-12B Topflytech TLW2-2BL Topflytech TLW2-6BL Topflytech TLW2-12BL Topflytech TLP1-LM Topflytech TLP1-P Topflytech TLP1-SM Topflytech TLP1-SF Topflytech TLP2-SFB Topflytech SolarGuard X100 Topflytech SolarGuard X110 Topflytech SolarGuard X200 Topflytech HeroX 100 Topflytech KnightX 100 Topflytech KnightX 300 Topflytech PioneerX 100 Topflytech TLD2-L Topflytech TorchX 100 Topflytech WarriorX 100 Topflytech WarriorX 300 Topflytech PioneerX 101

response from server for 0x04 packet type fixed. Alarm type as last byte was missing.

parameter external.powersource.voltage parsing fixed

TLP1 series device types added: Topflytech TLP1-LM Topflytech TLP1-P Topflytech TLP1-SM

Analog inputs as parameters ain.1 and ain.2 parsing added for TLW-series and T8808+ deivce

can.engine.ignition.status parameter renamed to engine.ignition.status We've also added validation position, speed and voltage parameters to exclude parsing errors and invalid coordinates

We've added parsing for BLE message type (TLW and TLD device series) and OBD message type (TLD device series). Fixed a bug with the GNSS/LBS bit parsing.

Topflytech protocol updated: event.enum parameter is added. Parameter's value corresponds to the alarm code, described in TLP1 series devices' User Manual (downloadable on the official Topflytech website ) Applicable for the following devices: Topflytech TLP1-LM Topflytech TLP1-P Topflytech TLP1-SM

We've added message parameter position.valid to messages with valid position latitude, longitude and altitude

Message type 0x06 - Driver Behavior via Acceleration Message parsing added.

Topflytech protocol updated - digital input 1 is registered in bit0 of parameter din .

[Changelog] topflytech protocol

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

bird

Bugfix: fixed 0x24 WiFi position field alignment for warrior_x100 devices - corrects temperature, odometer, lock state, acceleration values when position has no GNSS fix
New parameter battery.type added for all 0x2727 device types (0 = rechargeable, 1 = non-rechargeable)

bird

Extended VIDRA BLE sensor support: added Caçamba (dump truck) and Carregadeira (loader) modes alongside the existing Betoneira mode. New ble.beacons fields: vehicle.status, bucket.status, shovel.status, rollover.status, motion.counter, motion.counter.overflow.

bird

AES-128-CBC payload decryption is now supported for KnightX 100 devices. Encrypted location and alarm packets are decrypted and parsed into full telemetry (position, speed, battery, alarms, acceleration, mileage).

To use it, set the device's encryption.key configuration field to the MD5 hash (32 hex characters) of the key you programmed on the device with SETKEY. The fixed IV is handled automatically. Devices without an encryption key configured continue to send and parse unencrypted traffic as before.

bird

New device type added: SolarGuard X110

namo

Topflytech protocol is updated.
Parsing of 1-wire devices information (onewire message 0x252523) is refactored.
The update is applicable to the HeroX 100 device type.

bird

New parameters can.doors.position.enum, can.ramp.position.enum, can.doors.status2.enum added for FMS Door Control 1 (ID 19)

bird

Fixed invalid BLE humidity value (655.35%) being registered when sensor reports connection timeout

bird

New parameter support: BLE data code 0x0017 (QuecLink WFK300 keyfob) is now parsed in BLE Message (0x10) and BLE Message with Position (0x12) - reported in ble.beacons with mac, id, battery.voltage and rssi.

bird

WFK300 keyfob (BLE data code 0x0017) on KnightX 100 and SolarGuard X110: the new payload form with the 1-byte Event Type field is now parsed. An SOS keyfob press registers alarm.event; a Heartbeat carries no alarm. The legacy payload form continues to parse unchanged.

bird

New parameter ble.mac.address added for SolarGuard X100 and SolarGuard X110 lock data messages.
Fixed TLV loop in lock data parsing — battery.level was lost when other data types preceded it.

bird

New setting version added for all device types: firmware, hardware, and modem version extracted from login packet (Info tab)

New parameters device.firmware.version, hardware.version, modem.firmware.version added for all device types

EvgenyShatilo

Tachograph live activity parameters standardization

To make tachograph data consistent across all flespi protocols, we introduced unified live driver activity parameters (per card slot, .1 / .2):

tacho.driver.activity.state.enum - current activity: 0 - rest, 1 - work, 2 - drive, 3 - available, 4 - not available, 5 - error
tacho.driver.activity.state - the same as text: rest / work / drive / available / not available / error

The following parameters are deprecated and will be removed on 01.11.2026:

tacho.driver.work.state.enum -> tacho.driver.activity.state.enum (attention: enum values differ from the old ones)
tacho.driver.work.state -> tacho.driver.activity.state (attention: values are now lowercase, "Driver available" is now reported as "available")

Please update your expressions, calculators, plugins and streams before the removal date.