device is connected to the server but not getting lat/lon :
here is the server log :
2022-06-24 20:47:13 INFO: [6408cf9d: xrb28 < 18.196.213.123] HEX: 2a434d44522c4f4d2c3836313132333035323338383138362c3030303030303030303030302c4c312c302c302c30230a
2022-06-24 20:47:15 INFO: [95c2a42a: xrb28 < 185.57.216.145] HEX: 2a434d44522c4c482c3836303533373036313432323830342c3030303030303030303030302c4c312c302c313635363037343234302c34230a
2022-06-24 20:47:44 INFO: [6408cf9d: xrb28 < 18.196.213.123] HEX: 2a434d44522c4f4d2c3836313132333035323338383138362c3030303030303030303030302c4c312c302c302c30230a
2022-06-24 20:47:46 INFO: [95c2a42a: xrb28 < 185.57.216.145] HEX: 2a434d44522c4c482c3836303533373036313432323830342c3030303030303030303030302c4c312c302c313635363037343234302c34230a
2022-06-24 20:48:14 INFO: [6408cf9d: xrb28 < 18.196.213.123] HEX: 2a434d44522c4f4d2c3836313132333035323338383138362c3030303030303030303030302c4c312c302c302c30230a
2022-06-24 20:48:16 INFO: [95c2a42a: xrb28 < 185.57.216.145] HEX: 2a434d44522c4c482c3836303533373036313432323830342c3030303030303030303030302c4c312c302c313635363037343234302c34230a
2022-06-24 20:48:45 INFO: [6408cf9d: xrb28 < 18.196.213.123] HEX: 2a434d44522c4f4d2c3836313132333035323338383138362c3030303030303030303030302c4c312c302c302c30230a
2022-06-24 20:48:47 INFO: [95c2a42a: xrb28 < 185.57.216.145] HEX: 2a434d44522c4c482c3836303533373036313432323830342c3030303030303030303030302c4c312c302c313635363037343234302c34230a
2022-06-24 20:49:15 INFO: [6408cf9d: xrb28 < 18.196.213.123] HEX: 2a434d44522c4f4d2c3836313132333035323338383138362c3030303030303030303030302c4c312c302c302c30230a
2022-06-24 20:49:17 INFO: [95c2a42a: xrb28 < 185.57.216.145] HEX: 2a434d44522c4c482c3836303533373036313432323830342c3030303030303030303030302c4c312c302c313635363037343234302c34230a
Procol Document : https://bit.ly/3OiOoVD
It doesn't look like your device is sending any location data.
may be sever should acknoledge to the device ... if possible kindly once go through the protocol document ...
Protocol Document
Which message needs to be acknowledged specifically? Have you checked the protocol yourself?
Manufacturer Reply this to me ..
The log shows that after the lock sends a Q0 sign in command to your server, it is kicked off the line by your server. The lock keeps trying to sign in to your server, but it has been rejected by your server.
Where's the Q0
command in your log? Please make sure you double-check the information you're providing.
device is connected to the server but not getting lat/lon :
here is the server log :
Procol Document : https://bit.ly/3OiOoVD