> For the complete documentation index, see [llms.txt](https://docs.optitrack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.optitrack.com/v1.1/motive-ui-pages/device-connections-pane.md).
# Device Connections Pane
Device Connections pane
{% hint style="info" %}
In Motive 1.10 and above, Devices pane has been renamed to Device Connections pane.
{% endhint %}
The Devices pane can be accessed under the View tab in Motive or by clicking  icon on the main toolbar. This pane allows you to monitor device connections for the camera systems and other integrated external devices.
Cameras: A complete list of all cameras connected to the system, their model, and their serial number.
Devices: A complete list of all non-camera devices connected to the system. Hardware keys, synchronization devices, and other periphery will appear here with relevant information.
Devices By Connection: A complete list of all cameras and non-camera devices, ordered by connection to the computer. Detected connection paths will be displayed in tree form.
---
# 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://docs.optitrack.com/v1.1/motive-ui-pages/device-connections-pane.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.
