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
  • Local only configuration
  • Building search configuration
  • Placing data on a map
  • Defining map regions
  • Backoffice extensions
Export as PDF
  1. Tutorials
  2. Common Configurations

Sensor Data Collection

Using location services to collect sensor data

PreviousDesk bookingNextConfigure Kontakt IO

Last updated 8 months ago

There are two modes that location services can function in

  • Local only All sensor data is coming from platforms with drivers in the current system

  • Building search Sensors can exist in any system, as well as locally, and the building is searched for modules implementing the sensor interface

Before going further, see the guide on configuring and follow all steps, the desk booking driver is optional.

Local only configuration

Add the sensor platform sources and their location service modules to the location services system.

Some examples include

  • and corresponding

  • is a two in one

  • and

Building search configuration

Where sensors are communicated with directly, not via a 3rd party platform, they will be configured in that represent their physical location.

To enable building search, add the following setting to the buildings location services system

search_building: true

The location services driver auto-detects the building it is providing locations for.

Placing data on a map

Generate sensor metadata

Ensure all the sensor data is up-to-date in AreaManagement.

If the sensors have just been configured, perform the following actions in backoffice to ensure sensor meta data is saved (this occurs automatically periodically)

  1. select the location services system

  2. select the modules tab

  3. execute the following commands

    1. AreaManagement_1 -> synchronize_all_levels

    2. AreaManagement_1 -> write_sensor_discovery

This saves building level metadata: sensor-discovered

Place sensor data

Level zones have a Sensors tab that allows placement of sensor data on a map

  • Data coming from local only configuration is listed when selecting any level

  • Data coming from building search will only show on matching levels

Remember to click save!

Sensor locations are stored in level metadata called sensor-locations

Defining map regions

Level zones have a Sensors tab that allows drawing of regions on the map.

  1. Either select an existing region OR click New Region

  2. Click and drag the desired area on the map

  3. Remember to click save!

Region metadata is stored in map_regions - you can edit this for fine tuned adjustment or if you would like to define more complex polygon shapes.

Backoffice extensions

Both Sensor Placement and Map Regions UIs are backoffice extensions. The following will enable the tabs if they are not available

Sensor placement

Region mapping

desk bookings
Vergesense API
Vergesense Location Service
BACnet
Cisco Meraki Dashboard
Meraki Location Services
Juniper Mist Location Services
PlaceOS Systems
Sensor placement UI
Backoffice extension UI