WBE2-I-KNX

WBE2-I-KNX is an internal expansion module that adds a KNX TP bus interface to compatible Wiren Board controllers. It is intended for integrating KNX building-automation devices with controller services, MQTT and automation software.

Module overview

The module is installed inside a Wiren Board controller and provides a port for devices that communicate over KNX. The KNX bus must be powered for the module to operate.

Terminal assignment

Warranty and service life

Installation

Modules ordered together with a controller are normally factory-installed and only need to be enabled in the controller web interface. Install separately purchased modules as follows:

1. Shut down the controller and disconnect all power sources.
2. Open the controller enclosure.
3. Insert the module in a compatible internal slot. Observe polarity: the locating projection on the module must enter the matching cut-out on the controller PCB.
4. Reassemble the enclosure, connect the KNX bus and power the controller.

Controller compatibility

When installing the module in MOD3 on Wiren Board 6.7–8.4, or in MOD4 on Wiren Board 8.5, remove the interfering plastic projection from the enclosure with side cutters or a file. Remove only the marked projection and keep debris away from the electronics.

Controller configuration

Admin access

Configuration permissions are assigned to user accounts authenticated by login and password. To change controller settings, sign in with an account that has the Admin access level. Manage accounts under Settings → Users. On controller releases earlier than wb-2602, set the access level under Settings → Access level.

Enable the module

1. Open Settings → Configs → Expansion modules and ports in the controller web interface.
2. Select the internal slot containing WBE2-I-KNX.
3. Choose the installed module type from the Module type list.
4. Select the KNX-device option required by the configuration and click Save. The controller enables the ports needed by the module.

To remove the module from the software configuration, select Not installed for the slot and save the change.

Device nodes

The configuration creates symbolic links in /dev: ttyKNX1 for Internal slot 1 and ttyKNX2 for Internal slot 2. When the configuration contains only one KNX device, the additional ttyKNX link is created regardless of which of the two slots contains the module.

Operation

Preinstalled software

The recommended integration service is wb-mqtt-knx. It translates KNX telegrams to MQTT topics and MQTT commands back to KNX telegrams. Communication with the physical KNX bus is handled through the knxd router.

Use KnxTool for diagnostics, monitoring telegrams and checking communication. Confirm that the KNX power supply, polarity, bus topology and termination comply with the KNX installation design before diagnosing software.

Alternative software

iRidium Server can also be installed on a Wiren Board controller. It can communicate with the KNX bus directly through the serial module or through knxd. Use software versions compatible with the controller architecture and current Debian release.

Typical data path

1. A KNX device transmits a telegram on the powered KNX TP bus.
2. WBE2-I-KNX transfers it to the controller serial interface.
3. knxd provides bus routing and tunnelling services.
4. wb-mqtt-knx publishes the telegram to MQTT or converts an MQTT command into a KNX telegram.

Troubleshooting

• No device node: verify the physical slot, module type and saved expansion-module configuration.
• No KNX traffic: verify KNX-bus power and O1/O3 polarity, then inspect knxd and wb-mqtt-knx service status.
• Intermittent communication: check the module batch and revision against the history below. Early hardware has documented communication issues.
• ETS cannot discover the interface: verify that KNX tunnelling and discovery are enabled in knxd, and that the workstation network permits multicast discovery.

Hardware revisions

The batch number is printed on the label on the side of the enclosure or directly on the module PCB.