The /display player identifies its device, retrieves pairing state, and requests a server-computed broadcast snapshot.
Runtime resolution
- Authenticate the device identifier.
- Confirm that the paired screen is active.
- Load its channel and timezone.
- Calculate channel-local time.
- Select the active event, recurrence, or default schedule.
- Load the playlist, ready files, template, zones, and widgets.
- Generate short-lived media URLs.
- Return a snapshot consumed by the player.
stateDiagram-v2
[*] --> Unpaired
Unpaired --> Pending: code accepted
Pending --> Active: administrator approval
Active --> Playing: runtime available
Playing --> Playing: periodic refresh
Active --> Revoked: revoked
Revoked --> Active: reactivated
Event schedules take priority over recurring schedules, which take priority over the default. Resolution considers activation, date bounds, weekday, time range, and channel timezone.
The runtime cache and snapshot utilities reduce repeated work, but full offline playback is not guaranteed. Screens must periodically reach the application and renew signed media URLs. Pairing and runtime routes validate input, enforce screen status, and apply rate limits.