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

Bugfix: ignition_detection setting for FMC650, FMB641, FMC640, FMM640, FMM650, FMB640 devices now uses correct bitmask encoding (DIN1-DIN4, Movement, Power Voltage) instead of FMB-style enum

Bugfix: static_filter setting for the same devices now uses correct parameter ID 123 instead of 112

Bugfix: fixed crash on "Config same for all parameters" device response

bird

New settings for FTC devices: Digital Output control (outputs1/outputs2/outputs3, setdigout_1/setdigout_2/setdigout_3 depending on model) — FTC921, FTC927, FTC961, FTC965, FTC305, FTM305, FTC134

bird

Parameter custom.user.id removed.

AVL ID 238 (FMB family) is now reported as bluetooth.device.mac.address (MAC of NMEA Bluetooth receiver connected via auto-connect "User ID" mode).
AVL ID 854 (GH5200, TAT100) is now reported as user.id (decimal string).

bird

New device type added: Teltonika FTM880 4G LTE Cat M1 battery-mounted tracker

bird

gnss_source setting now offers only the GNSS constellation combinations each device family actually accepts, selected from a dropdown instead of independent checkboxes. This prevents configuring device-rejected combinations such as BeiDou+GLONASS. Applies across the FMB/FMC/FMM/OBD/SAS/TAT line and the FMx640 family.

baja

CAN-CONTROL window status (FMB family): mapped AVL IDs 1211-1214 to can.front.left.window.status, can.front.right.window.status, can.rear.left.window.status, can.rear.right.window.status. The legacy custom.param.1211-1214 stay available until 2026-06-17, then are removed.
FTC/FTM family: added Current LTE Band (AVL 1149 → network.lte.band), Fuel Used GNSS (fuel.consumed), Fall Down Detection (fall.status), Immobilizer state, and crash average/max vectors (average./max..acceleration + crash impact/max acceleration, direction, duration).
Added FTM927 device support.

bird

New setting added for FMB/OBD devices: Limit connection errors (Connectivity tab) - enables/disables the device's GPRS connection retry back-off (parameter 2038).

baja

I/O related settings update: the field "Event only" which was boolean became integer to reflect 3 possible states for FMB series: Every record, Event only, Crash record. This is the way Teltonika USB Configuring tool interface works.
the interface in flespi shows this field as a drop down list. FMX640 series and SAS devices remain with 2 options, but were moved to integer with dropdown list for consistency

The command setio schema also change to have integer for "Event only" field.

Parsing update for FMC150:
1158 can.engine.oil.pressure
1159 can.engine.oil.level
1270 can.engine.oil.temperature
1345 can.fuel.economy
1396 can.ambient.air.temperature
1331 can.gear.selected
1332 can.gear.current
custom.param. - prefixed parameters will be stored for a week until June 17th, after that will be no longer registered for these IDs.

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.

bird

Bugfix: AVL ID 235 oil-level indicator is now reported as can.oil.level.low.indicator.status (boolean) for FMB-family devices, instead of can.engine.oil.level (it is a binary indicator, not a percentage).

Bugfix: corrected trailer.axle.load.sum for FMC650 - removed an erroneous x2.0 multiplier; the value is now reported in kg as sent by the device.

bird

Reverted FMB150, FMC150, and FMM150 to 2 digital outputs. These device types no longer expose DOUT3 settings (setdigout_3, outputs3, and the DOUT3 scenario settings) - the standard hardware variant has only 2 digital outputs. Customers with the rare 3-output (QKIB0) FMC150 variant should register the device as FMC130.

bird

FMC150: tachograph data is now mapped to named parameters. See the FMC150 TACHO AVL ID list.