OH2 & KNX Binding - maximum send attempts error

fra_molf · May 6, 2018, 9:09am

Environment: openHAB 2.2.0 Release Build
Binding: org.openhab.binding.knx-2.3.0-SNAPSHOT.jar
Config Parameters:

At least 2 times in a day I receive the following error:
ERROR] [et/IP Tunneling 192.168.x.y:3671] - close connection - maximum send attempts
tuwien.auto.calimero.KNXAckTimeoutException: maximum send attempts, no service acknowledgment received

After this error, the KNX device is offline and the binding stop working.

Any clue about this error ?

Thanks
Francesco

Udo_Hartmann · May 6, 2018, 5:02pm

Afaik knx2 binding needs openHAB2.3.0.

fra_molf · August 16, 2018, 8:03am

Same errors with OpenHAB 2.3.
Any clue?

Udo_Hartmann · August 16, 2018, 10:09am

Please try to leave Local KNX GA empty.

fra_molf · August 18, 2018, 1:49pm

Hi Udo,
Do you mean 0.0.0 ?

Thanks

Udo_Hartmann · August 19, 2018, 12:20pm

This will be the used default, but afaik you can just leave the field empty (no data at all)

fra_molf · August 19, 2018, 5:24pm

Same issue with 0.0.0.
If you don’t specify the Address by default is 0.0.0 and I cannot leave it blank.

Any clue ?
Thanks
Francesco

andrzej_szymkowicz · September 13, 2018, 7:07pm

I have the same problem. Any idea what is wrong?

Udo_Hartmann · September 14, 2018, 11:40am

Well, what’s your hardware? What’s your OS? What’s your Java version? openHAB version? exact configuration?

fra_molf · September 14, 2018, 12:52pm

In my case:

VM
OS: Debian GNU/Linux 9
JAVA:
openjdk version “1.8.0_181”
OpenJDK Runtime Environment (Zulu 8.31.0.1-linux64) (build 1.8.0_181-b02)
OpenJDK 64-Bit Server VM (Zulu 8.31.0.1-linux64) (build 25.181-b02, mixed mode)
openhab2: 2.3.0-1
CONFIG:

Bridge knx:ip:bridge [
ipAddress=“x.x.x.x”,
portNumber=3671,
localIp=“x.x.x.y”,
type=“TUNNEL”,
readingPause=50,
responseTimeout=10,
readRetriesLimit=3,
autoReconnectPeriod=60
/* localSourceAddr="" */
] {
Thing device generic [
fetch=true,
pingInterval=300,
readInterval=3600
] {

Thanks
Francesco

Udo_Hartmann · September 14, 2018, 2:28pm

VM: Did you setup network to be bridged?
localIp is the actual IP of the VM?

When using a generic device, please never set fetch = true nor a pingInterval at all. Please avoid to set readInterval, this parameter should only be used if absolutely necessary, and for sure not for every Channel.

fra_molf · September 14, 2018, 4:26pm

VM: Did you setup network to be bridged?
How I can do it ?
localIp is the actual IP of the VM?
Yes

When using a generic device, please never set fetch = true nor a pingInterval at all. Please avoid to set readInterval, this parameter should only be used if absolutely necessary, and for sure not for every Channel.
Ok I will do it. In the example reported in the official documentation this parameters are specified: https://www.openhab.org/addons/bindings/knx/#things

Regards,
Francesco

Udo_Hartmann · September 15, 2018, 8:51am

Yes, but the document states:

requires the address

for fetch and pingInterval. As you can’t set an address for a virtual device, you shall not use the parameters.
But of course you can define one thing per real device and set the physical addresses for these devices.

In question of bridged network: Which host system do you use?

fra_molf · September 15, 2018, 10:30am

Many thanks !
The VM is on a public cloud, and there a VPN connection between the VM and my home. I know, this is not a very common deployment…

I will let you know.

Regards,
Francesco

Udo_Hartmann · September 15, 2018, 5:46pm

Oh, I see. I’m pretty sure it is not recommended to use openHAB this way
I don’t know if it’s possible to connect to a local knx/IP gateway easily through a vpn tunnel

andrzej_szymkowicz · September 15, 2018, 8:47pm

HW - Raspberry Pi 3
installation is done using openhabian 2.3 with knxd installed on the same server (installation also via openhabian)
java - version
openjdk version “1.8.0_152”
OpenJDK Runtime Environment (Zulu Embedded 8.25.0.76-linux-aarch32hf) (build 1.8.0_152-b76)
OpenJDK Client VM (Zulu Embedded 8.25.0.76-linux-aarch32hf) (build 25.152-b76, mixed mode, Evaluation)

Bridge knx:ip:bridge [
ipAddress=“127.0.0.1”,
portNumber=3671,
localIp=“127.0.0.1”,
type=“TUNNEL”,
readingPause=50,
responseTimeout=10,
readRetriesLimit=3,
autoReconnectPeriod=60,
localSourceAddr=“0.0.0”]

Thanks
Andrzej

Udo_Hartmann · September 16, 2018, 12:27am

please try not to use 127.0.0.1 as localIp but the real IP Address of your Raspberry Pi. Maybe (I’m not sure about this point) it also will be better not to use 127.0.0.1 as ipAddress either.
Please consider to use ROUTER mode instead of TUNNEL (this would use 224.0.23.12, you won’t need to set the ipAddress at all but only localIp)

andrzej_szymkowicz · September 16, 2018, 7:22am

OK. I will try to changed IPs.

In meantime the problem occurred again, here are the logs, maybe it will brings some new ideas about the problem reason:

2018-09-16 07:59:30.052 [WARN ] [p.KNXnet/IP Tunneling 127.0.0.1:3671] - received disconnect response status 0x21 (no active data connection with that ID)

2018-09-16 07:59:30.098 [ERROR] [p.KNXnet/IP Tunneling 127.0.0.1:3671] - close connection - maximum send attempts

tuwien.auto.calimero.KNXAckTimeoutException: maximum send attempts, no service acknowledgment received

at tuwien.auto.calimero.knxnetip.ConnectionBase.send(ConnectionBase.java:250) ~[266:org.openhab.binding.knx:2.3.0]

at tuwien.auto.calimero.knxnetip.KNXnetIPTunnel.send(KNXnetIPTunnel.java:178) ~[266:org.openhab.binding.knx:2.3.0]

at tuwien.auto.calimero.link.KNXNetworkLinkIP.onSend(KNXNetworkLinkIP.java:243) ~[266:org.openhab.binding.knx:2.3.0]

at tuwien.auto.calimero.link.AbstractLink.send(AbstractLink.java:351) ~[266:org.openhab.binding.knx:2.3.0]

at tuwien.auto.calimero.link.KNXNetworkLinkIP.sendRequestWait(KNXNetworkLinkIP.java:222) ~[266:org.openhab.binding.knx:2.3.0]

at tuwien.auto.calimero.process.ProcessCommunicatorImpl.write(ProcessCommunicatorImpl.java:401) ~[266:org.openhab.binding.knx:2.3.0]

at tuwien.auto.calimero.process.ProcessCommunicatorImpl.write(ProcessCommunicatorImpl.java:359) ~[266:org.openhab.binding.knx:2.3.0]

at org.openhab.binding.knx.internal.client.AbstractKNXClient.sendToKNX(AbstractKNXClient.java:444) ~[266:org.openhab.binding.knx:2.3.0]

at org.openhab.binding.knx.internal.client.AbstractKNXClient.writeToKNX(AbstractKNXClient.java:410) ~[266:org.openhab.binding.knx:2.3.0]

at org.openhab.binding.knx.internal.handler.DeviceThingHandler.lambda$6(DeviceThingHandler.java:211) ~[266:org.openhab.binding.knx:2.3.0]

at org.openhab.binding.knx.internal.handler.DeviceThingHandler.withKNXType(DeviceThingHandler.java:121) [266:org.openhab.binding.knx:2.3.0]

at org.openhab.binding.knx.internal.handler.DeviceThingHandler.withKNXType(DeviceThingHandler.java:115) [266:org.openhab.binding.knx:2.3.0]

at org.openhab.binding.knx.internal.handler.DeviceThingHandler.handleCommand(DeviceThingHandler.java:208) [266:org.openhab.binding.knx:2.3.0]

at sun.reflect.GeneratedMethodAccessor1199.invoke(Unknown Source) ~[?:?]

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]

at java.lang.reflect.Method.invoke(Method.java:498) ~[?:?]

at org.eclipse.smarthome.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:153) [103:org.eclipse.smarthome.core:0.10.0.oh230]

at org.eclipse.smarthome.core.internal.common.InvocationHandlerSync.invoke(InvocationHandlerSync.java:59) [103:org.eclipse.smarthome.core:0.10.0.oh230]

at com.sun.proxy.$Proxy200.handleCommand(Unknown Source) [266:org.openhab.binding.knx:2.3.0]

at org.eclipse.smarthome.core.thing.internal.profiles.ProfileCallbackImpl.handleCommand(ProfileCallbackImpl.java:75) [110:org.eclipse.smarthome.core.thing:0.10.0.oh230]

at org.eclipse.smarthome.core.thing.internal.profiles.SystemFollowProfile.onStateUpdateFromItem(SystemFollowProfile.java:61) [110:org.eclipse.smarthome.core.thing:0.10.0.oh230]

at sun.reflect.GeneratedMethodAccessor214.invoke(Unknown Source) ~[?:?]

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]

at java.lang.reflect.Method.invoke(Method.java:498) ~[?:?]

at org.eclipse.smarthome.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:153) [103:org.eclipse.smarthome.core:0.10.0.oh230]

at org.eclipse.smarthome.core.internal.common.Invocation.call(Invocation.java:53) [103:org.eclipse.smarthome.core:0.10.0.oh230]

at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]

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) [?:?]

2018-09-16 07:59:31.534 [ERROR] [nal.common.AbstractInvocationHandler] - An error occurred while calling method ‘ThingHandler.handleCommand()’ on ‘org.openhab.binding.knx.internal.handler.DeviceThingHandler@d1bb85’: process communicator detached

java.lang.IllegalStateException: process communicator detached

at tuwien.auto.calimero.process.ProcessCommunicatorImpl.write(ProcessCommunicatorImpl.java:400) ~[266:org.openhab.binding.knx:2.3.0]