Decoded HEX does not give any sense

I just tested a new gps-tracker (chinese version). I've tried all "possible ports for chinese trackers" but i no matter i still get a uncoded HEX.
When i decode the hex i just get symbols that does'nt make any sense, like [binary data]

When query for coordinates by sms i get the correct location.
I have 4 other trackers connected to the same server so i assume there is a problem with the device?

2020-06-07 02:35:39  INFO: [7482e6e8: gps103 < 46.15.102.118] HEX: 030411473236524142313839303630333334350d20026070005373d68ec301f81f840c18f09fe50000692a0000000000000600f000b4
2020-06-07 02:36:16  INFO: [0c407677: tk103 < 46.15.102.118] HEX: 030411473236524142313839303630333334350d200260700063410c8fc3011c20840c18f09fe50000642a0000000000000600f0007f
2020-06-07 02:36:18  INFO: [52fa280c] connected
2020-06-07 02:36:18  INFO: [52fa280c: gps103 < 34.76.78.209] HEX: 160301013801000134030318f7b0239e3f7b2129e84c157b825e8ae38d8377650f70fdd1cf9abb445a692b20cc3ddd4babde5abb35edbc4f60c014e2f9282c6647f665ecc517cd027c522e860056130213031301c02cc030c02bc02fcca9cca8009f009eccaac0afc0adc0aec0acc024c028c023c027c00ac014c009c013c0a3c09fc0a2c09e006b006700390033009d009cc0a1c09dc0a0c09c003d003c0035002f00ff01000095000b000403000102000a000c000a001d0017001e00190018002300000016000000170000000d0030002e040305030603080708080809080a080b080408050806040105010601030302030301020103020202040205020602002b0009080304030303020301002d00020101003300260024001d0020fb0c762afafbf3ac4b1d7187e1338d507661ef58aa3d5ac56d8f823f5bbb4b22
2020-06-07 02:36:18  WARN: [52fa280c] error - begin 21, end 23, length 4 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:411 < ExtendedObjectDecoder:51 < ... < WrapperContext:102 < ...)
2020-06-07 02:36:18  INFO: [52fa280c] disconnected
2020-06-07 02:36:38  INFO: [0c407677: tk103 < 46.15.102.118] HEX: 030411473236524142313839303630333334350d200260700063730c8fc3011c20840c18f09fe50000b42a0000000000000600f000fd
2020-06-07 02:36:51  INFO: [0c407677: tk103 < 46.15.102.118] HEX: 0511473236524142313839303630333334350d0052
2020-06-07 02:37:09  INFO: [0c407677: tk103 < 46.15.102.118] HEX: 030411473236524142313839303630333334350d200260700073700c8fc3011c20840c18f09fe50000802a0000000000000600f00024
2020-06-07 02:37:29  INFO: [0c407677: tk103 < 46.15.102.118] HEX: 0511473236524142313839303630333334350d0052

Do you have protocol documentation? HEX decoding doesn't work because it's a binary protocol.

This is a typical chinese version with chinese manual :(
Does binary protocol mean it's 0's and 1's while hex is 0-H?
Is it somehow possible to "sniff" the raw data and convert it in my settings file?

HEX is just a representation. Binary data can be represented as HEX, which is the case here.

It won't be possible to understand the data without documentation.