The device is connected to the traccar, but it is not sending a position. (DELETE)

Antonio Junior5 days ago

Greetings, I'm having the following problem and haven't been able to identify the cause. Some devices were sending positions to Traccar normally, but since December 8th, 2025, it connects but doesn't send positions. I didn't find any errors in the logs, and it only works normally again when it's deleted and registered again. Could someone help me? I'm using version 6.9.1.

logs from different devices.

Logs before deletion (not conect)

root@fleettb-backend:~# tail -f /opt/traccar/logs/tracker-server.log | egrep -i "865209075192600"
2025-12-10 15:51:00  INFO: [T545c3b52] id: 865209075192600, command type: custom sent
2025-12-10 15:51:44  INFO: [Tf4bd7ae5: gt06 < 177.69.143.158] 78780d0108652090751926000000c0a40d0a

this device is after deletion( postion ok)

root@fleettb-backend:~# tail -f /opt/traccar/logs/tracker-server.log | egrep -i "869731050000272"
2025-12-10 15:20:39  INFO: [T5ec2c338: gt06 < 200.233.216.106] 78780d01086973105000027200000ed30d0a
2025-12-10 15:20:39  INFO: Event id: 869731050000272, time: 2025-12-10 15:20:39, type: deviceOnline, notifications: 0
2025-12-10 15:20:45  INFO: [T5ec2c338] id: 869731050000272, time: 2025-12-10 15:20:40, lat: -24.35314, lon: -50.66029, course: 0.0
2025-12-10 15:21:16  INFO: [T5ec2c338] id: 869731050000272, time: 2025-12-10 15:21:11, lat: -24.35317, lon: -50.66028, course: 0.0
2025-12-10 15:21:46  INFO: [T5ec2c338] id: 869731050000272, time: 2025-12-10 15:21:41, lat: -24.35317, lon: -50.66028, course: 0.0
2025-12-10 15:22:16  INFO: [T5ec2c338] id: 869731050000272, time: 2025-12-10 15:22:11, lat: -24.35317, lon: -50.66028, course: 0.0
2025-12-10 15:22:17  INFO: [T5ec2c338] id: 869731050000272, command type: custom sent
2025-12-10 15:22:20  INFO: Event id: 869731050000272, time: 2025-12-10 15:22:17, type: commandResult, notifications: 1
2025-12-10 15:22:20  INFO: [T5ec2c338] id: 869731050000272, time: 2025-12-10 15:22:11, lat: -24.35317, lon: -50.66028, course: 0.0, result: GMT:W,0,0
2025-12-10 15:22:46  INFO: [T5ec2c338] id: 869731050000272, time: 2025-12-10 15:22:41, lat: -24.35318, lon: -50.66028, course: 0.0
2025-12-10 15:23:16  INFO: [T5ec2c338] id: 869731050000272, time: 2025-12-10 15:23:11, lat: -24.35318, lon: -50.66029, course: 0.0
2025-12-10 15:23:23  INFO: [T5ec2c338] id: 869731050000272, time: 2025-12-10 15:23:18, lat: -24.35318, lon: -50.66029, course: 0.0
2025-12-10 15:23:46  INFO: [T5ec2c338] id: 869731050000272, time: 2025-12-10 15:23:18, lat: -24.35318, lon: -50.66029, course: 0.0
Mauricio5 days ago

Hello, good afternoon! How are you? Were you able to resolve it? I am having the same problem and I am using the same version of Traccar.

Anton Tananaev5 days ago

First thing I would recommend is obviously upgrading.

Second, you should check full connection session in the logs. Filtering by IMEI will filter a lot of critical information.

Antonio Junior5 days ago

I understand about the update; I've already done the search without filtering by IMEI and no errors appear, only some reports of disconnection, and those aren't the devices involved.