Case studies
Meridian Event Hall
Twelve WB-1 nodes kept lighting, room-state, and accessibility cues coherent across three reconfigurable halls.
Meridian’s movable walls create three halls, one ballroom, or seven breakout rooms. That flexibility used to produce brittle automation: the lighting scene knew yesterday’s wall plan, the room scheduler knew today’s, and accessibility strobes lived on a third controller.
“We stopped treating every room flip like a new integration. The state follows the wall plan, and the show keeps its cues when the uplink does not.”
— Nia Brooks, Technical Operations Manager, Meridian Event Hall
Deployment
Twelve WB-1 nodes carry 108 active channels across lighting relays, BLE occupancy beacons, movable-wall contacts, audio cues, and room-state outputs. The nodes form three local stars joined by a LoRa relay. Cloud analytics sees the whole venue; each hall remains able to run by itself.
Before and after
| Measure | Before | After | Window |
|---|---|---|---|
| New room-plan scene deployment | 3.5 h | 14 min | nine plan changes |
| RF dead-zone incidents | 8 / month | 1 / month | four event months |
| Lighting / accessibility cue skew | 240 ms | 7.6 ms worst case | 8,400 cue fanouts |
| Shows completed through WAN loss | 92% | 100% | 25 controlled outages |
The one remaining RF incident was a metal scenic wall parked across an antenna; the mesh identified the missing path before doors opened.
Production rule
rule: hall-state-follows-partitions
priority: 72
when:
changed: venue.partition.*
then:
- derive: zone.plan
from: venue.partition.*
- apply: scene.${zone.plan}.house
to: [light.*, audio.assist.*, hvac.setpoint.*]
- emit: audit.room_plan_applied
Partition state is normalized before the rule sees it, so a mechanical bounce cannot deploy two plans. Safety and egress rules remain in the 90–100 band and win every conflict.
What changed operationally
Meridian’s technical manager can rehearse a plan against one hall, compare the audit trace, and promote the same rule data to the venue. Analytics may sync later; lighting and accessibility cues never route through the cloud.
See the smart-building pattern and the hub, mesh, and relay topologies.