Cisco Meraki

Overview

The Kloudspot Analytics Engine can receive events from many types of WiFi network.

One or more of event sources can be configured in the ‘Configuration - > Event Processing - > Wi-Fi’ screen.

Validate the Receiver URLs

The protocol (HTTP/HTTPS) used varies depending on the source. We support both HTTP and HTTPS protocols using port 48082 and 48083. Refer to the specific data source below to determine the correct one to use.

If you have set a SSL certificate for the UI, that will be used instead of the self signed one.

You can check access to both the HTTP and HTTPS urls with a ‘ping’:

$ curl http://{server}:48082/ping
hi from http receiver
$ curl -k https://{server}:48083/ping
hi from https receiver

Meraki MV Sense

Follow the instructions provided on the link to configure MQTT broker in the Meraki Dashboard:

Follow the instructions provided on the link to subscribe to different MQTT Messages

NOTE: Currently we subscribe Raw Detections and lux light levels topics.

Enable location Services: TCP port 6666 needs to be opened to start

capturing Meraki MV sense Data.

Cisco Meraki Location Scanning API

To enable, the Meraki scanning API feed, follow the following steps:

When enabling the API, set the following parameters:

  • API Version : 2
  • Post URL : https://{server}:48083/meraki/{name}
  • Secret : for example - kloudspot12345678

Meraki Docs Meraki Docs

For ‘{name}’ use a friendly alphanumeric label for the account.

  • Next go to the Kloudspot Web UI and select ‘Cisco Meraki’ source in the Event Sources.
  • Add an entry for each account (one is enabled by default) by clicking the ‘+’ sign.
  • Enter the ’name’, ‘validation’ and secret’ from above for each account and click ‘Save’.

Meraki Config Meraki Config

  • Restart the stream processing job.

Check Event Reception

Login to the Analytics Engine via SSH and run the kafka-listen command:

$ kafka-listen
{"vendor": "Kloudspot", "eventType": "PRESENCE", "location": null,..
{"vendor": "Kloudspot", "eventType": "PRESENCE", "location": null,..
{"vendor": "Kloudspot", "eventType": "PRESENCE", "location": null,..
{"vendor": "Kloudspot", "eventType": "PRESENCE", "location": null,..

You will be able to see the ‘raw’ event feed going into the stream processing.