Swarm Lighting: A Complete Guide to Presence-Aware Light
Most people who search for "swarm lighting" end up reading something it is not. They find motion sensors wired in parallel, daisy-chained timers, or generic mesh networking sold as swarm. None of that is swarm. Swarm is something more specific, more useful, and — until now — surprisingly hard to set up.
MESHLE did not invent the idea of swarm lighting. We made it actually usable. Same workflow whether you are commissioning five nodes in a stairwell or five hundred along a warehouse aisle. No floor plan upload, no rule scripting per fixture, no central controller. This post is the MESHLE definition of swarm lighting — what it is, what it is not, and how it works in our app and in the field.
What is MESHLE Swarm?
Swarm lighting is a presence-aware lighting behavior in which every luminaire in a network is aware of where movement is happening — and reacts together, not in isolation. The closest lights go to a configured brightness target. Lights further out dim down in a gradient. Lights beyond that gradient stay at their idle level. When the movement moves, the bright spot moves with it.
The result is light that is only there where it is needed and only as much as it is needed — always a step ahead of the person or vehicle moving through the space. A traditional motion sensor lights the fixture directly above its trigger point. MESHLE Swarm lights what surrounds the person instead — the area ahead, around, and to either side of them — not just the single spot underneath.
- Area-coordinated light — every luminaire knows about its neighbors and adjusts based on the closest active sensor in the group, not just its own paired one.
- A presence-aware gradient — two radii per sensor: a guaranteed-brightness zone close in, a falloff zone further out, idle beyond that.
- Multi-sensor cooperation — overlapping radii compose cleanly. A light does not flicker when sensors overlap, and it does not switch off when one sensor goes idle but another nearby is still active.
- Set-and-forget commissioning — one workflow, same number of steps for every project size. No per-light scripting, no rule groups to maintain.
The core concept: presence + gradient
Every sensor in a Swarm group is configured with two radii and one brightness target.
Drag the sliders to adjust Inner Radius and Outer Radius. Click the sensor to toggle it off and on.
Inner Radius — the guaranteed-brightness zone
Lights inside the Inner Radius go to the configured Brightness target whenever the sensor is active. Brightness can be a fixed percentage (for example, 100%) or, if the group includes a light sensor, a target LUX value. Inside this radius you get a guarantee: the light is there, at that level, as long as presence is detected.
Outer Radius — the gradient falloff zone
Lights between Inner Radius and Outer Radius calculate their own brightness based on how far they are from the sensor. The further out, the dimmer. The shape is a configurable gradient that fades from the Brightness target down toward the idle level as distance increases.
Lights beyond the Outer Radius stay at idle — typically off, or a low standby level if the scene calls for it.
An illustrative example
Picture a corridor with sensors and lights placed at regular intervals. With Brightness at 100%, an idle level of 25%, and a sensor whose radii reach the immediate neighbors and one ring beyond, the behavior when the sensor fires could look like this:
- The light at the trigger point: 100%
- The three lights in the immediate vicinity: 75%
- The lights in the next ring out: 50%
- Everything beyond: 25% (the idle level for the group)
Drag the sliders to widen or narrow the gradient along the corridor. Click the sensor to toggle it off and on.
These numbers are illustrative — the actual percentages, the size of each radius, and the idle level are all parameters you set in the app to match the space. Two sensors with different jobs in the same group can have completely different radii. A long-corridor sensor might have a wide Outer Radius to pre-light the path ahead, while a stairwell sensor stays tight to its own landing.
When several sensors fire at once or in sequence, each light picks the closest active sensor and uses that to recalculate its brightness. We will come back to this in the edge cases section.
Try it now: the Swarm Editor
Reading about a gradient is not the same as watching one. The embedded Swarm Editor on our swarm technology page uses the same visual model as the MESHLE App — the same Grid view, the same sensor markers, the same brightness gradient. The only difference: the on-site editor is deliberately not wired to real hardware, so you can drag radii and trigger sensors freely without commissioning a single device.
That is exactly what makes it a teaching tool. Several MESHLE clients use it to onboard their own installers and end customers to the concept before they open the App on a live site. If you are explaining swarm to a project stakeholder, the simulator gets there faster than any data sheet.
Where Swarm wins: use cases
Warehouse and corridor swarm lighting
Warehouses, garages, airports, train stations, corridors, underground passages, large open-plan offices, labs, production facilities, hangars, conference centers, and school or university corridors. These are the canonical cases. Conventional sensor-per-light installations leave dark gaps and noticeable switching. Swarm replaces both with a moving bright zone.
Outdoor swarm lighting: paths, streets, parking
Pathways and garden paths, streets, parking lots, building wall lights, and driveways. For more on outdoor specifics, see Outdoor Swarm Lighting: Smart Luminaires That Follow You.
Retail aisle and showroom swarm lighting
Shopping center and mall passages, supermarket aisles, and large showroom floors. Aisles light up around shoppers and dim back down behind them. Empty aisles stay at idle. The retail benefit is twofold: lower operating hours and a more deliberate visual rhythm in the space.
Stairwell swarm lighting and emergency routes
Stairways are the headline case. In many countries, standby lighting in stairwells is required by regulation for security and evacuation. The exact rules vary by jurisdiction. Swarm satisfies the requirement with the lowest possible operating cost: lights sit at the required standby level when nobody is in the stairwell and rise to full when someone enters. The same logic applies to emergency exit corridors and evacuation routes.
The standards that set the operating-light and emergency-light minimums for stairs are well-defined, and naming them helps a specifier check Swarm against what their authority actually requires:
- Germany — ASR A3.4 (Technische Regel für Arbeitsstätten, concretising the ArbStättV): stairs in workplaces require a minimum of 100 lx when in use.
- EU — EN 12464-1:2021: same 100 lx minimum for stairs in indoor workplaces.
- EU — EN 1838: emergency and escape lighting requires 1 lx along the centre line of an escape route and 0.5 lx in open anti-panic areas, with 50% of the required level reached within 5 seconds and the full level within 60 seconds. High-risk task areas require at least 15 lx (or 10% of the normal task illuminance, whichever is greater), available permanently or within 0.5 seconds.
- UK — BS 5266-1:2025: the UK Code of Practice for emergency lighting of premises, used in conjunction with BS EN 1838:2024 (which transposes EN 1838); effective 31 October 2025.
- US — NFPA 101, Sections 7.8 and 7.9: new stairs require a minimum of 10 footcandles (~108 lx) under normal power; emergency lighting requires an average of 1 fc (~10.8 lx) and a minimum of 0.1 fc (~1.1 lx) along the egress path.
Swarm lighting satisfies the operating minimum where presence is detected, and falls back to an idle level that respects the applicable emergency-lighting baseline.
Aircraft hangar swarm lighting
Aircraft maintenance hangars, MRO bays, FBO and general-aviation hangars, military hangars, and drone hangars. The pattern is the same: a vast floor lit ceiling-to-deck all-on, even when crews work on a single aircraft in one bay. MESHLE Swarm replaces the blanket with a moving bright zone that follows the maintenance crew or tow vehicle around the airframe, while the rest of the hangar sits at an idle baseline that still satisfies safety and movement requirements.
Setting up Swarm in the field: Grid view in the MESHLE App
The simulator is a teaching tool. The MESHLE App is where you commission a real installation. The workflow is the same whether you are setting up a stairwell or a multi-aisle warehouse.
- Create one group of devices. Once the group exists, the Swarm button appears in the bottom menu of the app. Tap it to enter Swarm setup.
- Open Grid view and size the canvas. Set rows and columns to match your layout — a row for a pathway, a grid for a warehouse, an L-shape for a corridor with a turn. No floor plan is required. Grid view is deliberately the default because it works on mobile and removes the friction of having to source and upload a building plan before you can start.
- Assign each circle a role: Light, Sensor, or Both. Some fixtures will be light-only, some sensors will be standalone, and many luminaires today ship with both built-in. All three cases are handled in the same view.
- Adjust Inner Radius and Outer Radius per sensor. Move the sliders, watch the visual gradient update in the grid, and tune until the coverage matches what the space needs. Each sensor can have its own radii values — long corridor sensors reach further than landing sensors.
- Link placeholders to physical devices. A list of the devices in the group appears. Tap a device — the matching real luminaire blinks. The installer walks the space, identifies where the blinking is happening, and drops it onto the right placeholder in the grid. Repeat until every circle is linked.
- Save. Settings propagate to all linked devices. A sensor's settings can be copied to all other sensors in one tap, so you do not need to repeat the configuration for identical fixtures.
- Live Preview. Open the Live Preview tab. Tap a sensor in the app to simulate presence — the grid visualizes the resulting brightness for every light, and the actual paired hardware responds at the same instant. This means you can tune the radii standing still in front of the installation, instead of running around triggering motion detectors with your arms.
Create a group
Once a device group exists, the Swarm button appears in the bottom menu of the app. Tap it to open Swarm setup with an empty grid.
The same seven steps cover any project size. There is no "enterprise mode" that swaps in a different workflow at scale. The installer who set up a five-light stairwell can set up a five-hundred-light campus the same way.
Edge cases and advanced behavior
Multi-sensor overlap — no flicker, no premature off
When two sensors' radii overlap, every light inside the overlap recalculates its brightness from the closest active sensor. If two people walk toward each other along a corridor, the lights between them stay bright as the two presence points converge. If one of them stops while the other keeps walking, the lights around the moving person follow the movement and the lights around the stationary person continue to hold their level — there is no flicker, no fight between sensors, no premature dim-down.
Group separation — walls and rooms
Different physical areas can be assigned to different Swarm groups. Two offices separated by a corridor get one group each, so movement in one office does not light the other through the wall. The grouping is logical, not radio-defined: the radio still reaches through walls, but the Swarm behavior is scoped to its group.
Manual override — floor lamps, desk lamps, accent lights
For products where a person consciously sets a state — floor lamps, desk lamps, accent lights — manual settings take priority over Swarm. Once a user sets a brightness or color manually, that luminaire stops responding to presence-driven changes until the state is reset. Nobody's desk lamp jumps to 100% because a colleague walked past their pod.
Daylight integration — lux thresholds and harvesting
A light sensor in the group delivers ambient lux. You can use that in two ways. As a threshold, Swarm only enables once ambient drops below a configured level — useful for outdoor paths that should remain dark in daylight. As harvesting, the Brightness target is a target LUX on the surface, and the luminaire output is whatever is needed to top up the available daylight. Both modes can be mixed inside the same Swarm group — some lights near a window regulate against daylight while lights deeper inside simply switch.
HCL on top of Swarm
Tunable-white luminaires (CCT or RGBTW) can run Human Centric Lighting on top of Swarm. Swarm decides "how bright," HCL decides "what color temperature." The two layers coexist: a warehouse can be presence-driven and circadian-aware at the same time, without either feature compromising the other.
Swarm lighting vs corridor function
Most lighting planners already know a closely related idea under a different name: corridor function. It is the term the established lighting industry uses for a DALI- or 1-10V-style sequence in which the luminaire at the trigger point goes to full output, the next one or two fixtures down the line follow at a reduced level, and everything beyond stays at a standby level. It is a real, useful pattern, and it has solved real problems for years. Swarm lighting is the broader, more flexible cousin.
The two ideas share the same intuition — light should be brightest where someone is and dim away from that point. Where they differ is scope and coordination. Corridor function is a one-dimensional, locally scripted pattern: one luminaire is the master, one or two neighbors are slaves, the chain is configured at the driver. Swarm lighting is an area-wide, peer-to-peer behavior: every luminaire knows the closest active sensor across the whole group and recomputes its own brightness from that, no master and no scripted chain.
| Classic corridor function | MESHLE Swarm | |
|---|---|---|
| Scope | One luminaire and its immediate neighbors along a line | An entire group of luminaires across an area, corridor, stairwell, or aisle |
| Setup | Configured per driver (DALI or 1-10V), usually one master and one or two follower offsets | Configured once per group in the MESHLE App Grid view, with Inner and Outer Radius per sensor |
| Sensor model | One sensor drives the master fixture; followers inherit the dim level | Every sensor in the group participates; every luminaire picks the closest active one |
| Coordination across luminaires | Sequential, along the wired chain | Peer-to-peer across the mesh; overlapping sensors compose cleanly with no flicker |
| Configurability | Fixed offset levels at the driver, retuned by re-commissioning each driver | Radius, brightness, idle level, hold and delay times tuned live from the app with visual preview |
If you have specified corridor function before, swarm lighting is a strict superset — everything corridor function does, plus area awareness and cross-zone propagation.
Compatibility and ecosystem
MESHLE Swarm is not a separate product line. It runs on the same MESHLE Bluetooth Mesh that every MESHLE-enabled device speaks. If a device is in the mesh, it can participate in Swarm.
- All MESHLE-enabled products — drivers, controllers, switch actuators, dimmers, the full product range participates natively.
- BLE-to-DALI / 0-10V / DMX / SPI controllers — Swarm drives existing third-party luminaires through MESHLE interface controllers. See interfaces for the available types.
- Internal, external, and standalone sensors — sensors built into a luminaire, mounted separately on a fixture, or installed as standalone ceiling or wall units all work the same way.
- Third-party sensors — supported on a case-by-case basis through MESHLE firmware integration. Not every third-party sensor is supported; we confirm compatibility per model on request.
- All lighting types — dimmers, CCT, RGB, RGBW, RGBTW. Color products participate in Swarm with their brightness channel; HCL on top is supported on tunable-white products.
- BMS integration — when the building requires higher-level integration, the MESHLE Gateway bridges the mesh to REST, MQTT, Modbus TCP/IP and BACnet without touching how Swarm itself runs locally.
Benefits across four audiences
For people in the space
- Never walk or drive into the dark — the light is already on ahead of the movement.
- Never stare into darkness around a lit screen — the area around the user stays lit.
- Always lit surroundings in the direction of movement, which reduces eye-strain and improves perceived safety.
- Comfort, security, and a sense of being expected rather than detected.
For installers and commissioners
- Set-and-forget workflow — fewer scenes and groups to maintain over the life of the installation.
- Same setup steps regardless of project size — five nodes or five hundred.
- Cross-product compatibility across the MESHLE ecosystem — no integration glue between fixtures.
- Late-trigger masking — after the first sensor in a path fires, all subsequent sensors find the light already ahead of the user, so timing imperfections are invisible to the end user.
- Live Preview from the app means tuning happens standing still, not walking the building.
For customers (building owners, facility managers)
- Lights only run when and where they are needed — meaningful reductions in operating hours over a year.
- Better comfort for workers, tenants, visitors and shoppers.
- Compliance with regulations that require standby lighting (notably stairwells), with minimal energy cost.
- Lower likelihood of dark-zone accidents and the liability that follows.
- One workflow that scales from a single building to a multi-building campus.
For end users
- Comfort — the room behaves like it is paying attention.
- Security — never reaching for a switch in the dark.
- Health — less eye-strain in offices, better circadian alignment when HCL is layered on top.
- An always-lit surrounding in the direction of motion, which makes corridors, stairs, and parking lots feel safer at every hour.
Frequently asked questions
What is swarm lighting?
Swarm lighting is a presence-aware lighting behavior in which every luminaire in a network is aware of where movement is happening and reacts together, not in isolation. The closest lights go to a configured brightness target, lights further out dim in a gradient, and lights beyond that gradient stay at idle. When the movement moves, the bright zone moves with it. In MESHLE's implementation, each sensor is configured with an Inner Radius (guaranteed-brightness zone) and an Outer Radius (gradient falloff), and the behavior runs locally on the MESHLE Bluetooth Mesh without a central controller.
How is swarm lighting different from a motion sensor controlling a single light?
A motion sensor controlling a single light only sees its own luminaire. The result is patchy: one light on, the next four off, the next on again as the user walks through the space. Swarm makes every luminaire aware of the closest active sensor in the entire group, so the light is already on ahead of the user and fades behind them. Late-triggering sensors stop being a problem because by the time the second sensor fires, the light is already on. Multi-sensor overlap is handled cleanly with no flicker and no premature off, which a chain of independent sensors cannot do.
What's the difference between swarm lighting and corridor function?
Corridor function is the term the established lighting industry uses for a DALI- or 1-10V-style pattern in which one luminaire goes to full output and the next one or two follow at a reduced level. It is one-dimensional and configured per driver. Swarm lighting is the area-wide, peer-to-peer cousin: every luminaire in the group knows the closest active sensor across the whole space and computes its own brightness from that, with no master fixture and no scripted chain. If you have specified corridor function before, swarm is a strict superset — everything corridor function does, plus area awareness and cross-zone presence propagation. See the Swarm lighting vs corridor function section for the full comparison.
Does swarm lighting work offline, without Wi-Fi, cloud, or a hub?
Yes. MESHLE Swarm runs entirely on the MESHLE Bluetooth Mesh, locally between devices. No internet, no Wi-Fi, no cloud, and no central hub is required for Swarm to function. Sensor events, radius calculations, and brightness updates all happen on the mesh itself. A MESHLE Gateway can be added later if you want remote access, BMS integration, or voice control — but that is optional and does not change how Swarm behaves locally.
Can I retrofit swarm lighting into an existing installation?
Yes — that is one of the main reasons MESHLE Swarm exists. You can retrofit by swapping existing drivers for MESHLE drivers, by adding MESHLE BLE-to-DALI / 0-10V / DMX / SPI interface controllers in front of existing luminaires, or by replacing fixtures with MESHLE-enabled equivalents. Sensors can be internal to a new luminaire, externally mounted on an existing one, or installed as standalone ceiling or wall units. There is no rewiring of switching circuits required — Swarm replaces the logic, not the cabling.
What sensors and lights are compatible with MESHLE Swarm?
All MESHLE-enabled products participate natively: drivers, controllers, switch actuators, dimmers, CCT, RGB, RGBW, RGBTW. Existing third-party luminaires can be brought in through MESHLE interface controllers (BLE-to-DALI, 0-10V, DMX, SPI). Sensors can be:
- Internal — built into a MESHLE-enabled luminaire
- External — mounted on a fixture and paired into the mesh
- Standalone — ceiling or wall units installed independently
Third-party sensors are supported case by case through MESHLE firmware integration. Compatibility per sensor model can be confirmed by our team on request.
Does swarm lighting save energy? How much?
Yes. Because lights only run at full brightness where presence is detected and dim or stay off everywhere else, total operating hours drop substantially compared with an always-on or schedule-only installation. The exact saving depends on the space, the occupancy pattern, and the idle level you configure — a 24/7 warehouse with sporadic forklift movement saves far more than a corridor that is busy during office hours. We do not publish a single percentage figure because any honest number is a function of how the space is used; we are happy to model the saving for your specific layout when discussing a project.
Is swarm lighting allowed in stairways and emergency contexts?
Stairways are one of the strongest use cases for Swarm. In many countries, regulations require a continuous standby level of illumination in stairwells for security and evacuation, and Swarm satisfies that requirement at the lowest possible operating cost: the standby level holds when nobody is present, and full brightness rises the instant someone enters. The exact rules vary by jurisdiction — building codes, fire codes, and workplace safety codes differ between countries. Confirm the applicable regulation locally before specifying a Swarm-based stairwell installation; Swarm is the implementation technique, not the regulatory certification.
Can I combine swarm with daylight harvesting?
Yes. A light sensor in the Swarm group delivers ambient lux. You can use lux as a threshold (Swarm only activates once ambient drops below a configured level — useful for outdoor paths that should remain dark in daylight) or for harvesting (Brightness becomes a target LUX on the surface, and luminaire output is whatever is needed to top up the available daylight). Settings can be mixed within the same Swarm group: lights near a window can regulate against daylight while lights deeper inside simply switch on and off based on presence.
How is MESHLE Swarm different from Casambi or Silvair?
Casambi is a proprietary Bluetooth Mesh platform with the largest installed base and the broadest luminaire partner ecosystem, but it does not implement a cross-group swarm presence model. Silvair is a major contributor to Bluetooth NLC (Networked Lighting Control), a SIG standard that covers dimming, occupancy and ambient-light response — but NLC does not standardise a multi-sensor swarm with configurable Inner/Outer Radius. MESHLE Swarm is the area-coordinated presence-and-gradient behavior described in this article, runs on MESHLE's own Bluetooth Mesh, and is set up through the Grid view in the MESHLE App. For a fuller comparison of platforms, see Best Bluetooth Mesh Platforms for Smart Lighting and The 7 Best Casambi Alternatives.
How does swarm lighting compare to a Bluetooth NLC system?
Bluetooth NLC (Networked Lighting Control) is a set of SIG-defined profiles that standardise the basics — dimming, occupancy sensing, ambient-light response, scenes — across vendors so devices from different manufacturers can interoperate at the profile level. That is the value of NLC: cross-vendor interop on a defined feature set. NLC does not standardise a multi-sensor swarm with configurable Inner Radius, Outer Radius, gradient falloff, and area-wide closest-sensor selection — that behavior sits above the NLC layer. MESHLE Swarm is that area-coordinated behavior, runs on the MESHLE Bluetooth Mesh, and is set up in the MESHLE App. The two are not mutually exclusive in concept, but Swarm is broader in scope and tuned end-to-end inside the MESHLE stack.
How many lights can be in one swarm group?
A single MESHLE Bluetooth Mesh network supports up to 255 nodes, and a single Swarm group can include as many of those nodes as the layout requires. For larger installations — multi-aisle warehouses, multi-building campuses — multiple mesh networks can be unified through the MESHLE Edge server, scaling to up to 20,000 devices across unified zones. Swarm behavior is scoped per group, so very large sites are usually broken into logical groups (per floor, per aisle, per zone) rather than one giant group.
Does swarm lighting require Wi-Fi, cloud, or a hub?
No. MESHLE Swarm runs locally on the MESHLE Bluetooth Mesh between the luminaires and sensors. No Wi-Fi access point, no cloud account, and no central hub is required. The MESHLE App connects directly over Bluetooth from a phone or tablet to commission and tune the installation. A MESHLE Gateway can optionally bridge the mesh to LAN, Wi-Fi, Matter, or a BMS later, but it is not a prerequisite for Swarm to work.
Does swarm lighting record or track what people are doing?
No. The sensors used for Swarm detect presence and motion — typically PIR motion plus optional ambient lux. They do not record video, audio, identity, or any personal data. The mesh exchanges only the minimum information needed to compute brightness for each light, and that information stays on the local Bluetooth Mesh unless you explicitly add a Gateway and choose to forward data to a building management system. MESHLE is a German company and the platform is designed offline-first; cloud connectivity is opt-in, never required.
Get in touch
Got a project that requires MESHLE Swarm?
Tell us about the space, the fixtures you already have or plan to use, and what you want the light to feel like. and we will work through the layout with you.
Want to adopt Swarm in your own projects?
If you specify lighting for clients or run an integrator practice, MESHLE Swarm is a behavior you can bring to every project without swapping your hardware story. See the integrator path for how we work with specifiers and consultants.
Want to integrate MESHLE in your drivers or fixtures?
For luminaire OEMs and driver manufacturers, MESHLE offers pre-certified modules, custom firmware profiles, and white-label app branding so Swarm ships as part of your own product. — mention "OEM" in your message and we will route you to the right team.
Further reading
- MESHLE Swarm technology overview
- Outdoor Swarm Lighting: Smart Luminaires That Follow You
- Offline-First Smart Lighting: why your building should not depend on the cloud
- What is Bluetooth Mesh? A practical guide
- The 7 best Casambi alternatives for smart lighting
- Smart street lighting with MESHLE
- Battery-free wireless switches