01
Replace “connect everything” with readable rules.
Choose three important situations and write what each occupant or operator expects. For “Leaving”, name the rooms, intended changes and what must remain available. Rephrase a function that nobody can explain clearly before adding equipment.
Split each rule into trigger, conditions, actions, confirmation and exception. A button requests a scene; it does not prove every action succeeded. Name the person validating behaviour and define local controls for others without giving them administrator accounts.
02
Separate intent from what can be measured.
Scroll the table horizontally to compare all three columns.
| Function | Write in the brief | Confirmation and limit |
|---|---|---|
| Lighting | Independent circuits, local control and intended scene in each zone. | A requested dimming value is not a measurement of room illumination. |
| Blinds and curtains | Desired opening, manual takeover and identified mechanism constraints. | Distinguish measured position, estimated position and missing feedback. |
| Climate | Setpoint, mode, associated window and agreed resumption conditions. | A setpoint proves neither achieved temperature nor energy savings. |
| Coordinated scene | Included and excluded actions and manual-override priority. | Show partial results; silence must not become global success. |
03
Verify interfaces and responsibilities individually.
Control, communication, power
Draw these three paths separately. For each circuit request the actual load, expected interface and manufacturer document. A contact, bus and IP interface are not equivalent. A competent professional validates wiring, protection and motor or climate-equipment constraints.
Protocol and supported function
Record models, versions and exchanged functions. KNX distinguishes TP, RF and IP links and interfaces; a protocol name does not replace that architecture. For a gateway, ask which commands and feedback actually cross each side.
Configuration and project ownership
Name who prepares, backs up and hands over configuration. In a KNX project, ETS structures and configures the installation; plan access to files, versions and necessary tools at handover. No licence purchase or partner status is implied here.
Dependencies and operation
List the controller, LAN, Internet and external services needed by each function. Clarify account and subscription ownership. Retaining a local control does not imply all supervision or scenes will work during a failure.
04
An open window changes demand, not the setpoint.
ILLUSTRATIVE EXAMPLE
Fictional case: zone C-01, illustrative 22 °C setpoint, window F-01 and office B-01 retained as a manual exception. Assumed equipment supports these functions; no universal comfort temperature is recommended.
Open the window
F-01 reports open. C-01 climate demand is suspended under the agreed rule, while the setpoint remains 22 °C. Show “paused — window open”, without claiming the room has reached the intended temperature.
Request a leaving scene
The scene affects only its permitted zones. B-01 stays excluded until the user clears its override. The open window still blocks C-01 demand; a new scene must not silently erase the condition or claim “all applied”.
Close and verify resumption
After confirmed F-01 closure, C-01 regulation permission returns according to the active mode and equipment safeguards. The 22 °C setpoint is retained; no immediate start is promised. B-01 stays independent until its override is explicitly cleared.
No example in this guide resets fire detection, disarms an alarm or unlocks an exit. These systems are not included in a comfort scene by default.
05
Validate a pilot room before repeating the logic.
Successive commands and manual takeover
Request opposite states then take over locally. Check the applied result, indicators and agreed priority. A stale command must not replay later against the latest choice; document any equipment-required delay.
Missing or inconsistent feedback
On a bench or authorised test, observe unavailable feedback. The display should separate unknown, requested and confirmed. Record the sensor, estimate or acknowledgement behind each indication; a timer is not physical evidence.
Loss of a dependency
Plan the test and recovery with the owner. Check what remains usable when the selected dependency is absent, without disrupting occupied premises. An Internet-loss test does not validate controller or power loss.
Handover and change
Hand over rules, plans, references, versions, backups and unresolved items. Demonstrate schedule changes and clearing overrides within permitted scope. Date later changes and repeat tests for affected functions.
06
Give the distributor and integrator a usable brief.
Link every equipment row to a zone and rule. Separate actuator, control, sensor, gateway, power and accessories without assuming they are bundled. Mark selected, alternative and unconfirmed items with sources; grouping them does not create a compatible kit.
Inovexia remains the distributor: references, available documentation and commercial enquiries. Detailed design, installation, programming and acceptance belong to the agreed integrator scope, including WEXON if selected. Timelines, configuration costs, licences and support terms require an explicit proposal.
07
Decisions to make before the first scene.
Does one app mean the building is integrated?
No. Identify actual function exchanges, feedback and local operation. A common interface can conceal different dependencies; document them instead of judging only its home screen.
Can we start with one room?
Yes, as a test scope with documented architecture and expansion. The pilot should represent functions to repeat, not automatically validate untested loads, protocols or mechanisms.
What if an occupant wants to keep a setting?
Define a visible override, its scope and how it ends. An override with no end rule can surprise users, as can silently clearing it on the next scene. Agree this behaviour in the brief.
Can offline operation be promised?
Only for precisely documented functions verified on the selected system. Separate local control, logic, supervision and external services. “Without Internet” does not mean without power or controller.
What belongs in the quotation brief?
Useful plans, zones, rules, known references and constraints, without passwords or named routines. Identify unknowns and the decision owner. A saved project prepares the enquiry; check submission confirmation in the professional workflow.
Technical sources
External reading references. These documents explain principles; they do not certify catalogue products or their combination.
- What is ETS? — Project configuration and documentationKNX Association · Sources consulted on
- KNX TechnologyKNX Association · Sources consulted on