So far my knx test installation with currently 2 MDT IP-Routers (SCN-IP100.03) commisoned as secure by ETS 6 works properly with OpenHAB 5.0. Setup in OH is as shown in subsequent screenshots.
The “only” issue I have is, that during restart of OH, the configuration of the IP-Gateways switches automatically from “secure router” to “router”! (2 identical IP-Routers for two Knx-lines are installed and act as Routers with IP-backbone). Sometimes also the broadcast address is changing to the address of the router itself. As a consequence, all installed knx devices will stay offline as no secure communication is possible. After manual switching back to “secure router” and correcing the broadcast address, the system works properly again until next restart.
Has someone an idea what could be the reason for this effect and what has to be changed to get that solved?
Thanks for your hints in advance.
No reaction on this topic lets me assume knx is not so no more intersting for OH-users and support and progress on knx-binding seems to be secondary, isn’t it?
Hey dont give up so fast. KNX secure is not tested and supported as non secure. You already posted here about it KNX secure - initial implementation - #9 by holgerf so you know its still not finished also by looking at the github entry its still not finished [knx] support for KNX secure · Issue #8872 · openhab/openhab-addons · GitHub I gave up using knx secure unless as knx secure is adressed more towards commercial setups where you have no control over the networking or the bus can be tapped or rf communication etc but there you dont use openhab there are other visu etc
I’m sure that a lot of users are using KNX (including me), but your problem sound very specific. Especially the KNX secure is not widely used.
It could also be a UI Bug. Do you see any error logs about not parseable configurations or other exceptions during startup?
I’m using a thing file based configuration for this device since years without any problems. Currently I’m running the same setup with openHAB 5.1.M4 also without any problems.
KNX IP secure should be more stable as the documentation says. I am running KNX IP secure setup since quite a while (Enertex IP Interface and file based config).
Routers are untested as I could never get hold of one or even two devices for testing.
Data secure works stable but only quietly listening (i.e. no initial reads and no writes) and with minor issues like showing devices offline when pa is set.
AFAIR the was exactly this problem mentioned a while ago and I could not reproduce.
The safest way to address an issue with KNX is by creating an issue on GitHub tagging user holgerfriedrich. If you don’t want to discuss here in the forum, please tag holgerf.
Can you please give more details about your setup? Thanks.
Small update: On latest 5.1-SNAPSHOT, I could not reproduce. I created two devices via the UI with most of the settings from the screenshot above. Both were still configured properly after restart.
I have now made a trial with the latest 5.1.0 snapshot, but w/o any difference. After restart the configuration for the MDT IP router changes to following parameters:
events.log during startup: 2025-12-17 10:24:43.412 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘knx:ip:0083-884016e7’ changed from UNINITIALIZED (NOT_YET_READY) to INITIALIZING
2025-12-17 10:24:43.416 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘knx:ip:0083-884016e7’ changed from INITIALIZING to UNKNOWN
2025-12-17 10:24:43.436 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘knx:device:0083-8440094b:9e5c33ef3f’ changed from UNINITIALIZED (NOT_YET_READY) to UNINITIALIZED (BRIDGE_UNINITIALIZED)
2025-12-17 10:24:43.442 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘knx:device:0083-8440094b:9287eddaff’ changed from UNINITIALIZED (NOT_YET_READY) to INITIALIZING
2025-12-17 10:24:43.459 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘knx:device:0083-8440094b:9287eddaff’ changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE)
2025-12-17 10:24:43.465 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘knx:device:0083-8440094b:e059adc993’ changed from UNINITIALIZED (NOT_YET_READY) to INITIALIZING
2025-12-17 10:24:43.466 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘knx:device:0083-8440094b:e059adc993’ changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE)
2025-12-17 10:24:43.467 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘knx:device:68d4ab0313:b26d1ad014’ changed from UNINITIALIZED (NOT_YET_READY) to UNINITIALIZED (BRIDGE_UNINITIALIZED)
2025-12-17 10:24:43.512 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘shelly:shellyplusht:e4b32331b7f0’ changed from UNINITIALIZED (NOT_YET_READY) to INITIALIZING
2025-12-17 10:24:43.519 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘knx:ip:0083-8440094b’ changed from UNINITIALIZED (NOT_YET_READY) to INITIALIZING
2025-12-17 10:24:43.522 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘knx:ip:0083-8440094b’ changed from INITIALIZING to UNKNOWN
2025-12-17 10:24:43.528 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘knx:device:0083-8440094b:ae61d4053c’ changed from UNINITIALIZED (NOT_YET_READY) to INITIALIZING
2025-12-17 10:24:43.568 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘knx:device:0083-8440094b:ae61d4053c’ changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE)
2025-12-17 10:24:44.811 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘knx:ip:0083-8440094b’ changed from UNKNOWN to OFFLINE (COMMUNICATION_ERROR): KNX Gerät meldet Fehler (KNXRemoteException, error response from control endpoint 192.168.100.118:3671: the requested connection type is not supported)
2025-12-17 10:24:44.863 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘knx:ip:0083-884016e7’ changed from UNKNOWN to ONLINE
2025-12-17 10:24:44.864 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘knx:device:0083-8440094b:9287eddaff’ changed from OFFLINE (BRIDGE_OFFLINE) to UNKNOWN
2025-12-17 10:24:44.864 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘knx:device:0083-8440094b:ae61d4053c’ changed from OFFLINE (BRIDGE_OFFLINE) to UNKNOWN
2025-12-17 10:24:44.865 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘knx:device:0083-8440094b:e059adc993’ changed from OFFLINE (BRIDGE_OFFLINE) to UNKNOWN
2025-12-17 10:24:45.516 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘shelly:shellyplusht:e4b32331b7f0’ changed from INITIALIZING to ONLINE (CONFIGURATION_PENDING): Gerät wird initialisiert oder im Schlafmodus.
2025-12-17 10:24:58.875 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘knx:device:0083-8440094b:e059adc993’ changed from UNKNOWN to OFFLINE
2025-12-17 10:25:10.885 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘knx:device:0083-8440094b:ae61d4053c’ changed from UNKNOWN to OFFLINE
2025-12-17 10:25:22.897 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘knx:device:0083-8440094b:9287eddaff’ changed from UNKNOWN to OFFLINE
2025-12-17 10:31:00.526 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘knx:ip:0083-8440094b’ changed from OFFLINE (COMMUNICATION_ERROR): KNX Gerät meldet Fehler (KNXRemoteException, error response from control endpoint 192.168.100.118:3671: the requested connection type is not supported) to OFFLINE
2025-12-17 10:31:00.531 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘knx:ip:0083-8440094b’ changed from OFFLINE to UNKNOWN
2025-12-17 10:31:02.020 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘knx:ip:0083-8440094b’ changed from UNKNOWN to ONLINE
openhab.log during startup: 2025-12-17 10:24:25.379 [INFO ] [org.openhab.core.Activator ] - Starting openHAB 5.1.0 (Build #5005)
2025-12-17 10:24:25.975 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Time zone set to ‘Europe/Berlin’.
2025-12-17 10:24:25.995 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Location set to ‘50.161580308464416,10.488019287586214’.
2025-12-17 10:24:25.997 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Locale set to ‘de_DE’.
2025-12-17 10:24:33.458 [WARN ] [.transport.servlet.ServletController] - Can’t find the request for http://192.168.100.152:8080/settings/things/'s Observer
2025-12-17 10:24:33.494 [WARN ] [.transport.servlet.ServletController] - Can’t find the request for http://192.168.100.152:8080/favicon.ico’s Observer
2025-12-17 10:24:34.377 [INFO ] [.core.model.lsp.internal.ModelServer] - Started Language Server Protocol (LSP) service on port 5007
2025-12-17 10:24:37.603 [INFO ] [nternal.manager.ShellyManagerServlet] - Shelly Manager gestartet und erreichbar unter http(s)://192.168.100.152:8080/shelly/manager
2025-12-17 10:24:41.402 [INFO ] [e.automation.internal.RuleEngineImpl] - Rule engine started.
2025-12-17 10:24:44.807 [ERROR] [et/IP Tunneling 192.168.100.118:3671] - establishing connection failed, error response from control endpoint 192.168.100.118:3671: the requested connection type is not supported
2025-12-17 10:25:45.811 [ERROR] [et/IP Tunneling 192.168.100.118:3671] - establishing connection failed, error response from control endpoint 192.168.100.118:3671: the requested connection type is not supported
2025-12-17 10:26:46.814 [ERROR] [et/IP Tunneling 192.168.100.118:3671] - establishing connection failed, error response from control endpoint 192.168.100.118:3671: the requested connection type is not supported
2025-12-17 10:27:47.817 [ERROR] [et/IP Tunneling 192.168.100.118:3671] - establishing connection failed, error response from control endpoint 192.168.100.118:3671: the requested connection type is not supported
2025-12-17 10:28:48.819 [ERROR] [et/IP Tunneling 192.168.100.118:3671] - establishing connection failed, error response from control endpoint 192.168.100.118:3671: the requested connection type is not supported
2025-12-17 10:29:49.822 [ERROR] [et/IP Tunneling 192.168.100.118:3671] - establishing connection failed, error response from control endpoint 192.168.100.118:3671: the requested connection type is not supported
2025-12-17 10:30:50.824 [ERROR] [et/IP Tunneling 192.168.100.118:3671] - establishing connection failed, error response from control endpoint 192.168.100.118:3671: the requested connection type is not supported
Possibly it could be an incompatibility with the MDT IP-Pouters? They have the latest firmware.
But it’s confusing for me that all works fine when configuration is manually adjusted after restart and get lost during start.
I have a similar behaviour, my Thing for the MDT Interface is jumping from Tunnel to Router. AFAIR others have mentioned this issue before.
My impression is that maybe some kind of auto discovery overwrites the settings of the already existing thing.
Effect is that after some days I loose the connection to the bus as the Router uses some multicast address, replacing the Tunnel setting and the IP address for the interface.
Don’t remember the exact release but afair it started some months ago. Maybe switching to text based config would prevent it, but I did not want to reconfigure all my knx Things to talk to the new IP Interface thing.
Thanks a lot for your fast reactionand trying to fix that. I have just now installed the RC2 version and have again not a proper working restart of the knx-system. Now the secure router mode in not changing during restart. This is really fixed. But I the broadcast IP-address of the knx IP-router is changing to the IP-address of the device itself. This has alo the effect the the knx system does not work. This is not always the case. sometimes the broadcast IP-address stay at the 224.0.23.12 and sometimes it changes to the device-address.
Maybe you have an idea what could be reason of this?
Thanks a lot in advance!
