Connecting a Device

A newly created player account has no device attached. Pairing binds a physical device (running the player application) to the player account using a one-time PIN. There are two symmetric flows — pick whichever is more convenient on site.

Pairing never creates a player account. The account must already exist — see Player Accounts.

Flow A: generate a PIN in CS Play, enter it on the device

  1. Open the player’s Parameters page and click Generate in the PIN generation row.

  2. CS Play shows the pairing code as ID:<player id> PIN:<code>.

  3. On the device, enter the PIN in the player application’s setup screen (or provide it via the configuration file for headless installs — see the player setup documentation).

  4. The device exchanges the PIN for its credential and connects. The PIN is deleted after use.

Flow B: the device shows a PIN, enter it in CS Play

  1. Start the player application on an unpaired device — it displays a code (digits and letters).

  2. In CS Play, open the target player’s Parameters page.

  3. Type the code into the Enter PIN field and click Send PIN.

  4. The device picks up its credential within a few seconds. CS Play confirms with "Player connected successfully"; a wrong code gives "Invalid PIN".

Codes shown by devices expire if unused; the device then displays a new code.

Re-pairing and replacing hardware

A player account holds exactly one device credential at a time. Pairing a new device with a fresh PIN moves the player identity to that device: the credential is rotated, and the previously paired device is signed out immediately.

This is the intended path for replacing broken hardware — create nothing, just pair the replacement device to the existing player.

Generating a PIN by itself does not disconnect the current device. The credential rotates only when some device actually authenticates with that PIN.
A PIN hands the player to whoever enters it. When someone asks you for a PIN or to pair a device, confirm who is asking before you generate or send it.

Disconnecting a device

Archiving a player deletes its device credential — the device is signed out and the license returns to the pool (see below). To detach a device without archiving, pair the account to another device or contact support.

Archive and restore

  • Archive — the device is signed out, the player license returns to the organization pool, and simple screens of this player are archived. The account and all its settings remain.

  • Return from archive — requires a free license; simple screens are restored.

Archiving is the end of a player’s lifecycle.

Why a device fails to connect

Message on the device Cause

Authorization code was not found

The PIN is wrong, already used, or expired.

Screen is blocked

The player was blocked by the platform administrator.

Screen is archived

The player account is archived — restore it first.

Owner is blocked

The whole organization is blocked on the platform.

Organization balance is below zero

Playback is suspended until the balance is settled.
Older server messages may say "screen" where the interface says "player" — they refer to the same entity.

See also