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 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

namo

Added new settings for Topflytech SolarGuard X100, Actions tab:

Lock/Unlock
Modify Lock Password

namo

Topflytech protocol is updated: Digital outputs settings are added for TLW2-6BL, TLW2-12BL and TLW2-12B devices, Input/Output tab:

omol

Topflytech protocol has been updated: protocol field Message Type is stored as report.reason message parameter in flespi.

YuryAheichyk

Topflytech protocol has been updated. BLE ELA sensor parsing added for devices:

YuryAheichyk

Topflytech protocol has been updated: fixed the parsing of the Setup Report Workmode setting response.

YuryAheichyk

Topflytech protocol has been updated. BLE ELA sensor "ID" Format parsing added

YuryAheichyk

Topflytech protocol has been updated, can.fuel.volume parameter added.

YuryAheichyk

Topflytech protocol will be affected by the deleting parameters:

ble.asset.tag.code
ble.sensor.battery.voltage
tire.pressure
tire.temperature
ble.sensor.state
ble.sensor.temperature
ble.sensor.battery.level
ble.sensor.humidity
ble.sensor.illuminance
ble.sensor.light.status
ble.asset.rssi
ble.door.open.status
ble.relay.id
ble.relay.status
battery.low.alarm
to be installed in 2 weeks - Aug 10th, 2023

Instead of these parameters, the array of objects ble.sensors has been added, which contains the specified sensor parameters (such as mac, battery.voltage, tire.pressure, tire.temperature, tire.pressure.state, battery.low.alarm, battery.level, tempeature, humidity, light.status, rssi, door.open.status, relay.status)

YuryAheichyk

YuryAheichyk Topflytech protocol has been updated, changes applied

YuryAheichyk

Topflytech protocol has been updated, fixed device disconnect issue with unknown BLE ELA tag

YuryAheichyk

Topflytech protocol has been updated, added Vibration detection time field to Setup Drag alert setting for TLW series devices

YuryAheichyk

Topflytech protocol has been updated, BLE Fuel Level Sensor parsing added

YuryAheichyk

Topflytech protocol will be affected by the refactoring custom command parameters to be installed in 1 week - Sep 4th, 2023

The "name" field will be removed from the custom command, and the full text of the command will need to be entered in one "payload" field.
The ability to send a custom command via SMS will also be removed. Settings will be used to configure the device via SMS.

YuryAheichyk

YuryAheichyk Updates installed

omol

Topflytech protocol has been updated: implemented parsing of Multiplex Segment parameter instead of outdated Analog Inputs 3-4 according to the latest protocol documentation.

YuryAheichyk

Topflytech protocol has been updated, made some improvements in part of parsing of commands response

omol

Topflytech BLE parameters (ble.sensors array) have been updated:

light.status parameter parsing is fixed according to the updated documentation
illuminance parameter is removed as undocumented

baja

Bugfix for TLW2 series:
parameter din.1 that was stored from the same Digital I/O Status Bit 14 as engine.ignition.status is now stored based on Bit 8. It might differ from engine.ignition.statuts if user sets ignition detection based on voltage, vibration etc.

baja

Parsing behavior update

when device sends the packet 0x81 (that is usually used to respond for commands) but no command from flespi had been sent (e.g. when device responds to SMS in TCP link), then the traffic would be stored as a message with payload.text parameter
Before that, such packets had been skipped

YuryAheichyk

Topflytech protocol has been updated, added BLE tags parsing:

0x0E BLE iBeacon
0x0F BLE Eddystone UID
0x11 BLE Eddystone TLM