LBS not work with Opencellid and old GPS position

ML2 years ago

Hello,

My gps watch (KT17S Wonlex) have this state because I'm in bulding :

GPS:OK(0); 
wifiOpen:true; 
wifiConnect:false; 
gprsOpen:true; 
NET:OK(100)

The watch only send old position (when I was out of the bulding ) :

2023-05-10 17:59:41  INFO: [T510ac1d3] id: XXXXXXXXXXX, time: 2023-05-10 12:43:29, lat: -1X.XXXXX, lon: -1XX.XXXXXXX, speed: 4.0, course: 349.2

LBS configuration seems right in traccar.xml :

    <entry key='geolocation.enable'>true</entry>
    <entry key='geolocation.type'>opencellid</entry>
    <entry key='geolocation.key'>XXXXXXXXXXXXXXXXXXXXXXX</entry>
    <entry key='geolocation.processInvalidPositions'>true</entry>
    <entry key='geolocation.mcc'>XXX</entry>
    <entry key='geolocation.mnc'>XX</entry>

Have you a idea about the issue ?

Thanks a lot !

Anton Tananaev2 years ago

Corresponding HEX sample from the logs?

ML2 years ago

Hi Anton,

This is what I have in log (decode HEX):

2023-05-11 10:07:45  INFO: [Te834a44a] id: 9024137380, time: 2023-05-10 12:43:29, lat: -17.56054, lon: -149.59431, speed: 4.0, course: 349.2
2023-05-11 10:07:45  INFO: [Te834a44a: watch > IP] [3G*9024137380*0002*LK]
2023-05-11 10:08:03  INFO: [Te834a44a: watch < IP] [3G*9024137380*0105*UD_LTE,110523,200802,V,0,N,0,E,0,0,0,0,100,100,0,0,00000000,2,1,547,15,262156,13,100,40114,262156,21,5,WIFI1,dc:90:88:42:55:87,-30,WIFI2,78:a3:51:40:1b:d4,-35,,f0:c4:2f:9e:6e:18,-44,WIFI3,f0:c4:2f:9e:6e:14,-45,WIFI4,a0:d8:07:5a:6b
Anton Tananaev2 years ago

Why is HEX decoded? And this is the wrong sample because the decoded data comes after the HEX.

ML2 years ago

I manually decoded HEX to make it easier for you.

Anton Tananaev2 years ago

Yeah, but unfortunately you cut the message, which makes what you provided completely unusable.

ML2 years ago

Anton, sorry for inconvenient,
Here log HEX :

2023-05-11 10:07:45  INFO: [Te834a44a] id: 9024137380, time: 2023-05-10 12:43:29, lat: -17.56054, lon: -149.59431, speed: 4.0, course: 349.2
2023-05-11 10:07:45  INFO: [Te834a44a: watch > IP] 5b33472a393032343133373338302a303030322a4c4b5d
2023-05-11 10:08:03  INFO: [Te834a44a: watch < IP] 5b33472a393032343133373338302a303130352a55445f4c54452c3131303532332c3230303830322c562c302c4e2c302c452c302c302c302c302c3130302c3130302c302c302c30303030303030302c322c312c3534372c31352c3236323135362c31332c3130302c34303131342c3236323135362c32312c352c5441484954492d574946492c64633a39303a38383a34323a35353a38372c2d33302c4d41444749432d322e3447687a2c37383a61333a35313a34303a31623a64342c2d33352c2c66303a63343a32663a39653a36653a31382c2d34342c49542c66303a63343a32663a39653a36653a31342c2d34352c4855415745492d423331312d364232372c61303a64383a30373a35613a3662
Anton Tananaev2 years ago

It's again not a full message. And you're still providing non-matching HEX and decoded data. As I already said, the decoded data logically comes after the raw data.

Anton Tananaev2 years ago

Maybe if you don't really understand the logs, it's better if you provide the full connection session "Te834a44a".

ML2 years ago

Ok sorry for misunderstanding,

Full log for Te834a44a :

2023-05-11 10:52:45 INFO: [Te834a44a: watch < IP] 5b33472a393032343133373338302a303030612a4c4b2c302c302c3130305d
2023-05-11 10:52:45 INFO: [Te834a44a] id: 9024137380, time: 2023-05-10 12:43:29, lat: -17.56054, lon: -149.59431, speed: 4.0, course: 349.2
2023-05-11 10:52:45 INFO: [Te834a44a: watch > IP] 5b33472a393032343133373338302a303030322a4c4b5d
2023-05-11 10:57:45 INFO: [Te834a44a: watch < IP] 5b33472a393032343133373338302a303030612a4c4b2c302c302c3130305d
2023-05-11 10:57:45 INFO: [Te834a44a] id: 9024137380, time: 2023-05-10 12:43:29, lat: -17.56054, lon: -149.59431, speed: 4.0, course: 349.2
2023-05-11 10:57:45 INFO: [Te834a44a: watch > IP] 5b33472a393032343133373338302a303030322a4c4b5d
2023-05-11 11:02:45 INFO: [Te834a44a: watch < IP] 5b33472a393032343133373338302a303030612a4c4b2c302c302c3130305d
2023-05-11 11:02:46 INFO: [Te834a44a] id: 9024137380, time: 2023-05-10 12:43:29, lat: -17.56054, lon: -149.59431, speed: 4.0, course: 349.2
2023-05-11 11:02:46 INFO: [Te834a44a: watch > IP] 5b33472a393032343133373338302a303030322a4c4b5d
2023-05-11 11:07:46 INFO: [Te834a44a: watch < IP] 5b33472a393032343133373338302a303030612a4c4b2c302c302c3130305d
2023-05-11 11:07:46 INFO: [Te834a44a] id: 9024137380, time: 2023-05-10 12:43:29, lat: -17.56054, lon: -149.59431, speed: 4.0, course: 349.2
2023-05-11 11:07:46 INFO: [Te834a44a: watch > IP] 5b33472a393032343133373338302a303030322a4c4b5d
2023-05-11 11:12:46 INFO: [Te834a44a: watch < IP] 5b33472a393032343133373338302a303030612a4c4b2c302c302c3130305d
2023-05-11 11:12:46 INFO: [Te834a44a] id: 9024137380, time: 2023-05-10 12:43:29, lat: -17.56054, lon: -149.59431, speed: 4.0, course: 349.2
2023-05-11 11:12:46 INFO: [Te834a44a: watch > IP] 5b33472a393032343133373338302a303030322a4c4b5d
2023-05-11 11:14:03 INFO: [Te834a44a: watch < IP] 5b33472a393032343133373338302a303130352a55445f4c54452c3131303532332c3231313430322c562c302c4e2c302c452c302c302c302c302c3130302c3130302c302c302c30303030303030302c322c312c3534372c31352c3236323135362c31332c3130302c34303131342c3236323135362c31352c352c2c66303a63343a32663a39653a36653a31382c2d33322c4d41444749432d322e3447687a2c37383a61333a35313a34303a31623a64342c2d33332c49542c66303a63343a32663a39653a36653a31342c2d33342c5441484954492d574946492c64633a3930
2023-05-11 11:14:03 INFO: [Te834a44a: watch < IP] 3a38383a34323a35353a38372c2d33372c4855415745492d423331312d364232372c61303a64383a30373a35613a36623a32372c2d34392c305d
2023-05-11 11:17:46 INFO: [Te834a44a: watch < IP] 5b33472a393032343133373338302a303030612a4c4b2c302c302c3130305d
2023-05-11 11:17:46 INFO: [Te834a44a] id: 9024137380, time: 2023-05-10 12:43:29, lat: -17.56054, lon: -149.59431, speed: 4.0, course: 349.2
2023-05-11 11:17:46 INFO: [Te834a44a: watch > IP] 5b33472a393032343133373338302a303030322a4c4b5d
2023-05-11 11:22:46 INFO: [Te834a44a: watch < IP] 5b33472a393032343133373338302a303030612a4c4b2c302c302c3130305d
2023-05-11 11:22:46 INFO: [Te834a44a] id: 9024137380, time: 2023-05-10 12:43:29, lat: -17.56054, lon: -149.59431, speed: 4.0, course: 349.2
2023-05-11 11:22:46 INFO: [Te834a44a: watch > IP] 5b33472a393032343133373338302a303030322a4c4b5d
2023-05-11 11:27:46 INFO: [Te834a44a: watch < IP] 5b33472a393032343133373338302a303030612a4c4b2c302c302c3130305d
2023-05-11 11:27:46 INFO: [Te834a44a] id: 9024137380, time: 2023-05-10 12:43:29, lat: -17.56054, lon: -149.59431, speed: 4.0, course: 349.2
2023-05-11 11:27:46 INFO: [Te834a44a: watch > IP] 5b33472a393032343133373338302a303030322a4c4b5d
2023-05-11 11:32:46 INFO: [Te834a44a: watch < IP] 5b33472a393032343133373338302a303030612a4c4b2c302c302c3130305d
2023-05-11 11:32:46 INFO: [Te834a44a] id: 9024137380, time: 2023-05-10 12:43:29, lat: -17.56054, lon: -149.59431, speed: 4.0, course: 349.2
2023-05-11 11:32:46 INFO: [Te834a44a: watch > IP] 5b33472a393032343133373338302a303030322a4c4b5d
2023-05-11 11:37:46 INFO: [Te834a44a: watch < IP] 5b33472a393032343133373338302a303030612a4c4b2c302c302c3130305d
2023-05-11 11:37:46 INFO: [Te834a44a] id: 9024137380, time: 2023-05-10 12:43:29, lat: -17.56054, lon: -149.59431, speed: 4.0, course: 349.2
2023-05-11 11:37:46 INFO: [Te834a44a: watch > IP] 5b33472a393032343133373338302a303030322a4c4b5d
2023-05-11 11:42:46 INFO: [Te834a44a: watch < IP] 5b33472a393032343133373338302a303030612a4c4b2c302c302c3130305d
2023-05-11 11:42:46 INFO: [Te834a44a] id: 9024137380, time: 2023-05-10 12:43:29, lat: -17.56054, lon: -149.59431, speed: 4.0, course: 349.2
2023-05-11 11:42:46 INFO: [Te834a44a: watch > IP] 5b33472a393032343133373338302a303030322a4c4b5d
2023-05-11 11:47:46 INFO: [Te834a44a: watch < IP] 5b33472a393032343133373338302a303030612a4c4b2c302c302c3130305d
2023-05-11 11:47:46 INFO: [Te834a44a] id: 9024137380, time: 2023-05-10 12:43:29, lat: -17.56054, lon: -149.59431, speed: 4.0, course: 349.2
2023-05-11 11:47:46 INFO: [Te834a44a: watch > IP] 5b33472a393032343133373338302a303030322a4c4b5d