Teltonika FMC150 – Attributes suddenly changed (IO → obdSpeed/throttle/etc)

Hello.

I am using Teltonika FMC150 with Traccar.

I noticed a strange behavior. Within a few minutes, Traccar started showing the same data but with different attribute names.

No configuration changes were made on the tracker.

Earlier, Traccar displayed raw IO values:

{
  "id": "XXXXX",
  "attributes": {
    "priority": 0,
    "sat": 14,
    "event": 0,
    "ignition": true,
    "motion": true,
    "rssi": 4,
    "io200": 0,
    "io69": 1,
    "io81": 59,
    "io82": 60,
    "io89": 75,
    "pdop": 1.0,
    "hdop": 0.7,
    "power": 27.818,
    "battery": 4.029,
    "io68": 0,
    "io85": 838,
    "io90": 0,
    "io115": 820,
    "io168": 28,
    "operator": "XXXXX",
    "odometer": 675075,
    "io449": 0,
    "io83": 3296445,
    "io87": 955426320,
    "io103": 1548,
    "io107": 131788852,
    "io123": 0,
    "io132": 3,
    "io517": 61,
    "io518": 0,
    "io388": "<hidden>",
    "distance": 31.2198,
    "totalDistance": 6730567.757,
    "hours": 104200910
  },
  "protocol": "teltonika"
}

A few minutes later, Traccar started showing parsed attributes:

{
  "id": "XXXXX",
  "attributes": {
    "priority": 0,
    "sat": 14,
    "event": 0,
    "ignition": true,
    "motion": true,
    "rssi": 4,
    "sleepMode": 0,
    "io69": 1,
    "obdSpeed": 59,
    "throttle": 60,
    "fuelLevel": 75,
    "pdop": 1.0,
    "hdop": 0.7,
    "power": 27.865,
    "battery": 4.029,
    "batteryCurrent": 0.0,
    "rpm": 848,
    "io90": 0,
    "engineTemp": 83,
    "io168": 28,
    "operator": "XXXXX",
    "odometer": 675108,
    "io449": 0,
    "fuelUsed": 13178885.2,
    "obdOdometer": 955426370,
    "io103": 1548,
    "io123": 0,
    "io132": 3,
    "io517": 61,
    "io518": 0,
    "io388": "<hidden>",
    "distance": 32.1253,
    "totalDistance": 6730599.882,
    "hours": 104202910
  },
  "protocol": "teltonika"
}

The values appear consistent:

io81 → obdSpeed
io82 → throttle
io89 → fuelLevel
io85 → rpm

Questions:

• Can Traccar change IO mapping automatically after restart/update?
• Could this be related to Teltonika decoder behavior?
• What typically causes this attribute renaming?

No tracker firmware/configuration changes were performed.

Thank you.

An update to a newer version can definitely cause something like this. Or maybe you just set/changed the model field.

Thank you for the clarification.

You were absolutely right.

I changed the model field,

@Anton Tananaev @Fan

We are also facing the same mapping issue. All the attributes are in raw io format. What do I need to do change the io mapping to correct naming attributes ?

Thanking you in advance for your prompt response.

Sounds like you have an opposite issue. What model are you using? Have you set the model is the device settings?