Do you have the protocol documentation for your device?
here is an example of one device ,
2025-01-05 14:20:28 INFO: [Ta26f2182: gps103 < 105.235.136.156] imei:864895036407029,tracker,250105132027,,F,132027.000,A,3607.78245,N,00527.52853,E,47.47,153.31,,1,0,0.00%,,;
2025-01-05 14:20:38 INFO: [Ta26f2182: gps103 < 105.235.136.156] imei:864895036407029,tracker,250105132037,,F,132037.000,A,3607.64733,N,00527.60811,E,58.26,155.04,,1,0,0.00%,,;
2025-01-05 14:20:48 INFO: [Ta26f2182: gps103 < 105.235.136.156] imei:864895036407029,tracker,250105132047,,F,132047.000,A,3607.50484,N,00527.69005,E,52.99,156.66,,1,0,0.00%,,;
2025-01-05 14:20:58 INFO: [Ta26f2182: gps103 < 105.235.136.156] imei:864895036407029,tracker,250105132057,,F,132057.000,A,3607.38247,N,00527.75109,E,46.68,151.46,,1,0,0.00%,,;
the device i use are gps103 protocol , already implemented and used to work perfectly , this happened just today
In the original comment you provided very different device and port.
i just found the issue , it was geofence speed limit , i touched them it was 120 , i deleted the 120 and kept the attribute there , i didint delete it , all the devices in those geofence got stuck . now after i went back and rewrote 120 like before all devices started working again
i have many gps device that send positions but the position arent being filtered or decoded and the device statys online in status but the position is not updated , also fixtime and devicetime get stuck when the issue accure
i checked the log and found this error