This is by design. If you set latest first, trips and other server calculations might get messed up.
Thanks for your reply
Is there any other gps you recommend can support this without missing up? For example can Get the latest updated date first than send the rest to history table?
I think you misunderstood something. This is how backend designed to process the data.
Understood, and thanks for the clarification.
This creates an issue for users of GPS trackers. If a vehicle goes offline for any reason and remains disconnected for a significant period, the device starts transmitting all the stored historical data once connectivity is restored. As a result, users may have to wait until the backlog is processed before they can see the vehicle’s latest position, which can cause considerable delays in obtaining the current location. Especially in countries where signal go offline every while. do you think we have any solutions that might help these users?
In my opinion and based on feedback from other users, quality of data has higher priority than some delay in processing.
Hi everyone,
I have a low-end GPS device: 303FG GPS tracker
specifically versions V3.7 and V5.3, using the GPS103 protocol in Traccar.
The issue is that when the device goes offline for some time, it later reconnects and starts sending all the stored/historical positions first. Because of that, Traccar keeps processing old positions before showing the latest real-time position, so the “latest update time” can take a long time to become current.
What is the best way to handle this?
Is there any Traccar configuration ?
Any advice from people using 303FG GPS tracker
specifically versions V3.7 and V5.3, devices with Traccar would be appreciated.