I can add some clarity here with the Location services. I highly suggest you begin your new BLE project using Scanning API v3 beta. - requires firmware r27 beta - the JSON is now structured as an array of client objects - (Note, this is beta, so we might adjust the JSON structure slightly, or rename a parameter. So, ensure you are flexible with your code while in beta) https://developer.cisco.com/meraki/scanning-api/#!api-version-3-beta Why? - v2 sends a JSON payload of calculated locations, per access point, per minute. This requires you to make sense of multiple AP calculations that could be confusing as well as processing potentially a large number of payloads per network. - v3 sends a JSON payload.. per network, per minute. This dramatically improves the efficiency for both delivering and receiving the payloads. - In addition, the accuracy was improved by mitigating some interference from known sources (other Meraki APs, etc) and some other adjustments with the calculations. Both versions have a delay in the location calculation and delivery, but v3 includes the path history between delivery periods along with historical RSSI records. This also provides you with the flexibility of calculating your own location if you wanted to be more advanced about it. Re: Accuracy - 3 APs need to observe a client for proper tri-lateration - WiFi is a little more difficult to predict location, because each client may broadcast at varying power levels, confusing the RSSI math. - BLE is easier to compute location because the power and broadcast interval are usually constant, providing more consistent values (less frantic RSSI measurements) Hope this helps. We are working on a lot of awesome enhancements to our Location services, so stay tuned for more info. We are always interested in your use cases and ways we can make leveraging our APIs easier and valuable, Cheers!
... View more
