# Connecting Cloud Devices

**Cloud devices** in **RUFUS Race Manager (RRM)** allow for flexible, remote connectivity, leveraging the cloud infrastructure to manage race timing data. These devices connect to the **RUFUS Cloud** and can be used for race timing across different locations, providing centralized management and monitoring. To connect a cloud device, users only need to assign it to an event within RRM.

<figure><img src="/files/INxur5WazmlJ6auVFa2S" alt=""><figcaption><p>Add Cloud Device Modal</p></figcaption></figure>

## How to Connect Cloud Devices

To connect a cloud device to **RRM**, users need to configure the device through the **Add Device** modal. The following fields must be completed:

### Add Device Modal Fields

* **Checkpoint(s)**: Select one or more checkpoints where the device is installed. This ensures that the device is accurately assigned to specific points in the race, allowing RRM to manage and record participant passings correctly.
* **Bounce Time**: Set the bounce time, which represents the interval (in seconds) during which the system will ignore repeated passings from the same device. This helps to avoid duplicate readings, ensuring that each passing is only recorded once.

Since the cloud device is already bound to the user's cloud account, users do not need to enter the IP address or port information. Instead, they simply assign the device to specific checkpoints in the event.

## Important Considerations for Cloud Devices

* **Event Assignment**: Cloud devices can only be assigned to **one event at a time**. Once the device has completed its use in an event, it must be **disconnected** from the event before it can be assigned to another. This ensures that devices are uniquely linked to one event, avoiding conflicts in data collection.
* **Internet Connectivity**: Cloud devices require an active internet connection to communicate with the **RUFUS Cloud** and to transmit passings data to **RRM**.

## When to Use Cloud Devices

Cloud devices are recommended for events that require **remote connectivity** and **centralized data management**. They are ideal for:

* **Multi-location events** where data needs to be collected from multiple locations and transmitted centrally.
* **Events with reliable internet access**, allowing for seamless data transmission to the cloud.
* **Scenarios where remote monitoring and control** of timing devices are needed, providing flexibility for race managers.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.runonrufus.com/rufus-race-manager/timing-devices-integration/connecting-cloud-devices.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.