Location issues with an specific device

federico2 years ago

I am not sure if this post should be here on in the server section. Please apologise if it's wrong.

I am facing a location issue with an specific device and I am not finding the way to fix it.
The device reports positions and I see it correctly in the map, but times to times (quite often) I see the device in a wrong location (an older but recognized one (my house), always the same).
This was a Motorola G6 phone running Traccar Client. I changed the device to a Samsung Galaxy S22 5G. I mean, I uninstalled the client from the old Motorola phone, I installed the client on the new Samsung phone and I configured it with the same device ID. The behavior is the same.
So, I deleted the device from the web and created a new one, with the same device ID. No changes.

At this moment, I am here (in the possition below), with the device in my hand (so this position is correct) :

2022-07-21 10:02:05  INFO: [T326b4737] id: eef4839fc99b3df, time: 2022-07-21 10:02:04, lat: 40.46298, lon: -3.78565, speed: 0.2, course: 13.9, accuracy: 12.4

And I see this in the logs:

2022-07-21 09:31:42  INFO: [Tc11d5fab] id: eef4839fc99b3df, time: 2022-07-21 09:31:41, lat: 40.46297, lon: -3.78566, speed: 0.1, course: 232.9, accuracy: 11.5
2022-07-21 09:35:03  INFO: [T57ee78e9] id: eef4839fc99b3df, time: 2022-07-21 09:35:03, lat: 40.50767, lon: -3.67280, course: 0.0, accuracy: 693.0
2022-07-21 09:36:50  INFO: [T638234da] id: eef4839fc99b3df, time: 2022-07-21 09:36:49, lat: 40.46297, lon: -3.78566, speed: 0.0, course: 53.9, accuracy: 11.7
2022-07-21 09:40:10  INFO: [T0e964735] id: eef4839fc99b3df, time: 2022-07-21 09:40:09, lat: 40.50767, lon: -3.67280, course: 0.0, accuracy: 693.0
2022-07-21 09:41:52  INFO: [Ta95284e4] id: eef4839fc99b3df, time: 2022-07-21 09:41:52, lat: 40.46297, lon: -3.78566, speed: 0.1, course: 144.6, accuracy: 11.9
2022-07-21 09:46:54  INFO: [T46a715f2] id: eef4839fc99b3df, time: 2022-07-21 09:46:53, lat: 40.46297, lon: -3.78565, course: 0.0, accuracy: 12.1
2022-07-21 09:50:10  INFO: [Tbd831784] id: eef4839fc99b3df, time: 2022-07-21 09:50:09, lat: 40.50767, lon: -3.67280, course: 0.0, accuracy: 693.0
2022-07-21 09:51:59  INFO: [T3e3685d0] id: eef4839fc99b3df, time: 2022-07-21 09:51:58, lat: 40.46297, lon: -3.78566, course: 0.0, accuracy: 11.7
2022-07-21 09:55:10  INFO: [Tbd831784] id: eef4839fc99b3df, time: 2022-07-21 09:55:10, lat: 40.50767, lon: -3.67280, course: 0.0, accuracy: 693.0
2022-07-21 09:57:03  INFO: [Tb7892050] id: eef4839fc99b3df, time: 2022-07-21 09:57:02, lat: 40.46297, lon: -3.78566, speed: 0.7, course: 240.7, accuracy: 13.2
2022-07-21 10:00:10  INFO: [Tce29368d] id: eef4839fc99b3df, time: 2022-07-21 10:00:10, lat: 40.50767, lon: -3.67280, course: 0.0, accuracy: 693.0
2022-07-21 10:02:05  INFO: [T326b4737] id: eef4839fc99b3df, time: 2022-07-21 10:02:04, lat: 40.46298, lon: -3.78565, speed: 0.2, course: 13.9, accuracy: 12.4

The different between the correct possitions (lat: 40.46298, lon: -3.78565) and the wrong ones (repored in between) is arround 20km,
I don`t know why I get the wrong "lat: 40.50767, lon: -3.67280" possition repeatedlly inserted in between the correct ones.

Client is configured as follows:
Precition: Medium
Frecuency: 300
Distance: 50
Angle: 0
Offline Buffering and Wake Lock: both checked.

At first I thought it was a client issue, but after changing the phone and getting the same results, I started thinking the problem coulb be on the server side, but now I am lost.
I have other devices working without any issue.

Does any of you can advice on what could be happening?

Thanks in advance.
Federico.-

Anton Tananaev2 years ago

Try changing location precision to high.

federico2 years ago

Hi Anton,
Thanks for your answer.
I changed the location precision to hign, but results seems to be the same.

Now, I am home, so the distance between positions are closer than this morning, but as you can see, the line with the wrong position (lat: 40.50767, lon: -3.67280) is still there, repeating. It's seems like it`s stored somwhere, because it's always exacly the same.

2022-07-21 18:10:41  INFO: [T2a987318] id: eef4839fc99b3df, time: 2022-07-21 18:10:41, lat: 40.50829, lon: -3.67303, speed: 0.0, course: 269.9, accuracy: 1.9
2022-07-21 18:13:41  INFO: [Tc713139f] id: eef4839fc99b3df, time: 2022-07-21 18:13:40, lat: 40.50767, lon: -3.67280, course: 0.0, accuracy: 693.0
2022-07-21 18:15:41  INFO: [T2a987318] id: eef4839fc99b3df, time: 2022-07-21 18:15:41, lat: 40.50820, lon: -3.67312, speed: 0.2, course: 180.0, accuracy: 3.8
2022-07-21 18:18:40  INFO: [Tc713139f] id: eef4839fc99b3df, time: 2022-07-21 18:18:40, lat: 40.50767, lon: -3.67280, course: 0.0, accuracy: 693.0
2022-07-21 18:20:00  INFO: [T2a987318] id: eef4839fc99b3df, time: 2022-07-21 18:20:00, lat: 40.50775, lon: -3.67321, speed: 4.5, course: 180.4, accuracy: 16.2
2022-07-21 18:23:27  INFO: [T2a987318] id: eef4839fc99b3df, time: 2022-07-21 18:23:27, lat: 40.50822, lon: -3.67304, speed: 0.1, course: 8.1, accuracy: 4.1
2022-07-21 18:23:41  INFO: [T78b06774] id: eef4839fc99b3df, time: 2022-07-21 18:23:41, lat: 40.50767, lon: -3.67280, course: 0.0, accuracy: 693.0
2022-07-21 18:28:27  INFO: [T2a987318] id: eef4839fc99b3df, time: 2022-07-21 18:28:27, lat: 40.50825, lon: -3.67301, speed: 0.0, course: 193.6, accuracy: 3.5
2022-07-21 18:28:41  INFO: [T78b06774] id: eef4839fc99b3df, time: 2022-07-21 18:28:41, lat: 40.50767, lon: -3.67280, course: 0.0, accuracy: 693.0
2022-07-21 18:33:27  INFO: [T2a987318] id: eef4839fc99b3df, time: 2022-07-21 18:33:27, lat: 40.50807, lon: -3.67287, speed: 0.0, course: 308.8, accuracy: 2.8
2022-07-21 18:33:41  INFO: [T78b06774] id: eef4839fc99b3df, time: 2022-07-21 18:33:41, lat: 40.50767, lon: -3.67280, course: 0.0, accuracy: 693.0
2022-07-21 18:38:27  INFO: [T2a987318] id: eef4839fc99b3df, time: 2022-07-21 18:38:27, lat: 40.50817, lon: -3.67296, speed: 0.0, course: 358.2, accuracy: 4.7
2022-07-21 18:38:41  INFO: [T78b06774] id: eef4839fc99b3df, time: 2022-07-21 18:38:41, lat: 40.50767, lon: -3.67280, course: 0.0, accuracy: 693.0
Anton Tananaev2 years ago

I noticed that connection ids are alternating. It probably means you have a second device reporting under the same identifier.

federico2 years ago

Correct! an old phone I turned on recently and I forgot the client was installed there.
Great sight Anton!
Thanks!