Skip to content

Configure Kontakt IO

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.

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`.

Step 1 screenshot

Step 2 screenshot

Step 3 screenshot

4. Search for the Kontakt IO Cloud API module

Section titled “4. Search for the Kontakt IO Cloud API module”

Step 4 screenshot

Step 5 screenshot

Step 6 screenshot

7. Find the KontaktIO Sensor Service module

Section titled “7. Find the KontaktIO Sensor Service module”

Step 7 screenshot

Step 8 screenshot

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

Section titled “1. From the services system, click on Kontakt IO Cloud API module”

Step 1 screenshot

Step 2 screenshot

3. Enter your Kontakt IO API Key as kio_api_key:

Section titled “3. Enter your Kontakt IO API Key as kio_api_key:”

Step 3 screenshot

Step 4 screenshot

Step 5 screenshot

6. Under Execute Command select KontaktIO 1

Section titled “6. Under Execute Command select KontaktIO 1”

Step 6 screenshot

Step 7 screenshot

Step 8 screenshot

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

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

Step 9 screenshot

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

Section titled “1. In your Services System, Execute command on KontaktIO 1 Module”

Step 1 screenshot

Step 2 screenshot

Step 3 screenshot

Step 4 screenshot

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

Section titled “5. Copy this data as you will require it in the next step.”

Step 5 screenshot

Step 6 screenshot

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

Section titled “7. On the services system, click on KontaktIO Sensor Service module”

Step 7 screenshot

Step 8 screenshot

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.

Section titled “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.”

Step 9 screenshot

Step 10 screenshot

Step 11 screenshot

Step 12 screenshot

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

Step 1 screenshot

Step 2 screenshot

Step 3 screenshot

Step 4 screenshot

5. Search for the KontaktIO Room Sensor Driver

Section titled “5. Search for the KontaktIO Room Sensor Driver”

Step 5 screenshot

Step 6 screenshot

Step 7 screenshot

Step 8 screenshot

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.

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:

SettingValueDescriptionLocation
pending_periodint Number of minutes the room will remain pending until the reservation is cancelled due to no presence.Zone: Org, Building, Level
penidng_beforeintThe number of minutes prior to a scheduled meeting it will show in the Pending state.Zone: Org, Building, Level
disable_end_meetingbooleanAllows PlaceOS to cancel meetings where no presence is detected.Zone: Org, Building, Level