Help determining correct port

Eda year ago

My device [model: TK113S] isn't listed on the devices page.

So far I've tried all the clone ports and several other ports listed for other devices.
For the majority of ports I get an INFO log and no error.

Here's a successful log entry using port 5002 (IP redacted):

  • tk103
INFO: [Te0175c6c: tk103 < XXX.XXX.XXX.XXX] 242400726375304189321599553139353232302e3030302c412c313033312e313531332c4e2c30363132322e373633302c572c302e30302c33312e34392c3131313232332c2c2c412a34437c302e39317c32322e337c303030307c303030302c303030307c303238303839333830b2420d0a

The HEX portion decodes partially as:

$$�rcu0A‰2™U195220.000,A,1031.1513,N,06122.7630,W,0.00,31.49,111223,,,A*4C|0.91|22.3|0000|0000,0000|028089380²B

The web console shows my device as 'offline'

For ports which throw errors, the output is usually:

  • watch
INFO: [T135f1a2d] error - readerIndex(1) + length(2) exceeds writerIndex(2): UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 1, widx: 2, cap: 256) - IndexOutOfBoundsException (... < WatchProtocolDecoder:205 < ExtendedObjectDecoder:75 < ... < WrapperContext:102 < ...)

or

  • gps103
INFO: [Ta06db5d4] error - begin 21, end 24, length 17 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:413 < ExtendedObjectDecoder:75 < ... < WrapperContext:102 < ...)

or

  • h02
[T7d5d6ad7] error - Longitude out of range - IllegalArgumentException (Position:249 < H02ProtocolDecoder:151 < *:633 < ExtendedObjectDecoder:75 < ...)

or

  • eelink
[Tf95df642] error - Adjusted frame length exceeds 1024: 4456 - discarded - TooLongFrameException (... < WrapperInboundHandler:57 < ... < StandardLoggingHandler:44 < ... < NetworkMessageHandler:37 < ...)
Anton Tananaeva year ago

Have you tried port 5009?

Eda year ago

I had not tried 5009.
Just did and it works perfectly. Device instantly appeared on the web interface as Online with coords etc.
I see now how successful log messages appear; encoded line, followed by decoded.
Brilliant.

Thank you, @Anton Tananaev