Real-time routes only work if I restart the server and add the device to Traccar, after a few hours it no longer works

Hello, after a few days I have managed to get the Traccar server working on an Oracle VPS.
I express my doubts to you
Say that the device time is always 4 hours ahead of the real time when I click on the car icon on the map.
If I start the traccar server
sudo service traccar restart and delete my gps device from traccar app and add it by putting name and imei and move my car in the Traccar Manager app I can see the real speed and the car moving on the map in real time. The time is now correct
When you stop and park the car, the hour in minutes moves forward 4 hours again.
If that same day I make another trip, yes, if I start my trip at 8:00 p.m. and it lasts 30 minutes, the time is not updated and remains frozen for 30 minutes and I cannot see the speed in real time (mark 0) and I cannot see movement on the map. When I finish the journey it is updated. Please note that if I look at parking/stop and trip reports, they are perfect and with the perfect time.
It seems that when he stays still he doesn't wake up.
The device is a gt02a in traccar identifies it as tk103 using 5002

If I send to port 5001 the log is

2024-01-29 22:48:41  INFO: [Td57af500] connected
2024-01-29 22:48:42  INFO: [Td57af500: gps103 < ip.ip.ip.ip] 283032373034343632393035334250303533353532323730343436323930353329
2024-01-29 22:48:45  INFO: [Td57af500: gps103 < ip.ip.ip.ip] 283032373034343632393035334250303033353532323730343436323930353348534f31613429
2024-01-29 22:48:52  INFO: [Td57af500: gps103 < ip.ip.ip.ip] 283032373034343632393035334252303132343031333056333732332e383137384e30303534332e31303031573030302e303031333434313230342e353330313030303030304c303030303030303029
2024-01-29 22:48:55  INFO: [Td57af500: gps103 < ip.ip.ip.ip] 283032373034343632393035334252303132343031323941333732332e383137384e30303534332e31303031573030302e303139333432373230342e353330313030303030304c303030303030303029
2024-01-29 22:48:58  INFO: [Td57af500: gps103 < ip.ip.ip.ip] 283032373034343632393035334252303132343031323941333732332e383234304e30303534332e31303032573030302e303231343335373037302e333630313030303030304c303030303030303029
2024-01-29 22:49:16  INFO: [Td57af500: gps103 < ip.ip.ip.ip] 283032373034343632393035334250303033353532323730343436323930353348534f31613429
2024-01-29 22:49:18  INFO: [Td57af500: gps103 < ip.ip.ip.ip] 283032373034343632393035334252303032343031323941333732332e383231364e30303534332e30393932573030302e303231343734373033392e363130313030303030304c303030303030303029
2024-01-29 22:49:27  INFO: [Td57af500: gps103 < ip.ip.ip.ip] 283032373034343632393035334250303033353532323730343436323930353348534f31613429
2024-01-29 22:49:27  INFO: user: 1, action: login, from: ip.ip.ip.ip
2024-01-29 22:49:41  INFO: user: 1, action: login, from: ip.ip.ip.ip
2024-01-29 22:54:40  INFO: [Td57af500: gps103 < ip.ip.ip.ip] 283032373034343632393035334252303032343031333056333732332e383232364e30303534332e31303239573030302e303031353434303332362e363830313030303030304c303030303030303029
2024-01-29 22:59:40  INFO: [Td57af500: gps103 < ip.ip.ip.ip] 283032373034343632393035334252303032343031333056333732332e383232364e30303534332e31303239573030302e303031353934303332362e363830313030303030304c303030303030303029
2024-01-29 23:04:31  INFO: [T34cb200a] connected
2024-01-29 23:04:31  INFO: [T34cb200a: autotrack < ip.ip.ip.ip 16030100ee010000ea03033b510ed8ce7aa7eae68e1eccbfb27568fe9fb2485ac1b7b3536f050860694372209cc6d13e308ac65529b8efb35f054ca331831c10a38ee4ea2411b180e3c0922c0026c02bc02fc02cc030cca9cca8c009c013c00ac014009c009d002f0035c012000a1301130213030100007b000500050100000000000a000a0008001d001700180019000b00020100000d001a0018080404030807080508060401050106010503060302010203ff0100010000120000002b0009080304030303020301003300260024001d00202bfa54b03d98a0b7dbba9787de26dcec074c70c94bbb4702db8950d28c617970
2024-01-29 23:04:31  INFO: [T34cb200a] error - Adjusted frame length exceeds 1024: 31447 - discarded - TooLongFrameException (... < WrapperInboundHandler:57 < ... < StandardLoggingHandler:53 < ... < NetworkMessageHandler:37 < ...)
2024-01-29 23:04:31  INFO: [T34cb200a] disconnected

And sending to 5002 which is where it "works"

2024-01-29 23:43:55 INFO: [T45444dfd] id: ididididid, time: 2024-01-30 03:43:54, lat: 37.xxxxx, lon: -5.xxxxxx, course: 326.7
2024-01-29 23:44:16 INFO: [T45444dfd: tk103 < ip.ip.ip.ip] 283032373034343632393035334250303033353532323730343436323930353348534f3161 3429
2024-01-29 23:44:16 INFO: [T45444dfd: tk103 > ip.ip.ip.ip] 283032373034343632393035334150303148534f29
2024-01-29 23:45:02 INFO: [T45444dfd: tk103 < ip.ip.ip.ip] 283032373034343632393035334250303033353532323730343436323930353348534f3161 3429
2024-01-29 23:45:02 INFO: [T45444dfd: tk103 > ip.ip.ip.ip] 283032373034343632393035334150303148534f29
2024-01-29 23:45:48 INFO: [T45444dfd: tk103 < ip.ip.ip.ip] 283032373034343632393035334250303033353532323730343436323930353348534f3161 3429
2024-01-29 23:45:48 INFO: [T45444dfd: tk103 > ip.ip.ip.ip] 283032373034343632393035334150303148534f29
2024-01-29 23:46:34 INFO: [T45444dfd: tk103 < ip.ip.ip.ip] 283032373034343632393035334250303033353532323730343436323930353348534f3161 3429
2024-01-29 23:46:34 INFO: [T45444dfd: tk103 > ip.ip.ip.ip] 283032373034343632393035334150303148534f29

can you help me?
Thank you

Port 5002 is clearly the right one, so trying other ports doesn't make sense.

As for the time issue, you have to check the logs at the time the shift happens. Remember that HEX comes before the decoded data.

Thanks for your response, I will send you tomorrow the log of when it works and when it doesn't.

GPS At 8:43 the car starts moving, at 8:48 stop/park, I delete and add the device with name and imei in traccar. At 8:51 the car starts moving again until 9:09 when it moves away again. Is this record worth it to you? Pastebin is down thank you

https://justpaste.it/ds2se

Here are the the two messages from your log at the specified time:

(027044629053BR00240130A3720.8189N00550.3846W000.0080902219.1401000001L00000000)
(027044629053BR00240130V3720.8189N00550.3846W000.0121403219.1401000000L00000000)

You can see the time value jumped, but you can also see that it reports the location as invalid, so you can potentially filter it out.

Hello, I don't understand what it says in those lines and how I should filter it. Is that why it doesn't work for me if I don't delete and add the device? Is there any documentation

Check the protocol documentation here to understand those lines:

https://www.traccar.org/protocols/

I understand that my protocol is tk103 but I can't understand what I should do I'd appreciate your help

I already gave you one suggestion. Enable invalid data filtering.

Hello, it seems that I solved it like this, it is true that now the time stays frozen if there is no movement, that is not a problem. But in the stop/parked/standing report. If it is not moving from 9 a.m. to 2 p.m. and I move the vehicle and stop it, it does not tell me that it is parked until I move it again.

<entry key='filter.enable'>true</entry>
<entry key='filter.invalid'>true</entry>
<entry key='filter.zero'>true</entry>
<entry key='filter.distance'>20</entry>
<entry key='filter.duplicate'>true</entry>
<entry key='filter.maxSpeed'>130</entry>
<entry key='coordinates.minError'>20</entry>
<entry key='coordinates.maxError'>30000</entry>
<entry key='filter.future'>86400</entry>
<entry key='status.timeout'>120</entry>