Mictrack MP91 not showing battery voltage

I am getting a low battery alarm on my Mictrack MP91 device but not able to find battery voltage.
here is the data in "tc_positions" table from the "attributes" field:

{"alarm":"lowBattery","ignition":false,"blocked":false,"charge":false,"odometer":31495800,"rssi":22,"sat":0,"distance":0.0,"totalDistance":2.20782228E7,"motion":false,"hours":200611489000}

How can I get voltage to display?

protocol docs
https://we.tl/t-HkfGV7OEDg

Please provide a sample from logs with a breakdown.

Here are the logs from a bunch of Mictrack devices, this is close to the time of the battery alarm for id: 019172428501.

logs: the device in question is id: 019172428501

2022-12-08 10:08:10  INFO: [T6695db25: huabao < 45.154.16.6] 7e0200007d010191724285010611000000000000000a02547b010677aaff00040000000022120901081401040004ce4ecc14383934343530313230313231303637373733374630011a3101009f173331302c3431302c393631392c354443383731312c3236820200638b1135344443345731423948533830343230328c04000150868d0200958e0117a000d77e
2022-12-08 10:08:10  INFO: [T6695db25: huabao > 45.154.16.6] 7e8001000501917242850100000611020000b57e
2022-12-08 10:08:10  INFO: [T6695db25] id: 019172428501, time: 2022-12-08 10:08:14, lat: 39.09095, lon: -108.50586, course: 0.0

2022-12-08 10:08:18  INFO: [Tf6d191d2: huabao < 45.154.16.6] 7e020000a60191724284951c07000000000000000b025446520678812e00040000010a221209010816010400061089cc14383934343530313230313231303637373638374630011831010e9f173331302c3236302c413131302c314443374630422c32348202008480010a810203ef83011484018285021d1c8601338702034e8801188901168b1135344443345731423046533830353435398c04000198988d0202288e0155a00b50303134302c50303434390f7e
2022-12-08 10:08:18  INFO: [Tf6d191d2: huabao > 45.154.16.6] 7e8001000501917242849500001c070200002c7e
2022-12-08 10:08:18  INFO: [Tf6d191d2] id: 019172428495, time: 2022-12-08 10:08:16, lat: 39.07746, lon: -108.56069, course: 266.0

2022-12-08 10:08:19  INFO: [T53aaffd4: huabao < 45.154.16.6] 7e0200007d010191724285080747000000000000000a025cd2f706596ebe000400000000221209010817010400076942cc14383934343530313230313231303637373639354630011931010f9f173331302c3431302c393630392c354443343130412c3235820200848b1135344443345731423047533830313231388c04000198d48d0202288e0155a0002a7e
2022-12-08 10:08:19  INFO: [T53aaffd4: huabao > 45.154.16.6] 7e8001000501917242850800000747020000eb7e
2022-12-08 10:08:19  INFO: [T53aaffd4] id: 019172428508, time: 2022-12-08 10:08:17, lat: 39.63775, lon: -106.52435, course: 0.0

2022-12-08 10:08:22  INFO: [Tbe0b8584: huabao < 195.226.133.53] 7e020000990191723743290a7d01000000008000000b0255284e067a13ba00040000010c221209010116010400092ebacc1438393434353031323037323138353530373736463001133101118202008f9f163331302c3236302c413146382c3639414130422c31398102021683011a84017c850215758601398702020789010e8b1131465438573342363646454431363337338c040005a1cc8d02016c8e0138a0055030343330e77e
2022-12-08 10:08:22  INFO: [Tbe0b8584: huabao > 195.226.133.53] 7e8001000501917237432900000a7d0200004e7e
2022-12-08 10:08:22  INFO: [Tbe0b8584] id: 019172374329, time: 2022-12-08 10:01:16, lat: 39.13531, lon: -108.66374, course: 268.0

2022-12-08 10:08:35  INFO: [T6695db25: huabao < 45.154.16.6] 7e000200000191724285010612327e
2022-12-08 10:08:35  INFO: [T6695db25: huabao > 45.154.16.6] 7e8001000501917242850100000612000200b67e

2022-12-08 10:08:43  INFO: [T6695db25: huabao < 45.154.16.6] 7e0200007d010191724285010613000000800000000a02547b010677aaff00040000000022120901084701040004ce4ecc1438393434353031323031323130363737373337463001163101009f173331302c3431302c393631392c354443383731312c3232820200638b1135344443345731423948533830343230328c04000150868d0200958e0117a0000e7e
2022-12-08 10:08:43  INFO: [T6695db25: huabao > 45.154.16.6] 7e8001000501917242850100000613020000b77e

2022-12-08 10:08:44  WARN: Geocoder network error - HTTP 403 Forbidden - ForbiddenException (... < JsonGeocoder:126 < NotificationManager:103 < *:148 < BaseEventHandler:40 < ...)

2022-12-08 10:08:46  INFO: [T6695db25] id: 019172428501, time: 2022-12-08 10:08:47, lat: 39.09095, lon: -108.50586, course: 0.0

Mictrack MP91 communication protocol V2.0 file:
https://we.tl/t-brZOpM8wrf

What about breakdown? How do you know that your device is reporting the data?

Only because i saw it listed in the protocol data sheet

Can I add "battery voltage" to attributes? Or do you need to add it?

1. Location Reporting Extension Extension (New after ID 0x80)

0x81 2 Engine speed WORD rpm
0x82 2 Battery voltage WORD 0.1V
0x83 1 Engine load BYTE %
0x84 1 Coolant temperature BYTE -40 ℃
0x85 2 Instantaneous fuel consumption WORD ML/H
0x86 1 Intake air temperature BYTE -40 ℃
0x87 2 Air flow WORD g / s

I'm pretty sure it's already supported in Traccar. That's why I asked you to provide a breakdown of a sample showing that your device is actually reporting it.

I have not found a breakdown sample.

I don't see this in the HuabaoProtocolDecoder file. Maybe I am not experienced with protocols enough to find it.

I looked for "0x82" in the decoder file that I got from the protocol docs on page 18

OBD Expand Protocol

1. Location Reporting Extension Extension (New after ID 0x80)
   0x81 2 Engine speed WORD rpm
   0x82 2 Battery voltage WORD 0.1V
   0x83 1 Engine load BYTE %
   0x84 1 Coolant temperature BYTE -40 ℃
   0x85 2 Instantaneous fuel consumption WORD ML/H

You couldn't find 0x82 in the decoder?

https://github.com/traccar/traccar/blob/master/src/main/java/org/traccar/protocol/HuabaoProtocolDecoder.java#L335-L337

Thanks, I had two versions that I downloaded this week and was looking at the wrong version.
Yes, I see it, thanks