Ignition parameter issue with teltonika

hypoclone3 days ago

Good day people,
I have a problem where the ignition parameter is not available on Teltonika FMB125 even though it was included in the configuration settings, but Teltonika FMB920 works fine and reports the Ignition parameter. Please how do i resolve this

Teltonika FMB920
Screenshot 2024-12-20 152137.png

Teltonika FMB125
Screenshot 2024-12-20 152313.png

Anton Tananaev3 days ago

What makes you think it's a server issue? Have you verified that your device is reporting this information?

hypoclone3 days ago

Thank you Anton
I am not sure where the issue is

  1. I have checked the logs but it's not much of help
  2. Similar configuration is on FMB125 and FMB920 and the later reports Ignition
  3. The ignition setting was configured on the device and it is working as seen below

Ignition off
Screenshot 2024-12-20 162957.png

ignition on
Screenshot 2024-12-20 162313.png

Anton Tananaev3 days ago

Why logs are not much help?

hypoclone3 days ago

i really couldn't figure it out from the log, below is a sample which shows Event id: 863844051332192, time: 2024-12-20 01:42:35, type: ignitionOn, notifications: 0, but ignition is not capture in the device detail view

2024-12-20 02:48:20  INFO: [T19784871] id: ~~000000000000000~~, time: 2024-12-20 02:48:18, lat: 6.91165, lon: 3.56941, course: 203.0
2024-12-20 02:48:20  INFO: [T19784871: teltonika > 197.210.70.68] 00000001
2024-12-20 02:48:50  INFO: [T19784871: teltonika < 197.210.70.68] 0000000000000064080100000193e1c0c800000220a3bc041ea070008100cb100000001407f00050001504c80045010100b3000ab5000bb600064263fd180000440000c903a1cb0000d20000d40000d6000001f10000f2b2024e0000000000000000cf000000000000000001000053da
2024-12-20 02:48:50  INFO: [T19784871] id: ~~000000000000000~~, time: 2024-12-20 02:48:48, lat: 6.91165, lon: 3.56941, course: 203.0
2024-12-20 02:48:50  INFO: [T19784871: teltonika > 197.210.70.68] 00000001
2024-12-20 02:49:20  INFO: [T19784871: teltonika < 197.210.70.68] 0000000000000064080100000193e1c13d30000220a3bc041ea070008100cb100000001407f00050001504c80045010100b3000ab5000bb600064263f1180000440000c903a0cb0000d20000d40000d6000001f10000f2b2024e0000000000000000cf0000000000000000010000afae
2024-12-20 02:49:20  INFO: [T19784871] id: ~~000000000000000~~, time: 2024-12-20 02:49:18, lat: 6.91165, lon: 3.56941, course: 203.0
2024-12-20 02:49:20  INFO: [T19784871: teltonika > 197.210.70.68] 00000001
...
Anton Tananaev3 days ago

You should take HEX, decode it and see if your device is reporting the relevant IO value.

hypoclone2 days ago

I tried that anton
on traccar hex-decoder i got
Binary Hex can't be converted to Text

using other online converter i got a mixture of unreadable character as shown below?
[binary data]

Could it be because i am using codec 8 extension?

Anton Tananaev2 days ago

You should use the tool that Teltonika provides.

hypoclone2 days ago

Thank you so much Anton, this gives a better understanding of the whole system.
it turns out that for some strange reasons the ignition parameter is not been sent by Teltonika FMB125
according to teltonika wiki page the property id should be 239

Screenshot 2024-12-20 193338.png
Screenshot 2024-12-20 193413.png

This is from a teltonika FMB920
Screenshot 2024-12-20 194039.png

Thank you once again Anton, i really appreciate your effort!