01Wired, wireless or a planned combination
KNX includes wired and KNX RF options. The appropriate design depends on access to cables, the building layout and compatible devices. A new villa offers different installation opportunities from an occupied apartment. We review what can be retained and where a gateway or additional equipment would be needed before proposing a system architecture.
02Match devices to real functions
List the required actions room by room: dim a particular lighting circuit, position a curtain or adjust a supported climate zone. A brand name alone does not establish those functions. Device selection must account for the actual electrical loads, control interfaces and proposed integrations; existing Wi-Fi products do not automatically become KNX devices.
03Agree scenes and local controls
A morning or leaving scene should have a written list of actions and a simple manual alternative. KNX core functions can operate locally, while added remote-access or voice services may introduce internet dependencies. Specify which functions continue during a network interruption and demonstrate that behaviour for the completed installation.
04Make the handover usable
ETS is the planning and configuration software used for KNX installations. The project scope should establish configuration responsibilities, commissioning, documentation and access to the relevant project files. Ask for circuit and device schedules, control labels, a record of scene behaviour and a clear process for future changes, backups and support.
KNX is presented as a system to evaluate. Zeta Nest does not claim KNX Partner status or certification here. Equipment, delivery responsibilities and any specialist involvement are confirmed in the project proposal.