Skip to content
Website
🧱 CFC 238KNX home automation: topology, addressing and parameter settingChapter 5 of 10 in the section

Commissioning: download, room-by-room testing and defect list

By the end of this chapter, you will be able to structure the download of devices on the KNX bus, systematically track down wiring and addressing reversals channel by channel, and conduct rigorous joint testing room by room in order to record reservations on a signed defect list prior to handover of the work.

Key takeaways

  • The initial download requires strict verification of each individual address on the bus line.
  • Labelling errors between channels account for the overwhelming majority of malfunctions identified during acceptance inspections.
  • Joint testing is carried out locally in each room by physically operating every control unit.
  • The signed defect list protects the telematics technician and formally defines the remedial work to be performed.

Methodical downloading of devices and tracking channel reversals

Commissioning a KNX network begins with physically connecting the IP or USB programming interface to the main bus line. Before initiating the overall transfer of the database, the telematics technician checks for the presence of the nominal 29 V DC voltage supplied by the bus power supply. The download takes place in two very distinct stages in the engineering software: first the device's individual address by pressing the hardware programming button, then the application program containing the parameters and group address links. Any overwritten address or rushing into a full download without line diagnostics creates physical address conflicts that paralyse the bus.

  1. Line scanning and address checkingLaunch the software's diagnostic function to scan the line. No device present on the bus must respond under the default address 15.15.255.
  2. Individual download of applicationsInject the configuration device by device, starting with the modular actuators in the panel, and ending with the push-buttons and ambient room sensors.
  3. Validation of status feedbackCheck on the telegram monitor that each switching object transmits its respective binary status object to its dedicated group address.
  4. Verification of crossed channelsTrigger the actuator output by output and immediately mark any discrepancy between the physical terminal block and the identification label using a marker pen.

Room-by-room joint testing and formalisation of the defect list

Functional testing is not carried out behind a laptop screen resting on a cardboard box in a plant room. It requires a methodical walk-through room by room, preferably conducted in the presence of site management or the representative of the interior installations electrician. For each zone, the telematics technician physically tests every control point: short press, long press, dimming, raising and lowering motorised blinds, as well as recalling ambient scenes. Visual feedback on the switch LEDs must strictly match the actual status of the controlled lighting.

Functional checklist for room-by-room acceptance
Item testedPhysical action requiredExpected behaviourCommon anomaly
Lighting push-buttonShort press on upper buttonDirect activation of assigned circuit and LED illuminatedUpper and lower channel inverted or incorrect status feedback
Blind controlSustained press on down buttonFull downward travel of the blind curtainReversal of up and down phases on the terminal block
Bus presence detectorCrossing the detection zoneTransmission of time-delayed ON telegram with lux levelForced mode locked or zone masked by a luminaire
Departure scene buttonSingle press on centralised buttonAll-off switching and transition to standby modeOmission of a circuit from the all-off group address

As soon as a non-conformity appears, such as a blind moving up when the command requires it to move down, it is recorded immediately on the test report. Under art. 367 CO, after delivery, the employer must inspect the condition of the work as soon as feasible and give notice of defects to the contractor. The joint defect list, drawn up room by room, precisely lists the location, the number of the KNX device concerned, the erroneous address group, and the corrective action to be taken.

Tracking crossed channels and methodical reloading in ETS

On new-build construction sites or major refurbishments, the majority of malfunctions identified during initial testing are not caused by hardware failure, but by address or labelling reversals. When connecting multi-function actuators in distribution boards, an inversion between two adjacent output channels — for example channels C and D of a switching module — leads to controlling corridor lighting instead of the adjacent office. Similarly, on motorised blind actuators, physically inverting the up and down phase conductors results in behaviour opposite to the programmed setpoint. These errors render the installation inconsistent in the eyes of users and must be systematically cleared before any presentation to site management.

Locating these reversals is achieved by combining visual inspection with telegram traffic analysis using the ETS group monitor. The operator filters traffic on the affected group address, sends a manual command from the wall-mounted control unit, then simultaneously verifies the network acknowledgement and the physical state of the relay on the actuator. Once a crossover is identified, two approaches are available to the technician: rectify the physical connection on the actuator terminal block if the initial wire labelling was incorrect, or modify the link between the communication objects and group addresses in the ETS database. In the latter case, a partial download of the application parameters is sufficient to update the KNX device without resetting its entire filter table.

Diagnostics and correction of channel reversals on the KNX bus
Observed symptomBehaviour on ETS monitorRoot cause of the anomalyCorrective action
Office A push-button switches Office B zoneTelegram transmitted to the correct group addressOutput channels crossed on the modular actuatorSwap outgoing circuits on terminal block or reassign channels in ETS
Blind moves up when down button is pressedValue 1 transmitted on the 1-bit move objectPhysical reversal of up and down phases at terminal blockInvert direction of travel in the channel's ETS parameter
Button status LED does not change stateNo telegram transmitted by the status objectStatus feedback object disconnected from the group addressLink status output to group address and reload parameters
Corridor detector switches on WC lightingTransmitting individual address does not match layout drawingConfusion of physical labels between two detectorsActivate programming LED to locate and readdress the device

Joint testing procedure and list of reservations

Final validation of a home automation installation requires joint testing performed room by room, conducted jointly by the electrical installer and the representative of site management. This joint approach prevents any subsequent dispute regarding the operating condition of the controls. Under art. 367 al. 1bis CO, the employer has 60 days to give notice of defects in an immovable work. Carrying out this comprehensive test immediately upon completion eliminates functional defects before occupants move in and certifies the compliance of programmed scenes.

  1. Systematic verification of local controlsTest every push-button rocker, touch screen and presence detector in its respective room. Visually check that the controlled load responds promptly with the correct time delay and illumination level.
  2. Checking feedback signals and interlocksVerify consistency between button indicator lights and central monitoring status feedback. Test the behaviour of priority override commands, such as window reed contacts or the weather station.
  3. Formal recording and signing of the reportRecord every discrepancy in a standardised defect list indicating the room, the physical address of the component, the nature of the anomaly and the intervention deadline granted for rectification.

Once testing is complete, the defect list is jointly signed off by both parties. This document records responsibilities and schedules the corrective interventions required prior to final handover of the work to the client.

Managing technical disagreements and clearing test reservations

When joint testing reveals an abnormal rate of anomalies, the reflex of correcting group addresses on the fly in ETS must be avoided. Reassigning a communication object to compensate for a wire connected to the wrong actuator output masks the error without resolving it. This practice destroys the correspondence between the panel's wiring schematics and the project's software configuration. When faced with repeated reversals between lighting channels or blind circuits, the testing session must be suspended to record the actual baseline condition on site.

The report records each discrepancy identified per room, along with the physical terminal number and the observed behaviour. The signed defect list freezes the technical situation. Under art. 367 CO, after delivery, the employer must inspect the condition of the work and give notice of defects to the contractor. In the presence of site management, the document determines whether the failure stems from the physical wiring carried out upstream or from the parameterisation of the KNX devices. A precise deadline is set for rectification, without disorderly alterations to the project files.

Clearing reservations requires methodical remediation: physical tracing of misrouted conductors, updating the panel schematic, restoring hardware compliance, then partially reloading individual addresses and application parameters. Under art. 368 CO, the employer may demand the repair of the work in the event of defects. Once physical corrections are completed by the electrical installer, the telematics technician runs line diagnostics again via the ETS group monitor. A second joint visit is arranged, restricted to the open items on the reservation list. Final sign-off certifies functional compliance and releases the transfer of ownership of the installation.

Frequently asked questions

What should be done if a device does not respond during an ETS download?

Check the operating voltage across the red and black terminal block using a multimeter to confirm the presence of 29 V DC bus power. If the voltage is correct, pressing the programming button should illuminate the indicator LED. Failure to respond indicates an incorrectly addressed line coupler, inverted bus cable polarity, or an overly restrictive telegram filter blocking the download.

How can you distinguish a wiring reversal from incorrect KNX addressing?

Direct manual operation on the front face of the DIN actuator isolates the problem. If manual operation of channel A switches the kitchen light instead of the hall, the defect is purely wired in the panel. If manual operation switches the correct light but the wall button operates the wrong room, the error lies in the group address link table within ETS.

Who must sign the commissioning defect list?

The document must be signed by the KNX integrator responsible for parameterisation, the electrical installer who carried out the connections, and the representative of site management or the client. This joint formalisation protects the commissioning technician against claims relating to subsequent wiring modifications or unauthorised tampering by other trades on control units or actuators following acceptance.

How should a channel reversal corrected during testing be documented?

Any terminal swap executed during the session must be marked immediately in red on the paper working drawing located inside the electrical enclosure. The integrator updates the text descriptions of objects and channels in the ETS project. The test report notes the modification made and makes final validation conditional upon delivery of the as-built revised schematic for the building documentation.

Texts and standards cited

  • CO art. 367inspection of the work and notice of defects by the client
  • CO art. 368client's rights in the event of defects in the work (rejection, price reduction, repair, damages)

In the same section