What protocol and port is this device

Assume that's eeLink but i got only this:

2018-03-31 11:37:38  INFO: [7C6AFE21] connected
2018-03-31 11:37:38 DEBUG: [7C6AFE21: 5064 < 109.41.130.242] HEX: 78780d0103536022000055630002f15a0d0a
2018-03-31 11:37:40 DEBUG: [7C6AFE21: 5064 < 109.41.130.242] HEX: 78780a1310054b00010002da310d0a
2018-03-31 11:37:42  INFO: [7C6AFE21] disconnected

Now i set port 5023 but something is still wrong.

2018-03-31 12:21:23  INFO: [861222F1] connected
2018-03-31 12:21:23 DEBUG: [861222F1: 5023 < 109.41.130.217] HEX: 78780d0103536022000055630002f15a0d0a
2018-03-31 12:21:23 DEBUG: [861222F1: 5023 > 109.41.130.217] HEX: 787805010002eb470d0a
2018-03-31 12:21:23 DEBUG: [861222F1: 5023 < 109.41.130.217] HEX: 7878222812031f0b151601060201548de21001548de315015420640b0154546309015465050800000000000002ea5a0d0a
2018-03-31 12:21:23  WARN: [861222F1] error - Not enough readable bytes - Need 2, maximum is 0 - IndexOutOfBoundsException (... < Gt06ProtocolDecoder:561 < *:496 < *:780 < ExtendedObjectDecoder:58 < ...)
2018-03-31 12:21:23  INFO: [861222F1] disconnected

Port 5023 seems to be the right one. Are you sure you are using latest release? Do you have protocol documentation?

Privet Anton,

i have NO protocol docs. I'm using version 3.16 on raspberry. Any suggestions how to got it working?
It's a device called LM002.

Message doesn't comply with protocol documentation that we have, so you need to get documentation for your device. It might be slightly different or it might be just device issue, sending invalid data.

Strange but since 23:03 yesterday the device sends location data. But unfortunatelly the timestamp is allways the same (e.g. 2018-03-31 22:31:52). So can you please help me?

brgds, Mike

OK, after driving a little bit around, the timestamp got also OK.

So this thread can be closed. Everything works fine now. SPASIBO Anton!