Hello Team,
I am trying to integrate a smartwatch (model VS3) with Traccar. The device is currently configured to send data to my AWS server on port 5093, and I can see consistent incoming packets in the server log.
Sample log (from Traccar server):
2025-09-28 15:13:57 INFO: [T04ae0546] connected
2025-09-28 15:13:57 INFO: [T04ae0546: watch < 1.39.141.142] ff41515348002b01000000d68db0ae6949ae8e0eabbd81155338569b56628fce7c2ffaeba9a473bda97af168d950b533
2025-09-28 15:13:57 WARN: [T04ae0546] error - readerIndex(1) + length(2) exceeds writerIndex(2): UnpooledByteBufAllocator...
at WatchProtocolDecoder:205
From what I understand, the packets start with FF 41 51 53 48 ... ("AQSH" in ASCII), which seems to be a vendor-specific header. It looks like Traccar’s built-in watch protocol decoder does not match this format, and therefore fails with a buffer underflow exception.
My questions:
1.Is this protocol already supported under a different Traccar decoder (e.g., H02, GT06, etc.)?
2.If not, what is the recommended approach to implement a custom decoder for this format?
3.Should I be pointing the device to a different port than 5013/5093, or is the only option to add a new protocol handler?
Any guidance on mapping this VS3 protocol to Traccar would be greatly appreciated.
Thank you for your prompt response.
You would need to find the protocol documentation for this format.
Thank you @Anton for your prompt response.
As always, you are the the true saviour.
I am sharing the link to the protocol document. Please go through & advise, how to proceed further.
Protocol Document
Thank you once again @Anton
This is definitely not the right documentation.
@Sanket
The protocol data you show is encrypted. This encryption is not implemented in traccar server. When you search the forum there a many topics about it.
Can you show a link to the watch so i can see the model details.
Actually you would need such a watch where the firmware should not use encryption to make it communicate with traccar server.
P.s.
I also wonder where you got the protocol doc ?
Regards,
Hello Team,
I am trying to integrate a smartwatch (model VS3) with Traccar. The device is currently configured to send data to my AWS server on port 5093, and I can see consistent incoming packets in the server log.
Sample log (from Traccar server):
From what I understand, the packets start with FF 41 51 53 48 ... ("AQSH" in ASCII), which seems to be a vendor-specific header. It looks like Traccar’s built-in watch protocol decoder does not match this format, and therefore fails with a buffer underflow exception.
My questions:
1.Is this protocol already supported under a different Traccar decoder (e.g., H02, GT06, etc.)?
2.If not, what is the recommended approach to implement a custom decoder for this format?
3.Should I be pointing the device to a different port than 5013/5093, or is the only option to add a new protocol handler?
Any guidance on mapping this VS3 protocol to Traccar would be greatly appreciated.
Thank you for your prompt response.