The Kontakt.io and Meraki integration offers a lower total cost of ownership (TOC) by leveraging your existing BLE-enabled network infrastructure. Meraki Access Points with an integrated Bluetooth Low Energy radio allow integration with the Kontatk.io IoT solutions and BLE beacons, tags, and badges.
Meraki Access Points collect and send Kontakt.io BLE device data to Kio Cloud. This data is then available through our APIs to allow integration with your web or mobile applications.
Our APIs for application developers are open and give you access to the full family of Kontakt.io products and capabilities.
Location & Occupancy API: real-time and historical Kio Cloud apps data, including location tracking, occupancy, and the full spectrum of sensor data from Kontakt.io devices.
Device Management API: configure, manage, and monitor your Kontakt.io devices in Kio Cloud.
Mobile SDKs: complete development libraries that enable you to power your own apps.
You can also expand your RTLS accuracy with the Kontakt.io Portal Light gateways in combination with your existing Meraki Access Points. The Kontakt.io Portal Light gateways add flexibility to enrich your current solution for more precise, room-level accuracy needed for contact tracing or asset tracking use cases.
Be sure all of the following requirements are met before you begin to configure the integration.
Compatible Access Points: the majority of Meraki Access Points are equipped with Bluetooth technology, but MR 20 and MR 70 do not support these capabilities. Please verify the Access Points are Bluetooth-enabled.
Integration requires at least the MR 27.5 software version installed on all Access Points.
Access Points online
Access Points associated with Meraki Cloud
Complete the following instructions to configure a Meraki integration with the Kontakt.io Kio Cloud platform and devices. Integration includes setup from both Meraki Cloud and Kio Cloud.
Integration with Meraki devices requires enabling access to Cisco Meraki Dashboard API.
Log in to your Cisco Meraki Dashboard > select Organization > select Settings.
Scroll down and verify Enable access to the Cisco Meraki Dashboard API is selected.
Click on the link in the description below the Enable access to the Cisco Meraki Dashboard API checkbox or in the top right corner click on your email address and select My Profile.
Scroll down to the API access section > click Generate new API key > copy the API key and save to a safe place. You'll need this later.
Go to the Network-wide section in the Dashboard's sidebar > from the Configure column, select General.
Scroll down to the Location and scanning section. Verify the Analytics and Scanning API is enabled > and copy the Validator value and save to a safe place. You'll need this later.
Sign in to your Kio Cloud account > select Device Management.
Select External Providers > select Start Meraki Integration.
Enter your Merarki API Key.
Enter your Meraki Validator key.
Select Generate Secret > copy and save to a safe place, you'll need this later.
Select Enable Meraki Integration.
Enter a MAC address that identifies your Meraki access point device > select Add Device.
Repeat this process for all Meraki access points you want to add as Location Engine sources.
Once all your access points are added, verify they are listed from the Gateways menu. From the left menu, select Gateways.
There are two integration options, each having a unique Kontakt.io endpoint and your Kio Cloud
Positions on map are being calculated by Kio Cloud only.
Positions on map are calculated by Meraki Cloud and sent to Kio Cloud.
Your Kio Cloud
company_id can be found on Meraki Integration Panel.
Go to your Meraki Cloud Panel > Network-wide > General.
Scroll down to section Location and scanning.
Paste your selected Kontakt.io endpoint with your Kio Cloud company_id > paste the secret key you generated from Kio Cloud > select Save Changes.
If you decide to use the positions endpoint, there are additional Meraki Cloud Panel configuration requirements. Please see the below two Meraki Documentation articles for details.
Using a Floor Plan or Custom Map in Dashboard https://documentation.meraki.com/General_Administration/Monitoring_and_Reporting/Using_a_Floor_Plan_or_Custom_Map_in_Dashboard
Placing Devices on the Map in Dashboard https://documentation.meraki.com/General_Administration/Monitoring_and_Reporting/Placing_Devices_on_the_Map_in_Dashboard