Gt02ProtocolDecoder: Any ideas for this problem?

Version: 4.11

2021-04-10 14:00:34  INFO: [2d5d1c95] connected
2021-04-10 14:00:34  INFO: [2d5d1c95: gt02 < 149.62.204.207] HEX: 68680f0604035160808240141000101a04000d0a
2021-04-10 14:00:34  INFO: [2d5d1c95: gt02 > 149.62.204.207] HEX: 54681a0d0a
2021-04-10 14:00:34  INFO: Position filtered by Zero filters from device: 351608082401410
2021-04-10 14:00:35  INFO: [2d5d1c95: gt02 < 149.62.204.207] HEX: 79790020940a0351608082401410028405004183248289359050000418324821000298920d0a
2021-04-10 14:00:35  WARN: [2d5d1c95] error - readerIndex(5) + length(8) exceeds writerIndex(5): PooledSlicedByteBuf(ridx: 5, widx: 5, cap: 5/5, unwrapped: PooledDirectByteBuf(ridx: 5, widx: 38, cap: 2048)) - IndexOutOfBoundsException (... < Gt02ProtocolDecoder:59 < ExtendedObjectDecoder:52 < ... < WrapperContext:102 < ...)
2021-04-10 14:00:35  INFO: [2d5d1c95] disconnected

Do you have protocol documentation?

Yes, I have:
https://we.tl/t-ZcXKKbaRCg

This protocol is not supported yet, as far as I know.

The version 4.11 support it. More than 50 units working well. When device lost the GPS signal, this error appears. As soon as device restore GPS position, it works perfect including buffered events in trackers.

It means that this specific message type is not supported.

I suspect, not implemented only the case if no GPS data in event

Yes, looks like it's a WiFi message, which is currently not supported.

In general such as cases have to be encapsulated in some exception block to proccess to next event. In this case the pareser freeze on this event and never proccess with next (known) events.

• Just suggestion *

Can I expect any solution for problem?
The message is not related to WiFi. It is basic tracker with power cable only

The bottom line is that it's not supported at the moment. If you are interested in sponsoring the implementation, you can contact support to discuss it. If not, you can submit a GitHub request and wait.