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
  • Add Required Service Drivers
  • Configure Cloud API Module
  • Configure Kontakt Sensor Service
  • Add Room Sensor Drivers
  • Configure Auto Release Rooms
Export as PDF
  1. Tutorials
  2. Common Configurations
  3. Sensor Data Collection

Configure Kontakt IO

A guide on configuring Kontakt IO Integration with PlaceOS

PreviousSensor Data CollectionNextConfiguring Meraki

Last updated 1 year ago

Kontakt IO offer a range of sensors that can be integrated with PlaceOS to:

  • Manage Room Auto-Release (no-show bookings).

  • Presence detection.

  • People Counting.

  • Desk Occupancy.

Prerequisites

  • KontaktIO API Key.

  • Created a Service System for your Org.

  • Added and configured the PlaceOS Location Services driver to your services system.

  • Added and configured the PlaceOS Area Manager driver to your services system.

Add Required Service Drivers

The first step in configuring Kontakt IO integration is to add the required drivers.

These drivers should be added to your services or tracking system, typically denoted by `*ORG Name Services`.

1. Select your Services System

Step 1 screenshot

2. Click on Modules

3. Click on Add new

4. Search for the Kontakt IO Cloud API module

5. Click on Save…

6. Click on Add new

7. Find the KontaktIO Sensor Service module

8. Click on Save…

Configure Cloud API Module

1. From the services system, click on Kontakt IO Cloud API module

2. Click Encrypted tab

3. Enter your Kontakt IO API Key as kio_api_key:

4. Click on Save [S]

5. Start the Kontakt API Module

6. Under Execute Command select KontaktIO 1

7. Select the Rooms Method

8. Click on Execute

9. Inspect the results, this should contain information about your Kontakt environment confirming you are now connected to the API Service.

Configure Kontakt Sensor Service

1. In your Services System, Execute command on KontaktIO 1 Module

2. Select campuses method

3. Click on Execute

4. Click on View

5. Copy this data as you will require it in the next step.

6. Click on close

7. On the services system, click on KontaktIO Sensor Service module

8. Click on Unecrypted

9. under floor_mappings: insert the level id from the Kontakt IO data copied in Step 5. You will need to repeat this metadata key for each floor.

10. Enter your PlaceOS Building Zone ID

11. Enter your PlaceOS Level Zone ID

12. Enter a friendly name for the Level

Add Room Sensor Drivers

Each room you would like to leverage occupancy and auto-release functionality will require the Kontakt IO Room Sensor Driver.

1. Click on Systems

2. Select a Bookable Room system

3. Click on Modules

4. Click on Add new

5. Search for the KontaktIO Room Sensor Driver

6. Click on Save…

7. Start the Module

8. Navigate to the About tab

9. Add the space_ref_id element.

The space_ref_id element can be found by executing the rooms method on the Kontakt IO API Module in your services system. As this is a string, ensure it is wrapped in quotation marks.

Configure Auto Release Rooms

We need to modify a couple of settings to ensure PlaceOS can release booked rooms when no presence is detected via the Kontakt IO Service.

Settings that are required:

Setting
Value
Description
Location

pending_period

int

Number of minutes the room will remain pending until the reservation is cancelled due to no presence.

Zone: Org, Building, Level

penidng_before

int

The number of minutes prior to a scheduled meeting it will show in the Pending state.

Zone: Org, Building, Level

disable_end_meeting

boolean

Allows PlaceOS to cancel meetings where no presence is detected.

Zone: Org, Building, Level

Step 2 screenshot
Step 3 screenshot
Step 4 screenshot
Step 5 screenshot
Step 6 screenshot
Step 7 screenshot
Step 8 screenshot
Step 1 screenshot
Step 2 screenshot
Step 3 screenshot
Step 4 screenshot
Step 5 screenshot
Step 6 screenshot
Step 7 screenshot
Step 8 screenshot
Step 9 screenshot
Step 1 screenshot
Step 2 screenshot
Step 3 screenshot
Step 4 screenshot
Step 5 screenshot
Step 6 screenshot
Step 7 screenshot
Step 8 screenshot
Step 9 screenshot
Step 10 screenshot
Step 11 screenshot
Step 12 screenshot
Step 1 screenshot
Step 2 screenshot
Step 3 screenshot
Step 4 screenshot
Step 5 screenshot
Step 6 screenshot
Step 7 screenshot
Step 8 screenshot