MinError doesn't work for me
You need to make sure the data was actually reporting in the right order.
Yes, for this device is in order, the first one at 12:25:51 and the second one at 12:25:56.
It's not just these two positions that matter. For example if your device reported 12:29:00 first and then it reported 12:25:51 and 12:25:56, it won't work.
Mmm, how the device could report 12:29:00 first than 12:25:51? Is time in future and I don't having this problem,. I'm trying to understand the whole proccess of filtering, but I didn't catch it. I'll attach a photo of previous positions to check if you can help me.
The same about knots, even if the position is changing due to GPS drifting, it shouldn't calculate or throw a >0 speed.
It could report time in the future because of some malfunction. But it also could report old buffered data after reporting new data. Both cases you will get similar result.
Mmm, you're right but the device report old buffered data with a real timestamp of the position, then how Traccar handles that? it should show the packet timestamp and not the received timestamp, even if it a buffered data, this buffered data have a date/time. Filters only consider serverTime? or consider deviceTime to apply filters?
The problem is that filters only have access to the latest position by fix time, which might not be the same as previous position in this case.
I'm having a problem with minError and filterDistance, it cause me to trigger a lot of false positive notifications (device in movement and high speed alarm).
For example I have this two location and the distance between is less than 40m and it should be filtered out.
I have this in my config file.
It cause me a lot of falses positives like high speed, device moving, device stopped, tow (with attribute -> if speed is more than 10 km/h and the ignition is off then throw a tow alarm)
Then I need to solve this.