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

EvgenyShatilo

Tacho functionality update: when sending the command request_tachograph_file, the server queries tachocheck, now if the ignition is turned off the command will be rejected. Previously, a warning log event was simply output which did not reject the command.
Just information. That for guaranteed operation of the tachograph, data is required on the CAN bus and the ignition is ON. If at least one of these conditions is not met the command will be rejected. All other warnings are for informational purposes only.

namo

Teltonika protocol has been updated: removed mac.address field from ble.beacons arrray ( see namo )

EvgenyShatilo

Tacho functionality update: Fixed a bug where commands were sent too frequently outside the automatic upload interval.

EvgenyShatilo

Tacho functionality update: Fixed a bug with automatic uploading mechanism. Previously, the interval timer might not work in some devices.

EvgenyShatilo

Tacho functionality update: warning messages in the log caused by the tachocheck setting will no longer be displayed. These messages are not actually useful, as the tracker may still work fine with the tachograph despite the warnings, and vice versa. In any case, the setting values are updated and can be viewed. TACHO > Checking the tachograph configuration.

baja

New device type added: Teltonika FTC927

For the models FTC921 and FTC961 removed settings:

on_demand_activation_source_din1 (added by mistake, non operating)
action setting setdigout_1 (non operating based on real traffic from the device)
The action commands can be sent via custom command interface.

shal

Devices with connected camera: Fixed request_video and take_photo commands when using "Configured camera" format with camera index parameter.

EvgenyShatilo

Tacho functionality update: Authorization algorithm change. The server now completes authorization not upon the tracker's command, but when the tachograph explicitly states that it has granted access to the data for reading.
This is due to the fact that some Stoneridge firmware versions may continue to access the server even after authorization has been completed.

shal

For all devices with Bluetooth settings (FMB/FMC/FMM series, OBD trackers, SAS trackers) fixed Eddystone UID validation in auth_beacons setting - now correctly accepts 16-byte Eddystone UIDs.

EvgenyShatilo

Tacho functionality update:

Numerous minor fixes and improvements.
Improved file parsing stability and file name recognition.
Processing of first-generation tachograph files has been disabled, as from January 1, 2025, the use of Gen1 analog and digital tachographs in international transport is PROHIBITED.
Improved file reloading management if a file was skipped for some reason.

EvgenyShatilo

Tacho functionality update: Changes in the "Tacho WEB settings" functionality. This setting is used only for configuring NON-flespi server address for downloading data via the Tacho Web mechanism.
To download tachograph data, please use the command or download scheduler in the device configuration. Using the flespi.gw host in the settings is now prohibited. Attempting to configure the flespi.gw address will result in an error.

All current settings that currently have the flespi.gw address saved will be automatically disabled, meaning the server will send the "setparam 200:0" command to disable this feature. A similar check has been added when an empty server address is used, as this may interfere with downloading tachograph data using the command.

EvgenyShatilo

Fixed a bug in previous tachoweb changes where the server would send a tachoweb command when logging in to a device before the server had responded. This could cause some trackers to stuck in certain cases. In the vast majority of cases, everything should be fine.
If any issues arise, the cpureset command restores the tracker to normal operation.

shal

Fixed parsing of VehicleRegistrationNumber in tachograph files — non-ASCII plate numbers (European diacritics, Cyrillic, Greek) are now correctly decoded using proper ISO character set encoding. Also improved null-byte trimming in all tachograph text fields (names, addresses, plate numbers).

EvgenyShatilo

Added protection against the use of TachoWeb functionality.

If the device is connected to the main channel and has a TachoWeb configuration, the server will detect this and send a command to the device to disable it.
If the device has a flespi server as a secondary address and connects to download data via TachoWeb, the server will disconnect with the error "Tacho data download session cannot be active without a command. The TachoWeb mechanism is unavailable, it must be disabled in the device configuration."

Note: downloading tachograph data for the Teltonika protocol is only possible using the "Request tachograph file" command and auto upload mechanism using device configuration.

bird

Bugfix in BLE beacon data parsing (AVL IDs 548, 11317, 10828, 10829, 10831): unknown beacon parameter IDs no longer cause connection drops — they are now skipped gracefully with a warning logged to device logs.