Update to 5.9

1205a year ago

I upgraded the system to version 5.9, but found that the id value parsed by CalAmp protocol did not correspond to the id value in the previous data transmission.
For example, in my two cars A and B, when A uploads data through this IP, B also uploads data through this IP, and it is found that the id value resolved by B is the id value of A, which is not supposed to be, and there is no relationship between car A and car B

2023-11-xx 14:11:37  INFO: [Uc7e381ce: calamp < 1xx.1xx.x30.122] 8305476436023501010102095d6565f5196565f5192036dcdebd1ad96a0000e2da0000000000b7ff9f4f04000122a09000000000000000000097e220000000000000000014dd600ddba00000c3a00000000
2023-11-xx 14:11:37  INFO: [Uc7e381ce] id: 4764360235, time: 2023-11-xx 14:11:37, lat: xx.xx664, lon: -xxx.xx254, course: x3.0

2023-11-xx 14:20:09  INFO: [Uc7e381ce: calamp < 1xx.1xx.x30.122] 8305486102321901010102bf696565f6f86565f6f8200b1cdcbcc3849e0000f93d00000000010e0000005e1e09000000003c0000349b000000f20000000000000000000002b00000026b000001f600000000
2023-11-xx 14:20:09  INFO: [Uc7e381ce] id: 4764360235, time: 2023-11-xx 14:19:36, lat: xx.xxx92, lon: -xxx.x0x72, course: xx0.0

The data on the top is the data of car A, and the data on the bottom is the data of car B. The id value is the ten digits following 8305
I need your help. Thank you

Anton Tananaeva year ago

The problem is that both devices are reporting from the same IP. Because of that Traccar thinking it's the same device.

1205a year ago

But why is it possible to make the correct distinction in 4.15

Anton Tananaeva year ago

Because the logic was a bit different due to caching.

1205a year ago

What changes should be made in version 5.9 to make the correct distinction, or can you tell me a new version that uses the same caching logic as 4.15.
thanks

Anton Tananaeva year ago

I don't have an answer off the top of my head. You would have to dig into the code to see where the changes were made and how to revert them if that's what you want to do.

1205a year ago

Thank you very much for your reply.
but now I have another question, about the problem that the device is not listed in the device list on the left side of the page, and the console has this problem

app.min.js:308 Uncaught TypeError: Cannot read properties of null (reading 'get')
    at g.getImageSvg (app.min.js:308:218)
    at g.getImageIcon (app.min.js:311:200)
    at g.getMarkerStyle (app.min.js:333:117)
    at g.getLatestMarker (app.min.js:334:29)
    at g.updateLatestMarker (app.min.js:326:344)
    at g.updateLatest (app.min.js:323:436)
    at F.fire (ext-all.js:22:146861)
    at F.dispatch (ext-all.js:22:447365)
    at a.doFireEvent (ext-all.js:22:448321)
    at g.fireEventArgs (ext-all.js:22:153235)
(svg = Ext.clone(category.get('svg'))) || (svg = this.cloneDocument(category.get('svg')));

The above line of code reported an error.
Do you think this error is related to the fact that my device list does not display device information

Anton Tananaeva year ago

Yes.

1205a year ago

I may need you to give me some advice about the problem that the device list cannot be displayed. I don't seem to know where to start

Anton Tananaeva year ago

You should use the debug version of the app to trace the root cause of the problem.