HydraIssues

Request for Citymesh, Cloud Seven (MikroTik RB5009 site). Prepared by ExperienceNet; this text is self-contained and can be forwarded as is.

Request

Move the five Sonos players at Cloud Seven onto one network segment: the segment where the two Sonos Ports already sit (11.0.6.0/24, the building infrastructure VLAN that our equipment can reach today). Three of the five players currently sit on a different VLAN (192.168.2.0/24) and are cut off from the other two.

Devices

We do not know whether the three players on 192.168.2.x are wired or on Wi-Fi. If wired: retag their switch ports to the 11.0.6.x VLAN. If Wi-Fi: map the SSID they use (or the players themselves) onto that VLAN, or tell us the SSID so venue staff can rejoin them to the correct one.

Why one segment matters (Sonos constraint)

Sonos players discover and group each other with multicast (SSDP/mDNS), which does not cross VLANs. Split across two VLANs the venue has two separate Sonos systems that cannot be grouped or controlled together. On one segment they can form a single household. Note for planning: after the move the venue staff must re-add the three moved players to the main Sonos system in the Sonos app (possibly after a factory reset of those players).

Keep existing reachability

Our render node (11.0.11.24) can currently reach the Sonos Ports on 11.0.6.x over TCP 1400 (HTTP). Please keep inter-VLAN routing/firewall so 11.0.11.0/24 continues to reach the Sonos segment on TCP 1400 after the move; that is what our monitoring uses.

Acceptance criteria (we will verify)

1. All five players hold a DHCP lease on 11.0.6.0/24.
2. From 11.0.11.24, HTTP GET to http://:1400/xml/device_description.xml succeeds for all five.
3. Venue staff can join all five players into one Sonos household in the Sonos app.

Contact

ExperienceNet (Cederik), cederik@cederik.com. We can verify remotely within minutes of the change; no site visit needed from our side.

Internal context (not for Citymesh): this is the "move Sonos to the experiencenet VLAN" option from #550. It completes the audio map for cloud-seven and makes all five players controllable from the venue body. It does NOT replace the #550 mesh-routing item: the hydraroar scale still cannot reach 11.0.x until a WG route exists; until then probing and future playback control run through cosmic-pretzel-98.

UPDATE 2026-08-26: forwarded to Citymesh by Cederik. Status: awaiting Citymesh response and scheduling. Next action on our side: when Citymesh confirms the change, verify the three acceptance criteria with a hydraroar scan on cosmic-pretzel-98 (targets 11.0.6.30-31 plus the three new leases) and expect one household with five members; then update the map in hydraroar/docs/runbooks/venue-audio.md and place the three players as audio assets in hydravenues.

RESOLVED 2026-08-27: request withdrawn, no move

• Citymesh (Stan): the three players are on the FDG WiFi network; moving them to the CS Op WiFi would land them in 11.0.0.0/20. No change made yet, awaiting our answer.
• Venue (Frederic, Cloud Seven): the three Sonos are the private residence system, one in the annex, one next to the kitchen, one in the living room. They have to stay as they are.

Conclusion: the 192.168.2.x household is private-residence audio, not venue PA. It is out of scope for Hydra; the venue audio system at cloud-seven is exactly the two Sonos Ports on 11.0.6.x, already fully mapped and placed. No action for Citymesh; Cederik answers Stan to withdraw the request. Map updated in hydraroar/docs/runbooks/venue-audio.md.