Missing Overspeed Events in Geofences

Hello everyone,

I'm experiencing an issue with geofences and Overspeed events in Traccar and would appreciate any insights or assistance.

I have set up several geofences with predefined speed limits, but I've noticed that Overspeed events are not always being generated as expected. I'm trying to understand why this is happening. Here are the details of my setup:

• Traccar Version: 5.10
• Configurations:
  1. Created a geofence with the attribute Speed limit = 35 km/h.
     
  2. Linked a vehicle group to this geofence.
  3. Set the configuration parameter event.overspeed.minimalDuration to 0 in my configuration file.
     

Despite these settings, I observed that a particular vehicle exceeded the speed limit of 35km/h within this geofence, but no Overspeed event was triggered. Here is a screenshot of the incident:

Any ideas on why this might be happening or suggestions for troubleshooting would be greatly appreciated.

It seems like everything is configured correctly.

I have another example to share. Consider the device with an identifier ending in 7F46, on December 18, 2023. This device repeatedly exceeded the designated speed limit, yet the Overspeed events were not consistently generated:

1. First Instance: Around 06:11 - The speed was recorded above the limit in the route report, but this did not trigger any event.

   

2. Second Instance: Around 10:30 - There were 4 instances of speed violation. Interestingly, only one of these resulted in an event trigger.

   • Recorded Situations:

   • Generated Event:

It's puzzling why some instances trigger an event while others do not, under seemingly similar conditions.

Wait. I see your data is not reported in the right order. That's why events weren't generated.

Thank you for pointing that out. It's indeed an unusual behavior, as I would understand if the data was only in descending order, suggesting that my device might be sending the most recent positions first due to some buffer issue. However, as you've mentioned, I now see that in some cases the data is sent without any logical sequence, such as = 13:58:11, 13:58:09, 13:11:43, 13:58:08, 13:58:07 (considering server time).

Is there any server-side configuration that can handle these discrepancies? Or do I need to check exclusively on the device to ensure it always sends information in an ascending chronological order?

It has to be fixed on the device side.