Issue with watch protocol

Himanshu3 years ago

I have seen this page (https://www.traccar.org/identify-protocol/) and found that smartwatches support watch protocol. The sample packet mentioned in this page and the data protocol provided by OEM is also similar.

As per OEM (Sentar Smart) the data should be as below:

[3G*2016001000*00BC*UD,120118,070625,A,22.570720,N,113.8620167,E,0.00,188.6,0.0,
9,100,51,14188,0,00000010,6,255,460,0,9360,5081,156,9360,4081,129,9360,4151,128,9360,
5082,127,9360,4723,122,9360,4082,120,5,buyaoxialian,a0:c5:f2:b0:7.4:d0,-34,3gtc-5g,92:76:
9f:48:4f:20,-48,726,38:37:8b:7:cf:99,-54,3gtc,d0:ae:ec:96:10:54,-63,ceshi,d0:ae:ec:96:10:55,-
64,22.4]

But in actual I am getting below data in log file on WATCH protocol port:

2022-05-16 16:30:07  INFO: [86926d76] connected
2022-05-16 16:30:07  INFO: [86926d76: watch < 157.37.159.61] HEX: ff41515348002b010a0000b01f307e316dd97274b006a6e77819e3ef5de641545aa3ac528c5c06cf21c8d90180cc8667
2022-05-16 16:30:07  WARN: [86926d76] error - minimumReadableBytes : -5 (expected: >= 0) - IllegalArgumentException (... < WatchProtocolDecoder:194 < ExtendedObjectDecoder:52 < ... < WrapperContext:102 < ...)
2022-05-16 16:30:07  INFO: [86926d76] disconnected

What could be the issue. Guide please.

Anton Tananaev3 years ago

Well, as you can probably see yourself, your device doesn't send the data in that format.