Dyegoo GPS tracker protocol help

Hi,
I have some aliexpress tracker that I cannot find the right decode for.
I tried ports 5001,5002,5006,5013,5015,5023 & 5036.

The messages do look like this:

2022-03-24 14:31:29  INFO: [c94d0e5d: gps103 < 109.40.242.221] HEX: 283032383034333234363637354250303033353532323830343332343636373548534f31393929
2022-03-24 14:31:36  INFO: [c94d0e5d: gps103 < 109.40.242.221] HEX: 283032383034333234363637354252303032323033323441353233322e393532324e30313331332e30373239453030302e303133333133343030302e303030313030303030304c303030303030303029

First decodes to (028043246675BP00355228043246675HSO199)
second decodes to (028043246675BR00220324A5232.9522N01313.0729E000.0133134000.0001000000L00000000)

I can confirm
028043246675 is ID of device
5232.9522N
01313.0729E is my approx position

000.0133134000.0001000000L00000000 i do not know

I tried looking into the test cases, but did not find anything that matches. Any hints?

I see you already tested port 5002. Can you please provide the log fragment with that port please.

Hi Anton, the fragment is with 5002 I believe. Can I get more verbose logs?

Why do you need more verbose logs? It has everything we need. Just wrong port. GPS103 is on port 5001.

Okay, now I changed the port to 5001 and got this

2022-03-24 21:47:30  INFO: [f86474f1] connected
2022-03-24 21:47:30  INFO: [f86474f1: gps103 < 109.40.241.177] HEX: 28303238303433323436363735425030353335353232383034333234363637352c7b3236322c322c3332332c31303830337d0a7b3236322c322c3332332c32383430327d0a7b3236322c322c3332332c33333538317d0a2c303130303030303029
2022-03-24 21:47:30  WARN: [f86474f1] error - begin 21, end 24, length 18 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:408 < ExtendedObjectDecoder:52 < ... < WrapperContext:102 < ...)
2022-03-24 21:47:30  WARN: [f86474f1] error - begin 21, end 24, length 18 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:408 < ExtendedObjectDecoder:52 < ... < WrapperContext:102 < ...)
2022-03-24 21:47:30  INFO: [f86474f1] disconnected

I wanted more verbosity as I have a second receiver that runs into an exception as supposedly the frame is too big that it sends, but I can open another thread for that.

Why are you providing a second example from port 5001 when I asked for an example on port 5002?

I misinterpreted your answer. Anyway, here's a fresh one from 5002:

2022-03-24 21:54:05  INFO: [c20c26a8] connected
2022-03-24 21:54:06  INFO: [c20c26a8: tk103 < 109.40.242.38] HEX: 28303238303433323436363735425030353335353232383034333234363637352c7b3236322c322c3332332c31303830337d0a7b3236322c322c3332332c3339337d0a7b3236322c322c3332332c33333538317d0a2c303130303030303029
2022-03-24 21:54:06  INFO: [c20c26a8: tk103 > 109.40.242.38] HEX: 283032383034333234363637354150303529
2022-03-24 21:54:06  INFO: [c20c26a8: tk103 < 109.40.242.38] HEX: 28303238303433323436363735425a30302c7b3236322c322c3332332c31303830337d0a7b3236322c322c3332332c3339337d0a7b3236322c322c3332332c33333538317d0a2c303130303030303029
2022-03-24 21:54:21  INFO: [c20c26a8: tk103 < 109.40.242.38] HEX: 28303238303433323436363735425a30302c2c30313030303030302

The problem is that your device is not reporting any GPS location. It only reports cell info, which is not supported at the moment.

If you want to sponsor support for cell info, please send an email to the support address.

Thanks, Anton. Actually, after putting the receiver closer to a window and waiting for the night, it is actually working now.

Thank you very much for your support!

Artur você pode nos ajudar informando qual porta você utilizou?