Can't get all information from device that use watch protocol
@Track-trace
@Anton Tananaev
Kindly, if you have a server for testing then I can connect my device to your server to test the result?
@James John
You better send a link to download the tracker-server.log file then ill have a look at it (without any sensitive data in it).
@James John
Your log does not include hex from watch protocol.. Send a link to the log From 2021-12-05 where we know there is Watch protocol data in it.
i did not check correctly.. here it is..
@James John
Let me check..
You see this..
2021-12-05 13:46:13 INFO: [1ae3ee60: watch < 46.32.121.90] HEX:
5b33472a323130343233363536392a303043412a414c2c3035313232312c3133343631322c562c33312e3936393231332c4e2c33352e383634393831372c452c302e30302c302e302c302e302c302c3130302c38312c302c302c30303430303030302c372c3235352c3431362c312c323132312c35353138312c3134332c323132312c35353436312c3133352c323132312c35353535322c3132392c323132312c35353138342c3132382c323132312c35353535332c3132362c323132312c35353138332c3132352c323132312c35353436322c3131392c302c35392e385d
[3G*2104236569*00CA*AL,051221,134612,V,31.969213,N,35.8649817,E,0.00,0.0,0.0,0,100,81,0,0,00400000,7,255,416,1,2121,55181,143,2121,55461,135,2121,55552,129,2121,55184,128,2121,55553,126,2121,55183,125,2121,55462,119,0,59.8]Like Anton said.. the log is correct. It must be your editors. Because i took the above from the logfile you uploaded.
okay, I will change mu editor.
Thank you very much
@Track-trace
I have test 3 devices that have Watch protocol and they give the same issue.
@Anton Tananaev
I opened the file with other editors such as notebad++ and internet explorer but the same code it appeared.