Teltonika is one of the most popular protocols in flespi platform and in the world of Telematics. This topic will be used to post changes in protocol implementation. Here is a guide how to obtain telematics data from Teltonika devices over API . Supported devices list Teltonika FM1100 Teltonika FM1110 Teltonika FM1120 Teltonika FM1122 Teltonika FM1125 Teltonika FM1200 Teltonika FM1202 Teltonika FM2200 Teltonika FM3001 Teltonika FM3300 Teltonika FM3612 Teltonika FM3622 Teltonika FM36M1 Teltonika FM4100 Teltonika FM4200 Teltonika FM5300 Teltonika FM6300 Teltonika FM6320 Teltonika FMA110 Teltonika FMA120 Teltonika FMA202 Teltonika FMA204 Teltonika FMB001 Teltonika FMB002 Teltonika FMB003 Teltonika FMB010 Teltonika FMC001 Teltonika FMM001 Teltonika FMB110 Teltonika FMB120 Teltonika FMB122 Teltonika FMB125 Teltonika FMB130 Teltonika FMB202 Teltonika FMB204 Teltonika FMB630 Teltonika FMB640 Teltonika FMB641 Teltonika FMC650 Teltonika FMB900 Teltonika FMB910 Teltonika FMB920 Teltonika FMB962 Teltonika FMB964 Teltonika FMT100 Teltonika FMU125 Teltonika FMU130 Teltonika GH5200 Teltonika MTB100 Teltonika TMT250 Teltonika TST100 Teltonika FMM125 Teltonika FMC125 Teltonika FMM130 Teltonika FMC130 Teltonika FMB204 Teltonika FMB140 Teltonika TFT100 Teltonika FMM800 Teltonika FMC800 Teltonika FMM920 Teltonika FMM150 Teltonika FMM13A Teltonika FMC13A Teltonika FMM80A Teltonika FMM650 Teltonika FMB930 Teltonika FMM880 Teltonika FMC880 Teltonika FMC234

BLE temperature and humidity sensor values parsing added to device types FMB

Dear flespi users. We have added a new device type Teltonika TST100 to the list of supported Teltonika devices. With this update we also announce major refactoring of the whole Teltonika protocol implementation for all device types. The newly integrated TST100 already works on the new base, and has all possible settings integrated. In the nearest future we will move all other devices messages parsing and settings operations to the new base. We will report here the log of the migration. The main goal is to make parameters parsing more faster and more precise. Update will touch only "secondary" parameters without influencing time and position parameters.

Teltonika FM3001 moved to new parsing scheme. FM3001 settings have been remastered to correspond Teltonika Parameter list With this update we also moved "Generic Teltonika" device type to new parsing scheme. So if you do not register a device in Telematics Hub and use it only in channel level - the parsing will work with correspondence to Teltonika FMB table as it is the most popular device family. Again, this relates only to "secondary" parameters without influencing time and position parameters.

As described in previous post we do major refactoring here. The list of updates installed today: (and the main): All device types moved to new parsing scheme. Device types added: FMC125 , FMM125 , FMC130 , FMM130 , FMB206 Wide range of settings added for devices: MTB100 , TMT250 . Digital inputs settings remastered to fit clearly to all FMB devices family list.

Device types added: FMC001 , FMM001 And for the OBD device family device settings are almost full. (We skip Geofence settings and Bluetooth OBD settings as they require settings Arrays work which is under construction on Telematics Hub back-end side)

tags 253 and 254 remastered as specified in Teltonika wiki . As for now it is parsed as following: if parameter 253 is: 1 – harsh.acceleration.event = true (parameter 254 is parsed to absolute.acceleration in G) 2 – harsh.braking.event = true (parameter 254 is parsed to absolute.acceleration in G) 3 – harsh.cornering.event = true (parameter 254 is parsed to harsh.cornering.angle in degrees) For FMB640, FMB630, FM3612 and FM36m1 254 tag have been parsed to eco.driving.events.number which is not valid parsing. This parameter will be removed from 254 tag parsing in a week - 20 November, 2019

Teltonika protocol updated: Parameter can.liquid.sensor.fuel.volume is renamed to can.fuel.volume For backward compatibility both parameters are registered for now. Old parameter will be removed 25 Nov 2019. Multiplier 0.1 is applied to can.fuel.volume parameter to get resulting value in liters.

namo Teltonika protocol updated: can.liquid.sensor.fuel.volume parameter is removed

Dear flespi users, there are minor changes in Teltonika protocol: overspeeding.event parameter will be renamed to overspeeding.status parameter. movement.event parameter will be renamed to movement.status . For now both parameters are registered. movement.event and overspeeding.event will be removed on December 4th There are also some bugfixes: Several parameters has wrong signed/unsigned parsing. E.g. external.powersource.voltage generated bad values as it was parsed as signed integer, now it switched to unsigned and has correct values. The same with gsm.lac or gsm.cellid (it was parsed as signed, and now as unsigned, so on big values it was possible incorrect). FMB630 device series parameter can.engine.coolant.temperature parsing fixed towing.event parameter parsing was incorrect. We've fixed it and now correct parameter value is stored in towing.alarm.status gsm.jamming.event parameter parsing was incorrect. We've fixed it to gsm.jamming.alarm.status If you will find something suspicious in Teltonika parameter parsing - please, contact us.

we've implemented special logic for parsing BLE connected devices. Teltonika protocol send it under tag 385 and now it is parsed to parameter ble.beacons which is JSON object, where keys are BLE beacons UUID, and values - JSON objects with beacon parameters, e.g. {... "ble.beacons": { "E2C56DB5-DEAD-BEEF-B060-D0F5A71096E0:1234:9876": { "rssi": -79 }, "E2C56DB5-DEAD-BEEF-B060-D0F5A71096E0:4321:6789": { "rssi": -86 } }, "channel.id": 12345, "event.enum": 385, "event.priority.enum": 0, "ident": "123451234512345", "position.altitude": 126, "position.direction": 60, "position.latitude": 12.3456, "position.longitude": 65.4321 ...} if("undefined"!==typeof hljs)hljs._ha();else if("undefined"===typeof hljsLoading){hljsLoading=1;var a=document.getElementsByTagName("head")[0],e=document.createElement("link");e.type="text/css";e.rel="stylesheet";e.href="//cdnjs.cloudflare.com/ajax/libs/highlight.js/9.7.0/styles/default.min.css";a.appendChild(e);e=document.createElement("script");e.type="text/javascript";e.onload=function(){var d={},f=0;hljs._hb=function(b){b.removeAttribute("data-hljs");var c=b.innerHTML;c in d?b.innerHTML=d[c]:(7

[Changelog] teltonika protocol

namo

Teltonika protocol is updated.

AVL_ID 1388 OEM HV Battery Lifetime Power Use has been fixed and now is registered as signed integer value
flespi parameters renamed:
for AVL_ID 1388 OEM HV Battery Lifetime Power Use: parameter is renamed from can.hybrid.battery.consumed.capacity to can.vehicle.battery.energy.consumed
for AVL_ID 1389 OEM HV Battery Lifetime Charge Power: parameter is renamed from can.hybrid.battery.charged.capacity to can.vehicle.battery.total.charge.energy
Old parameters will be registered along with the new ones for 2 week, until 2025-Jun-12.

The update is related to Teltonika FMB003 device.

namo

Teltonika protocol is updated: old parameters are removed after renaming namo

YuryAheichyk

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

EvgenyShatilo

Change in registration of OBDII standard DTC codes.
Extended manufacturer information contained in the DTC code is now registered in a separate parameter extension inside can.dtc array.
For example:can.dtc:[{"code":"U1000","description":"Unknown","extension":"00","standard":"OBDII"}]

EvgenyShatilo

Major tacho functionality update.
🆕 New Features
• Implemented tachocheck — automatic verification of tachograph connection before executing commands
• Improved handling of automatic tachograph file download: now fully controlled by device configuration. The server will try to download the file until it succeeds. If the task is successfully completed, the timer is updated to the time specified in the device configuration.
• Download starts only if all conditions are met (ignition on, card inserted, valid config), and proceeds in sequence until all file types are received
• File registration now reflects the actual save time, not the start of the download
• Tacho Web is no longer involved in the download process — such connections are ignored. It is recommended to disable this setting or not specify the flespi server as a host.
• tachocheck now adopted for older FMB tracker models

🛠️ Fixes
• Resolved issue with missing driver names causing incorrect or missing warnings
• Eliminated false warnings when second driver name was empty but file was successfully loaded
• Prevented invalid tracker behavior (e.g., sending data without a card or violating protocol)
• Improved validation of tachograph configuration settings

namo

Teltonika protocol updated
Fixed parsing of Param ID 142: Battery Level Percent (flespi parameter battery.level) for FMB630, FMB640, FMB641, FMC640, FMC650, FMM640, FMM650, FM6300 devices.

EvgenyShatilo

Tacho functionality update:

increasing the timeout for the server to wait for a response from the device when loading tachograph data. In practice, the tracker can respond with a pause of up to 5 minutes, which is a lot, but this is reality.
Increasing the timeout FIXED the case with repeating the command to the device when it is not necessary, which as a consequence could lead to a connection break error due to a repeated attempt to start downloading a file when the current one is not yet complete.

namo

Teltonika protocol updated:

New setting added:
For FMC920 added I/O Ignition ON Counter setting, Miscellaneous tab (Param IDs 52100- 52104):

For Sleep Mode setting, System params tab, Bluetooth will stay on in sleep mode (Param ID 60111) setting is fixed
For Network jamming with timeout scenario setting, Miscellaneous tab, title is updated to clearly denote that it's related to network jamming detection configuration (rather than GNSS Jamming detection).

namo

Teltonika protocol is updated.
Logic of parsing of driver name and driver surname parameters has been changed:

Param_IDs 10518 and 10520 are stored as parameters driver.first.name.1 and driver.first.name.2 correspondingly
Param_IDs 10519 and 10521 are stored as parameters driver.last.name.2 and driver.last.name.2 correspondingly
Param_IDs 10518 and 10519, if they both resent in the packet, will be merged and additionally registered as parameter driver.name.1 and param_IDs 10520 and 10521 - as parameter driver.name.2

namo

Teltonika protocol is updated: fixed LVCAN setup setting, CAN tab.

namo

Teltonika protocol is updated.
Distance Since Refuel and I/O Distance Since Refuel settings (Miscellaneous tab) are added for FMB003, FMC003 and FMM003 devices:

Also, Param ID 1443 "OEM Distance Since Refuel" is supported and stored into distance.since.refuel flespi parameter.

This makes it possible to configure the Smart Refueling feature directly from flespi panel.

namo

Teltonika protocol is updated: improved work of Checking the tachograph configuration setting, Tacho tab.

namo

Teltonika protocol updated.
Fixed Battery level, Battery voltage, External voltage, Analog Input 1 I/O and Analog Input 2 I/O settings (Input/Output tab).

baja

GH5200 Keyboard settings added

namo

Teltonika protocol updated.
Added DashCam configuration settings for FMC125 and FMC225 devices, Camera tab:

And added External UART Mode and RS232 Mode settings, Serial Port tab:

EvgenyShatilo

Tacho functionality update: using the main teltonika channel is not allowed in the tacho_web setting. This interferes with the native implementation of flespi for automatic uploading, generates parser errors and also interferes with the normal operation of the tracker. If the server sees that the channel name flespi.gw is used in this setting, the setting will be automatically disabled.
Using a third party server is allowed.

baja

Teltonika protocol refactored. No changes in parsing naming or API scheme of the settings or commands. The noticeable change in the UI is that settings cards in the interface may switch places.

baja

Enhanced Error Code Handling for BLE and EYE Sensors

BLE Humidity Sensors (IDs 86, 104, 106, 108)

Enhanced error handling with dual error code support for improved compatibility:

New error codes: 65535, 65534, 65533

Legacy error codes: 32735, 32734, 32733 (maintained for backward compatibility)

Error mappings:

65535/32735 → "sensor not found"
65534/32734 → "failed sensor data parsing"
65533/32733 → "abnormal sensor state"

EYE Sensor Error Codes

Comprehensive error handling added for all EYE sensor types based on Teltonika configurator documentation:

| Sensor Type | AVL IDs | Error Codes |
|-------------|---------|-------------|
| Temperature | 10800-10803 | 25000, 25001 |
| Humidity | 10804-10807 | 250, 251 |
| Magnet Status | 10808-10811 | 250, 251 |
| Movement Status | 10812-10815 | 250, 251 |
| Pitch Angle | 10816-10819 | 120, 121 |
| Low Battery Status | 10820-10823 | 250, 251 |
| Battery Voltage | 10824-10827 | 250, 251 |
| Roll Angle | 10832-10835 | 250, 251 |
| Movement Count | 10836-10839 | 65000, 65001 |
| Magnet Count | 10840-10843 | 65000, 65001 |

New Message Parameters

Added error code parameters for comprehensive EYE sensor diagnostics:

ble.sensor.battery.voltage.error.code
ble.sensor.low.battery.error.code
ble.sensor.magnet.status.error.code
ble.sensor.magnet.count.error.code
ble.sensor.movement.count.error.code
ble.sensor.pitch.angle.error.code
ble.sensor.roll.angle.error.code

All error parameters store descriptive messages:

"Data Not Received by FM tracker"
"EYE Sensor indicates error"