Traccar 5.5 - reports problem

Lukasz2 years ago

Hi

Question for users who migrated from traccara 4.x to 5.5.
In configuration I have keys:
report.trip.minimalTripDuration - 240s
report.trip.minimalTripDistance - 400m
In traccar 4.x everything worked perfectly.

After migration, I noticed that in trip reports I have trips with duration 0h0m, and distance 0.00km.
Is it so with you too?

Luaksha

Lukasz2 years ago

Comment out all report.trip keys in the configuration. Trips of 0.00 km and 0.00 h appear all the time.
On the other hand, I noticed negative values on one of my devices. It seems that the packets arrived in the right order (the distance was calculated correctly) but there are negative values in the trip report:

Route:

Trip:

I will add that I did the migration in December - so this is new data.

Anton Tananaev2 years ago

You're showing fix time, but where's the server time?

Lukasz2 years ago

In fact, the records were sent in parcels, but the order seems to be correct.

However, more important for me is why the standard settings (all report.trip keys have been commented out) have 0.00km 0h00m trips.

Lukasz2 years ago

Here is a trip report with 0h:00m, 0km trips. By default, it should be 300 seconds and 500 meters.

Anton Tananaev2 years ago

Have you tried the latest version of Traccar?

Lukasz2 years ago

No, I have 5.5. I'm moving one of the devices to a demo server right now. I will see the reports on the demo server.

Lukasz2 years ago

Hi Anton,

I checked the trip report on the demo server (demo3.traccar.org) - and there are trips that should not appear (less than 500m and less than 5 min). Give you login details?

Lukasz2 years ago

I found the cause.
I noticed that on the demo server the trips would appear but then disappear. Additionally, I had duplicate events.
It turned out that the error was caused by:
https://github.com/traccar/traccar/issues/5000
After update everything is fine.
Sorry for the confusion.

Anton Tananaev2 years ago

There was a small bug in the implementation. This should fix it:

https://github.com/traccar/traccar/commit/2ac77554f7771a014d62a6e5eeb381b4650dc4f4

Basically last trip/stop was counted even if didn't fully match the criteria.