problem with J16, using the wrong protocol?

The j16 uses the gt06 protocol, although it doesn't have it in the traccar device list, using it on port 5023 worked well, except that when creating a command and assigning the notification of leaving the fence, or ignition on, nothing happens, I noticed that in the log it seems to send via the gps103 protocol, and it gives several errors, I have already sent the command SZCS#PTL_SEL=2 to force it to use gt06, but I think that if it hadn't already been in use it didn't even connect to port 5023, below are the logs. Any help and direction is greatly appreciated, thank you all

2025-02-14 23:10:35  INFO: [Tc458586c] connected
2025-02-14 23:10:36  INFO: [Tc458586c: gps103 < 13.87.128.32] GET /v2/ HTTP/1.1\r\nHost: 63.142.255.156:5001\r\nUser-Agent: Mozilla/5.0 zgrab/0.x\r\nAccept: */*\r\nAccept-Encoding: gzip\r\n\r\n
2025-02-14 23:10:36  WARN: [Tc458586c] error - Range [21, 24) out of bounds for length 19 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:399 < ExtendedObjectDecoder:73 < ... < WrapperContext:102 < ... < WrapperInboundHandler:56 < ...)
2025-02-14 23:10:36  WARN: [Tc458586c] error - Range [21, 24) out of bounds for length 9 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:399 < ExtendedObjectDecoder:73 < ... < WrapperContext:102 < ... < WrapperInboundHandler:56 < ...)
2025-02-14 23:10:36  WARN: [Tc458586c] error - Range [21, 24) out of bounds for length 2 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:399 < ExtendedObjectDecoder:73 < ... < WrapperContext:102 < ... < WrapperInboundHandler:56 < ...)
2025-02-14 23:10:36  WARN: [Tc458586c] error - Range [21, 24) out of bounds for length 2 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:399 < ExtendedObjectDecoder:73 < ... < WrapperContext:102 < ... < WrapperInboundHandler:56 < ...)
2025-02-14 23:10:36  WARN: [Tc458586c] error - Range [21, 24) out of bounds for length 23 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:399 < ExtendedObjectDecoder:73 < ... < WrapperContext:102 < ... < WrapperInboundHandler:56 < ...)
2025-02-14 23:10:36  WARN: [Tc458586c] error - Range [21, 24) out of bounds for length 2 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:399 < ExtendedObjectDecoder:73 < ... < WrapperContext:102 < ... < WrapperInboundHandler:56 < ...)

I'm pretty sure it's not from your device.

btw please don't duplicate your comments.

So what is it about? I only have this j16, I don't have any other trackers

Not sure what I'm supposed to see, but even if you don't have a device, there's always some noise from the internet.

ok, I can't understand why it turns off the engine by sending the command, and creating the saved command, putting it in the notification and making the connection, it doesn't block, even though it appears in the log that was sent

457478955475 hablas español? si es asi me puedes explicar cual es tu problema.

From what I can see, the command was sent successfully. You have to check with your vendor on why the device didn't accept it.

Olá cristian, não sei ao certo o que vc disse, não falo espanhol, mas posso usar o tradutor do google

J16 trackers can support gt06, h02, and 808 protocol.

For 4G (especially now everywhere in the world the 2G networks are being shut down), the gt06 protocol versions 1 and 3 do not support cell tower ID's above 65535 (16bits) but in practice there are cell id's of 28 bits. And I've seen those higher cell ID values around here.
There are V4 and 4G protocol versions for GT06 but J16 trackers so far do not support those. I've asked the vendor (uniguard) and they confirmed there is no support, no new firmware available.
The h02 protocol (SZCS#PTL_SEL=1) on port 5013 does send the higher bits of the 4G cellIDs but in a rather peculiar way. In the binary dump of the 808 frames I also see the high bytes of the cellID in a "weird" place. But that's a whole different story..

But with GT06 protocol, if you don't care about LBS positioning when GPS fix is unavailable, it should work just fine.
If you see position but not alarms/mileage/acc status, you may want to send SZCS#GT06SEL=1 to switch to the V3 protocol which does. With SZCS#GT06IEXVOL=2 you can even have the tracker report the car's battery voltage.

As Anton indicated, the log file above is just some crawler hitting on the gps103 port. The J16 data on gt06 protocol should be recorded differently in the logs.

Hope this helps.

Oh, and the reason for asking if you speak spanish is probably the pesquisar dispositivos in the screen shot. But that sounds more like portuguese ;)

Thank you for trying to help, I will activate the extended protocol as you suggested, but I don't think this will solve the issue of not blocking when linked to notification and command. and yes I speak Brazilian Portuguese

I did what you said, it didn't work, and now I can't vote for the gt06 protocol, it only picks up the network on the h02, when I send a command to the gt06 it keeps the network LED blinking