# Acceptance Testing of Installed Lighting Controls: Scenes, Dimmers and Test Sequences

How to run acceptance testing on installed lighting controls: verify scenes, walk a dimmer test sequence, check dimming curves, and close with a signed test log.

Acceptance testing of installed lighting controls proves that every scene, dimmer and keypad in the room does what the design and the owner asked for. The work moves in a fixed order: set up the acceptance test checklist, verify each lighting scene, walk the dimmer test sequence, then record results in a test log and sign-off. Testing happens after commissioning lighting controls is finished, so a failure points to installation or programming rather than unfinished setup. 

- Test scenes and dimmers in a set order so a fault is caught at the step that causes it, not three steps later.
- Verify a scene by its recorded levels and by the fade between scenes, not by how the room looks at a glance.
- Walk each dimmer from off to full and back down to see that the light changes smoothly with no jump or dead band.
- Record every result as pass or fail with the fixture and control named, then close with a dated sign-off.
- Anything involving mains wiring or panel access belongs to a qualified electrician, not to the person holding the checklist.
 

## What an acceptance test proves 

An acceptance test confirms that the installed lighting control system matches the approved design and works as the owner expects. The test is a formal check against documents, not a walk-through with a casual switch press. A pass means the recorded intent and the built room agree. 

Functional testing covers scenes, dimmers, keypads, sensors and the links between them. Each item is exercised and its result written down. The test log and sign-off are the deliverable, because they show what was checked and who accepted it. 

Acceptance testing follows commissioning lighting controls, which is where the system gets set up and tuned. If tests run before commissioning is complete, failures pile up that have nothing to do with the installation. Set the test date only after the programmer reports the setup as finished. 

## Building the acceptance test checklist 

The acceptance test checklist is a written list of every control, device and state that must be checked in the room. Build it from the scene schedule, the dimmer schedule and the keypad layout. A checklist with no schedule behind it tests only what the tester happens to remember. 

Each line names one item, its location, the expected result and a place for pass or fail. Group the lines by scene, then by dimmer, then by keypad and sensor. Grouping lets one tester work through a zone without walking back and forth across the room. 

The checklist also fixes who does the testing and what counts as a fail. A visible flicker, an audible buzz, a scene that lands on the wrong level or a keypad button that does nothing all count. Write those definitions down before the test starts so the verdict does not drift. 

## Lighting scene verification, step by step 

Lighting scene verification checks that each named scene sets every controlled light to its recorded level. Call up the scene at the keypad and read the room against the schedule. Measure the light where the schedule gives a target, using a meter rather than the eye. 

The fade into a scene matters as much as the end state. A scene that snaps on instead of fading means the fade time is wrong or the fixture does not support it. Watch the transition for every scene in the list, not only the first one. 

Check the scene from every entry point: the wall keypad, the app and any remote control. A scene that works from one device and fails from another points to a programming gap. Record which entry point failed so the fault can be fixed once. 

## Walking the dimmer test sequence 

A dimmer test sequence takes each dimmer through a fixed path so that faults surface in the same place every time. The path goes from off to a low level, then up in steps to full, then back down to off. Repeat the path on every dimmer channel in the zone before moving on. 

Watch for a jump, a dead band at the bottom, a buzz at any level or a light that drops out near the top. Note the level at which each fault appears, because the level tells the programmer where the dimming curve is wrong. Dimming curve check is the follow-up step once a fault is noted. 

Test the low end carefully, since some lamps and drivers behave poorly below a small output. Where a fixture cannot dim cleanly all the way down, the fix may be a minimum level set for that channel. Record the accepted minimum level in the log so the setting is not lost. 

## Dimming curve check and level matching 

A dimming curve check confirms that light output rises and falls evenly as the control level changes. Feed the same level to lights that should match and read the result side by side. A pair that differs at the same level needs its curve trimmed or its driver changed. 

Matching levels across a scene keeps the room from looking uneven when the scene dims. Check each scene at a middle level and a low level, because a mismatch shows up more at the low end. Write the measured levels on the checklist next to the expected ones. 

The curve is a setting inside the control, and changing it affects every scene that uses that channel. Rework the curve, then re-run the scene tests that touch the channel. Do not close the dimmer section until the scenes affected by a curve change pass again. 

## Recording results in the test log 

A test log records what was tested, the result and the date, so an owner can trace a fault later. Each entry names the device, the scene or level, the expected result and the actual result. A log without the actual result is a plan, not a record. 

Store the log where the system documents live, and keep the version that matches the finished programming. Photographs of the keypad labels and the scene schedule help when a later change is made. The final sign-off names the tester and the owner's representative. 

Re-test any failed item after the fix, then update the line rather than adding a second one. A log that shows the fix and the re-test is stronger than one that hides the first failure. Keep superseded pages if the owner asks for a full trail. 

## Roles, safety and handover 

The person who performs acceptance testing needs access to the programming and a copy of the schedule. Scene and level changes are programming work, and a tester without that access can only observe faults. Agree before the test who can change settings and who records them. 

Work inside electrical panels, at mains terminals or on anything that needs a cover removed is a job for a qualified electrician. Do not reach into a panel to reset a dimmer or reseat a wire. Test only through the user controls and the programming interface the system exposes. 

Handover closes with the test log, the scene schedule and a short walk-through for the people who use the room. Show them how to call each scene and how to adjust a dimmer. Leave the accepted minimum levels and the curve settings noted where they can be found. 

## Test order that saves repeat visits 

The right test order runs from the single control up to the full scene, so a fault is caught at its source. Test dimmer channels first, then keypads and sensors, then scenes, then the links between rooms or zones. Reversing the order means a scene failure sends the tester back down to channels. 

Run the same order for every zone and keep the checklist pages in that order. When a fault appears at the scene step, the channel and keypad steps are already marked as passed. That shortens the fix to one device instead of a full-zone search. 

Finish with a full sequence run of every scene in the room as a final check. Use the fade times from the schedule and watch the whole sequence without stopping. A clean full run after fixes is the state that the sign-off should record. 

## Lighting control acceptance testing questions 

### What is a dimmer test sequence? 

A dimmer test sequence is a fixed path through each dimmer channel, run in the same order every time. It goes from off to a low level, up in steps to full, then back down to off. Walking that path on every channel makes a fault easy to find and easy to compare across dimmers. 

### How do I verify lighting scenes after installation? 

Verify lighting scenes by calling up each scene and reading the room against the scene schedule. Measure the light where the schedule gives a target and watch the fade into the scene. Repeat the check from every entry point, such as the keypad, the app and any remote. 

### What belongs on a lighting control acceptance test checklist? 

An acceptance test checklist lists every control, device and state to be checked, grouped by scene, dimmer and keypad. Each line names the item, its location, the expected result and a place for pass or fail. The scene and dimmer schedules are the source for those lines. 

### When should acceptance testing start? 

Acceptance testing starts after commissioning lighting controls is finished and the programmer reports the setup complete. Testing earlier mixes installation faults with unfinished setup and doubles the work. The test date should follow the end of programming, not run beside it. 

### What does a dimming curve check look for? 

A dimming curve check looks for even change in light output as the control level moves, and for matching output between fixtures at the same level. A jump, a dead band or a pair that differs at a middle level points to a curve setting or a driver issue. Correct the curve, then re-test the scenes that use that channel. 

### Who should sign off the test log? 

The test log is signed by the person who ran the tests and by the owner's representative. The sign-off names the finished programming version and the date. A signed log with recorded results is what closes acceptance testing.
