Dynalite And DALI Commissioning: Where Integration Usually Goes Off Track
A lighting package can pass a switch-on test and still be poorly commissioned. The trouble appears later, when one fitting refuse to dim, a replacement driver joins the wrong group, or a preset changes lights outside the intended area.
This article covers where Dynalite and DALI commissioning commonly breaks down, and what project teams should verify before handover.
The First Problem Is Often Addressing
DALI drivers need unique short addresses within each universe. They can also belong to groups, while Dynalite translates those assignments into DyNet areas and channels. If enumeration is incomplete or the mapping is wrong, a fitting may be online but respond to the wrong command.
A green status light does not prove the circuit is correctly assigned.
With Philips Dynalite, installers should flash each area or channel after assignment and confirm which luminaires respond. Dynalite’s System Builder documentation recommends this physical check before assignments are saved.
Replacement Drivers Can Create New Faults
A failed DALI driver rarely arrives at a convenient time. The fitting is replaced, power returns and everyone expects the old address to follow automatically.
Sometimes it can. Dynalite DALI-2 controllers may support automatic replacement when one failed driver is replaced and the required settings are enabled. Replacing several drivers is different. Each new driver must be identified, flashed and matched with the intended channel.
A practical note from live sites: once two contractors replace fittings without updating records, fault-finding becomes guesswork quickly.
Group Limits and Mapping Need Attention
A DALI universe supports up to 64 short addresses and 16 group addresses. Dynalite can create more logical areas than DALI has groups, so the controller manages the translation.
This is where apparently tidy Dynalite Systems can develop odd behaviour. Areas may be split poorly, drivers may inherit the wrong group, or individual-address control may cause visible delays across many fittings.
The commissioning team should confirm:
Which areas use DALI groups and which rely on short-address commands.
Whether emergency fittings are identified correctly.
Preset behaviour after a controller restart.
That drawings, device names and System Builder records agree.
Scenes Can Fail Even When Devices Work
Dynalite stores channel naming, area addressing and scene levels in its load controllers. DALI data is written to the drivers through the controller. Saving only one side of that relationship can leave the project file, controller and fittings out of step.
And that matters because a scene may work during testing, then behave differently after later programming or driver replacement.
A Better Way to Close Commissioning
For teams managing a Dynalite lighting control system, mySmart can review addressing, mappings and commissioning records before minor faults become repeated callouts. The useful outcome is not simply working lights at handover, but a system the next technician can understand.

















