Home
XtreamUIPro

Setup guide

Hotels & Resorts setup guide

Configure the platform as the television service of a property: channel packages per room category, one line per room driven by the PMS, nodes per building, and the hotel's own information videos.

These guides map an industry's concepts onto the objects the platform has today (bouquets, lines, packages, partner accounts, nodes, the API). They are conceptual mappings, not industry-specific features, and a partner account is a delegated account, not an isolated tenant.

Conceptual mapping

Nothing in the panel is called a room or a stay. The table says which object plays which role; the chapters below set them up in that order.

In your industryOn the platformWhere in the panel
Hotel operator or authorised partnerPartner account (reseller): a delegated dashboard with credits, permissions and its own linesUsers → add a reseller; Groups for its permissions
Channel packageBouquet: a named set of channels, films or series that a package grantsBouquets, from Streams and Movies / Series
Room or deviceLine: one access with its package, bouquets, expiry, connection limit and outputsLines → add, or activation codes, or the Reseller API
Hotel information videosVOD catalogue: movies and series with seasons and episodes, categories and metadataMovies and Series, or the VOD ingest job
Licensed television channelsLive channel: a stream with its sources, EPG and output formatsStreams → add a live stream (source URL or RTMP push)
Length of stayExpiry date of the line, renewed by a package, a credit or the APIThe line's expiry date and the package's duration
One node per building or wingStreaming nodes: edge servers enrolled from the panel, one per site or buildingServers → add a node, installed over SSH

Prerequisites

What to have before installing.

  1. A server on the property network (Ubuntu 22.04 or 24.04), the installer, and an address the room devices can reach.
  2. The channel feeds the property holds rights to (pull URLs or RTMP), the hotel's information videos, and the room devices (Android TV boxes, MAG or Enigma2 boxes, smart TVs with a player app or a browser).
  3. The PMS's ability to call an HTTP API on check-in and check-out, or a desk procedure for doing it in the panel.

Infrastructure deployment

The central server and a node per building.

  1. Run the installer on the central server; set the playback base to the property's internal address so the rooms stay on the local network.
  2. Add the channel feeds under Streams and the information videos under Movies; check them in the web player.
  3. Enrol a node per wing or building from Servers; the panel installs it over SSH and routes that building's rooms to it.
  4. Set the licence key on the server; activation happens on site and the service runs without the uplink.

Content organisation

Channel packages and hotel videos.

  1. Create one bouquet per channel package (standard rooms, suites, conference) from the property's channels.
  2. Create a bouquet of hotel videos (welcome, facilities, safety) and add it to every package.
  3. Create one package per room category with the bouquets it grants and a duration of one day: on check-in the room's line is renewed once per night of the stay (each renewal adds the package's duration), and on check-out it is disabled (chapter 8).
  4. Order the channels and give them logos so the menu on the television reads well.

Partner (reseller) configuration

The property, or an operator running several properties, as a delegated account.

  1. Create a group with permissions limited to lines (rooms) and no catalogue changes.
  2. Add the property's front desk, or the operator, as a reseller with that group and the room packages.
  3. An operator of several properties gets one reseller per property, each with its own rooms and credits.

Room (line) configuration

One line per room, named by its number.

  1. Create one line per room under Lines with the room number as its name and the room category's package.
  2. Set max connections to 1 (one television) or to the number of screens in the room.
  3. Bind the line to the room device's address when the network gives devices fixed addresses.
  4. Configure the device (Xtream Codes API or M3U with the line's credentials, or the MAG / Enigma2 portal) once; the credentials stay with the room.

Hotel information videos

The property's own videos on demand.

  1. Upload the welcome and information videos as movies, with the property's language versions as separate entries or audio tracks.
  2. Put them in the hotel videos bouquet so every room category receives them.
  3. Update them from the panel whenever the information changes; the rooms see the new version at once.

Licensed television channels

The property's channels as live streams.

  1. Add each licensed channel under Streams with its feed; enable timeshift or catch-up only where the licence allows.
  2. Add an EPG source so the guide on the television shows the programmes.
  3. Keep territory-limited channels in bouquets only the right packages grant.

Check-in, check-out and expiry

The stay as the line's validity.

  1. On check-in enable the room's line and renew it for the length of the stay (the PMS through the API, or the desk in the panel).
  2. On check-out disable the line; a new stay enables it again, so credentials never leave the room.
  3. Subscribe the PMS or the desk to the webhooks to see enabled, disabled and expired lines.

Integration with the PMS

Check-in and check-out drive the rooms.

  1. Create a Reseller API key for the PMS and keep it in the PMS's configuration.
  2. On check-in the PMS calls action=enable_line and action=renew_line for the room's line with a request id; on check-out action=disable_line.
  3. The guest-service application (call staff, housekeeping, express check-out, room service) and its back-office connection are part of the Enterprise plan and are scoped with the property.

Security considerations

Keep the channels inside the property.

  1. Keep the playback base and the nodes on the property's network; expose nothing to the internet that the rooms do not need.
  2. One connection per room, bound to the device; signed links expire, so a copied link stops working.
  3. Two-factor sign-in for the panel; the desk gets a limited permission group.
  4. Enable the encrypted database backup; the room credentials live in it.

Troubleshooting

The usual first checks.

  1. A room has no television: check that its line is enabled and not expired, then the device's credentials and address.
  2. A channel is missing in a room: check the bouquet of the room category's package.
  3. Television stops during an internet outage: check that the playback base and the sources are internal addresses; external feeds depend on the uplink.
  4. The PMS call fails: check the API key, that writes are POST, and the request id on retries.
Start free Help centre Contact