> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.kodelabs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connected Sensors

> Connect Connected Sensors to KODE OS for leak detection data

> Connect Connected Sensors to KODE OS for leak detection data integration

## Overview

Use this integration to ingest Connected Sensors water and leak telemetry into KODE OS over MQTT. You discover devices and collect historical point data for monitoring usage and leak-related signals.

| Property            | Value          |
| ------------------- | -------------- |
| **System Type**     | Leak Detection |
| **Communication**   | MQTT           |
| **Collection**      | Pull           |
| **Collection Mode** | HISTORICAL     |

## Supported Capabilities

* Discover Devices & Points
* Collect Sensor Data
* MQTT Data Collection

## Prerequisites

* Access to the MQTT broker used by Connected Sensors
* Broker hostname, port, and credentials
* KODE OS environment with access to Data Sources

## Generate API Credentials

1. Log in to the Connected Sensors platform or admin console
2. Navigate to the API settings, developer section, or account settings
3. Generate a new API key or token
4. Copy the key and store it securely -- you will need it when configuring the connector in KODE OS

## Configure Connector in KODE OS

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

| Field               | Required    | Type     | Description                                              |
| ------------------- | ----------- | -------- | -------------------------------------------------------- |
| **URL**             | Yes         | text     | The base URL or IP address of the external system        |
| **API Key**         | Yes         | password | The API key for authenticating with the external system  |
| **API Building ID** | Yes         | password | The building or source identifier in the external system |
| **Host**            | Conditional | text     | The host address for the connection                      |
| **Port**            | Conditional | text     | The port number for connecting to the system             |

## Discover Devices and Points

After configuring the connector, click **Discover** on the connector detail page. KODE OS will query the Connected Sensors 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](/products/integrations/capabilities/discovery).

## Devices and Points

When you discover devices from Connected Sensors, KODE OS maps them to the following device types:

* **Leak Detection Sensor** (`leakDetection`)

| Point                                    | Display Name                           |
| ---------------------------------------- | -------------------------------------- |
| `watermonkeyv3.0single`                  | watermonkeyv3 0single                  |
| `watermonkeyv3.0`                        | watermonkeyv3 0                        |
| `watercounter1.0`                        | watercounter1 0                        |
| `ambient_temperature`                    | ambient temperature                    |
| `maximum_ambient_temperature`            | maximum ambient temperature            |
| `maximum_ambient_temperature_fahrenheit` | maximum ambient temperature fahrenheit |
| `maximum_pipe_temperature`               | maximum pipe temperature               |
| `minimum_ambient_temperature`            | minimum ambient temperature            |
| `maximum_pipe_temperature_fahrenheit`    | maximum pipe temperature fahrenheit    |
| `minimum_ambient_temperature_fahrenheit` | minimum ambient temperature fahrenheit |
| `ambient_temperature_fahrenheit`         | ambient temperature fahrenheit         |
| `minimum_pipe_temperature`               | minimum pipe temperature               |
| `minimum_pipe_temperature_fahrenheit`    | minimum pipe temperature fahrenheit    |
| `pipe_temperature_rolling_fahrenheit`    | pipe temperature rolling fahrenheit    |
| `barometric_pressure`                    | barometric pressure                    |
| `ground_floor_pressure`                  | ground floor pressure                  |
| `middle_floor_pressure`                  | middle floor pressure                  |
| `humidity`                               | humidity                               |
| `pipe_temperature`                       | pipe temperature                       |
| `pipe_temperature_fahrenheit`            | pipe temperature fahrenheit            |

## 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](/products/integrations/capabilities/data-collection).

## Use Cases

Once connected, this integration enables you to:

* Receive real-time alerts when water leaks or abnormal flow is detected
* Track leak event history and response times for compliance reporting
* Correlate water consumption data with leak detection sensors

## Troubleshooting

<AccordionGroup>
  <Accordion title="No data arriving from MQTT broker">
    Verify the MQTT broker hostname, port, and credentials. Check that the topic patterns match the topics being published by the Connected Sensors devices. Ensure the MQTT client has subscribe permissions.
  </Accordion>

  <Accordion title="Discovery returns no devices">
    Verify the connector credentials have sufficient permissions in the Connected Sensors system to list devices. Run a test connection first to confirm connectivity. Some systems require specific API scopes or roles for device enumeration.
  </Accordion>

  <Accordion title="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 Connected Sensors API.
  </Accordion>
</AccordionGroup>