Knx stopped working after update to 3.3.0

Hi, I have a problem after update:

[ERROR] [KNXnet/IP Tunneling] - establishing connection failed, timeout connecting to control endpoint

2022-08-01 18:19:17.267 [DEBUG] [nx.internal.client.AbstractKNXClient] - Error connecting to the bus: timeout connecting to control endpoint timeout connecting to control endpoint

at ~[?:?]

at ~[?:?]

at ~[?:?]

at org.openhab.binding.knx.internal.client.IPClient.getConnection( ~[?:?]

at org.openhab.binding.knx.internal.client.IPClient.createKNXNetworkLinkIP( ~[?:?]

at org.openhab.binding.knx.internal.client.IPClient.establishConnection( ~[?:?]

at org.openhab.binding.knx.internal.client.AbstractKNXClient.connect( ~[?:?]

at [?:?]

at java.util.concurrent.ScheduledThreadPoolExecutor$ [?:?]

at java.util.concurrent.ThreadPoolExecutor.runWorker( [?:?]

at java.util.concurrent.ThreadPoolExecutor$ [?:?]

at [?:?]

2022-08-01 18:19:17.276 [DEBUG] [nx.internal.client.AbstractKNXClient] - Bridge knx:ip:bridge is disconnecting from the KNX bus

My thing is here:

Bridge knx:ip:bridge [  
] {
    Thing device generic "KNX QAX 913" [
    ] {

Type number          : knx_door1_R  "Dveře 1 (Garáž) "  [ga="2.001:<0/4/6"]
Type number          : knx_door2_R  "Dveře 2 "  [ga="2.001:<0/4/7"]

Type number          : knx_light1_R  "Světlo 1 "  [ga="2.001:<0/4/8"]
Type number          : knx_light2_R  "Světlo 2 "  [ga="2.001:<0/4/10"]
Type number          : knx_light3_R  "Světlo 3 "  [ga="2.001:<0/4/11"]
Type number          : knx_light4_R  "Světlo 4 "  [ga="2.001:<0/4/"]


When I downgrade to 3.2.0, it works flawlessly. Does anyone solve this kind of problem? Thank you for help.

Upgraded to 3.3.0 without any issue. Maybe restart your bridge after upgrading?

Hello Pavel,

I have same issue, after Upgrade to V3.3.0.

Connection to KNX Gateway flaps continously, after reboot of raspi it works for some time again.

How do you do the downgrade ?


Same Issue.
KNX not longer working with Siemens N148/22

this is not needed either the bus is working or not

Now most of the time connection issues are not due to openhab but due to the networking inside your home.

Connection State request / response
Connection state request / response can be considered as a heartbeat mechanism. It enables KNXnet/IP client to ping the server in regular intervals (every 60 seconds). KNXnet/IP server responds to sent Connection State request letting the client know that it is still there and that everything is ok.

In case that the KNXnet\IP server does not respond to the sent Connection State request client will try to resend the request and eventually client will drop the connection. Similar thing will happen if the client fails to send the Connection State request. After a while (120 seconds) server will conclude that the client is not available anymore and it will terminate the tunnelling connection.

Fresh installation of Openhab 3.3.0 solved the problem.