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

YuryAheichyk

The device type FMC650 was added.

Settings were added for TAT100 device.
As TAT100 is an asset tracker that works mostly on battery power for a long time, it might be critical that the current setting value should not be requested from the device. Thus "Settings polling" device configuration field was set to "never" for all devices of such type. If you need the settings to be synced - you may do it in SetBox, or via updating the "Settings polling" field in the device configuration.

"Secondary GPRS server mode" field was added to "Secondary GPRS Server Setup" (applicable for Professional trackers only)

YuryAheichyk

Changed EYE sensor parameters:
custom.param.10824...10827 to eye.sensor.battery.voltage.1...4
custom.param.10804...10807 to eye.sensor.humidity.1...4
custom.param.10820...10823 to eye.sensor.low.battery.status.1...4
custom.param.10808...10811 to eye.sensor.magnet.status.1...4
custom.param.10836...10839 to eye.sensor.movement.count.1...4
custom.param.10812...10815 to eye.sensor.movement.status.1...4
custom.param.10816...10819 to eye.sensor.pitch.angle.1...4
custom.param.10832...10835 to eye.sensor.roll.angle.1...4
custom.param.10800...10803 to eye.sensor.temperature.1...4

We added a new command "Set IO param". This will allow you to configure IO params as you wish.
For example, you want to setup Battery voltage input to generate an event when the voltage leaves the range from 2500mv to 3300mv. The event should have a low priority and should be added to every AVL record.
This is how it can be done using the new command:

This is how it can be configured using Teltonika Configurator tool:

EvgenyShatilo

Changing the naming of parameters:

The change applies to models: FMB001, FMB002, FMB003, FMC001, FMC003, FMM003
389 - can.vehicle.mileage
390 - can.fuel.volume
402 - can.service.mileage
410 - can.vehicle.battery.charging.status
411 - can.vehicle.battery.level
412 - can.vehicle.battery.power.consumption
755 - can.vehicle.remaining.range
1151 - can.vehicle.battery.health
1152 - can.vehicle.battery.temperature

General parameter changes:
can.vehicle.battery.range and can.vehicle.remaining.range now displays values in kilometers.
also added:
543 - can.hybrid.onboard.power.voltage
544 - can.hybrid.onboard.current

Attention!

01.05.2023 the battery.charging.status parameter will be renamed to can.vehicle.battery.charging.status.
The changes have already been added to the server and the parameter are registered with a new name. When the time is reached, the old one will be deleted.

baja

Parsing update for FMB640 series:
ID 10507: (Driver 1 current daily driving time) to parameter tacho.driver.daily.driving.duration.1
ID 10508: (Driver 1 current weekly driving time) to parameter tacho.driver.weekly.driving.duration.1
ID 10509: (Driver 1 time left until new daily rest period) to parameter tacho.driver.daily.before.rest.duration.1
ID 10514: (Driver 2 current daily driving time) to parameter tacho.driver.daily.driving.duration.2
ID 10515: (Driver 2 current weekly driving time) to parameter tacho.driver.weekly.driving.duration.2
ID 10516: (Driver 2 time left until new daily rest period) to parameter tacho.driver.daily.before.rest.duration.2
IDs 10518 + 10519 to parameter driver.name.1
IDs 10520 + 10521 to parameter driver.name.2
ID 10522: (Driver 1 Time Left Until New Weekly Rest Period) to parameter tacho.driver.weekly.before.rest.duration.1
ID 10523: (Driver 2 Time Left Until New Weekly Rest Period) to parameter tacho.driver.weekly.before.rest.duration.2
ID 10528: (Driver 1 Duration Of Next Break Rest) to parameter tacho.driver.next.rest.duration.1
ID 10529: (Driver 2 Duration Of Next Break Rest) to parameter tacho.driver.next.rest.duration.2
ID 10530: (Driver 1 Remaining Time Until Next Break Or Rest) to parameter tacho.driver.remaining.before.rest.duration.1
ID 10531: (Driver 2 Remaining Time Until Next Break Or Rest) to parameter tacho.driver.remaining.before.rest.duration.2

Parsing update for FMB series as notfied here EvgenyShatilo :
battery.charging.status in security state flags renamed to can.vehicle.battery.charging.status. (Old parameter removed)

Together with this baja update, the parameters prefixed with eye.sensor. will be renamed to ble.sensor.

baja

baja remastering of previously added parameters
ID 10828: array parameter visible.beacons renamed to ble.beacons
ID 10829: array parameter found.beacons renamed to ble.beacons with field state: found at each beacon object
ID 10831: array parameter lost.beacons renamed to ble.beacons with field state: lost at each beacon object

ID 11317 now stored to array parameter eye.beacons will be renamed to ble.beacons in 10 days, May 5th

ID 1151 (OEM Battery State Of Health) stored as can.vehicle.battery.health multiplier 0.1 removed
ID 1152 (OEM Battery Temperature) stored as can.vehicle.battery.temperature multiplier 0.01 removed

baja

Device types added:
FMM80A
FMM650
FMB930

baja
eye.beacons duplicated parameter removed
eye.sensor.temperature renamed to ble.sensor.temperature
eye.sensor.humidity renamed to ble.sensor.humidity
eye.sensor.magnet.status renamed to ble.sensor.magnet.status
eye.sensor.movement.status renamed to ble.sensor.movement.status
eye.sensor.pitch.angle renamed to ble.sensor.pitch.angle
eye.sensor.low.battery.status renamed to ble.sensor.low.battery.status
eye.sensor.battery.voltage renamed to ble.sensor.battery.voltage
eye.sensor.roll.angle renamed to ble.sensor.roll.angle
eye.sensor.movement.count renamed to ble.sensor.movement.count

shal

For Teltonika FMC640 series of devices new set of parameters integrated with readings from connected TK Transcan:

freezer.transcan.temperature: Sensor temperature reported by TK Transcan
freezer.transcan.state.enum: Status value as reported by TK Transcan
freezer.transcan.alarm.enum: Alarm value as reported by TK Transcan

baja

Parameters renaming schedule on June 19th:
AVL ID 331 to 334, ble.sensor.payload.hex.1 to ble.sensor.payload.hex.4 renamed to ble.1.custom.payload.hex.1 to ble.4.custom.payload.hex.1. Both parameters are stored now, old names will be removed in a week
New parameters parsing added for IDs 463 to 474. In Teltonika documentation they are described as
BLE X Custom #Y and may be unsigned 4 bytes integer or data chunk in HEX mode
so they are stored as
ble.X.custom.Y for integer mode
ble.X.custom.payload.hex.Y for HEX mode

baja

Parsing update for temperature and humidity sensors: when sensors report the code that shows that the value is incorrect, the parameter with the value will not be stored, but string error code will be stored instead
IDs 72 to 75: parameter sensor.temperature.1 to sensor.temperature.4 extra parameter sensor.temperature.error.code.1 to sensor.temperature.error.code.4
IDs 25 to 28: parameter ble.sensor.temperature.1 to ble.sensor.temperature.4 extra parameter ble.sensor.temperature.error.code.1 to ble.sensor.temperature.error.code.4
IDs 86, 104, 106, 108: parameter ble.sensor.humidity.1 to ble.sensor.humidity.4 extra parameter ble.sensor.humidity.error.code.1 to ble.sensor.humidity.error.code.4

YuryAheichyk

AVL ID 11317 parsing updated, added mac.address and magnet.count parameters to ble.beacons array

baja

Major update in ibutton.code parameter: Teltonika tech team reported to us that all the values for ibutton.code parameter parsed from ID 78 for all the device types are sent in reversed bytes order. So now flespi stores it in reversed order, and we need to reverse it back to be in touch with reality. So now, together with ibutton.code parameter we have parameters ibutton.code.old and ibutton.code.new. Now ibutton.code.old is the same as ibutton.code, ibutton.code.new is made of reversed bytes of ibutton.code. In 2 weeks, August 17th, ibutton.code will become reversed, the same as ibutton.new. In 1 month, September 3rd, ibutton.code.new and ibutton.code.old will be removed. You may now prepare your infrastructure and create a plugin that renames ibutton.code.new to ibutton.code. Contact our team in flespi chat if you need assist with that.

FMB640 series parsing update:
Bugfix in IO ID 109 that is parsed into fms.sfotware.version
FMS Eco driving parameters supported.

Parameter names

fms.event.enum
fms.vehicle.vin
fms.active.driver.id
fms.event.number
fms.coasting.mileage
fms.coasting.fuel.used
fms.coasting.time
fms.ecoroll.mileage
fms.ecoroll.fuel.used
fms.ecoroll.time
fms.braking.mileage
fms.braking.fuel.used
fms.braking.time
fms.braking.number
fms.retarder.mileage
fms.retarder.fuel.used
fms.retarder.time
fms.cruise.mileage
fms.cruise.fuel.used
fms.cruise.time
fms.torque.mileage
fms.torque.fuel.used
fms.torque.time
fms.pto.mileage
fms.pto.fuel.used
fms.pto.time
fms.driving.fuel.used
fms.idle.fuel.used
fms.engine.load.fuel.used
fms.total.mileage
fms.total.fuel.used
fms.total.time
fms.short.stops.number
fms.long.stops.number
fms.parking.brake.number
fms.harsh.acceleration.number
fms.harsh.braking.number
fms.harsh.cornering.number
fms.mileage.speed.range
fms.fuel.used.speed.range
fms.time.speed.range
fms.mileage.rpm.range
fms.fuel.used.rpm.range
fms.time.rpm.range
fms.mileage.torque.range
fms.fuel.used.torque.range
fms.time.torque.range
fms.mileage.braking.range
fms.fuel.used.braking.range
fms.time.braking.range

baja

baja ibutton.code first update postponed to August 24

EvgenyShatilo

DashCam Data Sending Parameters ID parsing parameters update:

Camera ping transmission and TF status checking parameters ID (id 498) recorded as 2 parameters:
camera.report.reason.enum - represented as numeric value.
camera.report.reason - and textual human-readable value with values:

0="Server request"
1="DIN1"
2="DIN2"
3="Crash"
4="Towing"
5="Idling"
6="Geofence"
7="Unplug"
8="Green Driving"

Image sending trigger parameters ID (id 499) recorded as 2 parameters:
camera.state.enum - represented as numeric value.
camera.state - and textual human-readable value with values:

    0="Camera not detected"
    1="No card"
    2="Card mount failed"
    3="Card mounted"
    4="Card faulty"

baja

baja Update installed, ibutton.code parameter has now the same value as ibutton.code.new. If this affects your operations contact flespi team immediately, we'll help you to deal with the problem. It can be done by simple using of ibutton.code.old, which is still available in message parameters

FMX640 series parsing change in AVL ID 548. It is now parsed the same way as other device series according to this specification

baja

The removal of ibutton.code.old and ibutton.code.new parameters postponed to 14th September

baja

baja ibutton.code.old and ibutton.code.new parameters removed

EvgenyShatilo

Teltonika DualCam with IMAGE uploading function is now implemented on flespi: https://wiki.teltonika-gps.com/view/Teltonika_DualCam
The process of uploading photos is integrated and works automatically, provided that the camera is correctly configured. You can also request a photo using the take_photo command.

The photo is loaded in an additional connection. Along with the photo, the media.url parameter is registered, which contains a link for public viewing of the image.

EvgenyShatilo

Corrections have been made to the take_photo photo upload command.
Reasons: there may have been an error with the media file type request.

EvgenyShatilo

Added VIDEO download support for DualCam and DashCam.
The photo is available for all models that can operate the camera: FMB125, FMB225, FMC125, FMC225. Video is currently limited to models only: FMC125, FMC225.
You can request videos and photos on the MEDIA tab, which becomes available when you enable the experimental functionality in your account settings.

When you click on the video download button, an additional window will appear in which you have to select:

Channel for downloading the video file
Indicate the time that will serve as the beginning of the video
Duration of the video. (at the moment, the duration of the video clip is limited to 10 seconds. Minimum value 1 second.)

All necessary information for the video file is recorded in logs and messages: metadata, title, public link to the file.

YuryAheichyk

Teltonika protocol has been updated, new devices were added: