We have noticed that even though the Bluetooth devices are showing in the Meraki dashboard, some are not showing up in the raw data.  We have also noticed that Meraki is very selective which devices it detects as well. Some IOS and Android devices are detected while others aren't. The same goes for headphones as well. We have a well-controlled testbed where we are able to isolate devices and we have also used various beacon tools to verify that the devices are broadcasting. Any Ideas? ... View more

Since it has now has officially been announced I can answer that yes, the July Systems technology will be a part of the new DNA Spaces. I have had a chance to play around with it and it looks pretty slick. You can find more info here: https://dnaspaces.cisco.com/   ... View more

Thanks @NolanHerring for the additional info.   I have pretty much hit a brick wall with regards to this issue and even after multiple escalations and support from the account team there doesn't seem to be much hope of a resolution with the current state of the scanning API.   Here's hoping that Cisco has it in their 'DNA' to provide reliable location data for these open 'Spaces' in the next iteration of their API 😉   ... View more

For God's sake please allow us to hide the above message and not have it repeatedly show every time we alter the maps and floor plans.  We GET it you moved the Maps and floor plans now give us back our valuable screen real estate! ... View more

Thanks Nolanherring!  Your follow-up response is very helpful and encouraging. Cheers and Kudos ... View more

Hello NolanHerring,   I did contact a rep. regarding this issue and they were a great help in accelerating the process.   You stated: "These forums are not really the right way to escalate an issue like this. I know they are monitored but I honestly do not know to what extent."   Unfortunately there is a very limited support structure in the country I reside in for Meraki based issues. I am told that this will change very soon but in the meantime I need to rely on the documentation and community for support. The support responses in the 'Cases' section encourage leveraging the community for support which is exactly what I did.     Now I don't condone 'Malicious Compliance' in every case but this issue seems to have been around for a while and the suggested resolutions in this thread did not seem to address what could very well be an underlying issue that is affecting multiple users.  The concept of a forum is a many to many approach to discuss issues and ideas that are relevant to the participants.  To what extent the forum is moderated is Meraki's discretion. I chose to post here to elicit responses to build and articulate my case to the support team to have this issue addressed   Someone who is an active and knowledgeable user here with a growing positive reputation posted this excerpt in one of their responses:   " I would reach out to support and see if there are any known issues, the more people that do this, the more pressure they get that its not just a random few people with this issue."   Do you not agree with the above statement?             ... View more

Just opened a case with Meraki Support and I even provided the link to this thread for reference. Here is the response I received:   "I checked internally and verified there is a known issue on our location heatmap page showing incorrect data that is still being worked by our development team. At the moment, we don't have an ETA when will it be fixed but I will let you know if there is an update."   How is this disturbing?  1) They mentioned 'known' issue and yet after scouring the documentation, community and Reddit forums it was clearly not 'known' but rather highly suspected. 2) They did not make it 'known' in ANY of the documentation.  Instead it seems that this was deliberately hidden or 'veiled' in the RTLS documentation.  3) This thread was created almost a year ago and the problem still persists. 4) The scanning API is being highly touted by Meraki and there are partners whose solution is predicated on it.   see: https://apps.meraki.io/details/aislelabs-flow/ 5) The suggested resolutions in this thread are smelling to me like 'red herring'.     I am hoping that by commenting here this raises the priority level of this issue since our proprietary solution is also based on the scanning API. I also hope that this thread is being monitored by Meraki employees and that this will be properly communicated to the product management team. Last but not least, I am hoping that the response that I received from the support rep was based on the limited scope of his job function and not the actual situation.   ... View more

Hey Meraki Dave,   Here is an example of the 'clustering' issue even IF a 4th AP is deployed. Even if you don't understand Portuguese I think you will get the gist of the issue. https://community.meraki.com/t5/T%C3%B3picos-em-Portugu%C3%AAs/Ajustes-no-Heatmap/m-p/28706#M94 . We plan on rolling out hundreds of sites using the raw data from the Meraki scanning API to our proprietary analytics platform.  If we can't get this resolved then we may have to rethink our solution entirely. Let me know, like, your opinion, man   Cheers ... View more

We are also experiencing the same issues on all of our sites.  The issue manifests exactly as depicted with 3 MR33 APs deployed.  Our layouts are scaled and aligned properly and after a site survey it was determined that there was adequate WiFi coverage.   The issue lies that very few devices are being displayed outside of the 'Bermuda Triangle' formed by the APs. We have also observed that in our case when any devices are detected outside of the triangle they are usually associated devices. We are using the scanning API and plotting to our own solution (using the Meraki raw data) using our proprietary heatmap and we are seeing the same issues there as well.  There seems to be an abnormal clustering of detected devices around the APs and along the direct 'line of site' lines between the APs. The OP is right.  After an exhaustive search of the documentation there doesn't seem to be any explanation or steps to resolve this issue. Are there any recommended radio settings?   Do we need to add more APs and if so where? Here is a document that outlines best practices when using Meraki RTLS that I found AFTER the fact that directly contradicts the marketing collateral that states that NO special physical placement is required and that the existing architecture is sufficient as long as the coverage is adequate. https://documentation.meraki.com/MR/Monitoring_and_Reporting/Real-Time_Location_Services_(RTLS) ... View more