Connect Cloudpop to KODE OS for indoor environmental quality data integration
Overview
Use this integration to connect Cloudpop to KODE OS. You can discover IEQ devices and points, pull snapshot environmental data over REST, and monitor air quality metrics from Data Sources.Supported Capabilities
- Discover Devices & Points
- Collect Sensor Data
Prerequisites
- An active account with Cloudpop and access to their API or developer portal
- KODE OS environment with access to Data Sources
Configure Connector in KODE OS
- Navigate to Data Sources in your building
- Click API Catalog and search for Cloudpop
- Click + Add Datasource
- 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 Cloudpop 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 Cloudpop, KODE OS maps them to the following device types and data points:Air Quality Sensor
Canonical Type:default
What Data You Get
Point History
Time-series readings including battery, temperature, signal, rssi, collected at regular intervals from connected devicesPolling Schedule
- Point History — Default polling: 1 minutes (min: 1 minutes, max: 1 hours)
Use Cases
Once connected, this integration enables you to:- Monitor air quality metrics (CO2, VOC, humidity, temperature) across all occupied spaces
- Generate compliance reports for indoor environmental quality standards
- Trigger ventilation adjustments when air quality thresholds are exceeded
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 Cloudpop platform.
Discovery returns no devices
Discovery returns no devices
Verify the connector credentials have sufficient permissions in the Cloudpop 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 Cloudpop API.