Unknown Device In Protocol Identification
2019-09-09 13:10:05 INFO: [c819540a] connected
2019-09-09 13:10:05 INFO: [c819540a: watch < 197.180.135.88] HEX: ff41515348002b01000000bd382ea7e51fc3692d2a6b4e19f0f217c5969f10f572cc62f98de8a8b1707f485d764f2cd3
2019-09-09 13:10:05 WARN: Unknown device - H+½8.§å Ãi- (197.180.135.88)
2019-09-09 13:10:59 INFO: [c819540a] disconnected
2019-09-09 13:11:26 INFO: [5f8aa806] connected
2019-09-09 13:11:27 INFO: [5f8aa806: watch < 41.81.166.154] HEX: ff41515348002b01000000bd382ea7e51fc3692d2a6b4e19f0f217c5969f10f572cc62f98de8a8b1707f485d764f7e81
2019-09-09 13:11:27 WARN: Unknown device - H+½8.§å Ãi- (41.81.166.154)
2019-09-09 13:12:36 INFO: [1d26c40c] connected2019-09-09 13:10:05 INFO: [c819540a] connected
2019-09-09 13:10:05 INFO: [c819540a: watch < 197.180.135.88] HEX: ff41515348002b01000000bd382ea7e51fc3692d2a6b4e19f0f217c5969f10f572cc62f98de8a8b1707f485d764f2cd3
2019-09-09 13:10:05 WARN: Unknown device - H+½8.§å Ãi- (197.180.135.88)
2019-09-09 13:10:59 INFO: [c819540a] disconnected
2019-09-09 13:11:26 INFO: [5f8aa806] connected
2019-09-09 13:11:27 INFO: [5f8aa806: watch < 41.81.166.154] HEX: ff41515348002b01000000bd382ea7e51fc3692d2a6b4e19f0f217c5969f10f572cc62f98de8a8b1707f485d764f7e81
2019-09-09 13:11:27 WARN: Unknown device - H+½8.§å Ãi- (41.81.166.154)
2019-09-09 13:12:36 INFO: [1d26c40c] connectedHow can I decode the correct device ID from - H+½8.§å Ãi- ?
You are using wrong port.
Hi thanks for the reply. I have tried all ports for chinese clones and only 5093 gives me at least unknown device error. The others are giving hex code which can't be decoded correctly. How can I identity the correct port?
This protocol is not supported, as far as I know. Do you have protocol documentation?
Yes. Can I upload and share the link here?
You can share a link here.
Unfortunately it doesn't match your samples.
I didn't quite understand you. Did you mean the communication protocol I attached isn't for that device? I have confirmed that it works for the watch protocol port 5093 using a similar device from the manufacturer. I will reach out to the manufacturer to confirm if they sent me the wrong device protocol. Thanks
Yes, your samples don't match the protocol.
Is it safe to say this device is not supported by traccar yet or is there some last tricks to manually identify this protocol you might recommend having followed the identify protocol documentation fully?
Most likely, but hard to tell for sure without documentation.
I will reach out if I get any more info from the manufacturer. Thank you very much
I reached out to the manufacturer and the documentation in the link above is the only one I could get. That's the communication protocol they have used on the device, Using that document is there a way to identify the protocol and port on traccal platform?
I have a Chinese watch which am trying to integrate with the server. I have tried all ports for the clones but it's not working. I am getting the hex code and unknown device in the logs. I have a similar device from the same manufacturer which is working correctly on the watch protocol port 5093 and the manufacturer claims they use the same protocol. After decoding the hex from logs I can't get anything readable but some weird characters. Am I using the wrong port?