watch protocol not working
That doesn't looks like logs from Traccar server.
2021-03-11 12:39:40 INFO: [10785bd2: 5093 < 27.59.59.128] HEX: ff41515348002b010000006ecf0e9fc27bac88735fce6b80bc0476be2cbd5a5c95ba59f398f668641fadb40178214c68
2021-03-11 12:40:40 INFO: [10785bd2: 5093 < 27.59.59.128] HEX: ff41515348002b010000006ecf0e9fc27bac88735fce6b80bc0476be2cbd5a5c95ba59f398f668641fadb40178214d69
2021-03-11 12:41:40 INFO: [10785bd2: 5093 < 27.59.59.128] HEX: ff41515348002b010000006ecf0e9fc27bac88735fce6b80bc0476be2cbd5a5c95ba59f398f668641fadb40178214e6a
2021-03-11 12:42:40 INFO: [10785bd2: 5093 < 27.59.59.128] HEX: ff41515348002b010000006ecf0e9fc27bac88735fce6b80bc0476be2cbd5a5c95ba59f398f668641fadb40178214f6b
2021-03-11 12:43:40 INFO: [10785bd2: 5093 < 27.59.59.128] HEX: ff41515348002b010000006ecf0e9fc27bac88735fce6b80bc0476be2cbd5a5c95ba59f398f668641fadb40178215074
2021-03-11 12:44:40 INFO: [10785bd2: 5093 < 27.59.59.128] HEX: ff41515348002b010000006ecf0e9fc27bac88735fce6b80bc0476be2cbd5a5c95ba59f398f668641fadb40178215175You would have to find protocol documentation. This format is not supported, as far as I know.
https://drive.google.com/file/d/1N08B2k_JlbSBhhKM-MVMYkWUzZGfPRsQ/view?usp=sharing
this is protocol doc can you tell me which port is supported
This protocol is supported, but your device doesn't use it.
the protocol is same but the device is not working
the only diffrence is 2g variant is working 4g variant is not working
the protocol is same
This is a false statement. You can easily verify that it's incorrect.
https://www.traccar.org/forums/topic/trouble-identifying-protocol-for-kids-smart-watch-q90/
some one have same issue before
2021-03-16 22:00:16 INFO: [2f30d1ff: 5093 > 117.136.33.223] HEX: 5b33472a343530343736333538342a303030322a4c4b5d
2021-03-16 22:00:16 WARN: Failed to store position - Data truncation: Incorrect datetime value: '1970-01-01 00:00:00' for column 'fixtime' at row 1 - MysqlDataTruncation (... < QueryBuilder:480 < DataManager:458 < DefaultDataHandler:30 < ...)
2021-03-16 22:00:16 INFO: [2f30d1ff] id: 4504763584, time: 1970-01-01 00:00:00, lat: 0.00000, lon: 0.00000, course: 0.0
2021-03-16 22:00:16 INFO: [2f30d1ff: 5093 < 117.136.33.223] HEX: 5b33472a343530343736333538342a303231332a434f4e4649472c54593a67363031782c554c3a36303030302c53593a302c434d3a312c57543a302c48523a302c54423a332c41423a302c43533a302c50503a302c48483a312c54523a302c4d4f3a302c464c3a302c56443a302c44443a322c53443a312c58593a322c57463a312c57583a302c50483a312c52573a302c4d543a312c58443a302c584c3a302c59463a302c534d3a302c48463a302c4a583a302c574c3a302c42513a302c51513a302c444c3a302c48543a302c50423a302c52533a3234303234302c44573a312c53533a302c4f463a312c494e3a302c4a543a302c47483a302c42543a322c544d3a312c42573a312c434c3a312c46413a312c46443a312c43543a312c534f3a312c4d453a312c4c523a302c544f3a312c52523a312c41433a312c44433a302c584d3a312c594a3a312c52593a312c52443a302c4c473a34302b33312b32342b32382b31392b33362b312b382b31312b342b302b332b33342b31342b32302b352b31332b32332b31362b31372b33332b31302b372b31322b392b32372c454d3a302c564c3a302c50563a302c46593a302c56523a4734485f454d4d435f4f5645525345415f3234305f354d5f5951545f54354c5f4144554c545f4950535f775f323032312e30312e32355f31342e31382e30302c44533a302c4c4c3a302c444d3a312c52503a312c41543a312c41443a302c4d503a302c4c533a332b362c4c443a302c44413a305d5b33472a343530343736333538342a303031362a5259494d45492c3836313234353034373633353834315dcan you tell me why the position data not store
Because your device doesn't report any location.
(1) Device Send:[CS*YYYYYYYYYY*LEN*LK]
Example:[SG*8800000015*0002*LK]
Platform response:[CS*YYYYYYYYYY*LEN*LK]
Example:[SG*8800000015*0002*LK]
Note:Once link, the datas will be send every 5 minutes, if the device not receive the reply from the
server , then it will try to link every minute, after failure of link 5 times, the terminal will reboot
(2) Device Send:[CS*YYYYYYYYYY*LEN*LK,step, tumbling number,battery status percentage]
Example:[SG*8800000015*000D*LK,50,100,100]
Platform response:[CS*YYYYYYYYYY*LEN*LK]
Example:[SG*8800000015*0002*LK]
Note: Once link, the datas will be send every 5-8 minutes, if the device not receive the response from the
server , then it will try to link every minute, after failure of link 5 times, the terminal will reboot
Both of these conditions exist. Very important tip: The server must reply all LK data! Otherwise the
device will not send any other
data and keep resent the LK data every 5 minutes. 2. Position data report
Device Send:[CS*YYYYYYYYYY*LEN*UD, the position data (see appendix one)]
Example:[3G*9403094122*00CD*UD,180916,025723,A,22.570733,N,113.8626083,E,0.00,249.5,0.0,6, 100,60,0,0,00000010,7,255,460,1,9529,21809,158,9529,63555,133,9529,63554,129,9529,21405,126, 9529,21242,124,9529,21151,120,9529,63556,119,0,40.7]
the problem is server can not send respond to the device so it is not seding the position data please check the protocoll this is little diffrent from orignal watch protocool please help me how can i change the response in source code
i will pay for paid support please help me to inegrate this watch
Feel free to email support if you are interested in sponsoring this work.
hi i have one chinece 4p touch watch which use the WATCH protoccol Unfortunate the 4g device is not working 2g device is work fine
when i check the log file get some string when i try to convert hexa decoder it says "Binary Hex can't be converted to Text"