> 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.md).

# Xovis

<figure><img src="https://627748108-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0shDrJltbdGiCRz6ip4Z%2Fuploads%2FSIx7CAT4vBSYNDx8yhI2%2Fxovis-card-white.png?alt=media&amp;token=becd4171-80a9-4316-85c9-5cc86f68b00e" alt="" width="375"><figcaption></figcaption></figure>

UMA Vision integrates with the Xovis PC2SE people-counting sensor, giving you accurate real-time occupancy data — whether the sensor is mounted in the centre of a room or over a building entrance.

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><p><mark style="color:$primary;"><strong>Getting started</strong></mark> </p><p>Everything you need to know about the Xovis PC2SE people-counting integration.</p></td><td><a href="https://support.meetuma.ai/uma-knowledgebase/integrations/iot-sensors/xovis.md#getting-started">Xovis</a></td></tr><tr><td><p><mark style="color:$primary;"><strong>Device configuration</strong></mark> </p><p>Step-by-step guide to configure the Xovis PC2SE Data Push and add the sensor to UMA Vision.</p></td><td><a href="https://support.meetuma.ai/uma-knowledgebase/integrations/iot-sensors/xovis/xovis-configuration.md">Xovis configuration</a></td></tr></tbody></table>

### Integration overview

Xovis PC2SE sensors push people-count data to UMA Vision over MQTT. Once connected, occupancy appears alongside all your other sensors on the floor map, device pages, insights, and analytics — with full support for auto-booking and auto-release.

#### Key features

1. **People counting:**
   * **Room occupancy** — a single sensor in the centre of a room counts how many people are present, updating within a minute of someone entering or leaving
   * **Floor and building occupancy** — mount several sensors over the entrances to a floor or building, assign them all to the same UMA resource, and the counts are combined into a single total. Adding or removing a sensor takes effect immediately
   * **Overnight reset** — entrance-based running counts reset automatically each night, so small miscounts don't accumulate from one day to the next
2. **Booking automation:**
   * **Auto-book** — enable automatic booking when occupancy is detected in a room
   * **Auto-release** — free the room automatically after the configured period with no one present. A momentary gap in the count does not release a room that is still in use
3. **Data visualisation:**
   * Live and historical occupancy data from Xovis sensors are accessible on the main **Insights dashboard** and **Device Insights** pages
   * The floor map shows **live occupancy** for any resource linked to a Xovis sensor, identical to resources backed by other occupancy sensors
   * Floor-level and building-level occupancy totals include Xovis people counts

## Getting started

{% hint style="info" %}
**Note:** This integration requires access to the Xovis sensor's management interface (typically via the sensor's local IP address in a web browser). UMA will provide customer-specific MQTT connection details to connect the sensor to UMA Vision — contact your Customer Success Manager if you haven't received them.
{% endhint %}

#### Sensor types

The Xovis PC2SE can be deployed in two modes depending on where it is mounted:

**Room centre (area counting)** — the sensor is mounted in the centre of a room and counts the number of people present at any given moment. This is ideal for meeting rooms, collaboration spaces, and any enclosed area where you need a live headcount.

**Entrance (in/out counting)** — the sensor is mounted over a doorway or entrance and tracks people entering and leaving, maintaining a running total. Mount multiple sensors over all the entrances to a floor or building and assign them to the same UMA resource to get a combined occupancy figure. The running count resets overnight to prevent drift.

#### What you get in UMA Vision

Once connected, Xovis sensors work identically to other supported sensors in UMA Vision:

* **Real-time readings** — live people count on device detail pages with online/offline status
* **Floor maps** — occupancy status visible on your floor maps
* **Auto-booking and auto-release** — occupancy sensors can automatically book and release rooms based on detected presence
* **Analytics and reporting** — historical data flows through to sensor dashboards, Space Usage & Trends, and reports (Analytics Pro)
* **AI insights** — use Explain with AI on sensor charts for plain-English summaries of trends and patterns (Enterprise)

### Firewall rules

To check relevant firewall rules for the MQTT connection, see the [Firewall rules page](https://support.meetuma.ai/uma-knowledgebase/getting-started/security/firewall-rules.md).


---

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