Hi, I'm trying out the wialon-lbs-geocoding plugin, but I don't see the position.lbs.latitude and position.lbs.longitude fields in device messages and no messages appear in the plugin itself.

My devices are FMC001 and TAT100 and they are sending mnc, lac and cellid. Could it be that LBS doesn't work, because there is no mcc?

When I check Utilities - Message Parameters - Teltonika protocol, the mcc parameter is also not there. So, does LBS work with Teltonika at all? At the same time, Gurtam documentation claims that Teltonika does support LBS.

Yes, you are right. LBS plugin requires four parameters: gsm.mcc, gsm.mnc, gsm.lac, gsm.cellid. We will check Teltonika protocol implementation.

I tried injecting a static gsm.mcc, but the lbs plugin doesn't still seem to be triggered.

amq Seems like it was a bug in gsm.mcc detection which is now fixed. Please check without your plugin if it works now.

shal I can see gsm.mcc now, but for some reason, no LBS data like position.lbs.latitude, and there is nothing in wialon-lbs-geocoding plugin logs. I tried removing and re-adding the plugin and re-assigning the device, but it didn't help.

If there is nothing then it means that the combination of mcc, mnc, lac and cell_id is not present in Wialon LBS database.

Wait! there was a bug in our LBS plugin. It has been fixed. It will definitely work now. Thanks for your report!

@baja it works now, thanks! Do you plan to later add lbs accuracy estimation in meters in the future? Something like lbs.location.precision and position.accuracy, or similar to how Google Geolocation API returns accuracy: https://developers.google.com/maps/documentation/geolocation/overview

amq you are right, that's because in teltonika protocol we store gsm.-prefixed parameters with indexes, while wialon-lbs-geocoding plugin uses unindexed parameters for its work.
We'll fix it. If you need a quick fix, you may rename gsm.mnc.1 to gsm.mnc, gsm.mcc.1 to gsm.mcc etc using another plugin that works before wialon-lbs-geocoding plugin, this will fix it.

amq that's interesting. Write to flespi chat and specify the device ID so I can check the details.

Thanks, got support on chat and the problem was that some cellid's I was testing with are missing in the wialon database. Would be cool if you could add a plugin for google geolocation https://developers.google.com/maps/documentation/geolocation/overview, one additional benefit there is that it additionally provides location uncertainty in meters.