description |
---|
A guide on configuring Kontakt IO Integration with PlaceOS |
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`.
9. Inspect the results, this should contain information about your Kontakt environment confirming you are now connected to the API Service.
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.
Each room you would like to leverage occupancy and auto-release functionality will require the Kontakt IO Room Sensor Driver.
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:
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 |