Zones and Streams: How to Organise What Plays in Every Corner of Your Hotel

A hotel is not a single audio environment. The lobby needs welcoming, energetic music that sets the tone for arrival. The spa needs something calmer. The gym needs something upbeat. The bar at 9 PM needs something different from the bar at 11 AM. Treating the entire hotel as one audio zone is not just a missed opportunity — it is actively wrong for most of these spaces.

At the same time, managing each zone as a completely separate system — with its own device, its own software, its own stream source — is operationally unmanageable at scale. The answer is a single management layer with fine-grained zone control underneath it.

The Basic Unit: The Zone

In RoomStream, each hotel is divided into zones: reception, pool, gym, bar, spa — each with its own audio atmosphere, controlled entirely independently. A zone always has:

• A stream assigned to it (the radio station, playlist, or audio source that plays).
• A playback state (playing or paused).
• Its own volume level.
• One or more physical devices (Raspberry Pi) that reproduce the audio in that space.

Pausing the spa does not affect the lobby. Turning up the bar does not change the restaurant. Each zone is entirely independent from the others, while still being visible and manageable from the same dashboard view.

Streams: The Chain's Audio Catalogue

Streams are managed at the chain level, not the hotel level. A hotel group might have a curated catalogue: an upbeat pop radio station, a chill-out playlist for spa and pool, a jazz stream for the restaurant, a local FM station for certain properties. Each zone in any hotel chooses which of these streams it wants to use.

This catalogue can be curated further: an administrator can limit which streams are available for selection from the player screen in a given zone, without restricting what can be assigned by an administrator manually. A hotel might want the spa to have only two calming options available to on-site staff, while the full catalogue remains available to the IT team.

Changing What Plays, Without Touching the Device

Pausing the pool music, raising the bar volume on a Friday evening, or switching the lobby to a special event stream — all of this happens at the zone level, not the device level. If a zone has two devices (for example, two Raspberry Pi units covering different areas of a large restaurant), changing the zone's stream or volume affects both simultaneously and consistently.

This sounds like a small thing, but it matters at the scale of 50 hotels. An IT manager changing stream assignments for 6 zones across 10 hotels does this in the zone management view — not by connecting to each of the 80 individual Raspberry Pis that collectively produce the audio.

Why Separating Zone from Device Matters

Keeping the "what plays and how" (the zone) separate from the "physical hardware that plays it" (the device) enables several things that would otherwise be operationally complex:

• Hardware replacement without reconfiguration: if a Raspberry Pi fails, replace it with a new one and assign it to the same zone. The zone's stream, volume and state do not need to be reconfigured — they were never stored on the device.
• Adding a device to an existing zone: a large lobby gets a second Raspberry Pi to cover a new wing. Assign it to the lobby zone and it immediately plays the same stream at the same volume as the existing device — no separate configuration needed.
• Reassigning a device: a device originally in the gym moves to the spa. Reassign it to the spa zone and it immediately starts playing the spa stream. No stream URL to configure, no volume to set manually.

A Typical Hotel Layout

As a reference, a medium-sized hotel might have 5–8 zones: main lobby, bar, restaurant, pool area, spa, gym, corridors (optional), and conference rooms (on-demand, often paused by default). Each of these has its own stream running 24 hours a day, with volume adjusted for time of day. The conference rooms might be paused and only activated when a booking is confirmed. The bar shifts to a different, livelier stream at 7 PM automatically or with one click from the dashboard.

Managing all of this does not require a dedicated person. It requires a good zone structure and a platform that makes changes fast. The actual ongoing management across all zones is typically a few minutes a day.