Most likely the device is still reporting low battery or maybe there's some issue in the protocol implementation.
Would I see that in the events table?
In the events table:
I see {"alarm":"lowBattery"} on Apr 12 of this year.
And do not see any other alert since.
The Manufacture says the "low battery" is triggered at 3.6v
My units are at 4.7v and 4.8v
Are you saying your device hasn't reported anything since then? Or where do you see it? Maybe if you provide a bit more details and screenshots it would help to understand the problem.
I have hundreds of events but only one "low battery" on April 12
sure, I can send screenshots, how do you want me to send them?
And what images do you want?
Upload them on any image sharing platform you prefer and share the links here. Images of everything that you mentioned and especially showing the problem.
images:
https://ibb.co/5M6ZY5N
https://ibb.co/8xZXn3Q
Please let me know if you need anything else
Where does it say low battery in the UI? I don't see it anywhere on your web app screenshot. Am I missing something? It's also unclear how to map your database data to the screenshot. Which device is that?
If you really want some help, please make an attempt to provide as much information as possible.
The red ! shows tooltip hover "alarm low battery" next to the device name
The device Truck#129 is the deviceid of 151
Truck#129(yabby) is a different device for backup
With more searching, I found
The events table shows one "alarm":"lowBattery" on April 12 but
In the positions table I have a report for today showing in the attributes col:
{"index":11706,"event":6,"pdop":1.2000000000000002,"ignition":true,"alarm":"lowBattery","input":1,"output":0,"status":31,"battery":4.751,"power":14.280000000000001,"deviceTemp":36.0,"rssi":9,"distance":529.7,"totalDistance":1.572449032E7,"motion":true,"hours":462113000}
"alarm":"lowBattery"
So you still have a low battery.
no, the device does not have low battery but looks like Traccar is recording it as low battery.
Note from the manufacture (not sure what to do with this):
The DevStat is in UINT16 and will need to be converted to binary for the bits.
Internal battery good flag is bit 1. The bits start from 0 on the far-right side.
22 = 10110 : this has the battery good flag set.
HeartbeatStatus. Utc:2022/12/05 18:03:05 Lat:391226652 Long:-1086595775 Alt:1389 Spd:0 SAcc:1 Head:134 PDOP:10 PAcc:3 GStat:3 DI:0 DO:0 Stat:22 A1:4797 A2:1268 A3:400 A4:12
If reviewing the status flag of 6 that was seen in the log you have sent over, it would still have the internal battery good flag active. 6 = 110
If you think something is not decoded correctly, please provide a HEX sample and the full protocol documentation.
I have requested full protocol documentation from the manufacture.
Would the hex sample be straight from the traccar log file?
I am using Digital Matters "bolt2" device.
When setting up the device, the batteries are not fully charged and show low battery.
After installation in-vehicle battery is at a good level.
But the "low battery" alert does not go away on the UI.
I am using Traccar 5.5 and the devices have been in use for many months.
Any help would be appreciated