Production Truck: Sports Hub integration

Sports Hub integration

Deploy Hub 0.0.3036. Open Video Production Trucks → your truck → Standalone Truck App. Station pairing details are available to Site Admins and managers of the truck organization, assigned venue or assigned event. The setup page provides the Hub address, truck slug and a dedicated 48-character station pairing token. It has a rotate-token control, separate from Stream Deck tokens. The token grants private camera configuration, the existing OBS scene collection and runtime reporting for that truck only.

Pair in the app's Engineering page. Assigned cameras, current event, custom scenes, overlay URLs and production output settings are loaded. Download the OBS collection from Camera setup, then import it in OBS. Review its camera sources and map each slot to its actual loaded scene and input. The application does not automatically replace your active OBS collection.

Refresh Hub after changing an event assignment, camera roster or scene design. Hub configuration remains authoritative; existing local camera connection overrides are preserved for matching slots. Newly assigned cameras adopt their Hub configuration. Adding/removing cameras on a paired truck happens in Sports Hub; refresh afterward.

Successful local scene/camera/overlay changes and output status synchronize to the existing truck/event runtime. Hub errors leave production working locally. Pending reports contain state only: camera/scene/overlay selection and last observed output status. They never start or stop a remote broadcast. The Hub rejects stale reports for a different assigned event. Refresh drops obsolete pending state when an event changes.

Station tokens and manually entered OBS passwords remain in memory and are omitted from application settings and logs. Re-pair after a restart. Managed kiosk OBS uses a generated long password in its private OBS configuration (owner-only directory and file permissions) so it can reconnect after a controller restart. This password is never placed on the process command line, in the environment, UI state, or support reports. OBS may bind its authenticated WebSocket to workstation network interfaces; configure your workstation firewall appropriately. Cached camera URLs may contain camera credentials; local configuration is saved with owner-only file permissions. Downloads of OBS collections may also contain private camera URLs and the existing audio/Stream Deck control credential. HTTP is accepted only for a localhost development Hub; production HTTPS certificates are verified, and credentialed requests do not follow redirects.

API:

Operation	Endpoint
Private truck manifest	GET /api/v1/production_trucks/{slug}/station
Existing OBS collection	GET /api/v1/production_trucks/{slug}/station/obs_config
Report validated operator state	POST /api/v1/production_trucks/{slug}/station

Authentication is Authorization: Bearer <station_token>. This reuses the truck's station/control design; it is separate from commercial data API keys and does not alter subscription scopes or existing broadcast entitlements. Stable overlay endpoints continue applying their own existing eligibility rules.