TRADE NOTES / OCTOBER 2026

Dimmable track lighting problems to investigate

Flicker, sudden jumps and uneven response are observations, not a diagnosis. A useful troubleshooting discussion identifies the actual equipment and the conditions under which the symptom appears before somebody orders replacement heads.

Review the buying questions

2026-10-14 / Trade lighting desk

01 / HOLDER / FORM
Identify the source arrangement
02 / RAIL / ADAPTER
Check the exact system
03 / TARGET / CONTROL
Describe the intended task
01 / TRADE NOTE

"It flickers" is not a diagnosis

Flicker. Won't start. Starts, then drops out. Jumps from dim to bright like the control has two settings and a grudge. These are four different complaints, and they get bundled into one sentence — "the dimming doesn't work" — which is where the trouble starts. Before anything gets blamed or replaced, somebody has to watch the lights and write down what actually happens, in plain language, while it's happening.

Which heads misbehave: all of them, or the ones at the far end of the run? When: at switch-on, while the control is moving, or after ten quiet minutes at a low setting? What's the room doing at the time? A fault report that answers those questions is worth more than a photograph of the spotlight, however sharp. The head is only one actor in this. The control is another, the driver or supply arrangement is a third, and they perform together or not at all.

02 / TRADE NOTE

Write down both references before you touch anything

Get the control's identity recorded — the model, the make, whatever the front plate and the paperwork can tell you — and the head's reference too. Put them in the same note. It sounds obvious. It almost never happens. What usually reaches the supplier is a picture of the new fitting and a hopeful question, and the reply has to guess at the half of the combination that stayed at home.

If the installation paperwork exists, dig it out. If several controls feed several runs, say which control feeds the run that flickers. A restaurant with three dining areas may have three separate arrangements wearing one description, and a fix proven in the front room proves nothing at all about the back.

03 / TRADE NOTE

Low is a place, not a percentage

"How low should it go?" sounds like a specification question. It isn't, really. One owner wants the track lights eased down a touch so the room stops feeling like a canteen. Another wants a faint glow for late service, candles doing most of the work. Both would nod at the same demonstration in a showroom at midday, then disagree completely at nine in the evening in their own rooms.

So describe the evening you actually want. Staff setting the room before service, guests arriving, the last hour before close — at which of those moments does the low setting get used, and what should people still be able to see? Menus? Faces? The step by the door? Buy for that setting. "Dims a bit" is not a setting, and a head bought against it will keep disappointing somebody every night.

04 / TRADE NOTE

Starting is a different event from dimming

Here's a trap that catches a lot of installations. The lights behave beautifully when they're brought down from full — smooth, steady, no complaints. The demo ends, everyone's happy. Then the next evening, staff switch on with the control left at that low position from the night before, and half the heads sulk, blink, or refuse entirely.

Dimming down and starting low are different demands. Test both. Note which one fails, because "it struggles at switch-on from the low setting, but dims down happily" points the conversation somewhere much more specific than "there's a flicker problem". The opening routine matters more than the demo: it's the version your staff will perform every day, in a hurry, with guests at the door.

05 / TRADE NOTE

One good head doesn't clear the whole run

A supplier sends a sample. It works — on a short test lead, alone, with the sample control. Then forty heads go up on the real run with the real control and the behaviour changes. Loading matters. The combination that gets installed is the combination that has to be judged, and a single-head trial, useful as it is for shortlisting, can't stand in for it.

Ask for the assessment to reflect the intended group: the actual control, a realistic number of heads, the actual run. If that's impossible before ordering, at least write down the gap between the trial and the installation in the comparison notes, so nobody later claims the sample "proved" something it never tested.

There's a cousin of this problem in mixed runs, where an older group of heads shares a control with a newer batch added during a refurbishment. The old heads behave; the new ones sulk at low settings; the report says "some flicker", which is true and useless. Split the observation by batch before anyone orders anything. Two populations on one circuit can have two different conversations with the same control, and the fix for one group may be a simple regrouping rather than a replacement programme for the whole ceiling.

06 / TRADE NOTE

Listen to the room as well

Some dimming problems are heard before they're seen. In a quiet room — a gallery in the morning, a dining room between services — a hum from a head or a control can be the complaint that outlasts the flicker. Turn the music off. Stand still. Note roughly where the sound seems to come from without deciding on the spot which component is guilty; localising a buzz through a ceiling is guesswork dressed as expertise.

Report it the way you'd report the flicker: when it happens, at what setting, how far away it's audible. "Buzzing at low settings, audible two metres away in a quiet room" gives the next person something to work with. "Noisy dimmer" gives them an opinion.

07 / TRADE NOTE

Change one thing at a time

The natural response to a misbehaving installation is to swap parts until it stops. New control, different head, someone's cousin re-terminates something. The lights settle. Everyone relaxes. And nobody knows which change did it — which means nobody can describe the working combination when the second room needs the same treatment, or when a replacement is needed next year.

Discipline, then: one change, one retest of the same routine (switch on at the low setting, raise, lower, hold). Write the result down even when it's "no change". A short log of three honest trials beats a shelf of swapped components and a shrug. It's slower this week and much faster every week after.

08 / TRADE NOTE

Before you order replacements, name the level you live at

Replacement enquiries usually ask whether a head "is dimmable", as if the word were a property of the fitting. The useful enquiry hands over the combination: the control reference, the rail details, and the observed behaviour at the settings the room actually uses — including that awkward switch-on. Ask for a model against that, with its control requirements stated, and test the proposed pairing against the same opening routine before the full order goes in.

It takes one more email at the start. It saves the particular misery of forty new heads faithfully reproducing the fault you already had.

09 / TRADE NOTE

Keep the log where the night staff can find it

All of this observing and note-taking dies in a drawer if the record lives with the project file, in a folder named by a contractor who left in spring. The people who meet the fault are the people closing the room at midnight. The log should live where they live: with the opening instructions, in the staff handbook, in the shared note the duty manager actually reads. One page. Plain words. The combination that works, the routine that tests it, and the settings the room is supposed to wake up at.

Update it when anything changes — a head swapped, a control replaced, a group re-purposed for a new layout. An out-of-date log is worse than none, because it gets believed. And when the next fault appears, the first entry in the investigation is already written: somebody adds what the lights did tonight, underneath what they did the last time anyone looked properly. Patterns confess over pages. Single incidents just shout.

It is fair to ask why a lighting installation needs a diary at all. Because dimming faults are intermittent by nature and memory is partial by design. The diary is how a room argues its case over months instead of re-litigating the same flicker from scratch, with the same guesses, every winter.

The back room is a separate question

The front room gets fixed. Log written, combination recorded, staff happy. Then the owner asks why the back room still misbehaves, as if the cure were a property of the building. It isn't. The back room has its own control, its own run, its own history of who installed what — and its behaviour at switch-on was never actually observed, because everyone was busy watching the front.

Give it the same hour the front room got: watch the opening routine, write down both references, test the low setting the room really uses. Maybe the answer rhymes with the front room's. Maybe it doesn't. Either way it will be an answer about the back room, which is the only kind worth ordering against.

What should I send Sampo about dimmable track lighting problems to investigate?

Include the control reference, rail identification and observed dimming sequence when asking Sampo about a suitable dimmable COB model.

Ask Sampo about fit

NEXT / HEAD SELECTION

Request a track light quotation

Send the holder family, rail details, quantity and market.

Ask Sampo about fit