Adding client devices

MK
Mack Kemper
Written By Mack KemperLast updated 15 days ago

A client device is any device other than the host computer that connects to Competition Control: a scoring tablet, a check-in laptop, a phone in a queuer's pocket, or a TV showing rankings. Client devices run entirely in a web browser. Nothing is installed on them and they store no event data, so you can swap or replace one at any time.

Every client device must be authorized before it can do anything. Authorizing a device gives it a role, and the role decides which pages it can see and what it can change.

Before you start

  • The host computer must have an event open. See Host computer setup.
  • The client device must be on the same network as the host computer. It does not need internet access.
  • You need a device with the Admin role to authorize other devices. The host computer itself is always an Admin device, so you can start there.
  • The client device needs a current web browser. Recent versions of Chrome, Edge, Safari, and Firefox all work.

How to connect a device

  1. On the host computer, open the Devices page from the sidebar. It is listed under Event.
  2. Find the Server address near the top of the Authorize Devices panel. If the host computer has more than one network connection, several addresses are listed. Use the one that matches the network your client devices are on.
  3. On the client device, open a browser and type the Server address exactly as shown, including http:// and the port number, for example http://192.168.1.20:53243.
  4. The client device shows a six-character device code in large type, along with a QR code. Codes use capital letters and digits and never include the letters O or I or the digits 0 or 1, so they are easy to read aloud.
  5. Back on the Devices page, type the code into Device Code. The field accepts up to 6 characters and converts them to capitals for you.
  6. Optionally, type a name into Device Name (optional), such as Field 1 Scorer or Pit Rankings TV. Names can be up to 64 characters. Leave it blank to keep the automatically generated name, which is two words and an animal, such as brave-curious-otter.
  7. Choose a role from the Role list. See Choosing a role.
  8. Click Authorize as followed by the role name, for example Authorize as Scorekeeper.
  9. A Device authorized notice confirms the name and role. Within a few seconds the client device leaves the code screen and opens the pages for its role.

[Screenshot: Client device showing a six-character device code and QR code]

[Screenshot: Devices page with the Authorize Devices panel and the Authorized Devices table]

A device code is valid for 10 minutes. If the client device shows Authentication request expired. Please try again., reload the page to get a fresh code.

Authorizing with the QR code

If you already have a phone or tablet authorized as an Admin, you can skip typing the code.

  1. On the Admin device, open the camera or a QR code scanner and point it at the QR code on the new device's screen.
  2. Open the link. The Devices page opens with Device Code already filled in and the Role list focused.
  3. Choose a role and click Authorize as followed by the role name.

The scanning device must already be authorized as an Admin. If it is not, the link shows that device's own pairing code instead.

Choosing a role

Pick the most restrictive role that covers the job the device will do. Each role is modeled on a volunteer position.

Role

Use it for

Admin

Event Partners and trusted staff. Can do everything, including event setup, authorizing devices, finalizing results, and running displays.

Check-In

The registration table. Marks teams present and records inspection results.

Display

TVs, projectors, and field monitors. Shows only the content of the display group it is assigned to and has no interactive pages.

Solo-Only Scorekeeper

Volunteers running solo fields. Controls solo field timers and enters solo match scores.

Scorekeeper

Volunteers running alliance match fields. Controls field timers, queues matches, and enters scores for alliance and solo matches.

Head Referee

The head referee. Everything a Scorekeeper can do, plus recording violations, viewing deleted matches, and editing team information.

Judge Advisor

The judging room. Views team information, assigns award winners, and records violations.

Queuer

Volunteers calling teams to the field. Marks teams as queued or present for their matches.

The full list of what each role can access is in Roles and permissions.

Important

An Admin device can change anything about the event, including deleting devices and finalizing results. Give the Admin role only to devices you control, and keep the number small.

What happens after authorization

  • Operator roles (every role except Display) open the pages their role allows. Pages the role cannot use do not appear in the sidebar.
  • Display devices show an Awaiting assignment screen with the device name in large type and the message Assign this device to a group to start the display. They start showing content as soon as you assign them to a display group. See Assigning a display group.
  • The browser remembers the authorization. Closing the tab, restarting the browser, or restarting the device brings it back into the event without a new code. Clearing the browser's site data or using a private browsing window forgets the authorization, and the device shows a new code.
  • The device appears in the Authorized Devices table on the Devices page.

Assigning a display group

Display devices show whatever their display group is showing. You can assign a Display device from two places:

  • On the Devices page, use the list in the Display column of the Authorized Devices table. It shows Unassigned until you choose a group. The column is only filled in for Display devices.
  • On the Displays page, which also lets you create groups and choose what each group shows. See Displays.

If a group is deleted while a device is assigned to it, the device returns to the Awaiting assignment screen with the message The display group assigned to this device no longer exists until you assign another group.

Managing devices

The Authorized Devices table lists every device with its Name, Role, and Display assignment. The device you are using is tagged This device, and devices that have been turned off are tagged Disabled.

Change a role

Use the list in the Role column. The change applies immediately and the device's pages update on its next request. You cannot change the role of the host computer or of the device you are currently using.

Rename, disable, re-enable, or delete

Open the Device actions menu at the end of a device's row.

Action

What it does

Rename

Changes the device name shown in the table and on the device.

Disable

Signs the device out and blocks it from reconnecting. The device shows a Device Disabled screen. Its authorization is kept, so you can bring it back without a new code. You are asked to confirm.

Re-Enable

Restores a disabled device. It reconnects on its own within a few seconds.

Delete

Removes the authorization completely. The device returns to the code screen and must be authorized again to reconnect. You are asked to confirm.

Some devices are protected and their Disable and Delete actions are grayed out:

  • The host computer. It cannot be disabled, deleted, or given a different role.
  • The device you are currently using. Use another Admin device to change it.
  • The longest-standing Admin device. It cannot be disabled or removed while it is the only way back into the event. Authorize another Admin device first, and then the protection moves to that device.

Auto disable devices

Setting

What it does

Default

Notes

Auto disable devices

Disables any operator device after one hour without use, so the Authorized Devices list stays current.

On

The host computer and Display devices are never disabled by this setting. A disabled device shows Device Disabled; use Re-Enable to bring it back. Turning the setting off applies to the whole event.

This setting is on the Devices page below the authorize form.

How this connects to other features

  • The role you assign controls which pages a device can open. The complete matrix is in Roles and permissions.
  • Display devices depend on display groups for their content. Creating groups and choosing what they show is covered in Displays and Display screens.
  • Authorized devices, names, roles, and display assignments are saved in the event file. When you open the same event file again, every device reconnects without a new code. Opening a different event file requires authorizing devices again.
  • The Server address comes from the host computer's network connection. If the host computer changes networks, the address changes and devices must use the new one. See Host computer setup.

Tips

  • Authorize a phone as an Admin device for yourself. You can then scan QR codes to authorize new devices as you walk the venue.
  • Name devices by location or job (Field 2 Timer, Check-In Table) rather than by owner. Names show up in the table and on display screens waiting for assignment.
  • Print or write the Server address on a card at the check-in table so volunteers can type it without asking.
  • Authorize TVs and projectors as Display devices before the venue fills up. They show the device name in large type until assigned, which makes it easy to tell them apart from across the room.
  • Delete devices that leave the event, such as a volunteer's personal phone, rather than leaving them authorized.

Troubleshooting

  • If the browser cannot load the Server address, confirm the device is on the same wifi network as the host computer, that the address includes :53243, and that the host computer's firewall allows Competition Control. See Network and firewall.
  • If you see Authorization Failed with Could not communicate with the server to start the authorization process, the device reached the page but lost the connection. Check the network and reload.
  • If you see Authentication request expired. Please try again., the code was not entered within 10 minutes. Reload the page for a new code.
  • If you see Authorization failed on the Devices page, check the code for typos. Codes never contain O, I, 0, or 1. If the code is correct, ask the device to reload and try the new code.
  • If you see Connection Lost, the device cannot reach the host computer. It retries on its own. If it does not recover within a minute, check that the host computer is awake and on the network, and click Reload Now.
  • If you see Device Disabled, an Admin disabled the device, or it sat idle for an hour with Auto disable devices on. Ask an Admin to open the Devices page and choose Re-Enable.
  • If a Display device shows Awaiting assignment, assign it to a display group from the Devices page or the Displays page.
  • If a Display device shows The display group assigned to this device no longer exists, the group it was assigned to was deleted. Assign it to another group.
  • If a device keeps asking for a new code after each restart, the browser is not keeping site data. Turn off private browsing or any setting that clears data on exit, then authorize it again.

Was this helpful?

Your feedback shapes what we write next.