Add and pair Browser, Android, Google TV, and Fire TV Players

What this does

Create the Player in the correct location, then use the temporary six-digit code shown on the physical or Browser Player.

Steps

1. Open Players and choose Add Player.
2. Choose the Player type, name, and location.
3. Open the matching Player app or Browser Player and keep its code visible.
4. Enter the current six-digit code and confirm.
5. Wait for registration and assigned content; then verify Online status.

Add Player fields

Type selects the compatible runtime; Name identifies the physical screen; Location determines scope. Required fields must validate before pairing starts.

Six-digit code lifecycle

The runtime issues a temporary code. Expiration or regeneration invalidates older codes. Successful use binds that runtime to the selected Player.

Platform behavior

Browser Player uses a browser runtime. Android/Google TV and Fire TV use the installed SmartQ Player app. All show a temporary code before registration.

Result and editing

A successful pair moves through provisioning to Online when heartbeats arrive. Later changes happen from Player detail; unpair/replacement are consequential actions.

Permissions and scope

• No Access hides or blocks the module. Read Only permits viewing but disables changes. Editor permits the documented create, edit, publish, or administrative actions within the user's assigned scope.

Mobile

• On narrow screens, open the sidebar or overflow menu to reach the same actions; labels and save behavior are unchanged unless this article says otherwise.

Customer-visible states

• waiting for code
• expired
• invalid
• paired
• provisioning
• online
• offline

Six-digit pairing code

This control is covered by the Add and pair Browser, Android, Google TV, and Fire TV Players workflow.

Applies to /pair

Expired code and regeneration

This control is covered by the Add and pair Browser, Android, Google TV, and Fire TV Players workflow.

Applies to /pair

Successful pairing result

This control is covered by the Add and pair Browser, Android, Google TV, and Fire TV Players workflow.

Applies to /pair

Pairing screen

This control is covered by the Add and pair Browser, Android, Google TV, and Fire TV Players workflow.

Applies to /player/:id

Playback loading and offline states

This control is covered by the Add and pair Browser, Android, Google TV, and Fire TV Players workflow.

Applies to /player/:id

Assigned content playback

This control is covered by the Add and pair Browser, Android, Google TV, and Fire TV Players workflow.

Applies to /player/:id

Runtime selection

This control is covered by the Add and pair Browser, Android, Google TV, and Fire TV Players workflow.

Applies to /tv/:signageId

Provisioning and loading

This control is covered by the Add and pair Browser, Android, Google TV, and Fire TV Players workflow.

Applies to /tv/:signageId

Offline and unsupported assignment states

This control is covered by the Add and pair Browser, Android, Google TV, and Fire TV Players workflow.

Applies to /tv/:signageId

Player type selection

This control is covered by the Add and pair Browser, Android, Google TV, and Fire TV Players workflow.

Applies to /admin/devices/new

Name and location fields

This control is covered by the Add and pair Browser, Android, Google TV, and Fire TV Players workflow.

Applies to /admin/devices/new

Six-digit pairing and cancellation

This control is covered by the Add and pair Browser, Android, Google TV, and Fire TV Players workflow.

Applies to /admin/devices/new

Post-pair status

This control is covered by the Add and pair Browser, Android, Google TV, and Fire TV Players workflow.

Applies to /admin/devices/new

What happens next

Your change is available within the scope you selected.

Warnings

• Pairing codes are short-lived. A regenerated code invalidates the previous one.

Troubleshooting

• If the code changes, use only the newest visible code; automatic regeneration protects an unpaired device.
• Confirm the Admin Player and on-screen device belong to the same intended location.
• Check device time, DNS, and outbound HTTPS when a valid code is rejected.
• Canceling before confirmation leaves the Player unpaired and does not consume the old hardware assignment.
• For expired code and regeneration, verify the selected scope, access level, required connection, and displayed validation or freshness status; retry once after correcting the cause, then create a context-rich Support case if it continues.
• For playback loading and offline states, verify the selected scope, access level, required connection, and displayed validation or freshness status; retry once after correcting the cause, then create a context-rich Support case if it continues.
• For offline and unsupported assignment states, verify the selected scope, access level, required connection, and displayed validation or freshness status; retry once after correcting the cause, then create a context-rich Support case if it continues.