Zigbee devices as KNX devices (zigbee2knx)
Beta
Open-source firmware for the TUL32 and TULX: the stick becomes the Zigbee coordinator, and every paired Zigbee device becomes a KNX device of its own, set up in ETS. A preview, not an end product.
Version v0.6.2 runs on: TUL32, TULX
Firmware for the TUL32 and the bus-powered TULX, both an ESP32-C6 with an NCN5130 KNX TP transceiver. The stick forms its own Zigbee network and turns every paired Zigbee device into a KNX device of its own, with its own individual address, application, parameters and group objects, programmed from ETS. No hub and no IP network sit in between; in operation the gateway needs nothing but the KNX bus.
A preview, not an end product. Not released for production installations yet. It runs with IKEA lights and plugs; the README lists what has been tested with which version. Free firmware you install yourself, without support from busware.

Features
- One KNX device per Zigbee device, up to 32 in the gateway’s own line. The gateway acknowledges their frames itself, so no coupler is needed.
- Pairing from ETS: when ETS programs an address in the gateway’s range, the first Zigbee device that joins takes it. A group object and the gateway’s button open a pairing window as well.
- Device classes instead of drivers: a class (dimmable light, white spectrum light, switch and plug, remote) is one KNX application plus a signed Berry program that maps KNX to Zigbee, derived from the device definitions of Zigbee2MQTT. An ETS download brings the program into the gateway, so a new device type needs no firmware update; a program without a trusted signature is refused.
- Devices so far are IKEA’s: 23 dimmable light, 48 white spectrum light, 14 switch and plug and 6 remote products, the remote class experimental (full list). Other makes are welcome as contributions.
Requirements
- A TUL32 (the older TUL with ESP32-C3 has no Zigbee radio) or a TULX. Other ESP32-C6 boards with an NCN5130 need their pins set in the source.
- ETS (tested with 6.4.1) and the product files (
.knxprod) for the gateway and the device classes. You build them yourself from the XML sources in the repository, with OpenKNXproducer and the signing library of your own ETS, as the README describes.
Getting started
- Flash. TUL32: in the browser at install.busware.de/TUL/zigbee2knx/ (Chrome, Edge or Opera). Erase on the first installation, not on an update, so the Zigbee network and the KNX devices stay. TULX: not with the web installer, it would overwrite its bootloader and partition table; read the whole flash, then write only the application with esptool, as the release notes describe.
- Build the product files with OpenKNXproducer and your ETS (how), and import them into ETS.
- Add the gateway: insert “Zigbee gateway (TUL32)”, the product for both boards, program its individual address and set the range for Zigbee devices (by default 200 to 231). Keep that range free of other KNX devices.
- Add a Zigbee device: insert its product into the same line with an address in that range and program it; while ETS waits, reset the Zigbee device or put it into pairing mode. Then download the application and link the group objects.
Limits
- No backup function yet; the only copy of the Zigbee network and the KNX devices is a full flash read over USB.
- Install codes are not supported.
- The TULX has been tested less than the TUL32, and the way back to its recovery system has not been tried.
- More under known limitations.
Discussion
Questions, experiences, bug reports? Discussion happens in GitHub Discussions : Open the discussion on GitHub ↗