Hello! I bought a Chinese G500M tracker and set up data transfer to the server. I chose the eelink protocol.
Some of the data arrives, but the location is determined in a very strange way. It seems that the location data arrives with a delay of several tens of minutes, or even hours.
In the logs, I see data from the device every 20 seconds, when requesting location via SMS, it sends the correct coordinates, but the route on the server is very late.
Perhaps the wrong protocol was selected? But I myself could not decode the data from the log file. They look like this:
867232056099915 eelink 676702001b002f678649a3066d8fb80341eef429009400fa00021e9c000f4b03
867232056099915 eelink 676702001b0030678649a6066d8e000341f23030008900fa00021e9c000f4b03
867232056099915 eelink 676702001b0031678649a9066d8c100341f5302e009300fa00021e9c000f4b03
867232056099915 eelink 6767070006003200970364
867232056099915 eelink 676702001b0033678649ac066d89d00341f79030009c00fa00021e9c005c7d03
867232056099915 eelink 676702001b0034678649b4066d83400341fdc835009800fa00021e9c005c7d03
867232056099915 eelink 676702001b0035678649b8066d80080342015434009200fa00021e9c005c7d03
what's wrong?
I don't know why, but somehow the data lag on the server was related to the overspeed limit. After disabling this functionality in the settings, the data began to arrive correctly. There was an error in the logs related to the request to the overspeed server. Apparently, if there is no response from the server, the data is not written or is written with a large delay to the database.
WARN: Speed limit provider failed - Connection timed out - ConnectException (...)
That's expected if you have to wait for connection timeout.
As an idea, it might be worth considering in different threads the request to the server and the recording of data about the move to the database
They are already on different threads, but you have to wait for the data first anyway.
Hello! I bought a Chinese G500M tracker and set up data transfer to the server. I chose the eelink protocol.
Some of the data arrives, but the location is determined in a very strange way. It seems that the location data arrives with a delay of several tens of minutes, or even hours.
In the logs, I see data from the device every 20 seconds, when requesting location via SMS, it sends the correct coordinates, but the route on the server is very late.
Perhaps the wrong protocol was selected? But I myself could not decode the data from the log file. They look like this:
what's wrong?