ST310 updates for a few minutes and stops
What timezone is set on the server?
In Server America/Sao_Paulo
root@central:/opt/traccar# timedatectl | grep "Time zone"
Time zone: America/Sao_Paulo (-03, -0300)
In device attributes I also put the same
E qual é o resultado do comando date ?
root@central:/opt/traccar# date
Fri Apr 18 11:50:25 PM -03 2025
Certo, você já reiniciou o Traccar ?
I don't see any decoded data in the log. I think you're missing one of the most important stuff there.
I restart traccar every time I make a change.
What points am I forgetting?
I am using port 5011
Zip disabled on the device
And the log I provided is info level
You don't have anything else in the logs? Then it means the data is not decoded at all.
log grep device
2025-04-18 23:58:33 INFO: [T758fcb2f: suntech < 191.38.201.206] ST300STT;007357219;213;603;20250419;02:58:18;139d48;-22.790161;-043.420874;000.000;027.56;17;1;288384;12.07;000010;1;0548;0152029;4.1;0\r
2025-04-18 23:58:48 INFO: [T758fcb2f: suntech < 191.38.201.206] ST300STT;007357219;213;603;20250419;02:58:48;139d48;-22.790153;-043.420873;000.000;027.56;19;1;288384;12.07;000010;1;0549;0152029;4.1;1\r
2025-04-18 23:59:32 INFO: [T758fcb2f: suntech < 191.38.201.206] ST300STT;007357219;213;603;20250419;02:59:18;139d48;-22.790147;-043.420873;000.000;027.56;19;1;288384;12.07;000010;1;0550;0152029;4.1;1\r
2025-04-18 23:59:48 INFO: [T758fcb2f: suntech < 191.38.201.206] ST300STT;007357219;213;603;20250419;02:59:48;139d48;-22.790144;-043.420872;000.000;007.78;19;1;288384;12.07;000010;1;0551;0152029;4.1;1\r
I added the ST310U device, and I didn't do any specific configuration for this device.
If it's not decoding, what should I look at?
More complete log?
You're either not providing full log or you're looking at some old data.
Estou ha 30 minutos tentando enviar mensagem aqui no forum (Too Many Requests)
This is the log I have in the terminal, copied at the time, see the time, now see it without grep
...
2025-04-19 00:16:04 INFO: [T6a8ce137] connected
2025-04-19 00:16:04 INFO: [T6a8ce137: suntech < 191.38.205.172] ST300STT;007357219;213;603;20250419;03:13:18;139d48;-22.790054;-043.420818;000.000;079.78;19;1;288384;12.07;000010;1;0578;0152029;4.1;0\r
2025-04-19 00:16:05 INFO: Event id: 007357219, time: 2025-04-19 00:16:04, type: deviceOnline, notifications: 0
2025-04-19 00:16:05 INFO: [T6a8ce137] id: 007357219, time: 2025-04-19 00:13:18, lat: -22.79005, lon: -43.42082, course: 79.8
2025-04-19 00:16:05 INFO: [T6a8ce137: suntech < 191.38.205.172] ST300STT;007357219;213;603;20250419;03:13:48;139d48;-22.790055;-043.420820;000.000;079.78;19;1;288384;12.07;000010;1;0579;0152029;4.1;0\r
2025-04-19 00:16:05 INFO: Position filtered by Distance filters from device: 007357219
2025-04-19 00:16:06 INFO: [T6a8ce137: suntech < 191.38.205.172] ST300STT;007357219;213;603;20250419;03:14:18;139d48;-22.790056;-043.420821;000.000;079.78;21;1;288384;12.07;000010;1;0580;0152029;4.1;0\r
2025-04-19 00:16:06 INFO: Position filtered by Distance filters from device: 007357219
2025-04-19 00:16:06 INFO: [Tebc09578] connected
2025-04-19 00:16:06 INFO: [Tebc09578: suntech < 191.38.200.88] 02000614807084810003
2025-04-19 00:16:07 INFO: [T6a8ce137: suntech < 191.38.205.172] ST300STT;007357219;213;603;20250419;03:14:48;139d48;-22.790056;-043.420822;000.000;079.78;19;1;288384;12.07;000010;1;0581;0152029;4.1;0\r
2025-04-19 00:16:07 INFO: Position filtered by Distance filters from device: 007357219
2025-04-19 00:16:08 INFO: [T6a8ce137: suntech < 191.38.205.172] ST300STT;007357219;213;603;20250419;03:15:18;139d31;-22.790165;-043.420934;000.278;000.00;13;1;288384;12.07;000010;1;0582;0152029;4.1;0\r
2025-04-19 00:16:08 INFO: Position filtered by Distance filters from device: 007357219
2025-04-19 00:16:09 INFO: [T6a8ce137: suntech < 191.38.205.172] ST300STT;007357219;213;603;20250419;03:15:48;139d48;-22.790170;-043.420917;000.000;000.00;20;1;288384;12.07;000010;1;0583;0152029;4.1;0\r
2025-04-19 00:16:09 INFO: Position filtered by Distance filters from device: 007357219
2025-04-19 00:16:18 INFO: [T6a8ce137: suntech < 191.38.205.172] ST300STT;007357219;213;603;20250419;03:16:18;139d48;-22.790177;-043.420909;000.000;000.00;21;1;288384;12.04;000010;1;0584;0152029;4.1;1\r
2025-04-19 00:16:18 INFO: Position filtered by Distance filters from device: 007357219
2025-04-19 00:16:29 INFO: [T2dcf2998] connected
2025-04-19 00:16:29 INFO: [T2dcf2998: gps103 < 191.38.202.20] ##,imei:863844052919526,A;
2025-04-19 00:16:29 INFO: Event id: 863844052919526, time: 2025-04-19 00:16:29, type: deviceOnline, notifications: 0
2025-04-19 00:16:29 INFO: [T2dcf2998: gps103 > 191.38.202.20] LOAD
2025-04-19 00:16:43 INFO: [Tcb45c1a9] connected
2025-04-19 00:16:48 INFO: [T00a88fda] connected
2025-04-19 00:16:48 INFO: [T00a88fda: watch < 191.38.201.203] [SG*9138828585*0007*LK,0,87]
2025-04-19 00:16:48 INFO: Event id: 9138828585, time: 2025-04-19 00:16:48, type: deviceOnline, notifications: 0
2025-04-19 00:16:48 INFO: [T00a88fda: watch > 191.38.201.203] [SG*9138828585*0002*LK]
2025-04-19 00:16:50 INFO: [T00a88fda: watch < 191.38.201.203] [SG*9138828585*0007*LK,0,87]
2025-04-19 00:16:50 INFO: [T00a88fda: watch > 191.38.201.203] [SG*9138828585*0002*LK]
2025-04-19 00:16:53 INFO: [T6a8ce137: suntech < 191.38.205.172] ST300STT;007357219;213;603;20250419;03:16:48;139d48;-22.790179;-043.420906;000.000;000.00;21;1;288384;12.07;000010;1;0585;0152029;4.1;1\r
2025-04-19 00:16:53 INFO: Position filtered by Distance filters from device: 007357219
2025-04-19 00:16:58 INFO: [T2dcf2998: gps103 < 191.38.202.20] imei:863844052919526,tracker,250419031656,,F,031656.000,A,2246.04601,S,04331.16767,W,0.91,346.26;
2025-04-19 00:16:58 INFO: [T2dcf2998] id: 863844052919526, time: 2025-04-19 00:16:56, lat: -22.76743, lon: -43.51946, speed: 0.9, course: 346.3
2025-04-19 00:17:01 INFO: [T2dcf2998: gps103 < 191.38.202.20] imei:863844052919526,tracker,250419031556,,F,031556.000,A,2246.04637,S,04331.16785,W,0.00,346.26;
2025-04-19 00:17:01 INFO: Position filtered by Distance filters from device: 863844052919526
2025-04-19 00:17:07 INFO: [T2dcf2998: gps103 < 191.38.202.20] imei:863844052919526,tracker,250419031626,,F,031626.000,A,2246.04579,S,04331.16766,W,0.00,346.26;
2025-04-19 00:17:07 INFO: Position filtered by Distance filters from device: 863844052919526
2025-04-19 00:17:18 INFO: [T6a8ce137: suntech < 191.38.205.172] ST300STT;007357219;213;603;20250419;03:17:18;139d48;-22.790181;-043.420905;000.000;000.00;21;1;288384;12.07;000010;1;0586;0152029;4.1;1\r
2025-04-19 00:17:18 INFO: Position filtered by Distance filters from device: 007357219
2025-04-19 00:17:28 INFO: [T2dcf2998: gps103 < 191.38.202.20] imei:863844052919526,tracker,250419031726,,F,031726.000,A,2246.04361,S,04331.16957,W,0.00,291.14;
2025-04-19 00:17:28 INFO: Position filtered by Distance filters from device: 863844052919526
2025-04-19 00:17:29 INFO: [T2dcf2998: gps103 < 191.38.202.20] 863844052919526;
There's only one real date point and the time matches the server, so it means everything is correct:
2025-04-19 00:16:05 INFO: [T6a8ce137] id: 007357219, time: 2025-04-19 00:13:18, lat: -22.79005, lon: -43.42082, course: 79.8
While you are filtering the positions, should it show up?
See the time in the image, and see the log
I know that the tracker has the device date 3 hours ahead, but I couldn't adjust it.
I tried device attributes, I tried in traccar.xml