Raspberry Pi digital signage player

HexitHive Player: hardened Raspberry Pi engine for your digital signage.

The HexitHive Player turns a Raspberry Pi into a predictable digital signage engine, with a local API, cached playlists, offline-safe behaviour and regular heartbeats back to the HexitHive portal. For typical deployment patterns across MSPs, enterprises and retail, see the Use Cases page.

Architecture of the HexitHive digital signage player

Under the hood, every HexitHive Player follows the same pattern: a local API service, a playback loop, a content cache and a small set of outbound HTTPS calls to the portal. For the broader view of tenants, screens, playlists and APIs, see the HexitHive architecture overview.

Local API: the player’s control surface

The local API is a small HTTP service bound to 127.0.0.1:7680. It is the single source of truth on the device:

  • Exposes /device for identity and pairing information.
  • Exposes /player/playlist so the playback loop can fetch the current playlist as JSON.
  • Runs /player/sync to contact the HexitHive portal, pull down new configs and download media into the local cache.

Playback loop and media engine

The playback loop is intentionally simple: it reads a playlist JSON from the local API, then hands each digital signage item to mpv in full-screen mode:

  • Video items are played for a defined duration or until completion.
  • Image items are displayed for their configured duration.
  • Any missing or corrupt files are skipped, so one bad asset does not take the whole loop down.

Local cache & offline safety

All media is cached under /var/lib/hexithive/content. If the internet connection or the portal is unavailable, the HexitHive Player simply continues using the last good playlist and local media until it can sync again.

Player data flow
Portal
Playlists & media
HTTPS APIs
/api/player/config.php
Local API
127.0.0.1:7680
Player loop
mpv + timings
Screen
HDMI output

Maintenance & local wizard

Each HexitHive Player exposes a local wizard and maintenance view so field technicians can see hostname, IP addresses, pairing status and last config sync, and trigger a manual resync or safe reboot using a maintenance PIN.

Heartbeats & health checks

The player posts regular heartbeats via the local API to /api/player/heartbeat.php, including last-seen time, playlist ID and basic health data. The portal turns that into clear “online / offline / stale” states per screen.

Secure by default

HexitHive Players only make outbound HTTPS connections, identified by a random device_key. The local API is bound to localhost, and sensitive state lives under root-owned paths on the Pi. No inbound firewall holes and no exposed admin panels on the public internet. For a broader view of tenant isolation, roles and operational practices, see the Security & Reliability page.