Hi, Anton. I know this question might seem irrelevant. Sorry for inconvenience. I'm a software developer and I created my own TCP server (in C#.NET) that currently works with Chinese cheap GPS watches. The problem is this watches break the connection and reconnecting every minute and sending unnecessary data (mostly 'LK', not 'UD'). That causes too much data consuming and battery usage. I ask this question to you because the watches work normal on your Traccar server (with written in Java). I absolutely followed the protocols mentioned in the documentation (like responding LK command back and so on). But it didn't work. Can you tell anything about it?
I would recommend you to compare communication between device and Traccar, and then your server. There must be some difference.
Hi, Anton. I know this question might seem irrelevant. Sorry for inconvenience. I'm a software developer and I created my own TCP server (in C#.NET) that currently works with Chinese cheap GPS watches. The problem is this watches break the connection and reconnecting every minute and sending unnecessary data (mostly 'LK', not 'UD'). That causes too much data consuming and battery usage. I ask this question to you because the watches work normal on your Traccar server (with written in Java). I absolutely followed the protocols mentioned in the documentation (like responding LK command back and so on). But it didn't work. Can you tell anything about it?