LogoLogo
  • PlaceOS Documentation
  • Overview
    • Key Concepts
      • Drivers
      • Interfaces
      • Modules
      • Settings
      • Systems
      • Triggers
      • Zones
    • Languages
      • Crystal
      • TypeScript
    • Protocols
      • MQTT
      • SAML
      • OAuth2
  • How To
    • Configure PlaceOS for Microsoft 365
      • Step 1: Room Calendar Access
        • Create Azure App Registration (Application Permissions)
        • Exchange Calendar Group
        • Limit Application Permissions
        • Configure PlaceOS Calendar Driver
      • Step 2: User Authentication & Calendar Access
        • Create a PlaceOS Authentication Source
        • Create Azure App Registration (Delegated Permissions)
        • Configure PlaceOS Authentication Source
        • Add User Login Redirects
      • Concierge Access
      • Troubleshooting
        • Blocked or Blacklisted IP Error
    • Configure PlaceOS for Google Workspace
      • Google Configuration
        • Create Google Cloud Project & Enable API
        • Configure Google Cloud Service Account
        • Add Google Workplace Permissions
        • Create Google Marketplace App (optional)
        • Google Workspace Service User (RBAC)
        • Configure Access to Google Resource Calendars
      • User Authentication
        • Create a PlaceOS Authentication Source for Google
        • Create Google Cloud OAuth2 Client App
        • Configure PlaceOS Auth Source for Google
        • Add User Login Redirects
    • Deployment
      • Deploy AWS Fargate on Modular CloudFormation Stacks
      • Deploy AWS Fargate on Nested CloudFormation Stacks
      • Writing Import Scripts
    • Analytics
      • MQTT Integration
    • Backoffice
      • Add a Domain to PlaceOS
      • Backoffice File Upload
      • Configure Staff API
      • Calendar Driver
      • Enable Sensor UI
      • Bookings Driver
      • Configure a webhook
    • Authentication
      • Azure B2C
        • Azure B2C Custom Policy Framework
        • Configure PlaceOS for Azure B2C
        • 365 Room Resources on Azure B2C
      • Configure SAML SSO
        • Configure SAML2 with AD FS
        • Configure SAML2 with Auth0
        • Configure SAML2 with Azure AD
        • Configure SAML2 with Google Workspace
      • Configure OAuth2 SSO
      • X-API Keys
      • Bearer tokens
    • Location Services
      • Location Services
      • Area Management
      • Discovering User Devices
      • Locating Users on a Network
      • People Finding with Cisco Meraki on PlaceOS
      • People Finding with Juniper Mist on PlaceOS
    • Notifications
      • Catering Orders
    • User Interfaces
      • Booking Panel App
      • Workplace App
      • Native Booking Panel App
      • Deploy a Frontend Interface
      • Microsoft Outlook Plugin
      • Configure Endpoint Auto Login
      • SVG Map Creation
      • Configuring a default UI
  • Tutorials
    • Setup a dev environment
    • Backend
      • Troubleshooting Backend Failures
      • Import Bookable Rooms
      • Writing A Driver
        • Testing drivers
        • ChatGPT / LLM Capabilities
          • Native GPT Plugins
      • Testing Internal Builds
    • Backoffice
      • Adding Drivers & Modules
      • Add Zone Structure
    • Common Configurations
      • Asset Manager
      • Catering
      • Locker Booking
      • Webex Instant Connect
      • Desk booking
      • Sensor Data Collection
        • Configure Kontakt IO
        • Configuring Meraki
        • Configuring DNA Spaces
      • Elevated Privileges
  • Reference
    • API
      • Real-time Websocket
      • Rest API
      • Staff API
    • Drivers
      • PlaceOS
        • Bookings
        • Staff API
        • Visitor Mailer
        • Lockers
      • Microsoft
        • Graph API
    • PlaceOS Skills
    • Privacy Policy
    • Recommended Products
    • Supported Integrations
    • System Architecture
    • System Functionality & Requirements
    • Infrastructure Requirements
    • Security Compliance
      • FAQ
      • GDPR
      • Security
    • Microsoft Azure Permissions
  • Glossary
  • 🎯PlaceOS Roadmap
  • 🆘PlaceOS Support
  • 👩‍💻PlaceOS Github
  • 📝PlaceOS Changelog
Powered by GitBook
On this page
  • Client Prerequisites
  • Dashboard API configuration
  • Scanning API configuration
  • Client Integration
  • Setup PlaceOS Location Services
Export as PDF
  1. Tutorials
  2. Common Configurations
  3. Sensor Data Collection

Configuring Meraki

Cisco Meraki wireless device tracking and camera sensors

PreviousConfigure Kontakt IONextConfiguring DNA Spaces

Last updated 2 years ago

Before going further, see the guide on configuring and follow all steps. This document covers

  • Client Prerequisites

  • Dashboard API configuration

  • Scanning API configuration

  • Client Integration

  • Setup PlaceOS Location Services

Client Prerequisites

  1. Upload and . The floor plans in use must be to scale. It is recommended to use PlaceOS Maps as the floor plans for accurate presentation in client applications.

  2. as accurately as possible based on their physical positions

Dashboard API configuration

Add the Cisco Meraki Dashboard module to the location services system. Add the following settings to the module

meraki_api_key:   "configure for the dashboard API, Client to provide"

meraki_validator: "configure if scanning API is enabled, Integrator to define"
meraki_secret:    "configure if scanning API is enabled, Client to provide"

NOTE: we'll update the values here once the client has configured Meraki.

Scanning API configuration

Scanning API uses to Webhooks to pass information to PlaceOS so we'll need to configure a webhook endpoint for the Dashboard module.

On the triggers tab, add a new trigger for handling the webhook.

  1. Enable webhook functionality

  2. Select GET and POST methods

Add the trigger to your location services system

Once added, edit the webhook to enable tunnelling the data directly to the module

The link will look something like:

  • https://poc.placeos.com/api/engine/v2/webhook/trig-DHgk0FU1~p/notify?secret=kfwu5WYc3a1suZ

  • Modify the link by adding the following parameters &exec=true&mod=Dashboard&method=scanning_api

  • So the webhook URL you will provide to the Meraki Dashboard would look something like https://poc.placeos.com/api/engine/v2/webhook/trig-DHgk0FU1~p/notify?secret=kfwu5WYc3a1suZ&exec=true&mod=Dashboard&method=scanning_api

  • This alternate format with no query params can also be provided: https://poc.placeos.com/api/engine/v2/webhook/trig-DHgk0FU1~p/notify/kfwu5WYc3a1suZ/Dashboard/1/scanning_api where 1 is the Module number (i.e. Dashboard_1)

Client Integration

Clients will need to perform the following steps for PlaceOS integration

    • We use Version 1 of the API

  1. Integrator to enter the API key into the Dashboard module settings

    • Integrator to provide the webhook URL generated above

    • Integrator to provide the validator code, this can be anything, like correcthorsebatterystaple

    • Use Version 3 of the API

  2. Client to provide the Scanning API secret

  3. Integrator to enter the secret into the Dashboard module settings

Setup PlaceOS Location Services

Add the Meraki Location Service module to the location services system

The following system level settings are important:

  • default_network_id - the Meraki network we are interested, typically one per-building

  • floorplan_mappings - we need to map Meraki floorplan IDs to PlaceOS IDs

To collect this information you can execute the following functions in backoffice:

Configure the network ID in the location services system

default_network_id: "N_627126248111343"

Obtain the list of floorplans for that network

Then for each floor plan find the matching PlaceOS building and level zone IDs and add the following setting

floorplan_mappings:
  # Meraki Floorplan ID -> PlaceOS IDs
  g_62712624811134:
    building: zone-HlczU_ONm2E
    level: zone-HlczK4a7UVR
    level_name: BUILDING - L1
  N_627126248111343:
    building: zone-HlczU_ONm2E
    level: zone-HDvg9XMV0Jr
    
    # level_name is here for readability, not used.
    level_name: BUILDING - L2

At this point Meraki device location data will start appearing in the AreaManagement module.

Click Save and copy the webhook link

Client to generate a for the PlaceOS driver to use, read only permissions

Client to enable the

Make note of the organisations ID

make note of the network ID from the list

Copy the result into a text editor

desk bookings
GEOALIGN the floor plans with google maps
Position the WAPS on that floor plan
Meraki Dashboard API Key
Meraki Location Services Scanning API
Webhook trigger
Adding webhook trigger
Enable action execution