It was decoded incorrectly. Un-precise position presumably means invalid:
https://github.com/traccar/traccar/commit/033e50725806fdd5597e37a24eff763800e1cdfa
Hi Anton,
Sorry for the silly question, does this mean with the next compile we should see the LBS data being used if "F" flags as unprecise positioning?
Thanks
I think so, but you need to enable geolocation for invalid positions.
Perfect, Next update I will let you know how it goes.
For geolocation I have these setting already running.
<entry key='geolocation.enable'>true</entry>
<entry key='geolocation.type'>google</entry>
<entry key='geolocation.key'>XXX Key</entry>
Thanks
Trent
Hi Anton,
Apologies it have been a while and only getting back to this.
I have done the latest Traccar update and now the valid satellite fix is "No" which is good. https://ibb.co/3chBX8t
But the LBS still doesn't appear to be working. Any ideas on what to look at next?
Have double checked the Geolocation entry - https://ibb.co/FgYDCNV
Network Information on Traccar Dashboard - https://ibb.co/gzHFVTC
OpenCelliD Dashboard with 0 Requests - https://ibb.co/fQFCyB6
Decoded HEX from Server Log showing the unit is sending Cell and Wifi information
*HQ201862109768005169,BA
&A0808142733126715316073550000131022
&B0100000000
&F0000
&R2100
&J000199
&X(11,1)(505A0)(E09C7)(J01E0)(L5)(PMODE,0,1440)(k8931089218072107899F)
&W0000003E
&Y1 505 01 7042 08C62A0B 42 <- Cell Information
&Q03 18828CD37EBF58 D4351D1A6DB35B FA8FCA54787F5D <Wifi information
&K00200
&T91
&N05#
Thanks
Have you tried any other providers?
Hi Anton,
Yes I have tried both Google and OpenCelliD.
Thanks
Trent
Have you enabled geolocation for invalid positions?
Hi Anton,
Just checking this is what you mean my enabled?
Screenshot of the traccar.xml file
https://ibb.co/x29qwtW
Thanks
Trent
I mean geolocation.processInvalidPositions
config parameter.
Hi Anton,
Link is https://we.tl/t-7I2YCLTmk3
I see two spots in the upro protocol that an invalid GPS signal could be picked up from.
Thanks