Thank you! 1. Meaning if someone disable Analytics he simply won't see the "Location Analytics" on dashboard and Scanning API will still work (if Scanning API is enabled)? 2. It is better than plain MAC addresses even though it is still pseudo-unique because you won't be able to associate it to someone else given same MAC address appears on different Cisco Meraki account (if hashing takes into account the AP or customer ID) 3. Do you have some reference hashing implementation in Github for example? 4. I have a Demo account in Meraki, but it does not send any data to Scanning API Post URL. Does it create a different type of account on create.meraki.io, because I wasn't able to find any other sandbox account. Thank you for the webinar and free AP note, we'll see if we can attend it!
... View more
Could you please clarify few questions: 1. What is a difference between Scanning API and Analytics dropdowns on "Location and Scananing" settings page. If I disable "Analytics" and enable "Scannig API" what would happen, and vice versa? 2. On this page: https://create.meraki.io/build/scanning-api-docs/ under "Location and Privacy" you mention that you use mac hashing and still send the raw mac address to Scanning API Post URL. Is it possible to add a flag to send a hashed version of mac address there too, because some of our customers in Europe have concerns regarding GDPR and would rather control mac hashing from Cisco Dashboard (it is related to this question i asked before but limited to Scanning API scope: https://community.meraki.com/t5/Dashboard-Administration/Hiding-clients-mac-address-in-API-response/m-p/21750) 3. Do you provide that hashing method for mac addresses as a library or code example that we could use as a reference? 4. Do you send any data to Demo accounts Scanning API Post URL?
... View more