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
  • Generate a Mist API token
  • Configure Mist Websocket Driver
  • Configure Mist Location Services
Export as PDF
  1. How To
  2. Location Services

People Finding with Juniper Mist on PlaceOS

How to locate people using Juniper Mist

PreviousPeople Finding with Cisco Meraki on PlaceOSNextNotifications

Last updated 3 years ago

Generate a Mist API token

You must record and save the API Token immediately after generating it, as the API Token cannot be re-displayed.

To generate a Mist API Token:

  1. In your browser, access the . The Mist Sign In page opens.

  2. Log in to your Mist account by entering your account credentials.

  3. While logged in to your Mist account, open another browser tab and access the URL

  4. Select POST The generated API Token displays in the following format:

    • "key": "<randomly generated character string>" where the character string is the API Token For example, "key": "34223XFE...e5"

    • also see the

  5. Record and save the API Token, before closing the browser tab.

Note the following about Mist API Tokens:

  • An API Token generated for a specific admin has the same privilege as the user

  • API Tokens are automatically deleted, if not used within 90 days.

Obtain the Site ID

When you configure the PlaceOS connection to Mist, you'll need the site_id for the network you want to monitor. You can obtain these by:

  1. logging into the

  2. select the organisation and site (orange arrow below)

  3. Record and save the UUID from the URL (highlighted in orange)

Configure Mist Websocket Driver

Add the Juniper Mist Websocket driver to the drivers list and configure the settings

{
  # the api token we generated above
  api_token: "<randomly generated character string>",

  # the id of the site we want to monitor
  site_id:   "site_id"
}

Then add the driver to the location services system.

Obtain the list of map ids

We'll need to link Mist maps to PlaceOS maps. Use backoffice to execute the following command:

  • MistWebsocket -> maps (execute)

This will return data like:

[{
  "id": "cbdb7f0b-3be0-4872-88f9-58790b509c23-j68kows8",
  "name": "Mist Office",
  "type": "image"
}]

Configure Mist Location Services

Add the Juniper Mist Locations driver to the drivers list and configure the settings

{
  floorplan_mappings: {
    "mist_map1_id" => {
      "building":   "zone-12345",
      "level":      "zone-123456",
      
      # free text field for reference
      "level_name": "BUILDING - L1"
    },
    "mist_map2_id" => {
      "building":   "zone-12345",
      "level":      "zone-7891",
      
      # free text field for reference
      "level_name": "BUILDING - L2"
    }
  }
}

Once the floor mappings are in place and the module has been added to your location services system, WIFI users will be searchable.

Mist management dashboard
https://api.mist.com/api/v1/self/apitokens
mist guide on this process
Mist management dashboard
Org ID (green), Site ID (orange)