LK-110 not showing on server. Port? ID

MrEd25 days ago

Hi.
I have been juggling for a while with a bike tracker LK-110 (NOT TK110). Is is supposed to work with traccar, according to manufacturer. Also, it is supposed to use port 5013, but it never shows. I´ve tried with the ID printed in the sticker, ID minus 1,2,3 or 4 characters in the left, adding zeroes instead, Etc. It never shows. I pointed it to manufacturer´s server, and he showed me a screen capture of his screen, with my tracker in my office.
Has anyone worked with it (and how)?
Thanks in advance.

Anton Tananaev25 days ago

Logs?

MrEd25 days ago

Here is what I got:

2025-03-27 01:55:46  INFO: [T2aac5a50] connected
2025-03-27 01:55:46  INFO: [T2aac5a50: watch < 194.165.16.165] 0300002f2ae00000000000436f6f6b69653a206d737473686173683d41646d696e697374720d0a0100080003000000
2025-03-27 01:55:46  WARN: [T2aac5a50] error - readerIndex(1) + length(2) exceeds writerIndex(2): UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 1, widx: 2, cap: 256) - IndexOutOfBoundsException (... < WatchProtocolDecoder:205 < ExtendedObjectDecoder:73 < ... < WrapperContext:102 < ... < WrapperInboundHandler:56 < ...)
2025-03-27 01:55:46  WARN: [T2aac5a50] error - readerIndex(1) + length(2) exceeds writerIndex(2): UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 1, widx: 2, cap: 256) - IndexOutOfBoundsException (... < WatchProtocolDecoder:205 < ExtendedObjectDecoder:73 < ... < WrapperContext:102 < ... < WrapperInboundHandler:56 < ...)
2025-03-27 01:55:46  WARN: [T2aac5a50] error - readerIndex(1) + length(2) exceeds writerIndex(2): UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 1, widx: 2, cap: 256) - IndexOutOfBoundsException (... < WatchProtocolDecoder:205 < ExtendedObjectDecoder:73 < ... < WrapperContext:102 < ... < WrapperInboundHandler:56 < ...)
2025-03-27 01:55:46  WARN: [T2aac5a50] error - readerIndex(1) + length(2) exceeds writerIndex(2): UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 1, widx: 2, cap: 256) - IndexOutOfBoundsException (... < WatchProtocolDecoder:205 < ExtendedObjectDecoder:73 < ... < WrapperContext:102 < ... < WrapperInboundHandler:56 < ...)
2025-03-27 01:55:46  WARN: [T2aac5a50] error - readerIndex(1) + length(2) exceeds writerIndex(2): UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 1, widx: 2, cap: 256) - IndexOutOfBoundsException (... < WatchProtocolDecoder:205 < ExtendedObjectDecoder:73 < ... < WrapperContext:102 < ... < WrapperInboundHandler:56 < ...)
2025-03-27 01:55:46  WARN: [T2aac5a50] error - readerIndex(1) + length(2) exceeds writerIndex(2): UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 1, widx: 2, cap: 256) - IndexOutOfBoundsException (... < WatchProtocolDecoder:205 < ExtendedObjectDecoder:73 < ... < WrapperContext:102 < ... < WrapperInboundHandler:56 < ...)
2025-03-27 01:55:46  WARN: [T2aac5a50] error - readerIndex(1) + length(2) exceeds writerIndex(2): UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 1, widx: 2, cap: 256) - IndexOutOfBoundsException (... < WatchProtocolDecoder:205 < ExtendedObjectDecoder:73 < ... < WrapperContext:102 < ... < WrapperInboundHandler:56 < ...)
2025-03-27 01:55:46  WARN: [T2aac5a50] error - readerIndex(1) + length(2) exceeds writerIndex(2): UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 1, widx: 2, cap: 256) - IndexOutOfBoundsException (... < WatchProtocolDecoder:205 < ExtendedObjectDecoder:73 < ... < WrapperContext:102 < ... < WrapperInboundHandler:56 < ...)
2025-03-27 01:55:46  WARN: [T2aac5a50] error - readerIndex(1) + length(2) exceeds writerIndex(2): UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 1, widx: 2, cap: 256) - IndexOutOfBoundsException (... < WatchProtocolDecoder:205 < ExtendedObjectDecoder:73 < ... < WrapperContext:102 < ... < WrapperInboundHandler:56 < ...)
2025-03-27 01:55:46  WARN: [T2aac5a50] error - readerIndex(1) + length(2) exceeds writerIndex(2): UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 1, widx: 2, cap: 256) - IndexOutOfBoundsException (... < WatchProtocolDecoder:205 < ExtendedObjectDecoder:73 < ... < WrapperContext:102 < ... < WrapperInboundHandler:56 < ...)
2025-03-27 01:55:46  WARN: [T2aac5a50] error - readerIndex(1) + length(2) exceeds writerIndex(2): UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 1, widx: 2, cap: 256) - IndexOutOfBoundsException (... < WatchProtocolDecoder:205 < ExtendedObjectDecoder:73 < ... < WrapperContext:102 < ... < WrapperInboundHandler:56 < ...)
2025-03-27 01:55:46  WARN: [T2aac5a50] error - readerIndex(1) + length(2) exceeds writerIndex(2): UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 1, widx: 2, cap: 256) - IndexOutOfBoundsException (... < WatchProtocolDecoder:205 < ExtendedObjectDecoder:73 < ... < WrapperContext:102 < ... < WrapperInboundHandler:56 < ...)
2025-03-27 01:55:46  WARN: [T2aac5a50] error - readerIndex(1) + length(2) exceeds writerIndex(2): UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 1, widx: 2, cap: 256) - IndexOutOfBoundsException (... < WatchProtocolDecoder:205 < ExtendedObjectDecoder:73 < ... < WrapperContext:102 < ... < WrapperInboundHandler:56 < ...)
2025-03-27 01:55:46  WARN: [T2aac5a50] error - readerIndex(1) + length(2) exceeds writerIndex(2): UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 1, widx: 2, cap: 256) - IndexOutOfBoundsException (... < WatchProtocolDecoder:205 < ExtendedObjectDecoder:73 < ... < WrapperContext:102 < ... < WrapperInboundHandler:56 < ...)
2025-03-27 01:55:46  WARN: [T2aac5a50] error - readerIndex(1) + length(2) exceeds writerIndex(2): UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 1, widx: 2, cap: 256) - IndexOutOfBoundsException (... < WatchProtocolDecoder:205 < ExtendedObjectDecoder:73 < ... < WrapperContext:102 < ... < WrapperInboundHandler:56 < ...)
2025-03-27 01:55:46  WARN: [T2aac5a50] error - readerIndex(1) + length(2) exceeds writerIndex(2): UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 1, widx: 2, cap: 256) - IndexOutOfBoundsException (... < WatchProtocolDecoder:205 < ExtendedObjectDecoder:73 < ... < WrapperContext:102 < ... < WrapperInboundHandler:56 < ...)
2025-03-27 01:55:46  WARN: [T2aac5a50] error - readerIndex(1) + length(2) exceeds writerIndex(2): UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 1, widx: 2, cap: 256) - IndexOutOfBoundsException (... < WatchProtocolDecoder:205 < ExtendedObjectDecoder:73 < ... < WrapperContext:102 < ... < WrapperInboundHandler:56 < ...)
2025-03-27 01:55:46  WARN: [T2aac5a50] error - readerIndex(1) + length(2) exceeds writerIndex(2): UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 1, widx: 2, cap: 256) - IndexOutOfBoundsException (... < WatchProtocolDecoder:205 < ExtendedObjectDecoder:73 < ... < WrapperContext:102 < ... < WrapperInboundHandler:56 < ...)
2025-03-27 01:55:46  WARN: [T2aac5a50] error - readerIndex(1) + length(2) exceeds writerIndex(2): UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 1, widx: 2, cap: 256) - IndexOutOfBoundsException (... < WatchProtocolDecoder:205 < ExtendedObjectDecoder:73 < ... < WrapperContext:102 < ... < WrapperInboundHandler:56 < ...)
2025-03-27 01:55:46  WARN: [T2aac5a50] error - readerIndex(1) + length(2) exceeds writerIndex(2): UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 1, widx: 2, cap: 256) - IndexOutOfBoundsException (... < WatchProtocolDecoder:205 < ExtendedObjectDecoder:73 < ... < WrapperContext:102 < ... < WrapperInboundHandler:56 < ...)
2025-03-27 01:55:46  WARN: [T2aac5a50] error - readerIndex(1) + length(2) exceeds writerIndex(2): UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 1, widx: 2, cap: 256) - IndexOutOfBoundsException (... < WatchProtocolDecoder:205 < ExtendedObjectDecoder:73 < ... < WrapperContext:102 < ... < WrapperInboundHandler:56 < ...)
2025-03-27 01:55:46  WARN: [T2aac5a50] error - readerIndex(1) + length(2) exceeds writerIndex(2): UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 1, widx: 2, cap: 256) - IndexOutOfBoundsException (... < WatchProtocolDecoder:205 < ExtendedObjectDecoder:73 < ... < WrapperContext:102 < ... < WrapperInboundHandler:56 < ...)
2025-03-27 01:55:46  WARN: [T2aac5a50] error - readerIndex(1) + length(2) exceeds writerIndex(2): UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 1, widx: 2, cap: 256) - IndexOutOfBoundsException (... < WatchProtocolDecoder:205 < ExtendedObjectDecoder:73 < ... < WrapperContext:102 < ... < WrapperInboundHandler:56 < ...)
2025-03-27 01:55:46  INFO: [T2aac5a50] disconnected
2025-03-27 02:18:15  INFO: [Tca4c69f5] connected
2025-03-27 02:18:15  INFO: [Tca4c69f5: startek < 44.220.188.50] <?xml version='1.0'?>\n            <stream:stream xmlns:stream='http://etherx.jabber.org/streams'id='1'\n            xmlns='jabber:client' from='localhost'>
2025-03-27 02:18:20  INFO: [Tca4c69f5] disconnected
2025-03-27 02:18:20  INFO: [T0ea111f4] connected
2025-03-27 02:18:20  INFO: [T0ea111f4: startek < 44.220.188.50] \r\n
Anton Tananaev25 days ago

That's not port 5013.

MrEd25 days ago

And now I´m trying different IDs and Ports:

2025-03-27 03:06:41  INFO: [Teee53b57: gps103 < 45.227.254.132] 0300002c27e00000000000436f6f6b69653a206d737473686173683d446f6d61696e0d0a0100080003000000
2025-03-27 03:07:04  WARN: [Teee53b57] error - Connection reset - SocketException (...)
2025-03-27 03:07:04  INFO: [Teee53b57] disconnected
2025-03-27 03:07:04  INFO: [Tb027e200] connected
2025-03-27 03:07:04  INFO: [Tb027e200: gps103 < 45.227.254.132] 0300002c27e00000000000436f6f6b69653a206d737473686173683d446f6d61696e0d0a0100080003000000
2025-03-27 03:07:27  WARN: [Tb027e200] error - Connection reset - SocketException (...)
2025-03-27 03:07:27  INFO: [Tb027e200] disconnected
2025-03-27 03:47:11  INFO: [T7bdd7213] connected
2025-03-27 03:47:11  INFO: [T7bdd7213: gps103 < 194.165.16.165] 0300002f2ae00000000000436f6f6b69653a206d737473686173683d41646d696e697374720d0a0100080003000000
2025-03-27 03:47:11  WARN: [T7bdd7213] error - Range [21, 24) out of bounds for length 5 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:399 < ExtendedObjectDecoder:73 < ... < WrapperContext:102 < ... < WrapperInboundHandler:56 < ...)
2025-03-27 03:47:11  INFO: [T7bdd7213] disconnected
2025-03-27 03:55:55  INFO: [T6ab5e013] connected
2025-03-27 03:55:56  INFO: [T6ab5e013: huabao < 91.238.181.96] 0300002f2ae00000000000436f6f6b69653a206d737473686173683d41646d696e697374720d0a0100080003000000
2025-03-27 03:56:16  WARN: [T6ab5e013] error - Connection reset - SocketException (...)
2025-03-27 03:56:16  INFO: [T6ab5e013] disconnected
2025-03-27 06:10:27  INFO: [T541c07fd] connected
2025-03-27 06:10:27  INFO: [T541c07fd: gps103 < 185.224.128.17] 434f4e4e454354206578616d706c652e636f6d3a383020485454502f312e310d0a486f73743a206578616d706c652e636f6d3a38300d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a0d0a00
2025-03-27 06:10:27  WARN: [T541c07fd] error - Range [21, 24) out of bounds for length 22 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:399 < ExtendedObjectDecoder:73 < ... < WrapperContext:102 < ... < WrapperInboundHandler:56 < ...)
2025-03-27 06:10:27  WARN: [T541c07fd] error - Range [21, 24) out of bounds for length 2 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:399 < ExtendedObjectDecoder:73 < ... < WrapperContext:102 < ... < WrapperInboundHandler:56 < ...)
2025-03-27 06:10:27  INFO: [T541c07fd] disconnected
2025-03-27 06:10:27  INFO: [T1a1b430b] connected
2025-03-27 06:10:27  INFO: [T1a1b430b: gps103 < 185.224.128.17] 050100
2025-03-27 06:10:27  INFO: [Tc68e6c10] connected
2025-03-27 06:10:27  INFO: [Tc68e6c10: gps103 < 185.224.128.17] 0401005000000001006578616d706c652e636f6d00
2025-03-27 06:10:42  INFO: [T1a1b430b] disconnected
2025-03-27 06:10:42  INFO: [Tc68e6c10] disconnected
2025-03-27 08:19:27  INFO: user: 1, action: edit, object: device, id: 18
2025-03-27 08:41:46  INFO: user: 1, action: edit, object: device, id: 18
2025-03-27 08:45:18  INFO: user: 1, action: edit, object: device, id: 18
2025-03-27 08:53:58  INFO: user: 1, action: edit, object: device, id: 18
2025-03-27 08:55:18  INFO: user: 1, action: edit, object: device, id: 18
2025-03-27 08:56:22  INFO: user: 1, action: edit, object: device, id: 18
2025-03-27 09:18:47  INFO: user: 1, action: edit, object: device, id: 18
2025-03-27 09:19:49  INFO: user: 1, action: edit, object: device, id: 18
MrEd25 days ago

At first (first log) I was pointing to 5013. In the second log I pointed it to 5002
Imagen de WhatsApp 2025-03-27 a las 13.34.40_1f9bfe69.jpg

Anton Tananaev25 days ago

I don't recognize the protocol. Do you have the protocol documentation?

MrEd25 days ago

It is supposed to be H02. I have it in PDF and Excel. How can I send it to you? Plain text?

Anton Tananaev25 days ago

Upload somewhere and provide a link here.

MrEd25 days ago
Anton Tananaev25 days ago

Doesn't open.

MrEd25 days ago

Please try again. I made it 100% public.

Anton Tananaev25 days ago

The documentation is for H02 protocol. But what I see in your logs doesn't match that documentation, as you can hopefully see.

MrEd25 days ago

OK, I´ll research more and eventually come back to you. THANK YOU!

MrEd25 days ago

After some fiddling, I got this in the log:

2025-03-27 14:26:10  WARN: Unknown device - 5110100434 (168.196.203.33)
2025-03-27 14:28:08  INFO: user: 1, action: edit, object: device, id: 18
2025-03-27 14:35:11  INFO: [Te0962a20] connected
2025-03-27 14:35:11  INFO: [Te0962a20: h02 < 186.189.74.47] *HQ,5110100434,V1,213510,A,3318.8449,S,7032.6903,W,000.00,253,270325,FF7FFBFF,730,09,3b6301,00e7,3#
2025-03-27 14:35:11  WARN: Unknown device - 5110100434 (186.189.74.47)
2025-03-27 14:44:11  INFO: user: 1, action: edit, object: device, id: 18
2025-03-27 14:45:11  INFO: [T36eafd0d] connected
2025-03-27 14:45:11  INFO: [T36eafd0d: h02 < 186.189.76.11] *HQ,5110100434,V1,214511,A,3318.8449,S,7032.6903,W,000.00,253,270325,FF7FFBFF,730,09,3b6301,00e7,4#
2025-03-27 14:45:11  WARN: Unknown device - 5110100434 (186.189.76.11)
2025-03-27 14:48:00  INFO: user: 1, action: edit, object: device, id: 18

As you can see, it is now recognizing h02, and the device ID (it is correct, from the SMS query and from the label). However, the server does not let it gain access. A number of attempts with IMEI and parts, plus zeroes do no work. Any ideas?