Travel report, trip marked zeroed
Have you read the documentation on how trips work?
I've definitely read the documentation and the mod, as it was applied in the XML, didn't have any zero-value trips.
You're just going to ask this question and not help at all? What's the point of this forum?
Then I'm a bit confused about your original comment. Because with your configuration you can easily get trips with zero distance, depending on the data your device reports of course. So if you want some productive discussion here, you should provide some evidence that something was not calculated correctly given the raw positions data.
Perfect, now we have a dialogue.
Perfect, now we have a dialogue. As stated above, in version 6.11.x no trips were reset and recorded; we only had this data in the stops section. That's precisely the question; it's only happening in version 6.12.1. The image mentioned above is highlighted and clearly shows that the device was in the same location, stationary, and was counted as a trip. The device did not move. A trip of 2h 39m was recorded with the vehicle in the same place. Distance of 0km.
Are you sure you're not using the new trips logic?
I'm definitely not; I haven't even added the flag as false. I don't have report.trip.newLogic in the configuration.
Then there should be absolutely no changes to the way trip reports work. All the changes are behind that gate.
Again, you have to review the raw positions data to understand why trips were detected where you didn't expect.
Okay, I'll analyze the logs, look for the data from that moment, but thank you for your inquiry.
Greetings, I've been researching for a while and have data from the device, but it's not the sound that's happening. The data shows:
lat_min = lat_max = -5.797590333333334 (same latitude)
lon_min = lon_max = -35.216113 (same longitude)
total_positions = 1 (ONLY ONE POSITION!)
positions_with_movement = 0 (speed = 0)
The device sent:
15:12:45 → 1st position (latitude: -5.79759, longitude: -35.21611)
16:13:34 → 2nd position (latitude: -5.79761, longitude: -35.21604)
Difference between positions:
Lat: 0.00002 degrees (~2 meters)
Lon: 0.00007 degrees (~7 meters)
Total distance: approximately 9 meters. First position at 15:12:45
Last position at 16:13:34
Time difference: ~1 hour
Calculated distance: ~9 meters
With new settings:
minimalTripDuration=301s → 1 hour > 301s (✓ MEETS)
minimalTripDistance=501m → 9m < 501m (✗ DOES NOT MEET)
SHOULD HAVE BEEN REJECTED! But it wasn't.
<entry key='report.ignoreOdometer'>true</entry>
<entry key='report.trip.minimalTripDistance'>501</entry>
<entry key='report.trip.minimalTripDuration'>301</entry>
<entry key='report.trip.minimalParkingDuration'>181</entry>
<entry key='report.trip.useIgnition'>true</entry>
2026-03-03 15:00:36 INFO: 865011031877559;
2026-03-03 15:01:36 INFO: 865011031877559;
2026-03-03 15:02:36 INFO: 865011031877559;
2026-03-03 15:03:36 INFO: 865011031877559;
2026-03-03 15:04:36 INFO: 865011031877559;
2026-03-03 15:05:36 INFO: 865011031877559;
2026-03-03 15:06:36 INFO: 865011031877559;
2026-03-03 15:07:37 INFO: 865011031877559;
2026-03-03 15:08:36 INFO: 865011031877559;
2026-03-03 15:09:37 INFO: 865011031877559;
2026-03-03 15:10:36 INFO: 865011031877559;
2026-03-03 15:11:36 INFO: 865011031877559;
2026-03-03 15:12:36 INFO: 865011031877559;
2026-03-03 15:12:45 INFO: imei:865011031877559,tracker,260303181244,,F,181244.00,A,0547.85542,S,03512.96678,W,,,,0,0,,,;
2026-03-03 15:12:48 INFO: id: 865011031877559, time: 2026-03-03 15:12:44, lat: -5.79759, lon: -35.21611, course: 0.0
2026-03-03 15:13:36 INFO: 865011031877559;
2026-03-03 15:14:36 INFO: 865011031877559;
2026-03-03 15:15:36 INFO: 865011031877559;
2026-03-03 15:16:36 INFO: 865011031877559;
2026-03-03 15:17:40 INFO: 865011031877559;
2026-03-03 15:19:07 INFO: ##,imei:865011031877559,A;
2026-03-03 15:20:07 INFO: 865011031877559;
2026-03-03 15:21:07 INFO: 865011031877559;
2026-03-03 15:22:07 INFO: 865011031877559;
2026-03-03 15:23:08 INFO: 865011031877559;
2026-03-03 15:24:07 INFO: 865011031877559;
2026-03-03 15:25:07 INFO: 865011031877559;
2026-03-03 15:26:07 INFO: 865011031877559;
2026-03-03 15:27:07 INFO: 865011031877559;
2026-03-03 15:28:07 INFO: 865011031877559;
2026-03-03 15:29:07 INFO: 865011031877559;
2026-03-03 15:30:07 INFO: 865011031877559;
2026-03-03 15:31:07 INFO: 865011031877559;
2026-03-03 15:32:07 INFO: 865011031877559;
2026-03-03 15:33:07 INFO: 865011031877559;
2026-03-03 15:34:09 INFO: 865011031877559;
2026-03-03 15:35:07 INFO: 865011031877559;
2026-03-03 15:36:07 INFO: 865011031877559;
2026-03-03 15:37:07 INFO: 865011031877559;
2026-03-03 15:38:07 INFO: 865011031877559;
2026-03-03 15:39:07 INFO: 865011031877559;
2026-03-03 15:40:07 INFO: 865011031877559;
2026-03-03 15:41:07 INFO: 865011031877559;
2026-03-03 15:42:07 INFO: 865011031877559;
2026-03-03 15:43:07 INFO: 865011031877559;
2026-03-03 15:44:07 INFO: 865011031877559;
2026-03-03 15:45:08 INFO: 865011031877559;
2026-03-03 15:46:07 INFO: 865011031877559;
2026-03-03 15:47:07 INFO: 865011031877559;
2026-03-03 15:48:07 INFO: 865011031877559;
2026-03-03 15:49:07 INFO: 865011031877559;
2026-03-03 15:50:07 INFO: 865011031877559;
2026-03-03 15:51:07 INFO: 865011031877559;
2026-03-03 15:52:07 INFO: 865011031877559;
2026-03-03 15:53:07 INFO: 865011031877559;
2026-03-03 15:54:07 INFO: 865011031877559;
2026-03-03 15:55:07 INFO: 865011031877559;
2026-03-03 15:56:07 INFO: 865011031877559;
2026-03-03 15:57:07 INFO: 865011031877559;
2026-03-03 15:58:07 INFO: 865011031877559;
2026-03-03 15:59:07 INFO: 865011031877559;
2026-03-03 16:00:07 INFO: 865011031877559;
2026-03-03 16:01:07 INFO: 865011031877559;
2026-03-03 16:02:07 INFO: 865011031877559;
2026-03-03 16:03:07 INFO: 865011031877559;
2026-03-03 16:10:07 INFO: 865011031877559;
2026-03-03 16:11:07 INFO: 865011031877559;
2026-03-03 16:12:07 INFO: 865011031877559;
2026-03-03 16:13:07 INFO: 865011031877559;
2026-03-03 16:13:34 INFO: imei:865011031877559,tracker,260303191333,,F,191333.00,A,0547.85654,S,03512.96268,W,,,,0,0,,,;
2026-03-03 16:13:37 INFO: Event id: 865011031877559, time: 2026-03-03 16:13:33, type: deviceStopped, notifications: 0
2026-03-03 16:13:37 INFO: id: 865011031877559, time: 2026-03-03 16:13:33, lat: -5.79761, lon: -35.21604, course: 0.0
Sorry for sending it using the company's username.
This is NOT how the distance is calculated. The distance it taken from attributes.
I will definitely downgrade to version 6.11.1.
There were no changes to how old trip logic works. You're welcome to downgrade, but it won't change anything.
This configuration I'm using was working fine up to version 6.11.x. In version 6.12.x, in the trip reports, a stopped vehicle is being counted as a trip even though the vehicle hasn't left the location.