Location APIs configuration update
Cisco Meraki has deprecated the HTTP support for Location and scanning APIs. Make sure to update the post URL with HTTPS instead of HTTP in the below section in Meraki Dashboard
Network- wide > General > Location and scanning > Post URLs
Enabling location services
The first step to getting your Cisco Meraki network feeding data to Cloud4Wi is to enable the location services on the Meraki dashboard. With this step, your Cisco Meraki network will start sending presence and location data to our system, and the Overview, Trends, Peak and Virtual Zone dashboard will start working automatically.
On the second step, you'll learn how to get to work also the Heatmap dashboard and enable the Polygon zones.
1. Accessing the web interface
Login to the Meraki Dashboard with your credentials to view this page:
Select your organization and the network where you want to enable communication with Presence Analytics APIs.
2. Enabling the Meraki CMX and the communication with APIs
Go to the Configure tab in the left sidebar, and select Network-wide settings as shown below.
Find the CMX section and set CMX API value to "CMX API enabled".
The CMX is enabled and next, you will activate communication with APIs.
Enter the following data that will be provided privately from Cloud4Wi:
- Post URL
When you click the Validate button, you should receive a success message, as shown below.
In this case, the communication with Presence Analytics APIs is successfully configured.
If you don't receive the success message, please check if the data is correctly entered.
Alternatively, you can open a ticket in our Support Center.
Enabling Heatmap and Polygon Zones
To get your Heatmap dashboard working and to start using the Polygon Zones, you need to take a further step. In order for these features to work, you need to sync the floor plans you have configured in your Meraki dashboard with the floor plans in your Cloud4Wi account.
1. Configuration on Meraki
The initial step is to upload a floor plan (.png or .jpeg files only) onto the Meraki dashboard and then place APs on this floor plan. You need to make sure that all the APs have been placed on the floor plan and there are no APs remaining under unplaced option. See below sample screenshot.
Also, take note of the Network name as this will be needed when configuring on Volare. Visit Meraki support for more information in regards to adding floorplan (https://documentation.meraki.com/MR/Monitoring_and_Reporting/Using_a_Floor_Plan_or_Custom_Map_in_Dashboard).
2. Configuration on Volare
The first step is to upload the same floorplan used on Meraki dashboard under the location where Heatmaps data is to be captured. The important field when creating a new floorplan is “Floor hardware manufacture ID”: this field should be the same as the floor plan name (it’s case sensitive) used on Meraki dashboard.
Please read the following article about how to Add and Manage floorplan (https://cloud4wi.zendesk.com/hc/en-us/articles/208154933-Adding-and-managing-floors) on Volare.
Once the configuration upload has been completed, the access point will be able to capture location data and feed it to the Cloud4Wi service. At this point, your Heatmap dashboard will start showing the data (it may take a few hours before you see data showing on the map).
You can also start using the Polygon Zones by drawing polygons on the floor plans and analyzing the zone traffic on the related Zone Traffic dashboard.