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 .

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

bird

Tachograph: automatic card T protocol switching on authentication failure. When a remote tachograph card authentication fails during the card exchange phase with an error that can be caused by the card using the other ISO 7816 T protocol (T=0 / T=1), the next authentication attempt is opened with the alternate T protocol. This requires Tacho Bridge App 0.8.0-alpha.4 or newer to take effect; older Tacho Bridge App versions are unaffected.

bird

A-GPS network permission settings added for FMB/OBD devices — agps_home_network, agps_roaming_network, agps_unknown_network (params 234/235/236), under the System params tab.

getver read-only setting added for FTC series devices — reports firmware/hardware/IMEI info.

bird

New parameters for FMB125: ultrasonic.fuel.level, ultrasonic.software.state
New setting ACK Type (Connectivity tab) for FMB and OBD device families, selecting how the device considers records delivered (TCP/IP ACK or AVL ACK). Note: codec documentation does not distinguish these options - flespi always sends a TCP acknowledgement for all device types (on login and for regular packets, with the number of parsed records), so AVL ACK is recommended; the TCP ACK option only affects device-side behavior.
Fixed odometer value setting (odoset) not being acknowledged - the device SET confirmation is now recognized.

bird

Bugfix: fixed tacho_web setting not updating correctly when the device reports it as disabled

bird

New parameters for ATC700, ATC704, ATM700, ATM704: AVL ID 236 now registers as alarm.event, and AVL ID 392 as button.id and button.action.type (1 - 1 click; 2 - 2 clicks; 3 - long click).

bird

New settings added for fmX640 family:

Manual CAN Request parameters setup (CAN tab) - configure up to 70 Manual CAN Request elements (Request ID/PGN, RTR, Payload, Request Period, Request Data Length)
Manual CAN Command parameters setup (CAN tab) - configure up to 10 Manual CAN Command slots (CAN Type, CAN ID, Data, Data Length, Send Type, Run On Startup, Target)
mcan_cmd - trigger a configured Manual CAN Command slot, with optional CAN ID and data payload override
mcan_stop - stop a periodic Manual CAN Command slot

bird

New parameters for FMC650 and FMM650 TrailerCAN, mapped from previously unregistered AVL IDs:

13672 -> trailer.vdc.active.state.enum
13673 -> trailer.lateral.acceleration
13675 -> trailer.supply.line.braking.state.enum
13676 -> trailer.stop.lamps.request.state.enum
13678 -> trailer.rop.system.state.enum
13775-13789 -> trailer.tire.air.leakage.rate.axle.N.wheel.M (Pa/sec, 3 axles x wheels 6-10)
13790-13804 -> trailer.tire.temperature.axle.N.wheel.M (Celsius, 3 axles x wheels 6-10)
13809 -> trailer.spring.brake.state.enum

bird

New setting Green Driving added for FMC640, FMC650 and FMM650 devices, Miscellaneous tab.

bird

Bugfix: BLE accessory battery for FTC and ATC devices is now reported as ble.sensor.battery.voltage in volts. It was previously incorrectly registered as ble.sensor.battery.level, which holds a percentage - update integrations reading that parameter.

bird

Codec 17 (0x11) is now supported: buffered serial data forwarded with message timestamp and GNSS position is parsed and registered.

bird

New device types added: Teltonika FTC924, Teltonika FTC920, Teltonika FTM887.

New parameters for FTC/FTM devices: AVL 5 => counter.impulses.2, AVL 359 => scenario.status.2, AVL 360 => scenario.status.3.

bird

New settings for FTC305 and FTM305: Manual CAN command parameters setup, Trigger Manual CAN Command, Stop periodic Manual CAN Command.

bird

ble.sensor.device.name.1 - .10 (AVL IDs 13325-13334) are now registered as readable text instead of a hex string on FTC/FTM/ATC/ATM devices. A sensor previously reported as 4D50315F313531363242 now reports as MP1_15162B.

bird

Custom command now supports an optional response_timeout (45–300 seconds) for connection responses.

EvgenyShatilo

FMC650/FMX640 tachograph parameters update.
Fixed parsing failure when driver 2 name fields (AVL IDs 10520 and 10521) contain all 0xFF bytes, which the tachograph sends when no driver 2 card is inserted.
Previously such messages could not be parsed and the device kept reconnecting without delivering data; now the empty driver 2 name is simply skipped, the same way as it was already done for driver 1.

bird

New settings added for FMC650: DualCam and DashCam camera configuration in the DualCam and DashCam tabs.

YuryAheichyk

FMC640: RS232 port settings
Added COM1 - RS232 and COM2 - RS232 settings (port mode and baudrate) under the Serial port tab. The mode list includes the camera modes — DualCam, DashCam, ADAS and DSM — which previously could only be set with raw getparam / setparam commands.

Media upload: camera type detection
The camera attached to a tracker is now resolved from the RS232 port mode instead of the camera settings byte of the media connection alone. This fixes photo and video upload from ADAS and DSM cameras on FMC640, which reports that byte as zero and so was rejected with Unknown camera connected. The port modes are read from the device automatically, no action required.

bird

New device types added: Teltonika ATC774 (LTE CAT 1) and Teltonika ATM774 (LTE CAT M1).

bird

ADAS I/O data is now available as named, COM-indexed parameters for Teltonika FMB125, FMC125, FMB225, FMC225, FMB630, FMB640, FMB641, FMC640, FMM640, FMC650, FMM650, FM6300 when these devices report ADAS data.

COM-port indexing

Append .1 for COM1/single camera or .2 for COM2 (not front/rear position). Example: adas.speed.1. FMB125/FMC125/FMB225/FMC225 use the COM1 column.

Measurements and signals

| AVL ID: COM1 / COM2 | New parameter | Value |
|---|---|---|
| 600 / 12944 | adas.speed | 0-255 km/h |
| 601 / 12945 | adas.left.turn.signal.status | Boolean: false = off, true = on |
| 602 / 12946 | adas.right.turn.signal.status | Boolean: false = off, true = on |
| 603 / 12947 | adas.brake.signal.status | Boolean: false = off, true = on |
| 604 / 12948 | adas.engine.rpm | 0-65535 rpm |
| 607 / 12951 | adas.lane.left.distance | 0-2.55 meters; converted from centimeters |
| 608 / 12952 | adas.lane.right.distance | 0-2.55 meters; converted from centimeters |
| 609 / 12953 | adas.time.to.collision | 0-25.5 seconds; converted from 0.1-second units |
| 617 / 12961 | adas.ahead.object.distance | 0-150 meters; device value 255 becomes null |
| 618 / 12962 | adas.ahead.object.speed | -128 to 126 km/h; signed speed of the object ahead |
| 620 / 12964 | adas.speed.limit | 1-120 km/h; device value 0 becomes null |
| 621 / 12965 | adas.speed.limit.sensitivity | 0-254%; device value 255 becomes null |

Full states

States have text and numeric .enum outputs, both COM-indexed: adas.lane.departure.left.state.1 = "Event", adas.lane.departure.left.state.enum.1 = 2.

| AVL ID: COM1 / COM2 | New parameters | Numeric value = text |
|---|---|---|
| 605 / 12949 | adas.lane.departure.left.state, adas.lane.departure.left.state.enum | 0=None; 1=Recognized; 2=Event; 3=Disabled |
| 606 / 12950 | adas.lane.departure.right.state, adas.lane.departure.right.state.enum | 0=None; 1=Recognized; 2=Event; 3=Disabled |
| 610 / 12954 | adas.distance.state, adas.distance.state.enum | 0=None; 1=Recognized; 2=Event; 3=Disabled |
| 611 / 12955 | adas.front.vehicle.start.state, adas.front.vehicle.start.state.enum | 0=None; 2=Event; 3=Disabled |
| 612 / 12956 | adas.proximity.state, adas.proximity.state.enum | 0=None; 2=Event; 3=Disabled |
| 613 / 12957 | adas.collision.warning.state, adas.collision.warning.state.enum | 0=None; 2=Event; 3=Disabled |
| 614 / 12958 | adas.pedestrian.state, adas.pedestrian.state.enum | 0=None; 1=Recognized; 2=Event; 3=Disabled |
| 615 / 12959 | adas.recording.state, adas.recording.state.enum | 0=Off; 1=Recording (mic off); 2=Recording (mic on) |
| 616 / 12960 | adas.error.state, adas.error.state.enum | 0=None; 1=Low visibility; 2=Camera blocked |
| 619 / 12963 | adas.speed.limit.recognition.state, adas.speed.limit.recognition.state.enum | 0=None; 2=Overspeed event; 3=Disabled |
| 665 / 12966 | adas.sdcard.state, adas.sdcard.state.enum | 0=Normal; 1=Not detected; 2=Faulty/unsupported; 3=Needs formatting; 4=Unavailable/formatting |
| 666 / 12967 | adas.camera.state, adas.camera.state.enum | 0=Unknown; 1=Not configured; 2=Ready; 3=No communication; 4=Updating FW; 5=Downloading snapshot; 6=Downloading video; FMB640/FMC640/FMM640 only: 7=Uploading to server; 8=Rebooting; 9=Remounting SD |

Migration from legacy outputs

Mapped custom.param.* outputs and the five legacy events below remain alongside the new fields until 2026-10-06, then will be removed. Only the mappings and device types listed here are affected.

Replace custom.param.<AVL ID> using the tables and COM suffix. Example: custom.param.607 becomes adas.lane.left.distance.1 in meters. Raw state codes move to .enum; account for unit conversions and null values.

Replace the legacy true-only events with a check for numeric state 2 in the current message:

| Legacy parameter | Replacement condition |
|---|---|
| adas.lane.departure.event | adas.lane.departure.left.state.enum.N = 2 OR adas.lane.departure.right.state.enum.N = 2 |
| adas.distance.event | adas.distance.state.enum.N = 2 OR adas.proximity.state.enum.N = 2 |
| adas.collision.warning.event | adas.collision.warning.state.enum.N = 2 |
| adas.pedestrian.event | adas.pedestrian.state.enum.N = 2 |
| adas.traffic.sign.violation.event | adas.speed.limit.recognition.state.enum.N = 2 |

N is 1 or 2. For the old combined-event behavior, check either reported port; lane departure combines left/right and distance combines safety-distance/proximity.

bird

AVL ID 17 ("Fuel Consumed counted") now correctly maps to can.tracker.counted.fuel.consumed instead of can.fuel.consumed for fmX640 family devices. AVL ID 107 fixed similarly for legacy device types
Fixed can.direct.fuel.rail.pressure (AVL ID 45) and can.absolute.fuel.rail.pressure (AVL ID 56) multiplier: values were 100x too low