Niko One is Belgium's premium KNX switch range — sold across Benelux, France and exported to international projects wherever architects specify tactile, minimalist switch finishes alongside professional KNX functionality. Unlike some manufacturers that offer a basic push-button with minimal ETS6 parameters, Niko One switches carry a full ETS6 application with action table, scene recall, LED feedback, and multi-function inputs. This guide covers installation, ETS6 programming, and best-practice configurations for a typical office or residential project.

Niko One hardware anatomy

The Niko One switch consists of two parts: the Niko One module (KNX TP bus coupler + electronics, snaps into any standard 45×45mm frame cutout) and the Niko One frame (available in glass, stainless, or Perspex — multiple finishes). The module connects to the KNX TP bus via YCYM cable (KNX standard: 29V DC SELV). The module has 2 or 4 push-button inputs (depending on SKU) and 2 or 4 associated LED feedback indicators. Physical addressing: programmed in ETS6 via the KNX programming button on the module — press button, ETS6 sends individual address. No tools required for frame removal: Niko One frames clip onto the module.

ETS6 application import and product database

Niko provides a KNX product database downloadable from niko.eu (Products > KNX > ETS product files). Import via ETS6: Settings > Import OPC > select Niko .knxprod file > Import. Once imported, Niko One modules appear under Niko in the ETS6 catalogue. Product families: 550-00xxx (2-button, 2 LED), 550-00xxx (4-button, 4 LED). Add to ETS6 project: drag module from catalogue into topology > line > click to place on group addresses. Note: Niko One modules require ETS6 version 6.0 or later for full DPT support.

Push-button action table configuration

The core of Niko One ETS6 programming is the action table — each button has 8 configurable actions triggered by: short press, long press, short press + release, long press + release, double press, and cyclic repeat. In ETS6 Parameters tab > Button 1 > Action 1 (Short Press): select function: Switch (DPT 1.001) → link to GA 1/1/0 (Office Lights On/Off). Action 2 (Long Press): function: Dimming (DPT 3.007 4-bit) → GA 1/1/1 (Office Lights Dim). Action 1 sends value 1 (on) on press. Toggle mode: enable Toggle in Parameters > Button 1 > Toggle = Yes — each short press alternates between 1 and 0 on GA 1/1/0. For a presence-override button: Action 1 (Short Press) → value object → GA 1/4/0 (Presence override, DPT 1.001). Long press action for dimming: send start-dimming on long press press, stop-dimming on long press release.

Scene recall configuration

KNX scenes stored in actuators (switch actuators, dimmer actuators) are recalled via DPT 18.001 telegrams. Niko One scene configuration in ETS6: Parameters > Button 3 > Function = Scene. Scene number = 1 (0-indexed: scene 1 = value 1 in DPT 18.001). GA for scene recall: 1/5/0 (Office Scene Recall). Learn mode: enable "Allow scene learn on long press" — long press stores current actuator states into the scene memory. Multiple scene buttons: Button 3 = Scene 1 (Presentation), Button 4 = Scene 2 (Meeting), use separate GAs per scene or shared GA with different scene numbers. Ensure actuator channel parameters also have scene enabled with matching scene number.

LED feedback programming

Niko One LED indicators show the status of the linked group object. LED configuration in ETS6 Parameters > LED 1: mode = Status (reflects GA status), link to feedback GA (e.g., 1/1/2 — dimmer actuator status feedback). LED brightness: adjustable 0–100% in Parameters > LED Brightness. LED colour: Niko One standard LEDs are red/green dual — active = green, inactive = red or off. Night mode: LED dimmed 30% automatically after 23:00 via internal time logic (NTP or KNX time telegram from router). Alarm LED mode: Parameters > LED 1 > Flash on value 1 — LED flashes if linked GA sends 1 (e.g., burglar alarm active).

Niko Home Control+ bridge for residential apps

In residential projects where the homeowner wants a smartphone app but the building has KNX: specify the Niko Home Control+ (NHC+) system alongside standard KNX. NHC+ uses its own proprietary bus (same YCYM cable), but the NHC+ Connected Controller has a built-in KNX TP interface. Configuration: NHC+ app > Devices > KNX bridge > assign KNX group addresses to NHC+ actions. Example: KNX GA 1/1/0 (lights) → NHC+ "Living Room Light" → visible in NHC+ iOS/Android app. This gives the homeowner a polished app experience while the installer retains full ETS6 control over actuators. Limitation: NHC+ to KNX bridge supports max 256 KNX group addresses — sufficient for typical residential.

Commissioning sequence for a 20-switch floor

Typical office floor with 20 Niko One 4-button switches: (1) Mount modules in back boxes, connect KNX YCYM bus chain. (2) Download Niko .knxprod to ETS6. (3) Create topology: Line 1.1 — add all 20 modules. (4) Individual address assignment: walk the floor, press each module's programming button, ETS6 assigns address 1.1.1 through 1.1.20. (5) Parameter setup: use ETS6 template device (configure one module completely), then Copy > Paste (Properties Only) to remaining 19 devices — adjust only the specific GAs that differ per room. (6) Group address assignment: link to pre-built GA structure (functional 3-level format: 1/room/function). (7) Download: select all 20 devices > Download > Full Device Configuration. (8) Test: walk floor, verify each button action and LED feedback. Total commissioning time: experienced engineer, 4 hours.