KNX app on Homey Self-Hosted Server – no_matching_interface despite successful discovery

Questions & Help
1

I’m testing Homey Self-Hosted Server (SHS) before deciding whether to purchase a Homey Pro or run SHS on my NAS. Unfortunately, I can’t get the KNX app to add any devices.

Setup

  • Homey SHS: macOS, version [version], running in a dedicated VM with bridged networking. The VM has its own IP on the same subnet as the KNX interface.

  • KNX app: Official Athom app, version [version].

  • KNX interface: Ekinex Delégo Server Mini (firmware 2.7.1-1), with KNXnet/IP tunneling enabled and no KNX Secure.

  • Other apps: Working correctly (e.g., Ring), so device pairing on SHS generally works.

Issue

  1. Go to Add Device → KNX → Light → Connect.

  2. The app automatically discovers Delégo

  3. After selecting it and pressing Continue, I immediately get no_matching_interface.

  4. On mobile, I get a generic “There was an error”, followed by “Cannot save device” when entering group addresses.

  5. Manual configuration fails too: entering the IP and selecting “Search interface” returns “Selected IP interface not found”. Occasionally, scanning returns “Already searching for IP interface(s)”.

The same issue occurs with every KNX device type (lights, dimmers, switches, sensors).

Troubleshooting performed

  • Discovery works: Packet captures confirm that the VM sends a KNXnet/IP SEARCH_REQUEST to the IP and receives a unicast response (74 bytes) from the Delégo interface.

  • Connection never starts: After pressing Continue, no further traffic appears on port 3671. In particular, there’s no CONNECT_REQUEST, suggesting the app fails before attempting to establish a tunnel.

  • Tunneling works independently: From the Mac host, I can establish a KNXnet/IP tunnel to the same interface and receive telegrams.

  • App reinstall: Restarting and reinstalling the KNX app makes no difference.

Questions

  1. Is no_matching_interface a known error? What exactly is the KNX app trying to match or validate after discovering an interface?

  2. Is the official KNX app fully compatible with Homey Self-Hosted Server, particularly when running in a macOS VM?

  3. Is there a way to access detailed KNX app logs on SHS to understand why the discovered interface is rejected?

Since discovery succeeds but no connection attempt follows, I suspect an issue with interface validation or SHS compatibility rather than KNXnet/IP connectivity itself.

Any suggestions would be appreciated. I’m happy to share packet captures or additional diagnostics.

Thanks!

2

How exactly are you running it? What’s the OS running inside the VM, and which specific version of SHS are you running on it?