Engine Hours Mismatch

Greetings all. I am wondering if anyone has encountered this situation before whereby the engine hours logged in summary are not matching the actual engine hours.
In the example below, the ignition was switched on at 14:19 and this is logged in events. It was then switched off at around 17:56 and this is also logged in the events. I also see the ignition status in the route report, however, the summary report only has "a few seconds" under engine hours.
What could be causing it?

PS* This is not happening on all devices. Some are actually working well though it's the same device type

1. I recommend upgrading to the latest version first.
2. Check what attributes your device is reporting. You either have to have hours or ignition value.

Hi Anton..

Thank you for the input.

1. We normally delay upgrading so as to minimize downtime as we have a number of users on the platform but we are planning to upgrade.
2. The device reports ignition value and it is seen in attributes as yes/no. It's a simple GT06 Accurate version. We use the same device on about 95% of all devices on the platform and a high majority of them have been working well on this issue (engine hours). This is happening on a select few.

We had made the assumption that the problem might not be at the device's side since it is reporting the ignition status and Traccar logging the same in Events and Route report so we had assumed it is something that we need to fix server side. We stand to be corrected

To add, the engine hours are also accumulating as expected on the "hours" data field located at the popup box that appears when tracking the vehicle.
The challenge is on summary side

As far as I know, GT06-based devices do not report ignition in every message. That could explain issues.

Hi Anton
Thank you. I was about to add ignition to copy attributes them decided to scan the route report entirely. It looks like every coordinate logged has an ignition value true/false. I assume this would mean that all messages have an ignition value. I stand to be corrected which is why i had to ask before i proceed to add the copy attribute and restart the service.
Here is the report (with sensitive data removed)

Route report hosted on dropbox

Hi Anton. I have now tested a different model of GT06 on a second instance of Traccar. Initially, i was still getting "a few seconds" under Engine Hours in summary. I upgraded the instance to the latest version and after sending new data to test, i get nothing at all under engine hours.
Ignition is present in my copy attributes.
I see the ignition events logged i,e ignition on and ignition off
I also see the ignition status in the route report as shown below.
I am kindly asking for any ideas as to what may be going wrong.
I have attached the screenshots below

Are you using default server configuration without any modifications?

Hi Anton. I have a very few modifications to traccar xml. I am sharing it below so you can kindly advise if there is any potential error. Thank you

<?xml version='1.0' encoding='UTF-8'?>

<!DOCTYPE properties SYSTEM 'http://java.sun.com/dtd/properties.dtd'>

<properties>

<entry key="config.default">./conf/default.xml</entry>
<entry key='status.timeout'>120</entry>
<entry key='database.driver'>com.mysql.cj.jdbc.Driver</entry>
<entry key='database.url'>jdbc:mysql://localhost:3306/traccar?useSSL=false&amp;al>
<entry key='database.user'>removed</entry>
<entry key='database.password'>removed</entry>


<entry key='processing.copyAttributes.enable'>true</entry>
<entry key='processing.copyAttributes'>ignition,driverUniqueId,power,batteryLevel>

<entry key='media.path'>./media</entry>
</properties>

I see you have copying for ignition. That would explain why you see it in every message, but it's not the same thing. Copying happens after engine hour calculation.

Thanks Anton. I will try upgrading the one that is exhibiting the same symptom on a device that transmits ignition in every message and advise if it works

Hi Anton

I am back again with another test.
I now used a GT06 device that transmits ignition status in every packet. I then removed copying ignition.
The Hours accumulator on the popup box actually picks these hours and accumulates them, the ignition changes are logged in events but summary has nothing under Engine Hours. Could you kindly advise what could be wrong?

If it's empty, it probably means hours are missing or zero.

Thanks Anton. Do you mean they are missing on the server side? (Just to make sure i understand). I got a bit lost there since the hours are visible and accumulating on the popup box (The one containing speed etc).