KNX.

ORG

Smart home and building solutions.

Global. Secure. Connected.

KNX
PROJECT PREPARATION
 KNX.ORG

CONTENT
KNX Project Preperation

KNX Project design guidelines

4 Structured Realisation of KNX Projects

Checklists

16 Implementing an eletrical installation

with KNX

20 Supplementary sheet
for other possible applications

25 Handover of an eletrical installation

with KNX

28 Increased security and privacy

in KNX installations

Content | KNX Project Preparation | 3

 Smart home and building solutions. Global. Secure. Connected.

KNX PROJECT
DESIGN GUIDELINES
Structured Realisation of KNX Projects

General
The “KNX Project Design Guidelines” intend to
assist KNX Partners to realise KNX projects in a
proper and structured manner. They are meant to
complement the “KNX Project Checklists”, which
concentrate on the project handling starting from
the identification of the customer requirements up
to the handover. KNX has elaborated these “KNX
Project Guidelines” in order to make the realisation
of KNX projects easier for all companies involved.

More Success
with a simple Structure Notes
Properly structuring a KNX Project is an important The content of this document
element in its eventual successful realisation. is mainly the result of many
Configuring the topology and the address scheme years of experience of KNX
according to a suitable structure is essential to be system integrators realising
able to finally hand over a properly functioning KNX projects with the aim to
installation to the customer. These “KNX Project install for their customers an
Guidelines” contain important basic information optimised, error free and ener-
and ideas for successful project design. gy efficient system. This docu-
ment has been worked out by
a KNX project team consisting
Users of these Guidelines
of training centres and system
The „KNX Project Guidelines“ are meant to com-
integrators. The information
plement the “KNX Project Checklists”. Amongst
and specification published
others they lend a helping hand to the below listed
in this document has been
companies in their daily work with KNX:
compiled to the best of knowl-
• Consulting engineers as a basis for the call for
edge. Errors and technical
tenders and as guidelines for the realisation of
alterations are reserved. KNX
projects
does not take responsibility
• Beginners as a basis for company-internal struc-
for the practical application of
turing of KNX Projects
these guidelines. Alterations
• Experienced integrators as an improvement and
and suggestions are welcome
a complement to their own project guidelines
via info@knx.org.
• Training centres for the integration into their
training documents
Note to trademarks
• KNX Certified training centers as supplementary
KNX and the KNX Partner-Lo-
information to the official training documents
go are registered trademarks
KNX wishes all partners involved in KNX Projects
of KNX Association Brussels.
lots of success and happy project designing!

4 | KNX Project Design Guidelines | Structured Realisation of KNX Projects

 KNX.ORG

Physical Topology Topology in Practice

In the same way as major construction projects are In major projects where 16 lines (15 lines and 1 main
subdivided in areas, buildings, floors and rooms, line) are insufficient or when required by the build-
the physical structure of a bus system needs to ing structure, lines are extended by areas. In a sin-
be organised accordingly. The more similar these gle family house (SFH) one line might be sufficient
structures can be made, the easier and clearer will either per floor or even for the entire building. In
be the project design and the programming. commercial buildings one area should be foreseen
per floor and one line per energy zone, even if not
It is recommended – in case of doubt – to foresee all areas contain the maximum number of 15 lines.
an additional line, if this improves the clear ar-
rangement of the project structure.
Examples of Topologies
Area 1: Building
Segmentation in Areas and Lines Main Line Staircase (Devices 1.0.xxx)
Line 1 Basement (Devices 1.1.xxx)
Number of possible areas and lines Line 2 Ground floor (Devices 1.2.xxx)
As it is well known, a KNX project can contain up Line 3 First floor (Devices 1.3.xxx)
to 15 areas. Per area again up to 16 lines (15 lines
Example: Topology SFH with only a few devices
and one main line) can be defined. Areas, respec-
tively lines are electrically isolated from each other
by a coupler. Therefore, each line, respectively each
segment of a line needs its own power supply.
Hence, the correct number of power supplies in a Area Line (Devices 0.0.xxx)
project is: number of line couplers + 1.

According to the KNX standard, the topology is Area 1: (North Building) Basement
structured in: Main Line (Devices 1.0.xxx)
• lines (always 1 – 15) Line 1 Energy zone 1 (Devices 1.1.xxx)
• main line (connects the corresponding Line 2 Energy zone 2 (Devices 1.2.xxx)
line couplers) Line 3 Energy zone 3 (Devices 1.3.xxx)
• area line (connects the corresponding Line 4 Energy zone 4 (Devices 1.4.xxx)
area couplers), in practice this line is often ...
referred to as the “backbone”. ...
Line 11 General corridors (Devices 1.11.xxx)
north
Line 12 General corridors (Devices 1.12.xxx)
south
Backbone Line Area n
BC n
Area 2: (South Building) Ground floor
BC 2
Area 2
Main Line (Devices 2.0.xxx)
Power supply with choke
LC 1 LC 15 Line 1 Energy zone 1 (Devices 2.1.xxx)
Area 1
BC 1 Line 2 Energy zone 2 (Devices 2.2.xxx)
Power supply Power supply Main LinePower supply
with choke
LC 1
with choke LC 15
with choke Line 3 Energy zone 3 (Devices 2.3.xxx)
...
Power supply Power supply
LC 1
with choke LC 15
with choke ...
Device 1 Device 1
Line 11 General corridors (Devices 2.11.xxx)
Power supply Power supply
with choke with choke north
Device 1 Device 1
Line 12 General corridors (Devices 2.12.xxx)
Device 63 Device 63
south
Device 1 Device 1

Line 1 Line 63
Device 63 Device 63
Area 3: (Shop floor)
Line 1 Line 63 Main Line (Devices 3.0.xxx)
Device 63 Device 63
Line 1 Energy zone 1 (Devices 3.1.xxx)
Line 1 Line 63 Line 2 Energy zone 2 (Devices 3.2.xxx)
... etc.
KNX Topology
LC: Line coupler | BC: Backbone coupler Example: Topology Commercial Building

Structured Realisation of KNX Projects | KNX Project Design Guidelines | 5

 Smart home and building solutions. Global. Secure. Connected.

Number of devices
As a general rule, per area and line (segment of a line) a maximum of
64 devices can be installed. As a result, the required output current of
the power supply usually is 640 mA.
However when designing a project, sufficient reserves should be
foreseen. While designing the installation, the number of devices in a
line should not exceed 60 % of the maximum possible number in com-
mercial buildings and 90 % in residential buildings. The exact power
consumption of the individual devices and consequently the resulting
maximum number of devices per area / line (segment) can be derived
from the technical product data as supplied by the manufacturers of
the devices.

Device 1 Device Device 64

Device

Line with
Line
Device maximum 64 devices

Power supply
Device
with choke

Device Device Device

Individual Addresses
Theoretically, the Individual Addresses of the
individual bus devices in a line could be assigned
without any structure. In order to improve the
overall overview, KNX recommends the creation of
an address structure that is adapted to the project,
when assigning addresses.

Example: Address Assignment

The following example should be understood as a
proposal that always needs to be adapted to the
realities of the actual project.

Possible Structuring
1.1 0 Line coupler
of the Individual Addresses
1.1 1
Depending on the number of actuators to be in- ... Actuators in the
stalled in the distribution board, the address range distribution board
20
can be segmented as shown below. Yet the shown
1.1 21
structure is only suited for smaller projects. ... Sensors
The individual areas should be designed with a 40
margin, to have the possibility to insert further de- 1.1 41
vices at a later stage. The following example shows ... ...
62
a possible assignment of addresses, as it could be
realised depending on the type of project at hand 1.1 255 e. g. USB-Interface
for programming
and the number of actuators.

6 | KNX Project Design Guidelines | Structured Realisation of KNX Projects

 KNX.ORG

Principal Scheme of the Documentation

Especially in case of larger projects, when starting the split-up and
structuring of the installation (as regards topology, areas and lines), a
principal scheme shall be designed. This ensures an optimum design
of the topology of a KNX installation and in this way the logical struc-
ture can be realised rather fast. Later the scheme helps to get a quick
overview during the commissioning stage of the system or when doing
maintenance. The principle scheme is therefore always part of the
documentation handed over to the customer after the completion of
the project.

Example: Principle Scheme

Area- / Line Coupler classic

Line 1.5 1.5.0 2.5.0 Line 2.5

LC Floor 5 LC

Line 1.4 1.4.0 2.4.0 Line 2.4

LC Floor 4 LC

Classical topology
Line 1.3 1.3.0 2.3.0 Line 2.3
Main line 2.0
Main line 1.0

with line and

LC Floor 3 LC
area couplers
KNX Topology based
Line 1.2 1.2.0 2.2.0 Line 2.2 on Twisted Pair
LC Floor 2 LC

Line 1.1 1.1.0 2.1.0 Line 2.1

LC Floor 1 LC

Area 1 Backbone line 0.0 Area 2

West wing BC BC East wing
1.0.0 2.0.0

IP Router as Line coupler

Line 1.5 1.5.0 2.5.0 Line 2.5

Floor 5

Line 1.4 1.4.0 2.4.0 Line 2.4

Floor 4

Line 1.3 1.3.0 2.3.0 Line 2.3 Topology with IP

Floor 3 couplers
KNX Topology based
on IP
Line 1.2 1.2.0 2.2.0 Line 2.2
Floor 2

Line 1.1 1.1.0 2.1.0 Line 2.1

Floor 1

Area 1 Network (LAN) Area 2

West wing East wing

Structured Realisation of KNX Projects | KNX Project Design Guidelines | 7

 Smart home and building solutions. Global. Secure. Connected.

Labelling Concept Identifiers for trades and functions

It is important that all parties involved in a project as first element
use common terms and have in mind the same KNX has defined the following identifiers for
meaning of these terms. The easiest way to do functions and trades. The list can be amended if
so is to have a common labelling concept. The required. In addition, the table lists the recom-
concept below proved its worth in practice and mended number of Group Addresses.
is therefore recommended by KNX. This standard
concept has the additional advantage that all
Id. Function Number
involved parties can easily understand the project
Group Address
even if they did not originally design the project
AM Alarm-Magnetic 5
themselves. A label as recommended by KNX is
contact (Collective
composed of the following elements: alarm / Alarm system)
• Label for trades and functions
AW Awning 5
• Room number
B Blind 5 / 10
• Consecutive number
C Curtain 5
These elements result a unique identifier, of which CL Clocks 5
an example is shown below:
BL Beamer 5
(projector)-Lift
«LD_E05_01»
DC Door contact 5
This label should now be used by default in: DMX DMX 5
• the installation plan E Energy meters 10
• for the electric circuit diagram and monitoring
• for ETS project design F Fans 5
The detailed format of this label is described in the
FS Fly screens 5
following pages.
G Garage door 5
(doors in general)
GB Gong / Bell 5
H Heating 5
HP Heat pump 10
IR Irrigation 5
L Lighting 5
LC Locking contact 5
LD Lighting dimmable 5
LDA Lighting dimmable 5
DALI
MM Multimedia 5
P Pump 5
PS Projection screen 5
RL Roof light 5
S Socket-outlet 5
SD Socket-outlet 5
dimmable (attention)
SH Shutter 5 / 10*
TS Temperature sensor 5
TVL TV lift 5
W Windows 5
WK Window contacts 5
WS Weather station 10

* Further information can be found on page 11:

Structuring of Group Addresses

8 | KNX Project Design Guidelines | Structured Realisation of KNX Projects

 KNX.ORG

Room numbers Consecutive number

as second element of the label as third element of the label
Each room requires its own unique number. If A consecutive number forms the third part of the
numbers have already been assigned to rooms, label. It is allocated to the electrical appliances per
these numbers can be taken over. The room num- room.
bers shall appear in the floor plan and have to be • This number starts in each room with 01,
agreed upon with the architect and if necessary • and starts again with 01 for each trade.
with further design experts. • Alternatively it can be counted up further for
other trades within the room (not shown in the
example below).

B 02 B 01 B 01

B 01
01 E02 E03 E04 E05

01 01 01
02

01 02

E05
01
B 03
02 E01 02
01

01 01
03 E07
B 01

Installation plan without room numbers (initial situation) Floor plan with consecutive numbers for each trade

Example of an Identification Label

Below a labelling example in accordance with the
E02 E03 E04 E05
KNX recommendation for the entrance area (ceil-
ing lamp in room E05).

B J_E02_02 B J_E03_01 B J_E04_01

B S_E03_01
J_E02_01 E02 E03 E04 E05

E05
E01 LD_E02_01 L_E03_01 L_E04_01

L_E02_02

S_E02_01 L_E05_02

E07

LD_E01_01
E05
B E01 LD_E05_03
Installation plan with allocated room numbers J_E01_02 L_E01_02 LD_E05_01

LD_E01_01
L_E07_01
L_E01_03 E07
B J_E01_01

LD_E05_01
Installation plan
Designation
of the function Electric circuit
diagram
Designation
of the floor / room ETS
(with additional info)
Consecutive number

Definition of the identification label

Structured Realisation of KNX Projects | KNX Project Design Guidelines | 9

 Smart home and building solutions. Global. Secure. Connected.

Final Example: Identification Concept Structures in ETS

Below the final labelling example in accordance
with the KNX-recommendation for the given plan.
Topology in ETS and in the Project
If a project is well structured, the topology cor-
responds – as mentioned earlier in this document –
B J_E02_02 B J_E03_01 B J_E04_01
more or less to the logical structure of the building,
B S_E03_01 such as e. g. to floors, energy zones etc.
J_E02_01 E02 E03 E04 E05
Building structure in ETS
LD_E02_01 L_E03_01 L_E04_01 The building structure in ETS is helpful for the ori-
L_E02_02 entation in the building. Push buttons and further
elements are placed into the corresponding rooms
S_E02_01 L_E05_02
or distribution boards. The building view is a sort
of filter, it does not influence the allocation of
LD_E01_01
E05 devices within the topology, but simplifies finding
B E01 LD_E05_03 devices in the project.
J_E01_02 L_E01_02 LD_E05_01

Labelling in ETS
LD_E01_01
L_E07_01
A further important chapter is the proper label-
L_E01_03 E07
ling in ETS. A lot of installers believe that proper
B J_E01_01
labelling of Group Addresses and devices just con-
stitutes a lot of unnecessary work. This is not the
case, as one can easily get lost in a project without
Additional Marking in ETS
proper labelling. The time invested when starting
When labelling Group Addresses in ETS it may be
the project will pay off many times even up to the
useful to add to the label the real room name and
stage where the project is finally commissioned.
if applicable the switching group (in brackets). This
How this is professionally done is shown below.
helps especially in smaller projects to improve the
overview. Project Properties
Example: Labelling of the group address in ETS When starting work, the most important entries
LD_E05_01 (entrance ceiling) in ETS are at least the project name and – if ap-
plicable – the internal project number. The date
will automatically be created when opening a new
project.
Reference to manual control elements
It definitely makes sense to describe the individual Function of the Project Log
push buttons and their functions in a separate The project log that appears when closing ETS
„room book“. The reference to this external docu- should always be active and kept up to date. It
ment can be made directly by means of the Indi- shows who did what and when as well as what
vidual Address or – if not yet defined – by means is the latest current version. If the project log is
of a position number especially created for this properly kept up to date, it will later help evaluate
purpose. Example: “E05-01” means, room 05 – more easily when and by whom changes and / or
consecutive number. amendments were made.

Labelling of the Group Objects

B J_E02_02 B J_E03_01 B J_E04_01
In practice it is recommended to assign a label to
B S_E03_01 the individual channels (the first Group Object)
J_E02_01 E02 E03 E04 E05
of sensors and actuators. How to proceed: When
a Group Object is selected in ETS, by clicking the
LD_E02_01 L_E03_01 L_E04_01
right mouse button the name of the sending group
L_E02_02
address can be taken over for this object. Alter-
S_E02_01 L_E05_02 natively this assignment can be done for a whole
line. After the allocation of Group Addresses within
E05
a line  select this line  determine the object
LD_E01_01
description by  selection of the sending group
B E01 LD_E05_03
J_E01_02 L_E01_02 LD_E05_01 address  all the addresses will be taken over.

LD_E01_01
L_E07_01
L_E01_03 E07 E05_01
B J_E01_01
Individual Address or
Example for the corridor Individual position number
with an individual position number

10 | KNX Project Design Guidelines | Structured Realisation of KNX Projects

 KNX.ORG

Structuring of Group Addresses Naming of the Function of Group Addresses

To ensure that the function of each single group
Main Groups address is clearly defined, the following naming
Generally main group 0 respectively 14 or 15 are scheme shall be used. Depending on the installed
allocated to central Group Addresses. In total up to devices respectively the needed Group Addresses
32 main groups (0 – 31) can be allocated. Attention this naming scheme can slightly deviate from the
has to be paid to possible restrictions in case of underneath recommendation.
line couplers, area couplers, plug-ins and gateways.

Main group 0 Central addresses ON / OFF Switch ON / OFF

Main group 1 Basement DIM Dim UP / DOWN
Main group 2 Ground Floor VALUE Control brightness
value
Main group 3 1. Floor
FB Status feedback
Main group 4 2. Floor (ON / OFF)
Main group 5 3. Floor FB VALUE Status feedback
... etc. (Object Value)

Identifiers for the function Light

Group Addresses UP / DOWN Move blind UP

Structuring the Group Addresses is an important and DOWN
task. Here again it makes sense to organise the STOP or Stop blind
addresses according to a very clear pattern. There SLATS
are two possibilities to realise this: the two level POSITION Control height
structure and the three level structure. HEIGHT of blinds
POSITION Control position
Two Level Structure of Group Addresses SLATS of slats
If there are more than 50 lighting groups or more
SHADING Control position
than 25 blind groups per floor, Group Addresses for shading
can be created according the 2-level-structure of-
BLOCK Block local manual
fered by the ETS. Accordingly, the sub groups have operation
to be segmented in a structured way. The segmen- STATUS Status feedback
tation and grouping has to be aligned with the POSITION height of blinds
project and the used functions. It is an advantage HEIGHT
to foresee packets of five and / or ten per luminaire, STATUS Status feedback slats
element, blind, heating, alarm etc. The segmenta- POSITION
SLATS
tion can be made similar to the structure of 3-level
Group Addresses described below. The difference Identifiers for the Function Blind
is that the Middle Group does not exist but allows
the sub group address to exceed 255, i. e. it can be
between 0 – 2047. The address 0 / 0 is a system ad- CONTROL Control value
VALUE for valve
dress and cannot be allocated. (ON / OFF or value)

Three Level Structure of Group Addresses CURRENT Current temperature

TEMP value
In case of three level Group Addresses, a corre-
sponding Middle Group is available between 0 – 7 BASIC Basic set-point
SETPOINT
that can also be used for segmentation. The three
level group address structure allows sub groups FB Feedback
between 0 – 255. Entries with higher numbers than FB Feedback
255 are not possible. The address 0/0/0 is a sys- CURRENT of current set-point
SETPOINT
tem address and cannot be allocated.
KNX recommends using the tree level structure for FAULT Fault
smaller projects. This can look like is shown below. STATUS Operation mode
OPERATION of controller
MODE
BLOCK Block manual
operation

Identifiers for the Function Heating

Structured Realisation of KNX Projects | KNX Project Design Guidelines | 11

 Smart home and building solutions. Global. Secure. Connected.

Detailed information Structure of the subgroups for lighting

to the three level Group Addresses The functions of each switching group shall be
segmented in blocks of 5 in order to have always
Definition and Segmentation
the same structure for a lighting group. Objects
of the Middle Group
that are not used are either left empty or a dummy
For trades like lighting, awnings, blinds but also for group address is attributed, in order to cater for
heating different Group Addresses are required. special functions requiring individual solutions.
Favorably, these are segmented by means of the
Middle Group. Below you will find a list of the most Example:
important trades. Further trades can be added at Structure of the subgroups for lighting
any time according to the pattern below. According to the segmentation described above
The KNX Project Design Guidelines offer two alter- two alternatives for the structuring of Group
natives for the segmentation of Middle Groups: Addresses are possible.

Middle Alternative Alternative

Group A B

0 Lighting Lighting
incl. feedback
Middle Group 0
1/0/0 ON / OFF
1/0/1 DIM
1/0/2 VALUE
1/0/3 FB
1 Blinds Blinds
incl. feedback 1/0/4 FB VALUE

1/0/5 ON / OFF
1/0/6 DIM
1/0/7 VALUE
2 Heating / HVAC Heating / HVAC 1/0/8 FB
1/0/9 FB VALUE

1/0/10 ON / OFF
...
3 Alarm Alarm ...

Alternative A:
Status feedback integrated in the same Middle Group

4 General General

Middle Group 0 Middle Group 6:

Status feedback
5 ... ...
1/0/0 ON / OFF 1/6/0 ON / OFF
6 Lighting Feedback*
1/0/1 DIM 1/6/1
1/0/2 VALUE 1/6/2 VALUE
1/0/3 1/6/3
1/0/4 1/6/4

7 Blinds Feedback* 1/0/5 ON / OFF 1/6/5 ON / OFF

1/0/6 DIM 1/6/6
1/0/7 VALUE 1/6/7 VALUE
1/0/8 1/6/8
1/0/9 1/6/9
*) The sub group address of the status
1/0/10 ON / OFF 1/6/10 ON / OFF
feedback for the Middle Groups 6 and 7
complies for each function always with ... ...
the same sub group address of the ... ...
switching group (in case of lighting
e. g. Middle Group 0). Alternative B:
For details refer to the examples below. Status feedback Middle Group 6 for lighting

12 | KNX Project Design Guidelines | Structured Realisation of KNX Projects

 KNX.ORG

Structure of the Subgroups for Blinds Example for subgroups Heating

As in the case of blinds etc. other functions are Because of the needed connections, KNX does not
required than in the case of light, other identifiers suggest a second alternative for heating.
are needed. Moreover, more Group Addresses are KNX recommends a segmentation in blocks of 10.
needed for more complex blind controls. KNX rec-
ommends for blinds a segmentation in blocks of 10.

Middle Group 2
1/2/0 CONTROL VALUE
(ON / OFF or value)
Middle Group 1 1/2/1 CURRENT VALUE (Temperature)
1/1/0 UP / DOWN 1/2/2 BASIC-SETPOINT
1/1/1 STOP 1/2/3 FB
1/1/2 POSITION HEIGHT 1/2/4 FB CURRENT SETPOINT
1/1/3 POSITION SLATS 1/2/5 ...
1/1/4 SHADING 1/2/6 ...
1/1/5 BLOCK 1/2/7 ...
1/1/6 STATUS POSITION HEIGHT 1/2/8 ...
1/1/7 STATUS POSITION SLATS 1/2/9 STATUS OPERATION MODE
1/1/8 ...
1/2/10 CONTROL VALUE
1/1/9 ... (ON / OFF or value)
1/1/10 UP / DOWN 1/2/11 CURRENT VALUE (Temperature)
1/1/11 STOP 1/2/12 BASIC-SETPOINT
1/1/12 POSITION HEIGHT 1/2/13 FB
1/1/13 POSITION SLATS 1/2/14 FB CURRENT SETPOINT
1/2/15 ...
1/1/14 ...
1/2/16 ...
Alternative A: ...
1/2/17
Status feedback part of the same Middle Group
1/2/18 ...
1/2/19 STATUS OPERATION MODE

1/2/20 CONTROL VALUE

(ON / OFF or value)
... ...

Middle Group 1 Middle Group 7:

Status feedback
Alternative Numbering
1/1/0 UP/DOWN 1/7/0 ...
for Subgroups starting with 1
1/1/1 STOP 1/7/1 ...
All examples above start with subgroup 0.
1/1/2 POSITION 1/7/2 POSITION
HEIGHT HEIGHT Alternatively it is also possible to start
1/1/3 POSITION 1/7/3 POSITION with subgroup 1.
SLATS SLATS
1/1/4 SHADING 1/7/4 ... Middle Group 0
1/1/5 BLOCK 1/7/5 ... 1/0/1 ON / OFF
1/1/6 ... 1/7/6 ... 1/0/2 DIM
1/1/7 ... 1/7/7 ... 1/0/3 VALUE
1/1/8 ... 1/7/8 ... 1/0/4 FB
1/1/9 ... 1/7/9 ... 1/0/5 FB VALUE

1/1/10 UP/DOWN 1/7/10 ... 1/0/6 ON / OFF

1/1/11 STOP 1/7/11 ... 1/0/7 DIM
1/1/12 POSITION 1/7/12 POSITION 1/0/8 VALUE
HEIGHT HEIGHT
1/0/9 FB
1/1/13 POSITION 1/7/13 POSITION
1/0/10 FB VALUE
SLATS SLATS
1/1/14 ... 1/7/14 ... 1/0/11 ...
Alternative B:
Status feedback as Middle Group 7

Structured Realisation of KNX Projects | KNX Project Design Guidelines | 13

 Smart home and building solutions. Global. Secure. Connected.

Marking of Group Addresses

Marking examples for the different Functions

According to the two rules mentioned above
(label and function) it is now possible to create a
well arranged and unique marking of the Group
Addresses.

Example: Lighting Example: Blinds

Below is an example of the detailed marking of Below an example of the detailed marking
Group Addresses for the lighting in the bedroom of Group Addresses for the blinds in the bedroom
based on the structuring according based on the structuring according to alternative
to alternative A. A. Alternative B can be realised in an analogue way.

Middle Group 0 Middle Group 1

1/0/0 LD_E01_01 ON / OFF 1/1/0 B_E01_01 UP / DOWN
(Bedroom ceiling) (Bedroom entrance side)
1/0/1 LD_E01_01 DIM 1/1/1 B_E01_01 STOP
1/0/2 LD_E01_01 VALUE 1/1/2 B_E01_01 POSITION HEIGHT
1/0/3 LD_E01_01 FB 1/1/3 B_E01_01 POSITION SLATS
1/0/4 LD_E01_01 FB VALUE 1/1/4 B_E01_01 SHADING
1/1/5 B_E01_01 BLOCK
1/0/5 L_E01_02 ON / OFF
(Bedroom wall left side) 1/1/6 B_E01_01 STATUS POSITION HEIGHT
1/0/6 ... 1/1/7 B_E01_01 STATUS POSITION SLATS
1/0/7 ... 1/1/8 ...
1/0/8 L_E01_02 FB 1/1/9 ...
1/0/9 ...
1/1/10 B_E01_02 UP / DOWN
(Bedroom garden side)
1/0/10 L_E01_03 ON / OFF
(Bedroom wall right side) 1/1/11 B_E01_02 STOP
1/0/11 1/1/12 B_E01_02 POSITION HEIGHT
1/0/12 1/1/13 B_E01_02 POSITION SLATS
1/0/13 L_E01_03 FB 1/1/14 B_E01_02 SHADING
1/0/14 1/1/15 B_E01_02 BLOCK
... 1/1/16 B_E01_02 STATUS POSITION HEIGHT
1/0/20 LD_E02_01 ON / OFF 1/1/17 B_E01_02 STATUS POSITION SLATS
(Children’s room ceiling)
1/1/18 ...
1/0/21 LD_E02_01 DIM
1/1/19 ...
1/0/22 LD_E02_01 VALUE
1/0/23 LD_E02_01 FB 1/1/20 B_E02_01 UP / DOWN
(Children’s room garden side)
1/0/24 LD_E02_01 FB VALUE
... ...
1/0/25 L_E02_02 ON / OFF
(Children’s room wall)

14 | KNX Project Design Guidelines | Structured Realisation of KNX Projects

 KNX.ORG

Project Documentation
The documentation of a KNX project comprises
of the following items:

Documents
All documents have to be placed in an indexed folder:
• Principle scheme of the facilities
• Revised electric scheme
• Revised electric plan
• Revised room book
• List of companies, responsibilities
• System specification, customer requirements
if applicable
• Acceptance certificate
• Possible test certificate (e. g. calibration of the room
thermostat)
• Report of the hand-over to the customer
• Description of logic functions and further details
• Manual/technical documentation of the installed
components
• Own documents that could be helpful later on for the
maintenance of the system

Software and legal aspects Additional Benefits

for Everyone
If requested by the customer, the software respectively
If anything should have been
the project data (not the ETS Software itself) should be
forgotten in this document
handed over, thereby taking into account all applicable
or if anything does not corre-
security measures.
spond anymore to best prac-
• Project data created by the current ETS Software
tice, handling or your ideas,
version
please inform us. As KNX we
• Project data of other used hardware (e. g. visualisation)
would like to keep on improv-
• Plug-ins and software of special devices that cannot be
ing this document, always with
programmed directly by means of the ETS.
the objective to sustainably
Guarantee after handing over the software optimise and improve the re-
When handing over the software, the integrator may alisation of KNX projects.
make additional arrangements with the customer settling For inputs please use
the issue of guarantee. the E-mail address
info@knx.org.
Backup
Moreover it lies within the responsibility of the system Contributors
integrator to ensure that the customer can access the The following companies and
current project data if requested. The integrator has to certified training centers have
take special care that the created project data and all participated in the creation of
other related data are securely archived by him. this document:
• Baumann Koelliker AG,
Taking over Software from another Integrator
Urs Zimmermann
In practice it may happen that a project is handed over
• EIBROM GmbH,
from one integrator to another. It shall be assured that
Jürg Keller
the software is transferred from one integrator to the
• Feller AG,
other exclusively via the building owner / customer.
Beat Bebi
To allow “the new integrator” to continue the project as
• raum consulting,
desired by the customer, the “old integrator” is obliged
René Senn
to hand over the very latest version of the project data to
• Höhere Berufsbildung BMP,
the customer. The “new integrator” has to check the soft-
Christoph Widler
ware for completeness immediately after the reception.
• Siemens Schweiz AG,
Always pay attention to preserve the reputation of KNX:
Bernhard Frei
KNX is an open bus system and exactly that is its asset.

Structured Realisation of KNX Projects | KNX Project Design Guidelines | 15

 Smart home and building solutions. Global. Secure. Connected.

CHECKLIST
Implementing an eletrical installation with KNX

Project: Distribution board:

Project no.: Date:

Distribution board:

1. Your question Customer response

What does your customer want their
living space to be like?

For your customer, what are the most

important characteristics that a house
should have?

Who will be living in the property?

Give your customer a little homework

to do: how will the rooms be used,
and by whom?

Basement:

Storeroom

Hobby / Craft room

Utility room

Laundry

Gym

Corridor

Garage

Only once your customers are clear about how their various rooms are to be used will you be
able to offer them an effective, intelligent building automation system.

Examples:
Storeroom Motion sensor
Hobby room Vacuum cleaner
Gym Air conditioning + air quality
Laundry Leak alarm
Conservatory Shading, ventilation, temperature control

16 | Checklist | Implementing an eletrical installation with KNX

 KNX.ORG

Ground Floor:

Hallway / Corridor

Downstairs toilet

Kitchen

Dining room

Living room

Lounge

Conservatory

Terrace

First floor:

Corridor

Bathroom

Children‘s bedroom 1

Children‘s bedroom 2

Children‘s bedroom 3

Playroom

Master bedroom

Walk-in wardrobe

Balcony

Attic floor:

Studio

Gallery

Room 1, 2, etc.

Implementing an eletrical installation with KNX | Checklist | 17

 Smart home and building solutions. Global. Secure. Connected.

2. Your query Results

Define a lighting plan for each room, on

the basis of 1): What devices need to be
switched? Where is dimming required?

On the basis of 1), define a plan for con-

trolling blinds, windows, doors and gates,
and specify their function.

Discuss with your customer a safety

and security concept, and identify
consequences.

Example:
If internal activation is selected, the client must not open the window,
because this would set off an alarm.

Example:
If a passive trap system with motion sensors is to be used, there must be no pets in the house.

Determine whether there are further tech-

nical devices that need to be controlled
via / connected to the building automation
system:

Swimming pool

Rainwater utilisation

Heat pump

Photovoltaic system

Hot water convectors

Central vacuum system

Garden watering systems

Home cinema

etc.

3. Customer tasks Results

Ask your customer to define, on the basis
of 1), what controls are required in each
room. (Explain to your customer that he or
she must think in terms of functions rather
than in terms of conventional switches).

Point out to your customer what controls

might be needed in the future.

For example, when the use of a room changes after children have left home, when furniture
is rearranged, or if family members move in who have special care needs.

18 | Checklist | Implementing an eletrical installation with KNX

 KNX.ORG

4. Together with your Results

customer, define operating
philosophies
E. g. for push-button sensors: left for on,
right for off, central functions always at
the bottom. Also: Use of status LEDs

Remote controls

Central control panels / touch displays /

visual displays

Room temperature controllers

Date and signature, installer:

Date and signature, customer / user:

Implementing an eletrical installation with KNX | Checklist | 19

 Smart home and building solutions. Global. Secure. Connected.

SUPPLEMENTARY SHEET
other possible applications
(list not exhaustive)

1. Switching and lighting (all lamp types)

1.1. Switching from one or several locations.

1.2. Central switching, e. g. light off, iron off and cooker off at entry door.

1.3. Dimming from one or several locations.

1.4. Staircase switching – time-delay switch-off.

1.5. Toilet switching – time-delay switch-on and switch-off of fan.

1.6. Switching on and off of devices via timer programmes.

1.7. Switching on and off of sockets for temporary or potentially dangerous devices (e. g. rotary
iron), but also to reduce power consumption by appliances in standby (TV, stereo, etc.).

1.8. Motion-dependent switching for corridor area, side rooms and outdoor areas.

1.9. Daylight-dependent switching on and off of lighting via internal or external light sensors
helps to save energy.

1.10. Preset scenarios allow several switchable or dimmable groups of lights, other devices or blinds
to be changed to a predefined status at the touch of a button. Scenarios can be defined by the
system integrator or the user.

1.11. Panic button, e. g. by the bed. When this is pressed, predefined lights are switched on to
deter any intruders.

1.12. Status notification: depending on the actuator, statuses of devices can be displayed on
e. g. push-button sensors, displays or visual displays.

20 | Checklist | Implementing an eletrical installation with KNX

 KNX.ORG

2. Screens, shading and light deflection

2.1. Raising and lowering of blinds and adjustment of slats. The advantage of bus technology
is that several blinds can be controlled via a single push-button sensor.
This increases transparency and saves space. Light and blind functions can also be controlled
via a push-button sensor.

2.2. Central raising and lowering of blinds or shutters – for an individual facade, floor,
or for the entire house.

2.3. Preset positions at the touch of a button, e. g. to protect against glare when watching TV,
or at PC workstations in studies or in children’s rooms.

2.4. Weather-dependent control: protection of awnings, sun shades and other facade elements
against damage by wind, rain and frost based on evaluation of weather data. For example,
the awnings will retract if wind speeds are too high, and manual operation will be prevented.

2.5. Solar shading: brightness and / or temperature sensors close the shutters or blinds far enough
to prevent excessive heat from entering and to protect plants / furniture from damaging
UV radiation, but keep them open wide enough to allow sufficient daylight to enter.

2.6. Control of facade elements via timer controls – with no need for additional cabling.

2.7. Scenarios allow roller and other blinds to be moved to specific positions at the touch of a
button, often in combination with lighting. e. g. dim lights and move blind to relevant position
when watching TV.

2.8. Status notification: depending on the actuator, the statuses of facade elements / blinds can be
displayed on e. g. push-button sensors, displays or visual displays.

3. Windows, skylights, doors etc.

3.1. Opening, closing and selection of intermediate positions for (roof) windows and skylights.
The advantage of bus technology is that several windows can be controlled via a single
push-button sensor. This increases transparency and saves space. These functions can also be
combined with light or blind functions.

3.2. Central opening and closing of (roof) windows, skylights and doors for each side of the
building, a particular floor, or for the entire house.

3.3. Weather-dependent control: protection of windows and roof windows from wind, rain, frost.
Protection of rooms, e. g. by automatically closing roof windows when it rains, is also possible.

3.4. Brightness, temperature or air quality-dependent switching, for example to automate the
functions of a conservatory. If the temperature exceeds a preset value, the shading will be
activated and the ventilation windows opened. The ventilation windows can also be opened if
the concentration of CO2 reaches too high a level.

3.5. Windows, skylights and doors can be opened or closed at specified times via timer control.
Timer controls can be used in conjunction with measured internal and outdoor temperatures
in order to achieve automatic night-time ventilation.

3.6. Status notification: depending on the actuator, statuses (open, closed or specific intermediate
position) can be displayed on e. g. push-button sensors, displays or visual displays.

Implementing an eletrical installation with KNX | Checklist | 21

 Smart home and building solutions. Global. Secure. Connected.

4. Heating / Cooling
4.1. With individual room regulation, a target value can be defined and modified for each room.
If the resident is out of the house for a short time (shopping, doctor’s appointment, etc.), the
room temperature can be reduced by e. g. 2 °C, or e. g. 4 °C at night. (A reduction in room tem-
perature of 1 °C corresponds to an energy saving of 6 %).

4.2. Integration of window contacts: when a window is open, the room temperature controller
switches to frost protection mode. This ensures that no energy is used to heat the outside air
and, particularly in winter, that the room is protected against frost.

4.3. The amount of energy used can be reduced by connecting the individual room controllers to
the heating / cooling system: thus if only one or two rooms need heating, the supply tempera-
ture can be reduced (for heating) or increased (for cooling).

4.4. Incorporation of various energy sources (fossil and renewable): limit values can be defined in
order to allow the most favourable energy source to be used automatically. The system can
thus determine whether the temperature of the solar panels is higher than the water tempera-
ture in the hot water tank. If so, there is no need to use fossil energy for the water heating.
For cooling, the application described under 3.5 can be used.

5. Ventilation
5.1. Automated, monitored ventilation of living space, e. g. for low-energy or passive houses.
Can also be implemented in conjunction with CO2 sensors to maintain optimal air quality.

5.2. Measurement of indoor and outdoor temperatures allows, for example, the thermal energy of
the outlet air to be recovered in case of low outdoor temperatures.

5.3. Control of air extraction devices in kitchens, bathrooms, toilets and hobby rooms on the basis
of motion sensors or in combination with lighting control.

22 | Checklist | Implementing an eletrical installation with KNX

 KNX.ORG

6. Alarm functions
6.1. Monitoring of the outer shell of the building via magnetic contacts on windows, doors and gates,
or via glass breakage sensors.

6.2. Monitoring of the interior by motion sensors.

6.3. Monitoring of the area around the house by motion sensors.

6.4. Incorporation of room sensors into the alarm system.

6.5. Via a panic button, a silent alarm can be triggered in case of a break-in, in order to send a
notification to e. g. the guard service by retransmission (by telephone, SMS or email).

6.6. Presence simulation creates the impression that the house is occupied when it is in fact not.
Depending on the time of day and / or brightness, or for example at dawn or dusk, specific
lights can be switched on or blinds can be opened or closed.

6.7. Via a push-button, for example by the bed, all preset lights can be switched on in order to
deter intruders.

6.8. If the alarm is triggered, all lights inside and outside the house will switch on, and all blinds will
be opened.

6.9. Activation devices allow the alarm system to be activated either internally or externally.
External activation can be combined with a sequence of further functions to activate “leave
house” status. This can include switching off critical appliances, blocking controls, reducing
room temperatures and / or activating presence simulation. When the alarm is deactivated, the
“coming home” sequence can be activated, whereby all the functions activated when the alarm
is armed are negated and, for example, a basic level of lighting is activated.

6.10 Pictures from video cameras displayed in visualisation interfaces show who is at the door.

7. Comfort and safety functions

7.1. The use of SELV* supply voltage for the bus system serves to reduce electromagnetic radiation
compared to conventional 230 V or Powerline installations.

7.2. Switch relays can be used to disconnect circuits automatically in order to also prevent these
lines from emitting electromagnetic radiation.

7.3. Automatic watering of the garden is possible, with activation via pumps or valves. This can be
controlled by a timer or on the basis of measurements of the dampness of the soil.

7.4. Potentially hazardous devices (irons, rotary irons, cookers, external power sockets, etc.)
can be disconnected simultaneously via central switch-off.

7.5. Notification of the status of intelligent household appliances (washing machines,

dishwashers, refrigerators, freezers, etc.) to a display element. This allows malfunction to be
detected quickly.

7.6. In the future: measurement of electricity, gas and water and automatic comparison of
energy suppliers’ prices allows appliances such as washing machines or dishwashers to start
only when the most favourable rate is available.

* SELV = Safety Extra Low Voltage

Implementing an eletrical installation with KNX | Checklist | 23

 Smart home and building solutions. Global. Secure. Connected.

8. Overview of available control and display options

8.1. Push-button sensors with up to eight different controls on a surface area of a normal switch.

8.2. Use of the status LEDs on push-button sensors – particularly to display status, in cases where
no biofeedback is available.

8.3. Infrared remote control units for room-specific execution of commands.

8.4. Radio remote controls for inter-room execution of commands.

8.5. Backlit LCD displays of the size of a push-button sensor can be used to manage devices and
display their statuses.

8.6. LCD touch displays are available for large-format, comfortable overviews and for controlling
individual subsections of the house automation system.

8.7. PC- / IP-based visual displays provide extensive overview and control functions.

8.8. Remote access can be set up online.

9. Ports and gateways

Via ports and gateways, applications and functions which are not provided by bus components can
be integrated into the KNX system.

Examples:
• Conventional mechanical contacts via push-button interfaces
• Ethernet via IP interfaces
• DALI via gateways (subordinate lighting control system)
• Applications and functions, which are not provided by bus components can be integrated
into the KNX system via ports and gateways
• Stereo / TV via manufacturer-independent gateways

24 | Checklist | Implementing an eletrical installation with KNX

 KNX.ORG

CHECKLIST
handover of an electrical installation with KNX

TASKS EXECUTED REMARKS

Not
Yes No
required

1. Visual Inspection
All branch and connection boxes closed

Connections for customer’s on-site lights are

at least insulated or fitted with a temporary
lampholder

All push-buttons are labelled as specified

by customer and have been cleanly and
securely fitted

Distribution boards are fully labelled and

cleaned

Distribution diagrams with distribution

boards

Bus components including push-buttons are

labelled with the physical address

Network sockets are labelled

System and equipment descriptions and

operating instructions are provided in a
separate folder

Maintenance documents, plans, diagrams

and specifications are also provided in a
separate folder

System documentation left with customer

Handover of an electrical installation with KNX | Checklist | 25

 Smart home and building solutions. Global. Secure. Connected.

TASKS EXECUTED REMARKS

Not
Yes No
required

2. Functional check
Installation checked and all measurements
performed (E-CHECK, network, etc.)

Lighting, dimmers, blinds, central

switch-off, scenarios, etc. checked for
correct functioning

Window contacts checked

Intercom checked

Interfaces with third-party systems checked

(music, alarm, ventilation, etc.)

Room-specific calibration of
room temperature controllers

3. Customer Induction
Customer briefed on the installation

Customer briefed on the location of specific

devices, e. g. wind sensors, central controls,
etc.

Customer briefed on safety / security appli-

cations and alarm control point

Switching, dimming and blind functions

explained to customer

Content and navigation of touch panel

menus and visual displays explained

Customer briefed on setting of timers and

operation of other customer-relevant func-
tions, e. g. calling up and saving of scenarios

Customer briefed on operation of

room temperature controllers and other
room control panels

Customer action in case of bus / supply

voltage failure and restoration discussed

Further issues relating to the installation

raised by the design engineer / system
integrator

26 | Checklist | Handover of an electrical installation with KNX

 KNX.ORG

TASKS EXECUTED REMARKS

Not
Yes No
required

4. Handover of System
Handover of project software, system docu-
mentation and all manuals

One-off subsequent programming after

approx. 3 months arranged for ....................
(date)

Customer service telephone number given

to customer, maintenance contract signed

Acceptance report signed as per the

specifications or DIN 18015 Part 4

Date and signature, installer:

Date and signature, customer / user:

Handover of an electrical installation with KNX | Checklist | 27

 Smart home and building solutions. Global. Secure. Connected.

CHECKLIST
Increased security and privacy
in KNX installations

1. Were the following measures taken into

account during installation?
Are devices and applications fixed mounted? Is it ensured that devices are properly
protected against dismounting (e. g. use of anti-theft protection measures)?

Is it ensured that unauthorized persons have limited access to distribution boards

with mounted KNX installations (e. g. always locked or located in locked rooms)?

Is it difficult to access devices in external areas? (e. g. mounted at a sufficient height)?

In case the KNX installation can be operated from areas in buildings that are public
and not surveilled, did you contemplate the use of binary inputs (mounted in distribution
boards) or push button interfaces?

Are KNX Touch panels password protected (user, group or guest mode)?

2. Is Twisted Pair used as communication medium?

Is the cable anywhere in- or outside the home or the building protected
against unauthorized access?

In case the twisted pair cable is used in areas requiring extra protection measures,
have you taken the measures as given in item 6?

3. Is Powerline used as communication medium?

Have band stop filters been installed?

If Powerline is also used outside the building, have you taken the same measures
for the media coupler as given in item 6?

28 | Checklist | Checklist for increased security and privacy in KNX installations

 KNX.ORG

4. Is IP used as communication medium?

Have the network settings been documented and handed over to the home owner
or the LAN administrator?

Have switches and routers been set in such a way that only known MAC addresses
are able to access the communication medium?

Is a separate LAN or WLAN network with own hardware used for KNX communication?

Is access to the (KNX) IP networks limited to authorized persons via appropriate user
names and strong passwords?

For KNX IP Multicast communication another IP address as the default address should be
used (normally 224.0.23.12). Was this IP multicast address changed?

Was the default SSID of the wireless access point changed? Was the periodic transmission
of the SSID after installation deactivated?

Have ports of routers for KNX been closed towards the internet and was the default gate-
way of the used KNXnet / IP router set to 0? Was the (W)LAN installation protected by an
appropriate firewall?
If internet access to a KNX installation is needed, check the possibility to implement:
1. Establishing a VPN connection to the Internet Router
2. Use of manufacturer specific KNX Object Servers

5. Is Radio Frequency used as communication medium?

Have you taken the same measures for the media coupler as given in item 6?

Does each RF domain have a different domain address?

6. Have you used couplers in the installation?

Were individual addresses of devices assigned according to their place in the topology?

Do you prevent via the setting of appropriate parameters in the couplers

that incorrect source addresses are not forwarded outside the line?

Do you block Point-to-Point and Broadcast communication across couplers?

Have the filter tables been loaded correctly and have settings been made
in such a way that filter tables are taken into account by the couplers?

Have you considered the measures as given under item 7 for the couplers?

7. Have devices been locked against re-configuration?

If not, enter a BCU key1 in the ETS Project.

8. Do you use KNX Secure2 devices?

For group communication that needs to be secured, use the foreseen authentication
and encryption mechanisms of the device.

Checklist for increased security and privacy in KNX installations | Checklist | 29

 Smart home and building solutions. Global. Secure. Connected.

9. Do you suspect unauthorized access to the bus?

Record telegram traffic and analyse it. In the case of KNX Secure devices, read the Failure
Logs. Document the time and observed effects (what happens, what does not happen, why
and when)? Disable the internet connection of the KNX system and check, whether the ef-
fects disappear or not. Contact the hotline of the manufacturer: are the effects or security
problems known at the manufacturer, are updates available?

Read the PID_Device_Control3 from devices and check whether devices

are sending using the same Individual Address.

Read the PID_Download_Counter3 from devices and check whether the device
was downloaded again after your configuration.

10. Have devices been locked against re-configuration?

When KNX is coupled to security installations, was this realized in any of the following
ways?
1. Via KNX devices or gateways certified by national loss insurers?
2. Via potential free contacts (binary inputs, push button interfaces, ...)?
3. Via appropriate interfaces (RS232, ...) or gateways: was it ensured
that KNX communication is unable to trigger security relevant functions
in the security part of the installation?

11. General Security Measures

Is ETS up to date?
1. Is the PC, on which the ETS is installed, secure (up to date virus scan, newest operat-
ing system update)? It is recommended, to use a dedicated device for KNX design and
commissioning.
2. During the installation, it shall be avoided to hook other untrusted data storage devices
up to the PC (USB, external hard drive, …).
3. ETS Plug-ins and Apps shall preferably be installed prior to the installation
4. Backup the project file after the installation (ideally on a secured USB stick, which is
stored safely) and delete the project from the PC.

Is the firmware of the used devices up to date?

12. Further Privacy measures (GDPR)

Installer and customer shall sign a privacy declaration.

In order to fulfil the GDPR regulations, the installer shall hand over a copy of the ETS project
file to the customer.

1
Not all devices can be protected against re-configuration – contact the relevant manufacturer
2
Available from ETS 5.5 onwards
3
Is not supported in all devices

30 | Checklist | Checklist for increased security and privacy in KNX installations

Smart home and building solutions.
Join us
Global. Secure. Connected. www.knx.org