> 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/pressac/pressac-configuration.md).

# Pressac configuration

<figure><img src="https://627748108-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0shDrJltbdGiCRz6ip4Z%2Fuploads%2FlMpRDjSrdGufBH9uez81%2Fpressac-primary-logo-blue.png?alt=media&amp;token=26e61415-eabe-4372-968e-082bfb023e2b" alt="" width="189"><figcaption></figcaption></figure>

## **Gateway setup**&#x20;

This guide assumes you’ve already connected your gateway to either an Ethernet, Wi-Fi or LTE network.

If you haven't, follow the manufacturers set up guide below:

{% embed url="<https://support.pressac.com/kb/gateway-configuration/>" %}

Log in to the gateway via a web interface and navigate to **connections** and **MQTT** and enter in the following details:

* Default Client ID: <mark style="color:blue;">{gateway name}</mark>
* Root Topic: <mark style="color:blue;">umavision</mark>
* Device Identifier: <mark style="color:blue;">Device ID</mark>
* Included Data: <mark style="color:blue;">Tick All</mark>
* MQTT Connection Name: <mark style="color:blue;">UMA Vision</mark>
* Client ID: <mark style="color:blue;">Use Default</mark>

{% hint style="info" %}
Unsure about UMA's MQTT server details? Click [here](/uma-knowledgebase/integrations/iot-sensors/mqtt.md).
{% endhint %}

***

## **Add a device to UMA**

To add a Pressac IoT sensor to UMA, you will need the Device ID which can be obtained either locally on the sensor or from the Pressac gateway. Use the Device ID as the UMA ID.

When adding a Pressac device in UMA, click on **add device** and then use the UMA card to find the device you want to add.

After some minutes, the device will come online and you will start recording the data coming from the sensor.

{% hint style="success" %}
Optionally, you can allow any Pressac occupancy sensor to auto book or cancel a meeting booking by configuring the device settings.
{% endhint %}

***

## Repeater setup

Repeaters are used to boost the signal to allow sensors to connect to the gateway without adding an additional gateway.

Follow the manufacturers set up guide here:

{% embed url="<https://support.pressac.com/knowledge-base/pressac-enocean-repeater/>" %}

***

## Sensor installation guides

### Desk occupancy sensor

{% embed url="<https://support.pressac.com/knowledge-base/desk-occupancy-sensor/>" %}

***

### Room occupancy sensor

{% embed url="<https://support.pressac.com/knowledge-base/room-occupancy-sensor/>" %}

***

### Co2, temperature and humidity sensor

{% embed url="<https://support.pressac.com/knowledge-base/co2-temperature-and-humidity-sensor/>" %}

***

### Current monitoring sensor (3 channel)

{% embed url="<https://support.pressac.com/knowledge-base/3-channel-ct-clamp-v3/>" %}

***

### Current monitoring sensor (1 channel)

{% embed url="<https://support.pressac.com/knowledge-base/single-channel-ct-clamp-v3/>" %}

***

### Pulse counter

{% embed url="<https://support.pressac.com/knowledge-base/pulse-counter/>" %}


---

# 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/pressac/pressac-configuration.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.