Duplicate data
You should check logs to see what your device is actually sending.
Are you serious? A screenshot of text logs?
2025-06-21 16:57:47 INFO: [T51291449: h02 < 128.124.25.134] 2491710343961458272006255218612400017130200e047088fbfff5ff001ead500000000000ff01335f582009
2025-06-21 16:57:47 INFO: [T51291449] id: 9171034396, time: 2025-06-20 14:58:27, lat: 52.31021, lon: 17.21700, speed: 47.0, course: 88.0
2025-06-21 16:57:49 INFO: [T51291449: h02 < 128.124.25.134] 2491710343961458272006255218612400017130200e047088fbfff5ff001ead500000000000ff01335f58200a
2025-06-21 16:57:49 INFO: [T51291449] id: 9171034396, time: 2025-06-20 14:58:27, lat: 52.31021, lon: 17.21700, speed: 47.0, course: 88.0
2025-06-21 16:57:51 INFO: [T51291449: h02 < 128.124.25.134] 2491710343961458272006255218612400017130200e047088fbfff5ff001ead500000000000ff01335f58200b
2025-06-21 16:57:51 INFO: [T51291449] id: 9171034396, time: 2025-06-20 14:58:27, lat: 52.31021, lon: 17.21700, speed: 47.0, course: 88.0
2025-06-21 16:57:53 INFO: [T51291449: h02 < 128.124.25.134] 2491710343961458272006255218612400017130200e047088fbfff5ff001ead500000000000ff01335f58200c
2025-06-21 16:57:53 INFO: [T51291449] id: 9171034396, time: 2025-06-20 14:58:27, lat: 52.31021, lon: 17.21700, speed: 47.0, course: 88.0
2025-06-21 16:57:55 INFO: [T51291449: h02 < 128.124.25.134] 2491710343961458272006255218612400017130200e047088fbfff5ff001ead500000000000ff01335f58200d
2025-06-21 16:57:55 INFO: [T51291449] id: 9171034396, time: 2025-06-20 14:58:27, lat: 52.31021, lon: 17.21700, speed: 47.0, course: 88.0
2025-06-21 16:57:57 INFO: [T51291449: h02 < 128.124.25.134] 2491710343961458272006255218612400017130200e047088fbfff5ff001ead500000000000ff01335f77220e
2025-06-21 16:57:57 INFO: [T51291449] id: 9171034396, time: 2025-06-20 14:58:27, lat: 52.31021, lon: 17.21700, speed: 47.0, course: 88.0
2025-06-21 16:57:59 INFO: [T51291449: h02 < 128.124.25.134] 2491710343961458272006255218612400017130200e047088fbfff5ff001ead500000000000ff01335f77220f
2025-06-21 16:57:59 INFO: [T51291449] id: 9171034396, time: 2025-06-20 14:58:27, lat: 52.31021, lon: 17.21700, speed: 47.0, course: 88.0
2025-06-21 16:58:01 INFO: [T51291449: h02 < 128.124.25.134] 2491710343961458272006255218612400017130200e047088fbfff5ff001ead500000000000ff01335f772210
2025-06-21 16:58:01 INFO: [T51291449] id: 9171034396, time: 2025-06-20 14:58:27, lat: 52.31021, lon: 17.21700, speed: 47.0, course: 88.0
2025-06-21 16:58:03 INFO: [T51291449: h02 < 128.124.25.134] *HQ,9171034396,V5,165803,A,5000.5488,N,3400.2566,E,0.00,48,21062
2025-06-21 16:58:03 INFO: [T51291449: h02 < 128.124.25.134] 5,FFFFF9FF,255,1,335f,7722,0#
2025-06-21 16:58:03 INFO: [T51291449] id: 9171034396, time: 2025-06-21 16:58:03, lat: 50.00581, lon: 34.00428, course: 48.0
2025-06-21 16:58:05 INFO: [T51291449: h02 < 128.124.25.134] 2491710343961458272006255218612400017130200e047088fbfff5ff001ead500000000000ff01335f772211
2025-06-21 16:58:05 INFO: [T51291449] id: 9171034396, time: 2025-06-20 14:58:27, lat: 52.31021, lon: 17.21700, speed: 47.0, course: 88.0
I tested one of those HEX samples and it seems like it's decoded correctly. And you can also see that they are all the same, so seems like something is wrong with the device.
Ok, thanks
Today I updated the server from version 6.5 to 6.7.3. I also decided to change the database to MySQL. I don't know if this is related to the updates, but for almost a day one of the trackers has been sending, in addition to real data, another one and the same point where it was yesterday. Rebooting the tracker did not work. Now it has been completely disconnected from the power supply for a day, but I don't think that will help solve the problem. Maybe it is waiting for some kind of response from the server for these transmitted coordinates?
