GPS connected and reporting but positions are not recorded.
I see a lot of this error, but I think isn't a blocker to stuck the device reporting.
2024-08-27 11:44:12 WARN: Firebase error - none of the tokens can be null or empty - IllegalArgumentException (... < NotificatorFirebase:111 < Notificator:39 < NotificationManager:140 < ... < *:133 < ... < *:132 < *:177 < ProcessingHandler:186 < ...)And this error but isn't related to the device with problem "F03"
2024-08-27 19:00:03 INFO: Event id: 865235057381283, time: 2024-08-27 18:59:57, type: alarm, notifications: 1
2024-08-27 19:00:07 INFO: [Tf0eaf359: startek < 147.75.51.168] &&e138,865413058612838,000,0,,240827230008,A,18.465768,-69.906733,5,5.1,0,295,42,857552,370|2|2EEB|0005A60C,25,003D,00,00,050D|0193|0000|0000,1,64\r\n
2024-08-27 19:00:07 INFO: [Tf0eaf359] id: 865413058612838, time: 2024-08-27 19:00:08, lat: 18.46577, lon: -69.90673, course: 295.0
2024-08-27 19:00:13 INFO: [T7126e969] error - us1.locationiq.com - UnknownHostException (... < JsonGeocoder:126 < NotificationManager:129 < *:177 < ProcessingHandler:186 < AlertEventHandler:50 < ...)
2024-08-27 19:00:13 INFO: [T7126e969] disconnected
2024-08-27 19:00:13 INFO: Event id: 865235057381283, time: 2024-08-27 19:00:13, type: deviceOffline, notifications: 2
2024-08-27 19:00:33 INFO: [T59f00fb5: startek < 147.75.51.166] &&p159,865235057380608,000,0,,240827230033,A,18.486415,-69.899441,13,0.9,0,213,55,2980197,370|2|2EF5|00047803,31,0000003D,00,00,0512|01A1|0000|0000,1,010000|020000,,71\r\n
2024-08-27 19:00:33 INFO: [T59f00fb5] id: 865235057380608, time: 2024-08-27 19:00:33, lat: 18.48642, lon: -69.89944, course: 213.0
2024-08-27 19:00:47 INFO: [T7839325a] connectedThere's a way to debug deeper? I don't want to restart the server until I solve that.
It could be a blocker. You should definitely solve it first.
But the device that throw this error is working fine (is not related to the one that don't work), this error is because some users are created and when they enter to my mobile app in the first time the app don't update the proper FCM token, but it solved after the user login again, but the user of the device that isn't sending the updates to websockets is ok with the FCM token.
Another thing, is there a way to disconnect and connect the device without needed of restart server to make it work?
No other ideas. There's no API to force disconnect a device, if that's what you're asking.
I also have almost the same problem but the solution has not been found so far. I will continue to investigate since I am not the only one.
And how do you deal with it? you need to check every X time for all devices like me? You reset the server each time that you have an one device with it? @Urdanegui Castillo
Exactly I have to be checking each device every x time and restart the server. That solves it, but it is not an adequate solution. It's a very strange thing.
I can't find any information about it either. The answers that appear here are a bit without so much information.
How many times do you have with that issue? Maybe we could assist one each other and try to solve that. any contact?
I'll try to do a job or script to get notified when a devices is not reporting for more than X time. If any other user have the issue, please post here to try to solve it.
Maybe, your device is continuously reporting older positions than last recorded position in server, then server discards those data but just updates connected status. Generally, it's a problem in device side to update fix time.
Yes, it looks like I have some entries that have this issue. For example
2024-08-29 12:43:37 INFO: [Td62f9a96: startek < 147.75.51.174] &&D145,865235057381283,000,0,,240829164338,A,18.476186,-69.955330,16,0.7,0,291,58,618182,370|1|139D|0006F502,31,0000003D,00,00,04F7|019F|0000|0000,1,,,7C\r\nthis 240829164338 is16:43:38 and the server came up to server at 12:43:37.
Mmm, there's a way to have a tolerance in this?, for example that the devices doesn't discards if the time is less than 10 minutes of diference? anyways, it looks like the server stuck because two reason: I need to restart the server to continue working (not the device) and not all data have this difference.
That's weird, I tested without adding any modification to configuration file and send packets with 2 and 200 seconds in the future and the traccar server proccess it, confusing about if it could be the error.
Hello, I also have the same problem with my own server. In my case it is not a device issue, since they are tested on DEMO servers and on some colleagues' servers and also on other review services and they work normally, some devices for example if I delete them or have been disconnected for a long time when re-adding or reactivating them it says that they are online but it does not record movement, nor does it record history. It is common if for some reason it is blocked, the last connection time appears online etc. but the location does not update on the map. If I test the same GPS equipment on another server, I have no problem.
The problem with mine is that random device at least one time a month stop storing position and send data to websocket. I'm not sure if it possible to share contact information in this forum, I'll to read to check but we can do a group to help each other, I could offer one of my servers to test and debug together.
Sharing personal contact information is not allowed.
I tested some of the samples and they work for me locally on 6.4, so I'm not sure what the problem is. I still suspect there are some errors or warnings.