Hi,
We are facing one issue in engine hours calculation in summary report.It is calculating based on fixed_time which is coming wrong when device is coming out from parking area.One case I have mentioned below.
xxxxxxxxx 76.671838° Yes 0.00 km/h 2023-05-26 12:35:44 Yes 12.274527° 1791 h 19 m 0 2023-05-26 08:48:43 2023-05-26 12:35:44 49645.86 km 78780a13060604000209ab90210d0a
xxxxxxxxx 76.671838° Yes 0.00 km/h 2023-05-26 12:37:00 Yes 12.274527° 1795 h 8 m 0 2023-05-26 12:37:00 2023-05-26 12:37:02 49645.86 km 78781f1217051a070700c7015121440839dadc00d51c019400
if you see here around 4 hours engine hours added because of fixed_time got didnt get updated from device for some pings after ignition turned on.Can somebody pleas suggest how to handle such kind of cases?Is there any configuration to change calculation from fixed time to device time or server time?
thanks
You can override time. There's a configuration parameter for it.
time.override config
Override device time. Possible values are 'deviceTime' and 'serverTime'
Are you talking about this?
this will override device time but my issue is coming because of fix time.
This should override fix time.
Hi,
We are facing one issue in engine hours calculation in summary report.It is calculating based on fixed_time which is coming wrong when device is coming out from parking area.One case I have mentioned below.
if you see here around 4 hours engine hours added because of fixed_time got didnt get updated from device for some pings after ignition turned on.Can somebody pleas suggest how to handle such kind of cases?Is there any configuration to change calculation from fixed time to device time or server time?
thanks