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

# Xovis configuration

## Xovis Sensor Data Push Setup

The Xovis PC2SE sends data to UMA Vision via MQTT. You configure the data push in the sensor's own management interface.

{% hint style="info" %}
**Note:** You will need access to the Xovis management interface for the sensor(s) you want to connect. This is typically accessed via the sensor's local IP address in a web browser.
{% endhint %}

{% hint style="info" %}
**Note:** Unsure about UMA's MQTT server details? See the [MQTT page](https://support.meetuma.ai/uma-knowledgebase/integrations/iot-sensors/mqtt.md).
{% endhint %}

#### Step 1 — Create an MQTT Connection

1. In the Xovis management interface, go to **Connections**
2. Click **+ Add connection** and select **MQTT**
3. Enter the **Server URI**, **Port**, and **authentication credentials** provided by UMA
4. Enable **SSL/TLS** and leave **Websocket** off
5. Under **Advanced settings**, set:

| Setting                | Value                                 |
| ---------------------- | ------------------------------------- |
| Connection timeout (s) | `10`                                  |
| QoS level              | `1 - At least once`                   |
| Client id              | Any unique identifier for this sensor |
| Topic                  | xovis                                 |

6. Save the connection

#### Step 2 — Create a Logics Push Agent

1. Go to **Agents** and click **+ Add new agent**
2. Select **Logics Push** as the agent type
3. Set the **Connection** to the MQTT connection you just created
4. On the **Data** tab, configure:

| Setting                 | Value                                    |
| ----------------------- | ---------------------------------------- |
| Logics (Data filtering) | Select the logic you want in the payload |
| Format                  | `JSON`                                   |
| Time format             | `Unix Time MS`                           |
| Normalization           | `None`                                   |
| Full package info       | **Off**                                  |
| Full sensor info        | **On**                                   |
| Pretty format           | **Off**                                  |

5. On the **Scheduling** tab, configure:

| Setting                 | Value      |
| ----------------------- | ---------- |
| Scheduler type          | `Interval` |
| Interval (package time) | `1 minute` |
| Resolution              | `1 minute` |

6. Save the agent
7. Ensure the agent shows as **active** (blue toggle enabled)

{% hint style="info" %}
**Warning:** The **Full sensor info** toggle must be **On** — UMA Vision uses the sensor information in the payload to identify the device. Without it, data will arrive but cannot be matched to a resource.
{% endhint %}

***

## Add the device to UMA

Once the sensor is pushing data to the MQTT broker, add it in UMA Vision:

1. Navigate to **Manage → Devices → Add Device**
2. Select **Xovis** as the device group
3. Select **Xovis PC2SE** as the sensor type
4. Enter the sensor's **serial number** as printed on the device
5. Assign the sensor to a **UMA resource** — select the building, floor, and resource (room or zone)
6. Click **Save**

Occupancy data will begin appearing within a minute of the sensor's next push.

#### Multiple sensors on one resource

To monitor a floor or building using entrance-based counting, assign all the entrance sensors to the **same UMA resource** (typically a zone representing the floor). Their counts are combined automatically — no additional configuration needed.

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

***

### Device page

Once connected, the Xovis device page shows:

* **Live people count** — the current number of people detected
* **Online / offline status** — the device shows as Online while it is sending data
* **Last seen** — when the last data push was received, including while the space is empty and no one is moving
* **Serial number** and **registration date**

***

### Removing a sensor

To remove a Xovis sensor from UMA Vision:

1. Navigate to **Manage → Devices**
2. Locate the Xovis sensor and open its detail page
3. Click **Delete** and confirm

Previously captured occupancy data is retained for historical reporting. To stop data arriving at the MQTT broker, also disable or delete the Logics Push Agent in the sensor's management interface.

***

### Troubleshooting

| Symptom                                     | Check                                                                                                                                                               |
| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Sensor shows as offline in UMA              | Verify the MQTT connection is active in the Xovis management interface. Check that the Server URI, port, and credentials match what UMA provided                    |
| Data arriving but not matched to a resource | Ensure **Full sensor info** is toggled **On** in the agent's Data tab. Verify the serial number in UMA matches the sensor's actual serial number (case-insensitive) |
| People count seems incorrect for a floor    | Check that all entrance sensors for the floor are assigned to the same UMA resource. The overnight reset clears accumulated drift each night                        |
| Sensor not appearing in UMA device list     | Confirm the agent is active and the connection is established. Wait at least one minute for the first data push to arrive                                           |


---

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