Cisco CMX Analytics has the capability to create an hourly heatmap of client activity for any floor as part of the analytics capabilities.
The heatmap is generated hourly and is in the format of a JPG image which is accessible via the GUI. As part of the GUI you can play the hourly generated heatmaps back to form an understanding of what has happened on the floor during the day.
The heatmap is generated by a dataset of devices that have had a locations calculated during the last hour. It is important to note the following;
- With Standard location, a datapoint for location is generated when the client decides to send a PROBE packet out. This is normally done when a client first enters a venue, and is done less frequently when a device is in a venue and is in a static location. This would mean location such as lounges that have static devices may not have as many devices shown with standard location as would be shown with HyperLocation. In addition, places where devices first encounter WIFI access points will be shown hotter.
- A new location is usually determined when a device has moved, as such for a large number of static devices, there will not be a lot of location calculated.
- With Hyperlocation, a datapoint is calculated much more frequently, approximately one time each 15 seconds. These datapoints give a more realistic view in the heatmaps of where devices are.
- The data in a heatmap and the colors are based on a logarithmic scale where the specific color will not associate to a specific number.
- The primary uses cases for HEATMAP is as a comparison tool for two different events or two different days. Given the same pattern of visitors the heat map would appear in the same way.
USE CASES FOR HEATMAP GENERATED WITH STANDARD LOCATION
1) Compare different days of the weeks to see if different days have specific times or places then a benchmark day
2) Compare different events to see if the timing of the event resulted in different enterances uses or different location of devices
USE CASES FOR HEATMAP GENERATED WITH HYPERLOCATION
1) Determine and compare different areas of the venue to see where CONNECTED devices are more likely to be.
2) Determine the flow of devices in and out of a venue during an event.
HyperLocation refers to the uses of Datapackets and if available Angle of Arrival for the determination of a client location. HyperLocation can be accomplished with either a standard AP in Enhanced Local Mode where it scans for other clients, it can be accomplished with a dedicated monitor mode radio such as the RM3010 or, in the most advanced method is accomplished with a dedicated HyperLocation Antenna Array and a RM3010L module.
Hi Team, We are working on an internal project links to DNA SPACES.We try to retrieve data using the DNA SPACES API.We connect Meraki with DNA Spaces using the API key
The Connection to the Cisco Meraki CBS looks complete on the dashboard where we have da...
Hi Experts,is there a way to register call back URL in Cisco CMX. It is required to integrate CMX with Cisco CKC.Requirement: CKC platform will initiate one API request to CMX, and it is expecting to get output from CMX on a call back URL.
I'm having trouble finding the Meraki Dashboard API endpoint to get/set Hotspot 2.0 configuration. According to these release notes it exists https://developer.cisco.com/meraki/whats-new/#!archive/january-2017. However I'm unable to find it in the AP...
Hi,Like to know is there an API for Meraki that allows me to pull the Power Source of an access point? Currently in the GUI dashboard, there is a "Power" field that say "AC adapter" or "POE 802.3au". Is there an equivalent for that in the API?