# Event-Devices View

The **Event-Devices View** in **RUFUS Race Manager (RRM)** allows users to access and manage all connected devices within an event. This view provides a comprehensive overview of both **Cloud** and **Local** devices, each represented with different icons for easy identification: the cloud icon for **Cloud devices** and an ethernet icon for **Local devices**.

<figure><img src="/files/NrziBYUHr66o8jOYUoUh" alt=""><figcaption><p>Event Devices View</p></figcaption></figure>

## Features of the Event-Devices View

### Device Management

* **Activate/Deactivate Passing Processing**: Users can activate or deactivate the passing processing for each device using the toggle switch.
* **Battery and Temperature Monitoring**: For **Local devices** and **connected CloudBox devices**, the view displays battery status and temperature thanks to IoT implementation. This helps ensure optimal performance and identify any issues related to device power or overheating.
* **Passings Information**: The number of passings, the timestamp of the last recorded passing, and the checkpoints assigned to each device are displayed for all devices.
* **Device Status**: The current status or last known status of each device is displayed to provide a clear understanding of device connectivity and performance.

### Local Device Controls

* **Time Synchronization**: Local devices can be time-synchronized, ensuring accurate timestamps for all recorded passings.
* **Start/Stop Device Operations**: Users can start or stop the timing operations for local devices directly from this view.

### Devices Actions

* **Remove Device from Event**: Users can remove each device from the event individually. It is important to note that removing a device (either Cloud or Local) from an event **will not delete the passings already acquired** by that device.
* **Purge Device Passings**: Users can also purge all passings related to a selected device. This action **will delete all passings** recorded by the selected device, but it should be used with caution.

## Device Statuses

The Event-Devices View displays the current status of each device, with the following possible statuses:

* **Not Set**: Device is not configured (icon: disabled signal).
* **Connecting**: Device is attempting to connect (icon: hourglass).
* **Stand By**: Device is on standby (icon: pause circle).
* **Not Available**: Device status is not available (icon: error).
* **Connected/Online**: Device is successfully connected (icon: check circle).
* **Offline/Disconnected**: Device is disconnected or cannot communicate (icon: disconnected signal).
* **Reading**: Device is actively reading passings (icon: play circle).
* **Reader Error**: Error in device reader (icon: warning).

The appropriate icon and color coding are used for each status to help users easily understand the current state of their devices.

## Important Considerations

* **Local Device Disconnection**: When exiting an event, all connected local devices will automatically be disconnected.
* **Cloud Devices and Internet Connection**: A cloud device cannot be removed from an event if no internet connection is available.
* **Limited Local Device Operations in Cloud Access**: When accessing this view from the cloud, local devices will be visible to the user, but operations on them will be limited to only purging passing data.

## Summary

The **Event-Devices View** in RRM provides a centralized interface for managing all devices connected to an event. With features for monitoring device status, battery, temperature, and managing passings, users can effectively ensure that their timing devices are correctly set up and functioning. Proper device management is crucial for smooth and accurate race timing, and the Event-Devices View makes this easy and intuitive.


---

# 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/event-devices-view.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.