Pair and identify digital signage players

Pair each physical TV or display player to the correct tenant, role, and stable screen ID before relying on screen assignments or fleet reporting. The pairing code identifies a pending device request; it does not authenticate the screen by itself.

Start pairing from the display

1. Open /tv on the TV, Android box, Chromecast with Google TV, tablet, Windows device, ChromeOS device, or supported browser player.
2. Keep the six-digit pairing code visible.
3. In Admin, open KDS & Guest Displays → Signage Readiness.
4. Under Pair ellich Display Player, enter the displayed pairing code.

For a user who can access more than one tenant, confirm the current Admin tenant before approval. The tenant used to approve the code becomes the owner of that screen.

Choose the correct role and identity

Select Digital Signage for menu boards, promotional TVs, and rotating signage. Select Order Status Display only for pickup, ready-order, or lane-flow screens. These roles open different customer-facing experiences.

Enter a stable Screen id, such as menu-wall-1, and a recognizable Display name. The screen ID connects the physical player to assignments, schedule targets, fleet health, and proof-of-play records. Changing the display name is safer than changing the screen ID after launch.

For Digital Signage, paste the current public-board TV key. The pairing action requires a key of at least 32 characters. The key grants the player access to the tenant's public board; do not place it in support screenshots, public documents, or chat messages.

Approve and assign the player

Select Pair Screen, then open Screens and assign the same screen ID to the intended scene. Save the draft and publish it before expecting the player to use that assignment.

The screen URL remains /digital-menu?screen=<id> even when the assigned scene changes. Keep that URL and screen ID stable so managers can update content centrally without reconfiguring the physical TV.

Confirm the player is reporting

Return to Signage Readiness and select Refresh. A paired player becomes useful operational evidence only after it opens its public board and sends a heartbeat. The fleet row shows screen ID, viewport, online state, scene, board revision, cache state, last-seen time, and any recorded player error.

If No reporting screens remains visible, confirm that the player is open, its tenant and TV key are correct, its URL contains the intended screen ID, and the network allows the player to reach the application. Pairing approval alone does not create heartbeat or proof-of-play history.

Diagnose a wrong or blank screen

• Wrong content: compare the URL screen ID with the saved screen assignment and the active schedule target.
• Default rotation instead of a fixed scene: confirm the screen has a published assignment.
• Pairing fails: recheck the six-digit code, selected role, current tenant, screen ID, and TV key.
• Player appears offline: check the last heartbeat, network, power, and whether the /tv player is still running.
• Correct draft but old live content: publish the draft and confirm the revision reported by the player.

Record the tenant, role, screen ID, display name, reported revision, last-seen time, and error code when escalating. Never include the TV key.