SELECTION FIELDNOTES

Interra: from a touch to a building response.

An ‘away’ button only makes sense when lights, blinds and setpoints respond as intended. Plan a KNX installation by linking each use to an identified control, actuator and load. Then define what the user will actually see as feedback.

View references

Integrators · homes, offices and buildings with coordinated controls.

AI-generated conceptual illustration. Generic equipment, not associated with a brand model. Neither a real installation nor a technical plan.

15references in the loaded catalogue

Before you choose. KNX, DALI and IP have distinct roles. Their presence in a range guarantees neither every function nor every pairing. A sent command is not proof of measured position, temperature or state.

Four roles behind one button

ROLES TO PLAN · PREPARATION OUTLINE

Control
A button, screen or event expresses an intent. Specify short press, long press, visual feedback and who may change the scene.
Communication
The project links commands, addresses and functions. Plan topology, bus power and interfaces; network access alone is not the building logic.
Actuator
The output performs a load-appropriate function: switching, dimming or movement. Channel count does not establish which functions can be combined simultaneously.
Result and feedback
Distinguish requested state, actuator-reported state and actual measurement. A blind displayed as closed may require evidence beyond a close command.

Start with loads, not button count

Interra presents controls, actuators, system components and gateways as separate families. Selection still depends on model and application: a family name is not a wiring design.

Use	Describe	Verify
Lighting	Circuits, drivers, required dimming and shutdown behaviour.	Load type, inrush current, dimming method and each output’s limits.
Blinds and curtains	Motor, movements, travel limits and manual priority.	Outputs intended for this use, interlocking and documented position feedback.
Comfort	Rooms, sensors, controlled equipment and permitted setpoints.	Actual heating or cooling interface; a screen alone does not provide it.
Gateways	Functions to exchange between KNX, DALI or an IP device.	References, capacity, available objects and versions; not universal compatibility.

Source 1 · Interra Technology

A brief the integrator can use

A room / function schedule
For each room list lighting, blinds, comfort, controls and expected feedback. Identify functions that must remain usable if supervision is unavailable.
Exact equipment
Include motor, luminaire, driver and climate-interface manuals. Have loads and combinations checked: a 16 A label alone does not validate every load on a channel.
Priority rules
Define priority between schedules, sensors, scenes and local control. Specify when an override ends so lighting does not react against the user’s intention.
Project handover
Plan the ETS file, versions, labels, backups and access handover to the authorised owner. Transfer keys and passwords securely, not in a public form.

‘I’m leaving’, but the office is occupied

Fictional case: close blinds and switch off shared areas while retaining office lighting. Describe this scene before choosing outputs.

Name the exception
The office does not join the general switch-off. Define who activates the exception and whether it remains valid next time.
Check feedback
The interface should show the applied scene without inventing measurements. If blind position is estimated, do not present it as a closed-position sensor.
Test manual recovery
Switch a room on locally, then check the agreed priority rule. Document recovery after an outage before user handover.

A specification example, not a universal configuration. The integrator validates available functions, programming and tests on the selected equipment.

Match reference, application and version

Interra’s download centre separates datasheets, product documentation, drawings and the ETS database. For a retrofit, retain the file actually used and exact reference; a recent catalogue does not prove an older installed device’s functions.

The schedule should trace every channel, load and project label. Do not transfer a newer Secure generation’s functions to an older reference because the front looks similar.

Source 2 · Interra Technology

Before finalising controls

Does a ‘Combo’ actuator perform every function at once?

Not necessarily. Channel allocation, enabled functions, loads and application need exact-model verification. Describe each output’s requirement first.

Does an IP connection replace KNX power and project configuration?

No. Network, bus, power and programming have different roles. The required interface depends on the architecture and exchanged functions.

What should handover include?

Scene tests, manual priority, explained status feedback, labels, files and backup procedure. Clarify who holds access and who may change programming.

Related guides and tools

From reading to a project brief

Discuss my selection

KNX, DALI and IP: distinguish the roles Plan an automation architecture Organise handover and backups

Sources, date and limits

Official documents are linked, not rehosted. Preparation advice is editorial; sources validate neither every catalogue reference nor a commercial partnership. Terms and variants still need checking.

Sources consulted on September 27, 2026

Explore catalogue classifications

This classification reflects loaded data, not technical validation or availability. Open the exact product page to check published information.

Four roles behind one button

Control

Communication

Actuator

Result and feedback

Start with loads, not button count

A brief the integrator can use

A room / function schedule

Exact equipment

Priority rules

Project handover

‘I’m leaving’, but the office is occupied

Name the exception

Check feedback

Test manual recovery

Match reference, application and version

Before finalising controls

From reading to a project brief

Brand references · Interra