> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/integrations/video-management-systems/bosch-cameo-vms-integration.md).

# Cameo VMS Integration

The Bosch Cameo VMS Integration has the same core capabilities as the [Bosch VMS Integration](/knowledge-hub/products/integrations/video-management-systems/bosch-vms-integration.md): live view from Site plans, Equipment list, Challenge viewer, and Status viewer; stored video from the Alarm viewer; playback; PTZ; event to preset; and motion and diagnostic alarms to Command Centre.

It uses the **BVMS Cameo SDK v10.1.0.1289**.

**Tested hardware:** Bosch Autodome 7000; Flexidome HD 1080P; Flexidome corner 9000 MP; Autodome Starlight 7000 HD 30X Inceil Tint.

{% hint style="danger" %}
Gallagher tests each integration with a small selection of cameras and can only guarantee those.
{% endhint %}

***

🔗 **Related**

* [Bosch VMS Integration](/knowledge-hub/products/integrations/video-management-systems/bosch-vms-integration.md). The other Bosch integration.


---

# 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://help.security.gallagher.com/knowledge-hub/products/integrations/video-management-systems/bosch-cameo-vms-integration.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.