Location Update Issue with CalAmp Device on Traccar
Can you provide logs?
2023-08-19 18:22:48 INFO: [U665ebd2e: calamp < 119.155.196.212] 8305133108510901010102015f64e1067564e1067514248d6d2b5a23d40000a60d00000000011c0a220003ffa70f090e0002150000
2023-08-19 18:22:51 WARN: Firebase user 1 error - Requested entity was not found. - FirebaseMessagingException (... < NotificatorFirebase:114 < NotificationManager:110 < ... < *:107 < ... < *:106 < *:148 < ConnectionManager:247 < ...)
2023-08-19 18:22:51 WARN: Firebase user 1 error - Requested entity was not found. - FirebaseMessagingException (... < NotificatorFirebase:114 < NotificationManager:110 < ... < *:107 < ... < *:106 < *:148 < ConnectionManager:247 < ...)
2023-08-19 18:22:51 INFO: [U665ebd2e] id: 1331085109, time: 2023-08-19 18:14:13, lat: 33.79398, lon: 72.73277, course: 284.0
2023-08-19 18:22:51 INFO: [U665ebd2e: calamp > 119.155.196.212] 0201015f020000000000
2023-08-19 18:22:54 INFO: [U665ebd2e: calamp < 119.155.196.212] 8305133108510901010102016064e106a764e106a714248d6d2b5a23d40000a60d00000000011c0b220003ffa70f090e0002150000
2023-08-19 18:22:54 INFO: [U665ebd2e] id: 1331085109, time: 2023-08-19 18:15:03, lat: 33.79398, lon: 72.73277, course: 284.0
2023-08-19 18:22:54 INFO: [U665ebd2e: calamp > 119.155.196.212] 02010160020000000000
2023-08-19 18:22:58 INFO: [U665ebd2e: calamp < 119.155.196.212] 8305133108510901010102016164e106d964e106d914248d6d2b5a23d40000a60d00000000011c0b220003ffa70f090e0002150000
2023-08-19 18:22:58 INFO: [U665ebd2e] id: 1331085109, time: 2023-08-19 18:15:53, lat: 33.79398, lon: 72.73277, course: 284.0
2023-08-19 18:22:58 INFO: [U665ebd2e: calamp > 119.155.196.212] 02010161020000000000
2023-08-19 18:24:39 INFO: [T2f3598e0] connected
2023-08-19 18:24:49 INFO: [T2f3598e0] disconnected
2023-08-19 18:25:44 INFO: [T6b9f1e45] connected
2023-08-19 18:26:15 INFO: [T6b9f1e45] error - Connection reset - SocketException (...)
2023-08-19 18:26:15 INFO: [T6b9f1e45] disconnected
2023-08-19 18:26:20 INFO: user: 1, action: edit, object: user, id: 1
2023-08-19 18:27:30 INFO: [U665ebd2e: calamp < 119.155.198.116] 8305133108510901010102016264e1070b64e1070b14248d6d2b5a23d40000a60d00000000011c0c220003ffa70f090e0002150000
2023-08-19 18:27:30 INFO: [U665ebd2e] id: 1331085109, time: 2023-08-19 18:16:43, lat: 33.79398, lon: 72.73277, course: 284.0
2023-08-19 18:27:30 INFO: [U665ebd2e: calamp > 119.155.198.116] 02010162020000000000
2023-08-19 18:27:32 INFO: [U665ebd2e: calamp < 119.155.198.116] 8305133108510901010102000164e1072900000000000000000000000000000000000000000000002c0000ff8f00000e082d240000
2023-08-19 18:27:32 INFO: [U665ebd2e] id: 1331085109, time: 2023-08-19 18:17:13, lat: 0.00000, lon: 0.00000, course: 0.0
2023-08-19 18:27:32 INFO: [U665ebd2e: calamp > 119.155.198.116] 02010001020000000000
2023-08-19 18:27:35 INFO: [U665ebd2e: calamp < 119.155.198.116] 8305133108510901010102000264e1075a64e1075a14248b8f2b5a25b50000a5a00000000000c609200003ffa70f0c0e0002150000
2023-08-19 18:27:35 INFO: [U665ebd2e] id: 1331085109, time: 2023-08-19 18:18:02, lat: 33.79393, lon: 72.73282, course: 198.0
2023-08-19 18:27:35 INFO: [U665ebd2e: calamp > 119.155.198.116] 02010002020000000000
2023-08-19 18:27:48 INFO: [T6280c453] connected
2023-08-19 18:27:48 INFO: [T6280c453: cartrack < 162.243.141.30] 4d474c4e44445f3135372e3233302e3139312e3138365f353036310a
2023-08-19 18:27:58 INFO: [T6280c453] disconnected
2023-08-19 18:28:40 INFO: [U665ebd2e: calamp < 119.155.198.116] 8305133108510901010102000264e1075a64e1075a14248b8f2b5a25b50000a5a00000000000c609200003ffa70f0c0e0002150000
2023-08-19 18:28:40 INFO: [U665ebd2e] id: 1331085109, time: 2023-08-19 18:18:02, lat: 33.79393, lon: 72.73282, course: 198.0
2023-08-19 18:28:40 INFO: [U665ebd2e: calamp > 119.155.198.116] 02010002020000000000Try the suggestion from this thread:
https://www.traccar.org/forums/topic/major-issues-after-upgrading-from-56-to-58/
Hello Traccar Community,
I hope you're all doing well. I'm reaching out to the community to seek help with a challenging issue we've encountered while using CalAmp devices with Traccar.
We are using Traccar to manage our fleet, which includes CalAmp devices. We have historically used an older version of Traccar (version 4.14), and during this time, we experienced consistent and reliable location updates from our CalAmp devices.
Recently, we decided to upgrade to the latest version of Traccar in order to benefit from its improved features and capabilities. However, after the upgrade, we've run into a significant problem: the location updates from our CalAmp devices are not being accurately reflected on the Traccar platform.
While the devices do appear as "online" on the Traccar interface, their location data remains static and doesn't update as expected. Interestingly, in our previous Traccar version (4.14), these devices provided timely and accurate location updates without any issues.
As you can imagine, this situation is causing disruptions in our fleet management operations. We're posting on this forum to see if anyone else has experienced a similar issue or if there are any insights or solutions that the community could provide.
If you've encountered a similar problem or if you have any recommendations, workarounds, or potential solutions, we would greatly appreciate your input. We're open to any technical suggestions, configuration changes, or even insights into the potential cause of this issue.
Although we understand that the Traccar community forum might not be an official support channel, we believe that the collective expertise here could help shed light on the matter. If you need any additional information or logs from our end to assist in diagnosing the issue, please let us know, and we'll be happy to provide whatever is necessary.
Our hope is not only to find a resolution for our own operations but also to contribute to the broader knowledge base of the Traccar community. We're committed to working toward a solution and appreciate any insights you can share.
Thank you for your time and consideration. We look forward to any responses or guidance from the community.
Best regards,
Haider