Skip to main content
Connect Attune to KODE OS for indoor environmental quality data integration

Overview

Use this integration to connect Attune to KODE OS. You can discover sensors and devices, receive environmental IoT data through webhook push collection with snapshot mode, and monitor indoor conditions from Data Sources.

Supported Capabilities

  • Discover Devices & Points
  • Collect Sensor Data
  • Receive Webhook Data
  • File Validation

Prerequisites

To integrate with the Attune API, ensure you have the following details:
  • An active account in https://my.senseware.co with the appropriate access permissions.
  • Valid username and password credentials for the Attune platform.

Configure Webhook

Steps to Enable Attune Data Forward
  • Log in to the Attune Platform using your username and password
  • From Left side bar Tools click Forwards button
  • Click button “Add Data Forward”
  • Configure the basic settings for your Data Forward:
  • Enter a Data Forward Name that clearly identifies the purpose or destination.
  • Set permissions like Can View and Can Modify/Delete based on your team’s access needs.
  • Input the Data Destination
  • Enter a descriptive name for the Data Forward.
  • Specify the URL where the data should be sent.
  • Choose the data type and update frequency.
  • Add optional key/value header pairs that you want to send along with each HTTP request.
  • Click Save Destination to apply your changes—this step is required, or all settings will be lost, and then click channels to move to the data selection section
  • Select the data to be forwarded:
  • Choose the relevant Modules (devices)—each contains 15 channels (data points).
  • Choose the relevant Modules (devices)—each contains 15 channels (data points).
  • Click Save Channels to apply your selections, then proceed to the Permissions section.
  • Permissions: Configure access rights using the same logic as in the previous step.
  • Click Done >> to confirm your Data Forward configuration

Configure Connector in KODE OS

  1. Navigate to Data Sources in your building
  2. Click API Catalog and search for Attune
  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 Attune 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 Attune, KODE OS maps them to the following device types:
  • Air Quality Sensor (airQuality)

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
For more details on collection modes, see the Data Collection guide.

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

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 Attune platform.
Verify the webhook URL is correctly registered in the Attune platform. Check that the authentication header matches the value from the KODE OS connector detail page. Ensure the Attune system can reach the KODE OS webhook endpoint over the network.
Verify the connector credentials have sufficient permissions in the Attune 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 Attune API.
Last modified on March 29, 2026