OH3 KNX: Getting disconnected from time to time

Add-ons Bindings
1

Hi,
I’m using openhab with my KNX installation for years now but unfortunately having big problems the last months. Openhab is loosing the connection from time to time to my KNX bus. Sometimes running for 1 or 2 days without problems, sometimes disconnected every 1-2 hours.
I updated from openhab 2.5 to 3.1 with a fresh installation.
I recently changed my IP-Interface from EIBPort to MDT, but did not help a lot.

This is my configuration:

Bridge knx:ip:bridge [ 
    type="TUNNEL",
    ipAddress="192.168.178.226",
    autoReconnectPeriod=60
] {
    Thing device Binaereingang18 [
        address="1.0.18",
        readInterval=0
    ] { 
        Type contact        : BWM_DG                    "Door"     [ ga="5/0/101" ]
        Type contact        : BWM_OG                    "Door"     [ ga="5/1/101" ]
        Type contact        : BWM_EG                    "Door"     [ ga="5/2/101" ]
        Type contact        : BWM_KG                    "Door"     [ ga="5/3/101" ]
        Type contact        : BWM_Technik_KG            "Door"     [ ga="5/3/102" ]
    }

    Thing device Praesenzmelder20 [
        address="1.0.20"
    ] {
        Type contact        : BWM_KG_Waschraum              "Door"      [ ga="1/3/15"  ]
    }

... more devices added here
]

I assume it has to do with the “polling” of the device, because in my log files I alway have a polling just before the timeout.

`2021-12-19 07:25:17.480 [DEBUG] [rnal.handler.AbstractKNXThingHandler] - Polling individual address ‘1.0.20’
2021-12-19 07:25:20.484 [WARN ] [et/IP Tunneling 192.168.178.226:3671] - response timeout waiting for confirmation
tuwien.auto.calimero.KNXTimeoutException: no confirmation reply received for 0.0.0->1.0.20 L_Data.req, system priority hop count 6 repeat, tpdu 80
at tuwien.auto.calimero.knxnetip.ClientConnection.doExtraBlockingModes(ClientConnection.java:244) ~[?:?]

[…]

2021-12-19 07:26:03.849 [DEBUG] [nx.internal.client.AbstractKNXClient] - The KNX network link was detached from the process communicator
2021-12-19 07:26:03.854 [DEBUG] [nx.internal.client.AbstractKNXClient] - Bridge knx:ip:bridge is disconnecting from the KNX bus
2021-12-19 07:26:03.854 [DEBUG] [nx.internal.client.AbstractKNXClient] - KNX link has been lost (reason: server request on object tunneling link (closed) 192.168.178.226:3671 TP1 medium, device 0.0.0, hopcount 6)
`

Is there any need for a polling of the device at all?
I actually understand readIntervall=0 as default, assuming it is not set in my configuration?

Any help appreciated, thank you very much. I’m so unhappy Openhab is working so unreliable :frowning: in my case and do not find out a way.

Best regards,
Simon

2

Check the following post:
https://community.openhab.org/t/solved-knx-version-2-x-binding-losing-its-connection-almost-every-day/75292/1

I faced disconnections as well and this solved it for me

3

Thank you, I changed my config and monitor the changes now.

4

Unfortunately no improvement. I still receive disconnections, at least every 1-2 hours.

What I did:
I changed my IP Interface from EIBPort to one from MDT.
I made a fresh installation of Openhab 3.2.0 (previsously run 3.1.0)
I made a very simple setup of my configuration. Only one Thing (the KNX bride) with minimal attributes and only 5 items, no rules, nothing else.

And still getting disconnections.

Anyone with a good idea how I can get deeper in the system and find the problem

My simple setup of thing file

Bridge knx:ip:bridge [ 
    type="TUNNEL",
    ipAddress="192.168.178.226",
    autoReconnectPeriod=60
] {
    Thing device generic [] 
    {
        Type contact        : BWM_DG                    "Door"     [ ga="5/0/101" ]
        Type contact        : BWM_OG                    "Door"     [ ga="5/1/101" ]
        Type contact        : BWM_EG                    "Door"     [ ga="5/2/101" ]
        Type contact        : BWM_KG                    "Door"     [ ga="5/3/101" ]
        Type contact        : BWM_Technik_KG            "Door"     [ ga="5/3/102" ]
    }
  }
5

My solution now is to use an ip router instead of an ip interface. After installing a router everything is working as expected.