1. Pairing & identity
When a new Player boots, it generates a hardware identity and pairing PIN.
You enter that PIN into the Portal, link it to a tenant and a screen, and
the Portal issues a device key. From that point on, the Player authenticates
using that key instead of the one-time PIN.
2. Fetching configuration
The Player periodically calls the Portal to fetch its configuration: which
screen it belongs to, which playlist is active, and which media assets are
required. The Portal responds with a compact JSON document that describes the
desired state for that device.
3. Downloading & caching media
Based on the configuration, the Player downloads any missing media files into
a local content directory. Once cached, playback is entirely local – the
device doesn’t need a permanent internet connection to keep running the
existing playlist.
4. Playback & monitoring
While the playlist is running, the Player sends regular heartbeats back to
the Portal with status information (up, down, last sync, last content
update). It can also log events such as media errors or configuration
changes to feed into monitoring and dashboards.