Device Details and Passings
The Device Details and Passings page in RUFUS Cloud provides an operational view of a specific timing device. From this page you can monitor device activity, inspect recorded sessions, and review the passings captured during timing operations.
This view is available for all devices connected to RUFUS Cloud, including:
RUFUS Race App devices
RUFUS CloudBox hardware
Custom timing devices integrated through the RUFUS Public API
Each device type may display slightly different information depending on the data it provides.
Device Types
RUFUS Race App
The RUFUS Race App is a virtual timing device used by judges and race officials to manually capture race events, such as bib numbers and race control actions.
Race App devices have a dedicated dashboard and passings view designed specifically for manual timing operations.
Learn more: Race App Device Dashboard
RUFUS CloudBox
The RUFUS CloudBox is the RFID timing hardware used to capture athlete passings from RFID readers and antennas.
CloudBox devices provide additional device-level information such as connectivity status, battery level, temperature, and GPS location.
CloudBox also has a dedicated dashboard optimized for monitoring hardware performance and reviewing RFID sessions.
Learn more: CloudBox Dashboard CloudBox Session Passings
Custom Devices (Public API)
Custom devices integrated through the RUFUS Public API use a simplified device dashboard that focuses on sessions and passings captured by the external timing system.
This interface allows developers and timing companies to monitor devices integrated through the API.
Device Details Page
The Device Details page provides basic information about the selected device.

Device Availability
This indicator shows whether the device is:
Available, meaning it can be used for timing operations
Assigned to an event, indicating it is currently part of a race configuration
This helps organizers quickly determine which devices are actively in use.
Sessions
The Sessions table displays all timing sessions recorded by the device.
Each session represents a timing activity performed by the device.
The table includes:
Session alias
Session status (Active or Ended)
Number of passings
Creation timestamp
If a session is currently running, it will appear with an ACTIVE badge.
Click Open to inspect the passings recorded during that session.
Location
If the device reports geographic coordinates, the page displays the last known location of the device using an embedded Google Maps view.
The map includes:
Device coordinates (latitude and longitude)
Timestamp of the last position update
Location data is typically available when passings include GPS information.
Viewing Session Passings
When opening a session, you will see the Passings table containing all detections recorded by the device during that session.

Passings are listed from most recent to oldest.
Each passing contains the following information.
Passing Number (#)
The sequential number of the passing within the session.
Bib
The participant bib number associated with the passing, when available.
Chip
The unique identifier of the RFID chip detected by the timing system.
ID
The participant identifier or device-specific identifier provided by the timing system.
Timestamp
The exact time when the passing was recorded.
Localization
The GPS coordinates of the passing location, when available.
Status
Additional status information related to the passing, such as processing flags or missing data indicators.
Real-Time Session Updates
When a session is Active, the passings table updates automatically as new passings are recorded.
This allows users to monitor timing activity in real time without refreshing the page.
Exporting Passings Data
Session passings can be exported as a CSV file for backup or analysis.
Click the Download CSV button at the top of the passings table to export the session data.
The exported file includes fields such as:
timestampnum_passinglatitudelongitudestatusparticipant_idgenderbibchip
This data can be imported into other timing software or used for external processing.
Editing the Device Alias
You can rename a device by clicking the edit icon next to the device name.
Assigning meaningful aliases (for example Finish Line Reader or 10K Race App Judge) helps organize devices and quickly identify them in the Devices List.
Unbinding and Purging Devices
The Device Details page also provides device management actions.
Unbind Device
Unbinding disconnects the device from your RUFUS Cloud account.
The device will no longer appear in your Devices List and must be bound again to reconnect.
Purge Device
Purging a device removes its stored sessions and passings from the device dashboard.
This action is irreversible and should be used with caution.
Important: Passings already processed as part of event classifications are not deleted, since they belong to the race results.
Summary
The Device Details and Passings page allows you to inspect device activity, monitor sessions, and review the passings recorded during timing operations.
Whether you are using Race App devices, CloudBox hardware, or custom timing integrations through the Public API, this interface provides a clear and centralized view of device activity within RUFUS Cloud.
Last updated