IHC Programming Capabilities in eConfigure

IHC Input → IHC Output

You can link any IHC input – push button, sensor, switch node – to an IHC output channel. This reproduces the classic IHC‑to‑IHC behavior from the original IHC controller.

How it works

• eConfigure creates virtual group addresses for the logic between the input and the output.

• These virtual groups allow the IHC Interface to exchange commands internally without relying on KNX or ZigBee addressing.

• You use this mapping when both sides belong to the IHC system (e.g., IHC push-button controlling an IHC relay module).

Use case example:

• A push-button connected to an IHC input module switches a lamp connected to an IHC output module.

IHC Input → KNX Output

You can connect any IHC input to a KNX output device. This allows you to reuse existing IHC push-buttons and sensors while replacing loads with KNX actuators.

How it works

• eConfigure assigns KNX group addresses, just like any standard KNX mapping.

• The IHC Interface sends KNX‑compatible telegrams through the Wiser for KNX controller.

• LED indication on IHC push-buttons works, because the KNX feedback can be mapped back to the IHC input LED node.

Supported behavior:

• Switching (toggle, on/off)

• Dimming via KNX dimmer actuators

• LED feedback on FUGA/OPUS push-buttons

Use case example:

• IHC push-button controls a KNX DIN-rail dimmer channel.

Summary