Teltonika FMC920 and OBDII data

I have Teltonika FMC920 installed on car and connected OBDII elm327 via BT.
I can see in Traccar Manager that some values were added when car ignition is on, so some data from OBD sending to GPS tracker.
For example, data from manager:

{"priority":0,"sat":9,"event":0,"ignition":true,"motion":true,"rssi":5,"io200":0,"io69":1,"in1":true,"io113":99,"io30":0,"io31":20,"io32":50,"io33":255,"io35":34,"io38":255,"io39":1,"io41":7,"io50":101,"pdop":1.8,"hdop":1.0,"power":14.396,"io24":0,"battery":4.103,"io68":63,"io40":319,"io51":14347,"io52":23,"operator":25503,"odometer":21202662,"distance":0.0,"totalDistance":2.163401182575188E7,"hours":640767540}

But there is no possibility to see what means io40 or io38. Moreover i can see this data only when press "More data" on my device in app.

How can i use this data in notifications and know what data is Oil Temp or Engine RPM?

Additional question: if some "io" value is not here it means that my obd dongle doesn't send it?
Is there some recommendations about choosing good dongle that will send at least Engine Oil Temp and Engine RPM?

You can use computed attributes to convert raw IO values into something useful.

And you can also display it in the popup if you want.

It would be great to see it in popup.
Could you give a hint how to do that with computed attributes? At least with one (io31). I will figure out how to do others.

By the way in my log file i just see only this info:

2025-02-27 08:45:22  INFO: [Tfbbee681: teltonika < 42.113.31.187] 00000000000000898e01000001954627100000122f87c11e13b19d007c003108000f0000001b001000ef0100f00100150500c800004501000101007164001e00001f0f0020590021fd00231e00260000270b002907003265000900b5000e00b6000a004238420018000f00430ff400440000002800e6003337dc00340012000200f10000639f00100143c522000000000100008e3d
2025-02-27 08:45:22  INFO: [Tfbbee681] id: 866344055631076, time: 2025-02-27 08:45:20, lat: 50.34071, lon: 30.51048, speed: 8.1, course: 49.0
2025-02-27 08:45:22  INFO: [Tfbbee681: teltonika > 42.113.31.187] 00000001
2025-02-27 08:45:25  INFO: [Tfbbee681: teltonika < 42.113.31.187] 00000000000000898e010000019546271bb800122f8a8d1e13b427007e00080a00080000001b001000ef0100f00100150500c800004501000101007164001e00001f150020590021fc00232600260600270b002909003265000900b5000b00b60008004238050018000800430ff400440000002801290033385200340018000200f10000639f00100143c52900000000010000814e
2025-02-27 08:45:25  INFO: [Tfbbee681] id: 866344055631076, time: 2025-02-27 08:45:23, lat: 50.34078, lon: 30.51055, speed: 4.3, course: 8.0
2025-02-27 08:45:25  INFO: [Tfbbee681: teltonika > 42.113.31.187] 00000001
2025-02-27 08:45:26  INFO: [Tfbbee681: teltonika < 42.113.31.187] 00000000000000898e010000019546271fa000122f8a2a1e13b510007f01530a00080000001b001000ef0100f00100150500c800004501000101007164001e00001f120020590021fd00232400261c00270b002909003265000900b5000b00b600080042383a0018000800430ff400440000002801710033386a00340015000200f10000639f00100143c52e000000000100000661
2025-02-27 08:45:26  INFO: [Tfbbee681] id: 866344055631076, time: 2025-02-27 08:45:24, lat: 50.34080, lon: 30.51055, speed: 4.3, course: 339.0
2025-02-27 08:45:26  INFO: [Tfbbee681: teltonika > 42.113.31.187] 00000001
2025-02-27 08:45:27  INFO: [Tfbbee681: teltonika < 42.113.31.187] 00000000000000898e01000001954627238800122f89621e13b5e9008001440a000a0000001b001000ef0100f00100150500c800004501000101007164001e00001f0e0020590021ff00231c00260300270b002907003265000900b5000b00b60008004238560018000a00430ff400440000002801260033386a00340010000200f10000639f00100143c531000000000100000ff3
2025-02-27 08:45:27  INFO: [Tfbbee681] id: 866344055631076, time: 2025-02-27 08:45:25, lat: 50.34082, lon: 30.51053, speed: 5.4, course: 324.0
2025-02-27 08:45:27  INFO: [Tfbbee681: teltonika > 42.113.31.187] 00000001
2025-02-27 08:45:29  INFO: [Tfbbee681: teltonika < 42.113.31.187] 00000000000000898e010000019546272b5800122f86e81e13b7680081013409000c0000001b001000ef0100f00100150500c800004501000101007164001e00001f0e00205900210300232500261d00270b002909003265000900b5000d00b600090042386d0018000c00430ff400440000002801da003337dc00340017000200f10000639f00100143c537000000000100005eca
2025-02-27 08:45:29  INFO: [Tfbbee681] id: 866344055631076, time: 2025-02-27 08:45:27, lat: 50.34086, lon: 30.51046, speed: 6.5, course: 308.0
2025-02-27 08:45:29  INFO: [Tfbbee681: teltonika > 42.113.31.187] 00000001

What kind of hint do you need? We have proper documentation for it:

https://www.traccar.org/computed-attributes/

Sorry, i'm new in traccar.
I found that "io32" is Coolant Temperature.
So i put in
Description - Coolant Temperature
Attribute - io32
Type - number

but with Expression i don't really understand what data to input.

Attribute is the output attribute, so you're not doing it correctly.

Yeap. I tried some variants and now system accept my input
Description - CoolantTemp
Attribute - coolantTemp
Type - number
Expression - (io32 ? io32 : 0)

So how can i now use it in popup. I add this on device settings in popup info, but there is no updates.

Link to your device and then select coolant temperature for popup attributes in preferences.

Great, it working! Thank you!
I see that not all data from obd sending to teltonika tracker. Obd with phone app showing a lot of data about car, but not sending them to tracker. I just wonder this is problem in obd or in tracker? What if I take another dongle, it will give the same data to tracker or not?