Protocol H02 - Tracker CJ780 (wrong ids - imei)

Hi, anyone can help please, I have these trackers CJ780 that uses h02 protocol, I have using 4.12 version before, Now I have upgrade to 5.12, and I having a lot of Unknow Devices coming in the logs.

logs:

2024-09-25 11:20:17  WARN: Unknown device - 2478010489 (200.233.197.30)
2024-09-25 11:30:32  WARN: Unknown device - 2478010419 (200.233.216.19)
2024-09-25 11:31:12  WARN: Unknown device - 02021268ff (200.233.197.30)
2024-09-25 11:31:12  WARN: Unknown device - 2317577406 (200.233.197.30)
2024-09-25 11:33:00  WARN: Unknown device - 2478010862 (200.233.197.30)
2024-09-25 11:33:55  WARN: Unknown device - 2a48512c37 (200.233.216.19)
2024-09-25 11:34:56  WARN: Unknown device - 52005278ff (200.233.216.19)
2024-09-25 11:34:56  WARN: Unknown device - 2320083406 (200.233.216.19)
2024-09-25 11:37:36  WARN: Unknown device - 2320181706 (200.233.216.19)
2024-09-25 11:42:41  WARN: Unknown device - 2478010493 (200.233.197.30)
2024-09-25 11:57:30  WARN: Unknown device - 2478010242 (74.208.89.24)
2024-09-25 12:01:28  WARN: Unknown device - 2478010431 (200.233.197.30)

the first line has this ID: 2478010489 - But this ID is wrong, because the correct ID is 7801048919

2024-09-25 11:20:17  INFO: [Tb708e72a: h02 < 200.233.197.30] 24780104891914201725092423176841060510875272031345ffffdfffff00065a0000023c02d40400000000009325
2024-09-25 11:20:17  WARN: Unknown device - 2478010489 (200.233.197.30)

If it was registered with 7801048919, why it keeps trying to connect with wrong ids ?

So what happens when you add id: 2478010489

I Dot not need to add, because it is already on the system with the original ID, if I add it, It will duplicate the device, and a few seconds later, this wrong ID will disconnect by itself

Why would it duplicate the device when rhe id is not the same?

Because in the logs I can see that is the same device, for example: 7801048919 is the real ID from the device, but sometimes the tracker keeps trying to connect with another ID , like 2478010489, and before (traccar version 4.12) it did not happened. I think it was something changed on the h02 protocol.

I don't think there were any changes to the way ids are decoded. Do you have a protocol documentation?

I will try to get the protocol documentation pdf from the factory, thanks