Part of #566 (Secure Inside hand-over). Venue: cloud-seven.
Problem
The Sonos sound system in the Cloud Bar does not work. The venue doc lists it under the urgent needs for September 1.
Request
Diagnose and fix. Report the root cause, because three open issues touch this same equipment and it is not yet clear which one, if any, explains the fault.
Related, already open
- #554 Citymesh request to move the three 192.168.2.x Sonos players at Cloud Seven onto the 11.0.6.x segment. Forwarded to Citymesh on 2026-08-26, awaiting their response. Verification steps are in that ticket.
- #550 hydraroar reach: mesh routing to venue subnets, Cloud Seven LAN options, the remaining 192.168.2.x household.
- #553 Cloud Seven network hygiene: personal PC on the infra VLAN, uncorrelated Mac Mini interface, unknown IoT.
None of the three report the system as broken today. This issue is the operational fault. If the cause turns out to be the VLAN split, close this one against #554 and say so.
Note
Venue staff control playback through the Sonos app. Read-only playback state through hydraroar is #564, active control is #563. Neither is required to fix this fault.
Remote evidence 2026-08-28 (hydraroar status read, #564)
Both Sonos Ports read remotely from the venue body:
- Bar Port (11.0.6.30): online, STOPPED, no source loaded, unmuted, output volume 100 (variable line-out). From the Sonos side this player is healthy.
- Yoga Port (11.0.6.31): online, STOPPED, unmuted, output volume 0. With a variable line-out, anything played to the Yoga zone is silent at the PA until this volume is raised in the Sonos app.
What this means for the Cloud Bar complaint:
- If the room labels match the physical wiring, the Cloud Bar fault is NOT at the Sonos level: check downstream of the Bar Port (rack amplifier power/input, speaker wiring).
- If the two Ports are swapped relative to the amps they feed, the volume-0 "Yoga" Port may be the actual Cloud Bar feed, and raising its volume fixes Cloud Bar.
Test to distinguish: raise the Yoga volume in the Sonos app, then play to each zone in turn and note which physical room sounds. Flagged to Frederic 2026-08-28.
Floor findings 2026-09-10 (Cederik, on site)
The bar has a Biamp wall controller (white box) selecting sources: AirPlay Bar, AirPlay Dining Room, local source bar (white/red RCA wall jack). So the PA chain is: sources (very likely the two Sonos Ports as the AirPlay inputs, plus the wall jack) -> Biamp Tesira DSP -> zone amps -> speakers.
- Volume calibration mismatch: Dining Room is background at 50 and party at 70; Bar is almost silent at 90 and loud only at 100. The Bar zone's gain range/taper in the Tesira is mis-set; both zones should behave the same. Tesira-side fix (gain structure), not hardware.
- Bar crackles, Dining Room clean, same source: the fault is after the source split, in the Bar chain: Tesira output -> bar amp channel -> cabling -> speakers. Physical inspection needed (this may be the whole original "Cloud Bar does not work" complaint).
- Open mapping question: our Sonos rooms are named "Bar" and "Yoga", the Tesira sources are "AirPlay Bar" and "AirPlay Dining Room". Verify which Port feeds which Tesira input (the "Yoga" Port may be the dining feed). Remote volume evidence: Bar Port vol 100, Yoga Port vol 0 on 2026-08-28.
Tesira-side items belong with the hydrabiamp work (TTP control); the crackle needs hands on the bar amp/cabling.
Mapping RESOLVED 2026-09-10 (live test, Cederik on site + remote control)
Method: with remote hydraroar control we made exactly one Port play at a time while Cederik walked the panels.
- There are TWO Biamp wall panels: one in the bar, one in the yoga/gym. The yoga panel's sources are correctly labeled Bar and Yoga and behave correctly (Yoga Port playing -> audible in the gym on source "Yoga").
- The Sonos room names are honest: Bar Port = bar source, Yoga Port = yoga/gym source. No renames needed.
- The defect is the bar panel's second source entry: labeled "AirPlay Dining Room", and with only the Bar Port emitting, selecting it STILL played Bar-Port audio, so its routing does not pull the Yoga/second input either. Confirmed precisely: the entry is a DUPLICATE of the Bar source: its crosspoint maps to the Bar Port input, so the bar zone gets Bar-Port audio on both selections. Two-part Tesira programming fix: relabel the entry to "Yoga" AND remap its routing from the Bar input to the Yoga Port input. Goes with the #682 .tmf/technician work.
- Still open from the floor findings: bar zone gain calibration (silent at 90 vs dining 50/70) and the bar crackle (physical chain).
Port state after testing: Bar Port paused (Cederik's Spotify session, resumable from the phone), Yoga Port playing at volume 40.
Update for the venue (2026-08-28): we can now read the state of the two Sonos units remotely, and it gives us a lead on this problem.
The "Bar" Sonos is online, unmuted, output at 100. From the Sonos side it looks fine. The "Yoga" Sonos is online but its output volume is at 0, so anything played to Yoga stays silent until that volume is raised in the Sonos app.
Two quick tests that tell us a lot:
One more possibility the test will reveal: if raising Yoga's volume suddenly makes the BAR sound, the two units are swapped relative to the amps they feed, and that alone would explain the Cloud Bar issue.
Either outcome is progress before Sept 1: a two-minute volume fix in the app, or confirmation the problem is in the rack so we get hands on the amplifier before the events.