Skip to content
TechnoGuru — Think Technology, Think TechnoGuru

02 / 06

Case file

01 · Smart Automation

Lighting Automation.

Light, tuned to the hour.

Dimmable, scene-based, daylight-aware lighting on Rako, Fibaro, KNX or DALI — programmed to the rhythm of the room rather than the switch on the wall.

Lighting Automation — representative visual (illustrative scene, not a project photograph)
Dimming vs lighting automation
Dimming vs lighting automation
AspectDimming aloneLighting automation
ScopeOne fixture on a knob or sliderWhole-room scenes, schedules, sensors and inter-room logic
Colour temperatureFixedTunable-white shifts from warm to cool across the day
EnergyManual switchingAstronomical timers, daylight harvesting and occupancy sensing recover energy automatically
ControlBank of togglesEngraved keypads carrying the room's real scenes

Educational comparison — design choices vary by fixture and architecture.

— Interactive · live scene state

One panel. The whole apartment responds.

Tap a scene. Every circuit, shade, AC zone and AV source shifts at once.

Reference luxury apartment — Welcome scene · isometric 3D renderReference luxury apartment — Dinner scene · isometric 3D renderReference luxury apartment — Film scene · isometric 3D renderReference luxury apartment — Rest scene · isometric 3D renderReference luxury apartment — Away scene · isometric 3D renderReference luxury apartment — Goodnight scene · isometric 3D render

/ The discipline, in detail

How we approach lighting automation.

Lighting is the single largest sensory layer in any premium space. Done well, it disappears. Done poorly, it dominates every room. We commission lighting scenes per zone — Welcome at 80% / 2700K, Dinner at 40% / 2200K, Film at 4% bias — and let the system fade between them at sunset, on a calendar, or on a single press.

Astronomical timers, daylight harvesting and occupancy sensors recover energy automatically. Engraved keypads replace the bank of toggles next to every door. Battery-backed circuits hold scene memory through power outages.

We work to the architect's lighting plan, not against it — specifying drivers, dimmer curves and load-balancing for every fixture before the wiring is pulled.

On record

Every lighting automation engagement is documented end-to-end — design, programming, commissioning, calibration — and handed over with the files our successors would need if we were never to return.

/ Protocol stack

Keypads, bus and fixtures

The three-layer lighting-control stack — scene keypads over an addressable bus over dimmable circuits. Brand-neutral; the exact stack is per brief.

Lighting protocol stackA three-layer canonical lighting control architecture: BMS supervisor layer at the top, scene/keypad layer in the middle (proprietary protocols Rako, KNX, Lutron), an addressable bus layer connecting the scene controls to fittings (DALI-2 typically), and fittings at the bottom with addressable drivers and emergency self-test. The arrows show the direction of control telegrams; the gateway bridges proprietary scene protocols to DALI-2 at the fitting layer.Lighting stack · Hybrid scene + addressable fixtures01 · SupervisorBMS / FacilitiesHoneywell EBI · Siemens Desigo · BACnet/IP02 · Scene / KeypadRako KeypadLiving · Dinner · GoodnightKNX SwitchABB · Gira · SchneiderLutron HW QSXEngraved ArchitecturalTouch PanelWall · Mobile · Tablet03 · Bus / GatewayKNX TP BusTwisted-pair backboneDALI GatewayKNX → DALI bridge04 · FittingsDownlightDALI-2 driverPendantTunable whiteLinearArchitecturalWallwashRGBWEmergencySelf-test (Part 202)Each layer is loosely coupled — a failed keypad does not bring down the bus; a failed gateway does not bring down adjacent zones.
Hybrid keypad-over-DALI pattern — canonical above 100 fixtures. Indicative only.

Diagrammatic view — a system planning illustration for design discussion, not a project drawing or live interface.

/ Where we deploy this

Active across 5 sectors.

Lighting Automation is rarely a standalone brief — it sits inside a wider sector practice with its own codes, expectations and operating rhythm.

/ Where this system has been deployed

Lighting Automation on the ground.

The reference projects below carry a lighting automation layer engineered as part of an integrated stack. Each case study walks through the engineering challenges that were solved, the standards the work was held to, and the operational outcome on the day-two team.

Public project summaries describe systems and outcomes only — BOQ values, quantities, device counts and security layouts are kept off public surfaces.

Request a feasibility review

/ Plan it right

Lighting Automation — getting the brief right.

Common mistakes to avoid

  • Finalising the lighting layout and circuiting without the control intent, so scenes and dimming zones cannot be created afterwards.
  • Mixing dimmable and non-dimmable drivers on one circuit and discovering the flicker on site.
  • Ignoring tunable-white and daylight strategy where the architecture clearly calls for it.
  • Engraving keypads with numbers instead of the room's real scenes — Welcome, Dinner, Film, Goodnight.
  • Treating lighting control as separate from the shade, AV and climate scenes that should fire together.

What to share before a quotation

  • Reflected ceiling plan and the lighting layout with fixture types and driver / dimming detail.
  • Circuit and panel zoning, and whether DALI, KNX or wireless is preferred.
  • The scenes and daily rhythm each space should support.
  • Whether shade, AV and climate need to join the same scene logic.
  • New-build or retrofit, and the keypad / app control preference.

/ Frequently asked

Lighting Automation — what buyers ask first.

Difference between dimming and lighting automation?

Dimming is a hardware function on a single fixture — a knob, a slider, a smart dimmer. Lighting automation is the control layer above it: scenes, schedules, sensors and inter-room logic. A dimmer changes one fixture; an automation system changes the entire room's character at one press.

Will lighting automation work with my existing fixtures?

Yes — if the fixtures use standard mains-dimmable, 0–10V, DALI or DMX drivers, lighting automation works with them as they are. Many premium decorative fixtures need a driver swap or a dedicated leading-edge dimmer — we audit every fixture during the survey and tell you upfront.

What is tunable-white lighting?

Tunable-white fixtures shift colour temperature on demand, typically 2200 K (warm candle-glow) to 6500 K (cool daylight). Paired with automation, the home brightens and cools through the morning and warms toward evening, mirroring the sun. The effect on circadian rhythm and the perceived warmth of a space is significant.

How many scenes should I plan for?

Programme 6–10 scenes per primary room for residential projects (Welcome, Day, Dinner, Film, Read, Goodnight is a complete starting set), and 4–6 named states for commercial spaces. We typically programme 6–10 scenes per primary room — Welcome, Day, Dinner, Film, Read, Goodnight is a complete starting set. Scenes beyond that count are rarely used in practice and clutter the keypad UX. For commercial spaces we keep scenes per zone to 4–6 named states.

Will tunable-white fixtures work with all dimmers?

No — tunable-white fixtures require DALI-2, dual-channel 0–10V or proprietary protocols (Rako Tunable, KNX dimming); standard mains dimmers cannot drive them. Tunable-white needs DALI-2, 0–10V dual-channel, or proprietary protocols (Rako Tunable, KNX dimming). Standard mains dimmers cannot drive tunable-white fixtures. We specify the driver, dimmer and fixture together at the design stage.

How does daylight harvesting work in practice?

Daylight harvesting uses perimeter lux sensors that dim artificial fixtures inversely as daylight rises, typically saving 20–35% on perimeter-zone lighting bills. Lux sensors mounted at the perimeter measure incident daylight; the controller dims the artificial fixtures inversely so the total illuminance at the work plane stays constant. Done well, occupants do not notice the change; the energy saving on a perimeter office zone runs 20–35% on the lighting bill.

Which lighting-control brands does TechnoGuru work with?

We work across the Rako, KNX and DALI ecosystems, with FutureKNX keypads and drivers, Fibaro and Nice devices where the project fits, and MADRIX or ProtoPixel controllers for dynamic and facade lighting. These are families we specify where suitable, matched to the scheme rather than fixed in advance. The final control topology is selected after the lighting layout, circuit schedule and driver type are reviewed against the drawings.

How are the keypad, dimmer and driver families chosen for a project?

The keypad, dimmer and driver are specified together against the load type — LED, tunable-white, mains, 0–10V or DALI — because a keypad is only as useful as the driver it commands. Rako and KNX keypads follow different wiring and scene conventions, so we match the family to the electrical layout rather than the brochure. Final make and model stay subject to project requirement, site conditions and availability.

How does lighting automation hand off to a hotel or GRMS platform?

In hospitality projects the room lighting integrates with the guest-room management system so check-in, welcome and do-not-disturb states drive the lighting scenes through a documented interface. KNX and DALI both bridge into common GRMS platforms, and the exact integration is designed against the property's chosen room-management system. Share the room drawings and the GRMS platform through /contact for a written scope.

· Begin

Begin a
lighting automation
brief.

Tell us about the building, the timeline, and what success looks like a year after handover. We will reply within two working days with a written response, not a sales pitch.