1. What Is KNX Topology?
KNX topology defines how KNX devices, lines, areas and backbone infrastructure are organised within a KNX installation. It determines both the physical arrangement of the bus and the logical structure represented in ETS. A well-designed topology makes the system easier to commission, troubleshoot and expand. For larger projects, it also determines how individual KNX lines communicate with each other.
KNX BACKBONE
│
┌────────────┼────────────┐
│ │ │
Area 1 Area 2 Area 3
│ │ │
┌──┴──┐ ┌──┴──┐ ┌──┴──┐
Line 1 Line 2 Line 1 Line 2 Line 1 Line 2
│ │ │ │ │ │
Devices Devices Devices Devices Devices DevicesA professional KNX topology should consider:
- Building architecture
- Device distribution
- Bus current
- Voltage drop
- Cable distances
- Line and area structure
- IP network architecture
- Future expansion
2. What Is a KNX Line?
A KNX line is a basic section of a KNX installation in which KNX TP devices communicate through twisted-pair bus cable. Sensors, push buttons, actuators, presence detectors, room controllers and gateways can all be connected to the line. Line design should consider electrical loading and physical distribution, not just the number of devices connected.
KNX POWER SUPPLY
│
│
───────── KNX TP BUS ─────────
│ │ │
Sensor Actuator Gateway
│ │ │
Push Button Presence DALI
Sensor GatewayA line normally contains:
- KNX power supply
- KNX TP cable
- Sensors
- Actuators
- Controllers
- Gateways
- Other KNX TP devices
The line is therefore both an electrical unit and a logical ETS unit.
3. KNX Individual Addressing
Every KNX device is assigned an individual address that identifies its position within the topology. A traditional three-level individual address uses the format Area.Line.Device, such as 1.2.35. A consistent addressing strategy makes commissioning, troubleshooting and maintenance considerably easier.
For example:
1.1.x → Ground Floor
1.2.x → First Floor
1.3.x → Second FloorWhere:
- 1 = Area
- 2 = Line
- 35 = Device
The individual-addressing strategy should be agreed before ETS commissioning begins.
4. What Is a KNX Area?
A KNX area is a higher-level structure used to group multiple KNX lines within a larger installation. Areas are particularly useful for commercial buildings, hotels, campuses and multi-building projects where many lines need to be organised logically. A well-planned area structure makes the ETS project easier to understand and provides a clear path for system expansion.
Example:
Area 1
├── Line 1.1
├── Line 1.2
└── Line 1.3A project could use areas based on:
- Building
- Tower
- Functional zone
- Floor grouping
- Campus section
The exact structure should reflect the project’s physical and functional requirements.
5. What Is the KNX Backbone?
The KNX backbone provides communication between different areas of a larger KNX installation. Traditional KNX architectures could use TP as the backbone, while modern installations can use KNX IP to provide high-speed communication over Ethernet infrastructure. A backbone becomes increasingly important as a project grows beyond a small number of KNX lines.
A simplified architecture is:
KNX BACKBONE
│
┌─────────────┼─────────────┐
│ │ │
Area 1 Area 2 Area 3
│ │ │
TP Lines TP Lines TP LinesFor large projects, the backbone allows the installation to be divided into manageable sections instead of creating one large, difficult-to-maintain bus structure.
6. KNX Line Coupler
A KNX line coupler connects two KNX line sections and controls communication between them. Besides providing the topology connection, it can use a filter table to prevent unnecessary group telegrams from being propagated between lines. This makes line couplers important for both system architecture and bus-traffic management.
KNX LINE 1
│
│
┌──────────────┐
│ Line Coupler │
└──────────────┘
│
│
KNX LINE 2A line coupler can help with:
- Line segmentation
- Telegram filtering
- Fault isolation
- Topology organisation
- Larger KNX installations
7. KNX Area Coupling
Area coupling allows separate KNX areas to communicate while maintaining the hierarchical structure of the installation. In a large project, each area can contain several KNX lines, while the backbone provides communication between areas. This approach makes the architecture scalable and easier to manage.
Area 1
├── Line 1.1
├── Line 1.2
└── Line 1.3
│
│
Backbone
│
│
Area 2
├── Line 2.1
├── Line 2.2
└── Line 2.3The exact implementation depends on whether the backbone uses TP, IP or a combination of KNX media.
8. KNX IP Backbone
KNX IP allows KNX communication to use Ethernet networks and is particularly useful for large installations. KNX IP routers can connect TP sections to an IP-based KNX backbone, allowing multiple areas and lines to communicate over the building’s network infrastructure. However, the IP network must be properly designed to support KNX communication.
Ethernet Network
│
┌────────────┼────────────┐
│ │ │
KNX IP KNX IP KNX IP
Router Router Router
│ │ │
TP Line TP Line TP LineThe network design may need to consider:
- IP addressing
- Multicast
- VLANs
- IGMP
- Switch configuration
- Network segmentation
- Firewall policies
9. KNX IP Interface vs KNX IP Router
KNX IP interfaces and KNX IP routers have different roles and should not be treated as interchangeable devices. An IP interface is commonly used to provide a connection between a computer or application and the KNX installation, while an IP router can participate in KNXnet/IP routing between KNX sections. Choosing the correct device depends on the intended architecture.
KNX IP Interface
Typically used for:
- ETS programming
- Tunnelling
- Visualisation
- PC-to-KNX communication
PC / ETS
│
Ethernet
│
KNX IP Interface
│
KNX TPKNX IP Router
Typically used for:
- KNX IP routing
- Backbone architecture
- Connecting TP lines to IP networks
- Communication between KNX areas
KNX TP
│
KNX IP Router
│
Ethernet
│
KNX IP Backbone10. KNX IP Routing and Multicast
KNX IP routing uses IP multicast to distribute KNXnet/IP routing telegrams across the IP network. Because of this, the network infrastructure must correctly handle the required multicast traffic. Incorrect switch, VLAN or multicast configuration can cause communication problems even when the KNX devices themselves are correctly configured.
A simplified architecture is:
KNX Router 1
│
├──────── Ethernet Network ────────┐
│ │
KNX Router 2 KNX Router 3For larger projects, the network engineer and KNX integrator should coordinate on:
- Multicast configuration
- VLAN design
- IGMP behaviour
- Switch configuration
- IP addressing
- Routing and firewall policies
A dedicated KNX IP networking article should cover these subjects in greater depth.
11. KNX Topology for a Small Residential Project
A small residential KNX installation may only require one TP line if the device count, electrical loading and physical installation permit it. Keeping the architecture simple can reduce hardware, configuration and maintenance requirements. However, even a small installation should consider future expansion and cable distribution.
Example:
KNX PSU
│
─────── KNX TP ───────
│ │ │
Lights HVAC Sensors
│ │ │
Actuators KeypadsFor a small project, one well-designed line can often provide a straightforward architecture.
12. KNX Topology for a Large Building
Large commercial buildings usually require a structured topology because of the number of devices, physical distances and functional zones involved. Multiple lines can be grouped into areas and connected through a suitable backbone. This approach also makes fault isolation and future expansion more manageable.
Example:
KNX IP BACKBONE
│
┌────────────────┼────────────────┐
│ │ │
Area 1 Area 2 Area 3
│ │ │
┌───┴───┐ ┌───┴───┐ ┌───┴───┐
Line 1.1 Line 1.2 Line 2.1 Line 2.2 Line 3.1 Line 3.2Possible allocation:
- Area 1 – Offices
- Area 2 – Meeting rooms
- Area 3 – Building services
The final structure should be based on the project’s engineering requirements.
13. How to Decide Where to Create KNX Lines
Line division should be based on a combination of electrical, physical and functional considerations. A building floor may naturally become a line, but that is not a universal rule. Device count, bus current, cable distances, fault isolation and future expansion should all be considered before deciding where one line ends and another begins.
Consider creating additional lines when:
- Device count becomes high
- Bus current becomes significant
- Cable distribution becomes complex
- Physical zones are clearly separated
- Fault isolation is important
- Future expansion is expected
- Different building sections need logical separation
14. Avoid Creating Too Many KNX Lines
More lines do not automatically create a better KNX system. Excessive segmentation introduces additional couplers, power supplies, addressing and commissioning requirements. The objective should be to create a topology that is technically sound without making the installation unnecessarily complex.
Too many lines can result in:
- More hardware
- Higher installation cost
- More configuration
- More potential failure points
- More complex ETS projects
- More maintenance effort
A good designer should balance:
Electrical requirements + physical layout + logical organisation + cost
15. KNX Topology and Fault Isolation
A structured topology makes it easier to identify which section of the installation is affected by a fault. If a project is divided logically into lines and areas, the engineer can isolate the investigation instead of troubleshooting the entire building at once. This becomes particularly valuable in large commercial installations where downtime can affect multiple systems.
For example:
Area 1
├── Line 1.1 → OK
├── Line 1.2 → Fault
└── Line 1.3 → OKThe troubleshooting process can immediately focus on Line 1.2.
16. KNX Topology and Filter Tables
Line and area couplers can use filter tables to control which group-address telegrams are passed between different parts of the installation. This prevents every telegram from unnecessarily travelling through the entire KNX architecture. Correct group-address planning is therefore closely connected with effective topology design.
Conceptually:
Line 1.1
│
│ Telegram
▼
Line Coupler
│
├── Required → PASS
│
└── Not required → BLOCKThis becomes increasingly important as the KNX installation grows.
17. KNX Topology Design Workflow
A professional topology should be developed before the ETS project is fully configured. Start with the building and device schedule, then work through electrical loading, physical distribution and line/area structure. Finally, create the ETS topology so that the software representation accurately reflects the engineered installation.
Recommended workflow:
1. Review building drawings
↓
2. Create device schedule
↓
3. Calculate bus current
↓
4. Check voltage drop
↓
5. Define KNX lines
↓
6. Define areas
↓
7. Select backbone
↓
8. Select couplers and routers
↓
9. Coordinate IP network
↓
10. Build ETS topology
18. Common KNX Topology Design Mistakes
Poor topology decisions can create unnecessary complexity or make troubleshooting difficult later. Many problems originate because the KNX architecture is created directly in ETS without first developing a proper engineering design. A few simple planning steps can prevent significant commissioning and maintenance problems.
Mistake 1: Designing ETS before the physical system
ETS should represent the engineered system rather than replace the engineering process.
Mistake 2: Putting everything on one line
Large installations may require structured segmentation.
Mistake 3: Creating too many small lines
Over-segmentation increases complexity and cost.
Mistake 4: Ignoring the IP network
KNX IP routing depends on correct network configuration.
Mistake 5: Random individual addresses
A structured address plan makes maintenance easier.
Mistake 6: Ignoring future expansion
A topology should allow reasonable room for future modifications.
19. KNX Topology Design Checklist
Before finalising the topology, the KNX consultant or integrator should verify both the electrical and logical architecture. The ETS structure should match the approved engineering drawings and device schedule. This provides a consistent reference for installation, commissioning and future maintenance.
- Building zones identified
- KNX devices scheduled
- Bus current calculated
- Power supplies selected
- Voltage drop checked
- Lines defined
- Areas defined where required
- Couplers selected
- IP backbone requirements defined
- Multicast requirements considered
- IP addressing planned
- Individual addresses structured
- Group-address structure coordinated
- Future expansion considered
- ETS topology matches the engineering design
- Final topology documented
Conclusion
KNX topology design is the foundation for building a scalable and maintainable KNX installation. A small residential project may need only a single TP line, while a large commercial project can require multiple lines, areas, couplers and a KNX IP backbone. The correct architecture depends on the building, device distribution, electrical requirements and project objectives.
A well-designed topology provides logical organisation, reliable communication, easier commissioning, better fault isolation and simpler future expansion. It should therefore be developed as part of the engineering design rather than being treated as an ETS programming exercise.
Design the KNX topology first. Configure it in ETS second.
