> ## 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.

# EnOcean

> Connect EnOcean to KODE OS for controller data

> Connect EnOcean to KODE OS for controller data integration

## Overview

Use this integration to connect EnOcean SmartServer IoT data to KODE OS over MQTT. You can discover devices and points and collect wireless sensor data for smart-building monitoring.

| Property            | Value      |
| ------------------- | ---------- |
| **System Type**     | Controller |
| **Communication**   | MQTT       |
| **Collection**      | Pull       |
| **Collection Mode** | SNAPSHOT   |

## Supported Capabilities

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

## Prerequisites

* Access to the MQTT broker used by EnOcean
* Broker hostname, port, and credentials
* 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 **EnOcean**
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         |
| **Username**              | Yes         | text     | The username for authenticating with the external system  |
| **Password**              | Yes         | password | The password for authenticating with the external system  |
| **Collect Mode**          | Yes         | dropdown | The data collection mode (e.g., SNAPSHOT, DELTA)          |
| **IP Address**            | Conditional | text     | The IP address of the on-site controller or device        |
| **Port**                  | Conditional | text     | The port number for connecting to the system              |
| **Segment Controller ID** | Conditional | text     | The segment controller identifier in the lighting network |

## Discover Devices and Points

After configuring the connector, click **Discover** on the connector detail page. KODE OS will query the EnOcean 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 EnOcean, KODE OS maps them to the following device types and data points:

### Controller

Canonical Type: `default`

| # | Point            | Description                                                                      | Unit | Writable | Collection |
| - | ---------------- | -------------------------------------------------------------------------------- | ---- | -------- | ---------- |
| 1 | `in`             | Input signal value                                                               | --   | No       | MQTT       |
| 2 | `locValue`       | **True** -- locValue is active / **False** -- locValue is not active             | --   | No       | MQTT       |
| 3 | `state`          | Current operating state                                                          | --   | No       | MQTT       |
| 4 | `health`         | Device health status                                                             | --   | No       | MQTT       |
| 5 | `connection`     | Device connection status                                                         | --   | No       | MQTT       |
| 6 | `action`         | Last triggered action                                                            | --   | No       | MQTT       |
| 7 | `wasProvisioned` | **True** -- wasProvisioned is active / **False** -- wasProvisioned is not active | --   | No       | MQTT       |

## What Data You Get

### Point History

Time-series readings including in, locValue, state, health, connection, action, wasProvisioned, collected at regular intervals from connected devices

### Polling Schedule

* **Point History** -- Default polling: 1 minutes (min: 1 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:

* Monitor real-time HVAC, lighting, and building automation data from a single dashboard
* Set up automated alerts when equipment deviates from normal operating parameters
* Track energy consumption and optimize building performance with historical trend data

## 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 EnOcean devices. Ensure the MQTT client has subscribe permissions.
  </Accordion>

  <Accordion title="Discovery returns no devices">
    Verify the connector credentials have sufficient permissions in the EnOcean 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 EnOcean API.
  </Accordion>
</AccordionGroup>