BUS · wired backbone

KNX installation and ETS programming in Hungary

We design the KNX topology, install the bus and program it in ETS — and we do the mains wiring too, so it is one job. We also take over KNX systems someone else built: if the ETS project is missing, we read it back from the bus and rebuild it. At handover the ETS project file is yours.

What we do
Topology design, bus installation, ETS programming, taking over existing systems
Where
On site, anywhere in Hungary
What you receive
The ETS project file, documented group addresses, a commissioned system

What KNX installation means in practice

The bus runs on twisted pair, with the data cable separated from the mains. We break the topology into lines and areas, and line couplers segment the traffic — that is what stops one faulty device taking down the whole system. The design is produced together with the cable routes, because the path of the bus cannot be changed afterwards.

  • Topology design: lines, areas, line couplers, power supply sizing
  • Bus cabling and mains installation, distribution board assembly
  • ETS programming: group addresses, parameters, scenes
  • Commissioning and documented handover — including the ETS project file

Taking over an existing KNX system

A common situation: the system works, but the ETS project is missing, the original installer is unreachable, and every change hits a wall. The actual topology and the use of the group addresses can be read back from the bus, and the project rebuilt from that. From then on the system can be extended again — and you get the project file, so you do not end up in the same position twice.

When you actually need a KNX specialist

If a new build or a full renovation is on the table and the walls are open now, designing in KNX is the decision that cannot be retrofitted cheaply later. In a finished, occupied flat, KNX rarely pays off — there the realistic route is wireless and behind-the-faceplate devices, and we say so, rather than selling a bus system into a building it does not belong in.

related systems

What we work with here

The full list, organised by layer on the home page, and protocol by protocol in the compatibility matrix.

KNX installation — related systems and protocols
System Bridge What we do with it
KNX (TP1 / IP / RF) KNX IP router Topology design, terminal and cabling work, ETS programming, taking over and extending an existing system.
DALI DALI gateway Designing and wiring DALI lines, fitting a gateway to KNX or the controller, addressing and scene setup.
Modbus (RTU / TCP) RS-485 / TCP Reading the register map, building the RS-485 segment with proper termination, wiring the data into the controller.
BACnet BACnet/IP Discovering and wiring existing BACnet points, fitting them to apartment- or office-level control.
Home Assistant — Setup, wiring in integrations, writing automations, backup and update policy, remote troubleshooting.

what we fix

The situations people bring us for this

Symptom, cause, intervention. These are the most common situations people bring to us — most of them do not need a new system, only a survey and a clean-up of the existing one.

Extending or reprogramming an existing KNX system

BUS on-site
Symptom · cause · fix Close
Symptom
There is a KNX system, but the original installer is unreachable, the ETS project is gone, and every small change hits a wall.
Typical cause
Without the project file the meaning of the group addresses is invisible — the bus works, but nobody can safely touch it blind.
What we do
We read the bus back, rebuild the ETS project from the actual topology, document the group addresses, and from then on it can be extended. You get the project file.

Bringing a mixed system under one interface

CONTROLLER on-site
Symptom · cause · fix Close
Symptom
KNX on the lighting, Shelly on the blinds, Zigbee on the sensors, a separate app for each — and none of them aware of the others.
Typical cause
The layers were built separately, there is no common controller looking across them, and no single place where the automation logic lives.
What we do
We bring the layers under one controller through gateways and move the logic to one place, while the bus keeps working on its own if the controller goes down.

what we do

The other layers of the stack

A system rarely stops at one layer. We handle these too, as part of the same installation.

contact

Book a consultation

Describe what is installed today and where you got stuck. You do not need a finished plan — the point of the consultation is to work out what is realistic. The more specific you are (protocols, devices, controller), the more precise an answer we can give, even without a site visit.

Please enter your name (at least 2 characters).
We will reply here. Please check the email address.
Please check the phone number.
Please write a few sentences about what you need (at least 20 characters).

Your data will be processed as described in our privacy notice (opens in a new tab).