UPLOAD Tab

When you work in the UPLOAD tab, the workflow is generally the same for KNX, Zigbee, and IHC. However, there are some differences:

IHC Interface Pairing

The IHC Interface cannot be identified in the UPLOAD tab. It must be paired inside the IHC plugin installed on the Wiser for KNX/spaceLYnk controller. If the interface is not paired, you cannot upload any IHC devices.

Identification Behavior

Most IHC devices cannot be identified in the UPLOAD tab.
Identification works only for the RS-485 LED dimmer.
Other IHC input modules, output modules, and non-RS-485 dimmers do not support a learn/identify function. The IHC Interface also cannot be identified, because pairing is done exclusively in the IHC plugin.

Connection and Controller Access for IHC

The parametrization of IHC devices is performed through the controller, not through the local device network. Because of this, IHC requires a specific method for controller access.

In the Controller access dialog, select the access type User defined. You must manually enter the IHC Interface's IP address. This allows the controller to reach the IHC plugin and apply the IHC configuration.

NOTE: If you select Default access, you will receive an error message stating that default controller access is not allowed for IHC devices. This is expected behavior because the IHC Interface requires explicit addressing through the IHC plugin.

Using the correct access settings ensures that eConfigure KNX can communicate with the IHC Interface through the controller and complete the upload of IHC device configurations.