Event Duration
Not sure what you mean by that.
Sometimes we need the "event starting" and the "event ending" (or event closing) and also the duration, for example in the speeding event it takes just few seconds, the driver can hit the max speed just for just a second, so we don't need to trigger a notification it can be just a mistake, but if the driver keeps this speed for more than 5 second we can trigger it.
Specifically for speeding, we do have a threshold.
Yes, I saw that in the config file, but I mean it can be useful for other events too, like staying in a geofence for more than X time, idling status or POIs
For geofences we already have separate events for enter and exit.
Yes I know, the idea is, do we have to trigger a notification right after the event is raised? Or we can delay it to avoid any mistake.
We worked with many GPS tracking systems before and now, we switched to Traccar and we are Really satisfied, this feature was useful.
It very much depends on the type of the event. For some events we already have it exactly for that reason. For example movement, stops and speeding.
I think it will be useful for all events, mostly the calculated attributes, temperature sensors… fuel and oil levels, sometimes the sensors sends wrong data or even the gps tracking devices does, and having this delay before triggering the event is helpful to filter this scenarios, well it’s just an idea that we are sharing with you
Dear Team,
At first, I want to thank you for the great job that you've done with Traccar and for making it open source. I wanted to ask you if the event duration is implemented? If no, will it be implemented in the future?