Cisco Meraki CMX Scanning API adapter for ioBroker
An ioBroker adapter for the Cisco Meraki CMX Scanning API.
This adapter exposes a receiver for the Cisco Meraki CMX Scanning API. The Cisco Meraki CMX Scanning API pushes location and analytics information for any wireless devices seen by your cloud managed Cisco Meraki access points.
Depending on the access points' feature sets the API pushes information for Wifi and bluetooth devices like BLE beacons, etc. .
The adapter transforms the device information into ioBroker states. Any states will get updated typically in between 1 up to 2 minutes.
Right now you'll have to add the adapter to your ioBroker using a custom url pointing to the corresponding GitHub repository at https://github.com/MiGoller/ioBroker.merakicmx/tree/master .
The adapter does not incorporates any ioBroker Web or Socket adapters. The adapter creates a small dedicated web-service endpoint to be exposed to an public endpoint.
Read the disclaimer, please!
Setting up a reverse proxy
Set up a reverse proxy to protect your receiver for the Cisco Meraki CMX Scanning API and your ioBroker installation.
Setting up the Cisco Meraki CMX Scanning API
First of all you'll have to enable the Cisco Meraki CMX Scanning API.
Login to your Cisco Meraki Dashboard and navigate to the general settings. Scroll down to
location and analytics.
- Ensure to enable
- Copy and write down the
- Add a Post URL pointing to your public endpoint (e.g. your reverse proxy's public IP or CNAME). Enter a
Secretfor that Post URL and select API version 2.0. Select
WiFias Radio Type.
- Add another Post URL for your
Bluetoothdevices pointing to the same location as the previously added Post URL. Ensure the
Secretis the same.
Setting up the receiver
Finally set up the receiver.
- Type in the
Secretyou have entered in the Meraki Dashboard.
- Select the IP, port and the route the adapter will listen on for Meraki API request.
- The regular expressions for filtering the Wifi and Bluetooth devices have not reached production level.
- Check if you want the receiver to report only
connectedWiFi devices (recommended). In that case the adapter will report only device connected to one of your SSIDs and with a valid IP-address.
- Set the amout of time the adapter will consider a device as offline, when there's no more report.
- Set the interval on how often to check for offline devices.
I strongly recommend to put the receiver in behind of a reverse proxy like NGINX Reverse Proxy or Traefik. Do not forget to configure HTTPS & TLS properly to encrypt any public network traffic to your reverse proxy.
I strongly recommend to never expose any native ioBroker services to public endpoints. Don't do that!
The Cisco Meraki wireless access points will report any WiFi device in range, even if the devices are not connected to any of your SSIDs. This is great in some situations like burglar or robbery to provide wireless fingerprints of any device around at that special point of time. But you'll get a lot devices in your database.
- (MiGoller) Added Meraki CMX API raw data (JSON) as status per device.
- (MiGoller) Added integration of the Places-adapter.
- (MiGoller) Bugfix missing dependencies.
- (MiGoller) First release reporting WiFi and Bluetooth devices.
- (MiGoller) initial release
Copyright (c) 2019 MiGoller email@example.com
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.