> For the complete documentation index, see [llms.txt](https://support.meetuma.ai/uma-knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.meetuma.ai/uma-knowledgebase/integrations/iot-sensors/enocean.md).

# EnOcean

<figure><img src="https://627748108-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0shDrJltbdGiCRz6ip4Z%2Fuploads%2FX12BRGXzVVwcAkha78R3%2FEnOcean_logo_frame_claim_pos_rgb.png?alt=media&amp;token=ee80d74d-652b-41ee-8e42-e7bf284c02ec" alt=""><figcaption></figcaption></figure>

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>Getting started</strong></mark></td><td>Everything you need to know about our integration.</td><td></td><td><a href="/uma-knowledgebase/integrations/iot-sensors/enocean.md#getting-started">EnOcean</a></td></tr><tr><td><mark style="color:blue;"><strong>Device configuration</strong></mark></td><td>Just need to set up a device? Click here.</td><td></td><td><a href="/uma-knowledgebase/integrations/iot-sensors/enocean/enocean-configuration.md">EnOcean configuration</a></td></tr></tbody></table>

## Integration overview

EnOcean Smart Studio enables organisations running Cisco Catalyst Access Points to use their existing network infrastructure for IoT sensors — without additional gateway hardware.

By connecting a simple EnOcean USB 300 dongle to a Cisco Catalyst Access Point, EnOcean sensors can communicate wirelessly through the building's existing Wi-Fi infrastructure. Sensor data is forwarded via EnOcean Smart Studio's cloud platform to UMA Vision over MQTT, where it appears alongside all your other devices with full support for real-time monitoring, auto-booking, auto-release, and analytics.

This integration is ideal for organisations that already have Cisco Catalyst APs deployed across their buildings and want to add occupancy, environmental, and energy monitoring without investing in separate gateway hardware.

## How it works

Sensor → EnOcean USB 300 dongle → Cisco Catalyst Access Point → EnOcean Smart Studio → MQTT → UMA Vision

## Getting started

{% hint style="info" %}
This integration requires an EnOcean Smart Studio subscription and Cisco Catalyst Access Points with IOx application hosting support. UMA will provide customer-specific MQTT credentials to connect Smart Studio to UMA Vision.
{% endhint %}

To learn more about EnOcean Smart Studio, visit [app.enocean.cloud](https://app.enocean.cloud/).

UMA supports the following EnOcean sensors via EnOcean Smart Studio:

#### Desk occupancy sensor

{% embed url="<https://www.pressac.com/desk-occupancy-sensors/>" %}

#### Room occupancy sensor

{% embed url="<https://www.pressac.com/room-occupancy-sensors/>" %}

#### Co2, temperature and humidity sensor

{% embed url="<https://www.pressac.com/co2-temperature-and-humidity-sensors/>" %}

#### Current monitoring sensor

{% embed url="<https://www.pressac.com/current-monitoring-sensors/>" %}

## Firewall rules

To check relevant EnOcean firewall rules click [here](/uma-knowledgebase/getting-started/security/firewall-rules.md#pressac-devices).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.meetuma.ai/uma-knowledgebase/integrations/iot-sensors/enocean.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.