DALI lighting controls and BMS integration

DALI is not a brand, a dimmer plate, or a way to avoid writing a control narrative. It is a digital lighting bus with rules, power limits and a commissioning job that Australian sites still treat as optional. This essay sits in energy and controls because a well-commissioned bus is how an LED retrofit keeps its savings after the cleaners invent a night shift.

I write DALI the way I write a switchboard schedule: name the devices, name the groups, name who owns the scene after handover. If that sounds unromantic, good. Romance is how you get a “smart” floor that only works from one iPad left in a drawer.

What DALI-2 actually bought us

The original DALI (IEC 62386, the first wave) gave us addressable gear, groups and scenes. It also gave us a marketplace of almost-compatible ballasts. DALI-2 is the certification programme that tests control gear, input devices and application controllers against those parts of the standard. For a specifier in Melbourne or Sydney that means you can write “DALI-2 certified” and mean something a test house has already argued about.

Write the parts you need:

• Control gear (drivers, emergency modules) with DALI-2 marks.
• Input devices if you want certified sensors and switches on the bus.
• An application controller — the brain — that is also certified, not a hobby board in a riser.

Broadcast-only “DALI” that never addresses fixtures is a dimming cable with better marketing. It can be fine for a single warehouse aisle. It is not a strategy for a multi-tenancy office that wants Section J credits, NABERS evidence and a facilities manager who can turn off Level 12 without walking there.

The bus is a physical thing

A DALI line is polarity-insensitive in theory and abused in practice. It needs a bus power supply, a length limit, a device count limit, and cable that was not leftover fire-alarm pair. I still find DALI taped onto the lighting circuit earth “because it worked in the showroom”. It will work until the first VSD in the plant room starts.

Design rules I will not negotiate on commercial jobs:

• One documented power supply per line, sized and labelled.
• A line map, not a verbal “it loops the floor”.
• Surge and segregation from ELV that is not lighting.
• Emergency DALI devices treated as first-class citizens, not afterthoughts on the last two addresses.

If the floor plate is large, plan multiple lines and a controller that can see them. Do not daisy-chain 180 devices onto one tired supply because the schematic fitted on one A3 sheet.

Groups, scenes and the people who press buttons

Addressing every driver is the start. The design is the grouping. Group by visual task and daylight, not by circuit leftover from 1998. A north perimeter in Brisbane is not the same group as the core meeting rooms. See daylight integration and AS/NZS 1680 before you copy the electrical distribution into the lighting groups.

Scenes are how you stop occupants from inventing lighting. A meeting room needs present, present-with-screen, clean, and off. An open plan needs day, evening, after-hours and a genuine off that the BMS cannot accidentally override at 2 a.m. Hospitality-adjacent receptions need a scene that does not look like a dentist. Write the scene table in the spec with target levels, not “dim to taste”.

Absence detection belongs on the bus as an input device with a timeout the client has agreed. Presence detection that turns lights off while someone reads a contract is how DALI gets a bad name. In accessible and neurodiverse workplaces the timeout and the fade are not cosmetics. Read accessible lighting before you set a thirty-second drop to black.

Gateways and the BMS

Building management systems in Australian commercial stock speak BACnet, sometimes Modbus, occasionally something proprietary that a 2009 integrator still supports from a shed. Lighting should meet the BMS at a gateway you specified, with a points list you approved.

Decide the granularity before anyone prices a “full integration”:

• Floor on/off and after-hours extend — usually enough for base-building energy.
• Tenancy scenes and daylight set-points — useful, and easy to break.
• Individual luminaire feedback — powerful for maintenance, noisy for the BMS historian.

I have watched a BMS operator slide “all lights” to 40 per cent during a demand-response event and take a legal mark-up room with it. Put interlocks in writing. Emergency lighting stays out of the slider. Critical task lighting in plant rooms stays out of the slider. If the energy manager wants a shed load, give them a named scene, not raw levels.

The gateway is also where time schedules should live or not live. Two clocks — BMS and lighting controller — will drift and then fight. Pick an owner. Document it. The commercial lighting specification essay has the hold-point language.

Commissioning is a paid activity

A DALI bus that has not been commissioned is a random collection of factory addresses. Commissioning includes:

1. Identify and record every device against the lighting layout.
2. Assign groups and scenes from the approved table.
3. Set fade times, power-on levels and system-failure levels.
4. Calibrate photocells in the real room, at night and by day.
5. Test emergency DALI function and the link to the 2293 logbook.
6. Export a project file the owner can open without the commissioner’s laptop.

Power-on level matters. After a Monday outage I want a safe, legal lighting state, not last-scene-memory that comes back at 10 per cent in a stair. System-failure level matters when the bus dies. Occupants should still be able to leave the building. That is a WHS decision, not a vendor default.

Allow time. A 2,000 square metre tenancy is not a two-hour “point-to-point”. If the builder has scheduled commissioning on the same afternoon as the furniture delivery, you will commission furniture.

Sensors, photocells and the Australian sun

PIR sensors on glass-faced northern rooms will see heat and lie. Ultrasonic sensors will see a waving plant. Use the sensor type the room deserves, mask it, and put it on the drawing. Photocells that only switch a row on and off create a flicker people blame on “cheap LEDs”. Dim continuously in a daylight zone. Priya covers the politics of blinds in the daylight piece; I will only add that a photocell behind a permanently down blind is a brick.

In tropical and arid buildings the sensor enclosure is a dirt and insect problem. Specify IP and a cleaning cycle. A DALI sensor that has filled with hoppers is not a software fault.

Emergency, monitoring and the forgotten line

DALI emergency gear can report duration-test results if you buy it and commission it. That does not retire the need for a competent person and a logbook. It does mean you can stop climbing every fitting for a six-monthly poke. Write the monitored-system responsibilities. Write what happens when the controller flags a failed pack. A red pixel on a screen is not a repair.

If the project is a retrofit, decide whether old analogue emergency stays analogue. Mixed systems are legal if they are tested. They are miserable if only the new half reports to the pretty dashboard.

What I write in the specification

• Protocol: DALI-2, named IEC parts, certified devices.
• Line topology, power supplies, cable, surge.
• Group and scene tables tied to rooms and tasks.
• Gateway protocol, points list, who owns schedules.
• Commissioning method, as-built file format, training.
• Substitution rule: no analogue stand-in, no uncertified “DALI compatible” driver.

If a value-management workshop tries to replace the application controller with a pile of standalone sensors, make them explain how the BMS scene, the after-hours regime and the emergency report still work. Controls are where “value” usually hides, right next to glare.

A working DALI job is boring to watch. Buttons do what the label says. The BMS sees the points it was promised. The logbook has a file date. That boredom is the product. If you have a gateway horror story that taught a general rule, write for us. We will edit it against the editorial standards, including the rule that we do not launder a manufacturer sequence as journalism.