@protean Hi, when you click on "get location button", Device scans the wifi networks around and sends the result to Pybytes. Pybytes is using Google location API to figure out and the location.

@robert-hh that's true, you can have the libraries anywhere (with Pymakr as well)

@jmarcelino said in Get the Location using LoPy: @beyonlo The NetID has several implications, for example it becomes part of the assigned device addresses (devaddr, not EUIs) which gateways can then filter on amongst other details. It's a complex subject, I recommend reading the LoRaWAN specification and the NetID allocation policy: https://www.scribd.com/document/317164891/20160603-NetID-Alloc-Policy-Application-1178-1 "3rd party" means if you're running a network that will accept devices from users outside your company and/or devices made by other companies (namely LoRaWAN Certified devices) If you're running a private network just for your application using your own devices then you shouldn't need your own NetID. Again owning a NetID shouldn't have anything to do with LoRa geolocation, I mentioned it because this sort of access usually only makes sense (economically) for very large deployments but I suggest that you contact Semtech sales and enquire about it (and let us know if you can!) Follow the link at the bottom at https://www.semtech.com/wireless-rf/lora-geolocation to obtain your contact. Thank you :)