Managed flooding for stage lights

Managed flooding for stage lights

animation
bluetooth
protocols

Managed flooding for stage lights

Narrated audio tour. The full transcript is below. These are schematic teaching states, not measured protocol or elapsed lifecycle time. Choose Reduced motion for a complete still at each beat. Explanations beyond the model remain in captions.

Full transcript — ble-mesh (8 beats)

B1 — Lighting commissioning
You are the technician setting up a building's lighting control. One wall switch must reach both stage lights, so a missed command leaves part of the group unchanged. Your job is to choose how messages travel while keeping repeated traffic under control.

Model caption: Your switch must reach both stage lights while repeated traffic stays controlled.

B2 — Group publishing
Bluetooth Low Energy is the radio family used by Bluetooth Mesh. Mesh uses managed flooding: selected devices pass a message onward. A switch publishes a command to a group address, and lights subscribed to that group can act when the command reaches them.

Model caption: Bluetooth Mesh builds on Bluetooth Low Energy. Selected relays carry a group command toward subscribed lights.

B3 — Relay choice and cache
A relay is a device enabled to pass messages onward. The chapter recommends mains powered fixtures or wall devices for that work. Choosing relays matters because enabling every fixture may increase collisions. Managed flooding also uses a message cache, which remembers messages already received and discards duplicates.

Model caption: Choose relays deliberately; the chapter recommends mains powered devices and warns that enabling every fixture may increase collisions. A cache discards repeated messages.

B4 — First hop
Time to live is the message's limit on forwarding. Take the teaching model's stage lighting example, starting at three, with balanced relays and one transmission per relay. The switch sends without subtracting, so Relay A and Relay B each receive the value three. Neither stage light has received the command yet.

Model caption: Initial time to live: three. Relay A and Relay B receive three from the switch. Stage lights reached: zero of two.

B5 — First relay wave
During the first relay wave, each forwarding relay subtracts one: three minus one gives two. Stage light one receives the command at two. Relay C also receives it at two from Relay A. When Relay B sends another copy to Relay C, the cache discards that duplicate.

Model caption: Three minus one gives two. Stage light one receives at two. Relay C accepts A's first copy and discards B's duplicate. One of two lights reached.

B6 — Second relay wave
During the second relay wave, Relay C subtracts one again: two minus one gives one. Stage light two receives the command at one. Both intended lights have now received it. In the teaching model, a relay needs a received value greater than one to forward, so forwarding stops at one.

Model caption: Two minus one gives one. Stage light two receives at one; both lights have received the command. The model forwards only received values greater than one.

B7 — Duplicates still cost airtime
The misconception is that discarding duplicates removes their radio cost. A copy has already used radio time before a receiver discards it. Stage light one hears another copy during the second wave, but its cache discards it. Two lights reached therefore does not mean only two transmissions occurred.

Model caption: Both lights received the command. Stage light one then discards another copy, which already consumed radio time. Delivery count is not transmission count.

B8 — Limit the spread
For your lighting job, remember: managed flooding carries the command outward, while relay choice, time to live, and caching limit the spread.

Model caption: Managed flooding carries the command outward, while relay choice, time to live, and caching limit the spread.

Open the BLE Mesh Managed Flooding Workbench

Back to the chapter