Skip to main content
Connect Kontakt to KODE OS for occupancy data integration

​
Overview

Use this integration to connect Kontakt.io BLE beacons and indoor location to KODE OS. You can discover beacon and sensor assets, then collect snapshot presence and proximity data for occupancy, wayfinding, and safety workflows.

​
Supported Capabilities

  • Discover Devices & Points
  • Collect Sensor Data

​
Prerequisites

  • An active account with Kontakt and access to their API or developer portal
  • KODE OS environment with access to Data Sources

​
Configure Connector in KODE OS

  1. Navigate to Data Sources in your building
  2. Click API Catalog and search for Kontakt
  3. Click + Add Datasource
  4. Fill in the fields below and complete the three-page setup flow

​
Discover Devices and Points

After configuring the connector, click Discover on the connector detail page. KODE OS will query the Kontakt system and return a list of available devices and their data points. Review the discovered items and select the devices you want to register in KODE OS. For more details on the discovery process, see the Discovery guide.

​
What Data You Get

​
Point History

Time-series sensor readings such as temperature, humidity, CO2, occupancy counts, energy consumption, light levels, and other measurable values from physical sensors

​
Polling Schedule

  • Point History — Default polling: 5 minutes (min: 5 minutes, max: 1 hours)
For more details on collection modes, see the Data Collection guide.

​
Use Cases

Once connected, this integration enables you to:
  • Track real-time space utilization rates across floors and zones
  • Optimize HVAC and lighting schedules based on actual occupancy patterns
  • Generate utilization reports to inform space planning and real estate decisions

​
Troubleshooting

Verify that the credentials are correct and have not expired. Check that the URL is reachable from the KODE OS environment. Double-check all credential fields match the values from the Kontakt platform.
Verify the connector credentials have sufficient permissions in the Kontakt system to list devices. Run a test connection first to confirm connectivity. Some systems require specific API scopes or roles for device enumeration.
Check the connector status on the Data Sources page. If the status shows an error, review the error logs on the connector detail page. Common causes include expired credentials, network changes, or rate limiting by the Kontakt API.
Last modified on March 29, 2026