[Xnet/IP Tunneling] - close connection - maximum send attempts tuwien.auto.calimero.KNXAckTimeoutException: maximum send attempts, no service acknowledgment received

Add-ons Bindings
1

My knx binding goes offline at apparently regular intervals at 5:25 (each few days)

Installation is on a synology diskstation.

openhab Version and knx binding is 2.4.0

I never had this problem with binding 1.x

This is my openhab.log

2019-06-22 05:25:31.376 [ERROR] [Xnet/IP Tunneling 192.168.0.226:3671] - close connection - maximum send attempts
tuwien.auto.calimero.KNXAckTimeoutException: maximum send attempts, no service acknowledgment received

at the same time in my event.log

2019-06-22 05:25:34.106 [hingStatusInfoChangedEvent] - ‘knx:ip:bridge’ changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): maximum send attempts
2019-06-22 05:25:34.163 [hingStatusInfoChangedEvent] - ‘knx:device:bridge:generic’ changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2019-06-22 05:25:34.166 [hingStatusInfoChangedEvent] - ‘knx:device:bridge:generic’ changed from OFFLINE (BRIDGE_OFFLINE) to OFFLINE
2019-06-22 05:25:34.240 [hingStatusInfoChangedEvent] - ‘knx:ip:bridge’ changed from OFFLINE (COMMUNICATION_ERROR): maximum send attempts to OFFLINE (COMMUNICATION_ERROR)
2019-06-22 05:25:34.243 [hingStatusInfoChangedEvent] - ‘knx:device:bridge:generic’ changed from OFFLINE to OFFLINE (BRIDGE_OFFLINE)
2019-06-22 05:25:34.246 [hingStatusInfoChangedEvent] - ‘knx:ip:bridge’ changed from OFFLINE (COMMUNICATION_ERROR) to ONLINE
2019-06-22 05:25:34.249 [hingStatusInfoChangedEvent] - ‘knx:device:bridge:generic’ changed from OFFLINE (BRIDGE_OFFLINE) to UNKNOWN
2019-06-22 05:25:49.319 [hingStatusInfoChangedEvent] - ‘knx:ip:bridge’ changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): maximum send attempts
2019-06-22 05:25:49.344 [hingStatusInfoChangedEvent] - ‘knx:device:bridge:generic’ changed from UNKNOWN to OFFLINE (BRIDGE_OFFLINE)
2019-06-22 05:25:49.347 [hingStatusInfoChangedEvent] - ‘knx:device:bridge:generic’ changed from OFFLINE (BRIDGE_OFFLINE) to OFFLINE
2019-06-22 05:25:49.351 [hingStatusInfoChangedEvent] - ‘knx:ip:bridge’ changed from OFFLINE (COMMUNICATION_ERROR): maximum send attempts to OFFLINE (COMMUNICATION_ERROR)
2019-06-22 05:25:49.354 [hingStatusInfoChangedEvent] - ‘knx:device:bridge:generic’ changed from OFFLINE to OFFLINE (BRIDGE_OFFLINE)
2019-06-22 05:25:59.351 [hingStatusInfoChangedEvent] - ‘knx:ip:bridge’ changed from OFFLINE (COMMUNICATION_ERROR) to OFFLINE (COMMUNICATION_ERROR): timeout connecting to control endpoint /192.168.0.226:3671
2019-06-22 05:26:00.358 [hingStatusInfoChangedEvent] - ‘knx:ip:bridge’ changed from OFFLINE (COMMUNICATION_ERROR): timeout connecting to control endpoint /192.168.0.226:3671 to ONLINE
2019-06-22 05:26:00.361 [hingStatusInfoChangedEvent] - ‘knx:device:bridge:generic’ changed from OFFLINE (BRIDGE_OFFLINE) to UNKNOWN
2019-06-22 05:26:00.392 [hingStatusInfoChangedEvent] - ‘knx:device:bridge:generic’ changed from UNKNOWN to ONLINE

this is the first part of my knx.things file

Bridge knx:ip:bridge [
ipAddress=“192.168.0.226”,
portNumber=3671,
localIp=“192.168.0.205”,
type=“TUNNEL”,
readingPause=50,
responseTimeout=10,
readRetriesLimit=3,
autoReconnectPeriod=1,
localSourceAddr=“0.0.0”
] {
Thing device generic [
address=“1.1.1”,
fetch=false,
pingInterval=600,
readInterval=0
] {

due to this Openhab is not reliable and needs to be rebooted constanly

please help, …

2

Less is more. Please change your configuration to

Bridge knx:ip:bridge [
    ipAddress="192.168.0.226",
    type="TUNNEL"
 ] {
 Thing device generic {
    ...
 }
}

Please be aware that a generic device won’t have an individual (in german “physikalische”) address, as it’s, well, generic :wink:

Please NEVER set autoReconnectPeriod to 1 as it’s very unlikely that knx is able to rebuild all item states within a second. In the upcoming version there will be an update which will ignore any value less than 30 (and 30 is only applicable to very small knx installations)

3

De KNX binding is, after about a week, again offline, this time the errors seem to be different.

First error, which doensn’t cause the binding to go offline, but occurs frequently in the log is

2019-06-29 02:11:20.874 [INFO ] [io.openhabcloud.internal.CloudClient] - Disconnected from the openHAB Cloud service (UUID = [HIDDEN], base URL = http://localhost:8080)
2019-06-29 02:22:59.706 [INFO ] [io.openhabcloud.internal.CloudClient] - Connected to the openHAB Cloud service (UUID = [HIDDEN], base URL = http://localhost:8080)
2019-06-30 00:25:58.700 [ERROR] [io.openhabcloud.internal.CloudClient] - Socket.IO error: {}
io.socket.engineio.client.EngineIOException: websocket error
at io.socket.engineio.client.Transport.onError(Transport.java:71) [207:org.openhab.io.openhabcloud:2.4.0]
at io.socket.engineio.client.transports.WebSocket.access$500(WebSocket.java:28) [207:org.openhab.io.openhabcloud:2.4.0]
at io.socket.engineio.client.transports.WebSocket$2$5.run(WebSocket.java:150) [207:org.openhab.io.openhabcloud:2.4.0]
at io.socket.thread.EventThread$2.run(EventThread.java:80) [207:org.openhab.io.openhabcloud:2.4.0]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
at java.lang.Thread.run(Thread.java:748) [?:?]
Caused by: java.io.EOFException
at okio.RealBufferedSource.require(RealBufferedSource.java:59) ~[?:?]
at okio.RealBufferedSource.readByte(RealBufferedSource.java:72) ~[?:?]
at okhttp3.internal.ws.WebSocketReader.readHeader(WebSocketReader.java:115) ~[?:?]
at okhttp3.internal.ws.WebSocketReader.processNextFrame(WebSocketReader.java:104) ~[?:?]
at okhttp3.internal.ws.RealWebSocket.readMessage(RealWebSocket.java:97) ~[?:?]
at okhttp3.ws.WebSocketCall.createWebSocket(WebSocketCall.java:152) ~[?:?]
at okhttp3.ws.WebSocketCall.access$000(WebSocketCall.java:41) ~[?:?]
at okhttp3.ws.WebSocketCall$1.onResponse(WebSocketCall.java:97) ~[?:?]
at okhttp3.RealCall$AsyncCall.execute(RealCall.java:126) ~[?:?]
at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32) ~[?:?]
… 3 more

But the one thats caused the binding to go offlline (i think) is :

2019-06-28 22:11:16.451 [WARN ] [Xnet/IP Tunneling 192.168.0.226:3671] - connection state response: server could not find active data connection with specified ID (channel 19)
2019-06-28 22:11:36.396 [WARN ] [Xnet/IP Tunneling 192.168.0.226:3671] - connection state response: server could not find active data connection with specified ID (channel 19)
2019-06-28 22:11:58.073 [WARN ] [Xnet/IP Tunneling 192.168.0.226:3671] - received disconnect response status 0x21 (no active data connection with that ID)
2019-06-28 22:11:58.224 [WARN ] [Xnet/IP Tunneling 192.168.0.226:3671] - close connection - no heartbeat response
2019-06-28 22:11:58.919 [ERROR] [Xnet/IP Tunneling 192.168.0.226:3671] - establishing connection failed, null

this is the events.log at that time

2019-06-28 22:11:59.008 [hingStatusInfoChangedEvent] - ‘knx:ip:bridge’ changed from ONLINE to OFFLINE (COMMUNICATION_ERROR)
2019-06-28 22:11:59.011 [hingStatusInfoChangedEvent] - ‘knx:device:bridge:generic’ changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)

My knx.things looks like this now

Bridge knx:ip:bridge [
ipAddress=“192.168.0.226”,
type=“TUNNEL”
] {
Thing device generic {

any help would be greatly apprciated, I need this to be stable

4

Was this ever resolved?

5

yes, by re-installing and upgrading to the latest version

6

Hi,
i also have the same issue since I upgraded from KNX binding 1.0 to 2.0.
I have my house completly installed with KNX components and therefore, configured a lot of KNX things.
The error described within this post occurs regularly, ~ every 3-4 days. I have to restart Openhab 2.5 to fix that.
I tried several configurations, some which were mentioned in other posts, but nothing worked for me.
In my point of view, the KNX 2.0 binding is (compared to version 1.0) unreliable and buggy.

My plan is to try Home Assistant because I need a reliable smart home system, which is currently not available for me in case of Openhab 2.5.
The issue may have the root cause in calimero which is used in the KNX binding, I found the following post: maximum send attempts, no service acknowledgment received · Issue #88 · calimero-project/calimero-core · GitHub

@tomd: I wonder if a complete reinstall solved that problem for you. Did you use a complete new Raspberry image for Openhab? And without any change to the KNX configuration?

Thank you in advance
Christian

8

yes, by a complete reinstall and upgrade to the version 2.5 o a synology diskstation