IP4KNX IP4KNX
Open-source KNXnet/IP firmware for the busware TUL, TUL32 and TULX: tunnelling with up to ten concurrent connections, routing and a web dashboard. Not an end product: you install it yourself.
Version v1.4.44 runs on: TUL, TUL32, TULX
Open-source firmware that provides KNXnet/IP tunnelling and routing between the KNX TP1 bus and your IP network. It runs on the busware TUL (ESP32-C3), the TUL32 (ESP32-C6) and the bus-powered TULX (ESP32-C6), and is built on the OpenKNX stack, patched for the NCN5130 transceiver on these boards.
Not an end product for end users! busware sells the TUL sticks as a hardware platform for your own projects. ip4knx is not part of that product: you install it yourself, and busware provides no support for it. The firmware is meant as inspiration for the community — testers are wanted, and pull requests are always welcome.
Features
- Up to ten concurrent tunnels, for example ETS and Home Assistant at the same time. Each tunnel gets its own individual address, and frames a client sends carry it, so a client cannot send under another client’s or a bus device’s address.
- Home Assistant without knxd or add-on: the KNX integration finds the stick with its gateway scan and connects through a tunnel (HowTo). FHEM connects directly through its
KNXIOmodule (HowTo). - Routing starts once the stick has an individual address other than the default
15.15.0; ETS can assign one in programming mode. Routing forwards main groups 14–31 only. - Setup over Wi-Fi: without stored credentials the stick opens the access point
TUL AP xxxxwith a captive portal. If the stored network is out of reach after boot, the same access point opens as a fallback; storing a different network there needs the push button held for more than 2 seconds. KNXnet/IP does not run over this access point. The TUL and TUL32 also take Wi-Fi credentials over USB (Improv) during the first 120 seconds after boot. - Optional wired Ethernet on the TUL32: a W5500 module on the FPC header is detected at boot; with a cable link and a DHCP lease the Wi-Fi radio is parked.
- Dashboard at
http://tul.local: network, active tunnels, NCN5130 self-test (UART link, bus voltage, power rails), bus statistics, programming mode and an online update check. - Updates: on the TUL and TUL32 from the dashboard, online or as a file, MD5-checked, with two app partitions and bootloader rollback. The TULX installs updates through its recovery system.
Requirements
- A TUL of either generation (ESP32-C3 or TUL32 with ESP32-C6) or a TULX, on a KNX TP1 line.
- 2.4 GHz Wi-Fi, or Ethernet on a TUL32 with W5500 module.
- A KNXnet/IP client: Home Assistant, ETS, FHEM, Node-RED or similar.
Getting started
- TUL and TUL32: install from the browser at install.busware.de/ip4knx/ (Chrome, Edge or Opera). The page writes the image and hands over the Wi-Fi credentials.
- TULX: it has no USB port; its recovery system installs the image over the network, see install.busware.de/tulx/.
Setup, the push button and the individual address are described in the README.
Versions
Releases are tagged v1.4.x on GitHub (tags, also as an Atom feed). The dashboard shows the firmware version 1.4.<build> and the Git hash: release v1.4.44 is firmware 1.4.210.
Limits
- No KNX IP Secure; KNX Data Secure is untested.
- No ETS application (product database entry) of its own.
- The firmware is specific to these boards: pin assignment and NCN5130 handling differ per board, so the installer writes the image for the board it finds.
Discussion
Questions, experiences, bug reports? Discussion happens in GitHub Discussions : Open the discussion on GitHub ↗