Recently upgraded our development and test servers from version 6.7.3, to 6.10.0 and noticed the Live routes have a problem.
I saw this post which gives an similar visual experience, the live traces are lacking detail, and appear very as the crow flies, rather than the real position detail as per the replay/trips. https://www.traccar.org/forums/topic/delay-in-displaying-the-position-in-the-live-view/ but that talks about websockets, and our dev server is localhost on wsl, and our test server is an unmodified docker deployment of 6.10.0. so there is no reverse proxy to consider lack of websockets. (on that note, i have left developer tools open on a 6.10.0 web browser instance and see multiple socket ws connections (101 status). however on a 6.7.3 browser instance, there is only 1 socket connection (101 status)).
I'm not sure exactly how to replicate it exactly, because if i'm watching a vehicle in real time, the live routes appear to work fine. It seems when I leave my machine (locked), and then later return to my PC, the live traces are missing heaps of resolution of tracking points, and they do not appear to be cleaning themselves up.
ie, here is a image of approx 20KM of live routes that are still visible on the screen
here is another example.
and for reference, here is the same route from the trip report showing how many position points are missing
I do have Web: Live route length attribute set to 20 points. and when watching it in real time, it appears to be a detailed 20 points, as mentioned, when coming back to my pc, it still appears to be 20 points, but lacking alot of details in between.
I have also pointed a 6.10.0 traccar-web deployment at a 6.7.3 production server api instance, and I see the exact same result. So the problem is not on the traccar server api, but appears to be whatever changed going from 6.7.3 -> 6.10.0 in the traccar-web code.
Recently upgraded our development and test servers from version 6.7.3, to 6.10.0 and noticed the Live routes have a problem.
I saw this post which gives an similar visual experience, the live traces are lacking detail, and appear very as the crow flies, rather than the real position detail as per the replay/trips. https://www.traccar.org/forums/topic/delay-in-displaying-the-position-in-the-live-view/ but that talks about websockets, and our dev server is localhost on wsl, and our test server is an unmodified docker deployment of 6.10.0. so there is no reverse proxy to consider lack of websockets. (on that note, i have left developer tools open on a 6.10.0 web browser instance and see multiple socket ws connections (101 status). however on a 6.7.3 browser instance, there is only 1 socket connection (101 status)).
I'm not sure exactly how to replicate it exactly, because if i'm watching a vehicle in real time, the live routes appear to work fine. It seems when I leave my machine (locked), and then later return to my PC, the live traces are missing heaps of resolution of tracking points, and they do not appear to be cleaning themselves up.
ie, here is a image of approx 20KM of live routes that are still visible on the screen
here is another example.
and for reference, here is the same route from the trip report showing how many position points are missing
I do have Web: Live route length attribute set to 20 points. and when watching it in real time, it appears to be a detailed 20 points, as mentioned, when coming back to my pc, it still appears to be 20 points, but lacking alot of details in between.
I have also pointed a 6.10.0 traccar-web deployment at a 6.7.3 production server api instance, and I see the exact same result. So the problem is not on the traccar server api, but appears to be whatever changed going from 6.7.3 -> 6.10.0 in the traccar-web code.