Connect Verge Sense to KODE OS for occupancy data integration
Overview
Use this integration to connect VergeSense workplace sensors to KODE OS. You can discover spaces and devices, mix scheduled polling with webhooks for hybrid collection, and consolidate real-time occupancy and utilization metrics with non-sensor context where exposed.Supported Capabilities
- Discover Devices & Points
- Collect Sensor Data
- Collect Non-Sensor Data
- Receive Webhook Data
- Collect Historical Data
- Webhook Verification
Prerequisites
- An active account with Verge Sense and access to their API or developer portal
- KODE OS environment with access to Data Sources
Configure Webhook
This integration uses webhooks for real-time data delivery. After creating the connector in KODE OS:- Copy the webhook URL provided on the connector detail page
- In the Verge Sense platform, navigate to the webhook or notification settings
- Add a new webhook endpoint using the KODE OS URL
- Configure the authentication header as specified on the connector detail page
- Save and enable the webhook
Configure Connector in KODE OS
- Navigate to Data Sources in your building
- Click API Catalog and search for Verge Sense
- Click + Add Datasource
- Complete the three-page setup flow using the credential prerequisites for this integration
Connector field metadata is not exposed in code for this integration. Configure the connector using your standard credentials and endpoint details shown in the prerequisites and vendor onboarding references.
Discover Devices and Points
After configuring the connector, click Discover on the connector detail page. KODE OS will query the Verge Sense 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.Devices and Points
When you discover devices from Verge Sense, KODE OS maps them to the following device types and data points:Presence / Occupancy Sensor
Canonical Type:presenceDetection
What Data You Get
Point History
Time-series readings including capacity_hourly, avg_person_count_hourly, min_person_count_hourly, max_person_count_hourly, minutes_actively_occupied_hourly, minutes_passively_occupied_hourly, avg_pct_utilization_hourly, min_pct_utilization_hourly, and 17 more, collected at regular intervals from connected devicesPolling Schedule
- Point History — Default polling: 5 minutes (min: 5 minutes, max: 1 hours)
- CustomSync — Default polling: 1 hours (min: 1 hours, max: 1 hours)
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
Authentication or connection error
Authentication or connection error
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 Verge Sense platform.
Webhook data not arriving
Webhook data not arriving
Verify the webhook URL is correctly registered in the Verge Sense platform. Check that the authentication header matches the value from the KODE OS connector detail page. Ensure the Verge Sense system can reach the KODE OS webhook endpoint over the network.
Discovery returns no devices
Discovery returns no devices
Verify the connector credentials have sufficient permissions in the Verge Sense system to list devices. Run a test connection first to confirm connectivity. Some systems require specific API scopes or roles for device enumeration.
Data collection stops or gaps appear
Data collection stops or gaps appear
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 Verge Sense API.