> 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/video-conferencing/logitech.md).
# Logitech
UMA Vision integrates with Logitech Sync Cloud to bring occupancy and environmental telemetry from your Logitech devices into your existing dashboards, reports, and live floor map insights — with no additional analytics configuration required.
Admins can connect their organisation's Logitech Sync Cloud account to UMA Vision to monitor room occupancy and environmental conditions in real time. Devices are discovered automatically via the Sync Cloud API and assigned to UMA resources, so telemetry flows into the same pipeline used by Milesight, EnOcean, Neat, and other supported integrations.
**Key Features**
1. **Device Integration:**
* Admins can add the following Logitech devices using a scalable auto-scan feature:
* Rally Bar
* Rally Bar Mini
* Rally Board 65
* Spot
* Rally
* Sight
* Tap
* Tap IP
* Tap Scheduler
* Logi Dock Flex
* Brio 505
* The system fetches and displays basic device details from the Sync Cloud API upon scanning. Devices can be assigned to UMA resources individually or in bulk.
2. **Occupancy and Environmental Monitoring:**
The following telemetry is available from supported devices:
| Device | Presence | People count | CO₂ | Temp | Humidity | TVOC / VOC | PM2.5 | Auto-book / release |
| -------------- | -------- | ------------ | --- | ---- | -------- | ---------- | ----- | ------------------- |
| Rally Bar | ✅ | ✅ | – | – | – | – | – | ✅ |
| Rally Bar Mini | ✅ | ✅ | – | – | – | – | – | ✅ |
| Rally Board 65 | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| Spot | ✅ | – | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| Rally | – | – | – | – | – | – | – | – |
| Sight | – | – | – | – | – | – | – | – |
| Tap | – | – | – | – | – | – | – | – |
| Tap IP | – | – | – | – | – | – | – | – |
| Tap Scheduler | – | – | – | – | – | – | – | – |
| Logi Dock Flex | – | – | – | – | – | – | – | – |
| Brio 505 | – | – | – | – | – | – | – | – |
* **Rally Bar** and **Rally Bar Mini** provide occupancy data (presence and people count), enabling auto-book and auto-release for the rooms they are assigned to.
* **Rally Board 65** and **Spot** add a full environmental suite — CO₂, temperature, humidity, TVOC, and PM2.5 — giving you room-level air quality alongside occupancy from a single device.
* Devices without telemetry columns are discovered and visible in your device list but do not currently report data to UMA.
3. **Data Visualisation:**
* Live and historical data from Logitech devices are accessible on the main **Insights dashboard** and **Device Insights** pages along with Analytics and Analytics Pro.
* Device-specific information is also shown on device cards and zone views, allowing admins to monitor data directly from the associated resources.
* Occupancy data from supported devices feeds into auto-book and auto-release workflows, so rooms are freed up the moment they are vacated.
***
**Logitech Sync Cloud Certificate Setup**
To connect UMA Vision to your Logitech Sync Cloud organisation, you will need the **certificate**, **private key**, and **Org ID** from the Logitech Sync Cloud portal.
1. Log in to the [Logitech Sync Cloud portal](https://sync.logitech.com/).
2. Navigate to **System → Sync Cloud API**.
3. Generate a new certificate. The portal will display your **certificate**, **private key**, and **Org ID**.
4. Copy all three values — store them securely, as the private key cannot be retrieved again after generation.
{% hint style="info" %}
You will need a Logitech Sync Cloud licence that includes API access to generate certificates. Contact your Logitech account manager if the Sync Cloud API section is not available in your portal.
{% endhint %}
***
**UMA Vision Integration**
1. Navigate to **Settings → Integrations** in UMA Vision.
2. Locate the **Logitech Sync Cloud** integration and toggle it on.
3. Paste your **certificate**, **private key**, and **Org ID** into the corresponding fields.
4. Click **CONNECT**. UMA will validate the connection with a test call before saving your credentials.
Once connected:
5. Navigate to **Manage → Devices → Add Device**.
6. Select **Logitech** as the device group.
7. Use the **auto-scan** feature to discover all devices in your Sync Cloud organisation.
8. Select the devices you want to add and assign each one to a UMA resource (building, floor, and resource).
9. Click **Save**. Telemetry will begin flowing within minutes.
***
**Disconnecting**
To disconnect the Logitech Sync Cloud integration:
1. Navigate to **Settings → Integrations**.
2. Locate the **Logitech Sync Cloud** integration.
3. Click **Disconnect** and confirm.
Telemetry ingest stops immediately and credentials are removed. Previously captured data is retained for historical reporting.
---
# 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/video-conferencing/logitech.md?ask=&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.
