Are you using standard traccar without any modifications to the code or configuration? I'm pretty sure it doesn't happen to me. We load data from the database on launch.
I am compiling directly from master (testing the solution to the cache invalidation delay), apparently it only has that behavior if I use the master branch, with the 5.10 release it does not happen.
Please try with this change:
https://github.com/traccar/traccar/commit/5cebbfccae29dad81d89591a798d6aa29dd42b75
This worked, thank you very much!
Good morning, I recently updated an old traccar 5.2 to 5.10 and I noticed that if a device is within a geozone and for some reason (for example scheduled server maintenance) it restarts, the geozone entry events are triggered again, This did not happen when geofencesids was within the devices table.
the problem is that users are notified again of entering a geozone and it can be confusing