Did you check that knxd is working correctly?
knxd is also used for other software and working without any problems (in tunnel mode)
OK. Finally openhba is working in Router mode with knxd. We will see if problem occurs again.
I’m about to go crazy! Sending are working in Router mode but statuses are not coming to openhab.
Can someone show example of openhab 2.3 knxd (both installed via openhabian) properly working!!!
Same issue with Raspberry Pi 3:
2018-09-17 21:53:15.421 [ERROR] [et/IP Tunneling 192.168.214.201: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) ~[?:?]
What type of knx/IP gateway do you use? Did you setup the correct ip and localIp?
KNX/IP router: https://www.schneider-electric.com/en/product/MTN680329/knx-ip-router-reg-k%2C-light-grey/
IP address are correct.
Thanks
Same problem here after 2-3days since update to OH2.4M5 (running KNX1 before with OH2.2):
[ERROR] [NXnet/IP Tunneling 192.168.1.10:3671] - close connection - maximum send attempts
tuwien.auto.calimero.KNXAckTimeoutException: maximum send attempts, no service acknowledgment received
Using MDT KNX IP Interface SCN-IP000.02 in TUNNEL mode and following configuration in KNX2 binding:
Bridge knx:ip:myKNXbridge [
ipAddress=“192.168.1.10”,
portNumber=3671,
type=“TUNNEL”,
readingPause=50,
responseTimeout=10,
readRetriesLimit=3,
autoReconnectPeriod=0,
localSourceAddr=“15.15.251”,
useNAT=true
] {
Hey everybody,
i’ve got the same Problem on one of my OpenHAB installations. HW is a synology Rackstation (RS818+).
The System runs for some days or weeks and then suddenly the error appears.
I tried to set
autoReconnectPeriod to 60.
After saveing OH reloaded knx.things and everything works for now. I will have a look at it an see how Long this works.
IP / KNX IF is Siemens N151
Any News About this?
Hmm… no real solution here yet?
I had:
openhab 2.3
knx 2.3 binding
knxd 0.14.25
all on the same raspberry pi 3+
running since august 2018 without a problem
I have upgraded to end of decemer to:
openhab 2.4
knx 2.4 binding
knxd 0.14.25
all on the same raspberry pi 3+
running since then without a problem, until yesterday
Aparrently openhab wasn’t connected to knxd anymore.
Trying to turn on a light from openhab2 didn’t work.
Send the command appropriate command to knxd with knxtool was working.
So I restarted openhab2. After restarting openhab2 all was back up and running
This is the last knx related message in the logs:
2019-02-02 03:04:01.003 [WARN ] [KNXnet/IP Tunneling 192.168.0.8:3671] - received disconnect response status 0x21 (no active data connection with that ID)
2019-02-02 03:04:01.043 [WARN ] [KNXnet/IP Tunneling 192.168.0.8:3671] - connection state response: server could not find active data connection with specified ID (channel 1)
2019-02-02 03:04:01.006 [ERROR] [KNXnet/IP Tunneling 192.168.0.8: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) ~[?:?]
at tuwien.auto.calimero.knxnetip.KNXnetIPTunnel.send(KNXnetIPTunnel.java:178) ~[?:?]
at tuwien.auto.calimero.link.KNXNetworkLinkIP.onSend(KNXNetworkLinkIP.java:243) ~[?:?]
at tuwien.auto.calimero.link.AbstractLink.send(AbstractLink.java:351) ~[?:?]
at tuwien.auto.calimero.link.KNXNetworkLinkIP.sendRequestWait(KNXNetworkLinkIP.java:222) ~[?:?]
at tuwien.auto.calimero.mgmt.TransportLayerImpl.connect(TransportLayerImpl.java:327) ~[?:?]
at tuwien.auto.calimero.mgmt.ManagementClientImpl.send(ManagementClientImpl.java:796) ~[?:?]
at tuwien.auto.calimero.mgmt.ManagementClientImpl.sendWait2(ManagementClientImpl.java:824) ~[?:?]
at tuwien.auto.calimero.mgmt.ManagementClientImpl.readDeviceDesc(ManagementClientImpl.java:447) ~[?:?]
at tuwien.auto.calimero.mgmt.ManagementProceduresImpl.isAddressOccupied(ManagementProceduresImpl.java:310) ~[?:?]
at org.openhab.binding.knx.internal.client.AbstractKNXClient.isReachable(AbstractKNXClient.java:338) ~[?:?]
at org.openhab.binding.knx.handler.AbstractKNXThingHandler.pollDeviceStatus(AbstractKNXThingHandler.java:144) ~[?:?]
at org.openhab.binding.knx.handler.AbstractKNXThingHandler.lambda$1(AbstractKNXThingHandler.java:184) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [?:?]
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) [?:?]
2019-02-02 03:04:01.173 [WARN ] [KNXnet/IP Tunneling 192.168.0.8:3671] - received service acknowledgment with wrong send sequence 0, expected 1 - ignored
2019-02-02 03:04:01.168 [ERROR] [calimero.link.192.168.0.8:3671 ] - send error, closing link
java.lang.InterruptedException: null
at java.lang.Object.wait(Native Method) ~[?:?]
at tuwien.auto.calimero.knxnetip.ConnectionBase.waitForStateChange(ConnectionBase.java:541) ~[?:?]
at tuwien.auto.calimero.knxnetip.ConnectionBase.send(ConnectionBase.java:242) ~[?:?]
at tuwien.auto.calimero.knxnetip.KNXnetIPTunnel.send(KNXnetIPTunnel.java:178) ~[?:?]
at tuwien.auto.calimero.link.KNXNetworkLinkIP.onSend(KNXNetworkLinkIP.java:243) ~[?:?]
at tuwien.auto.calimero.link.AbstractLink.send(AbstractLink.java:351) ~[?:?]
at tuwien.auto.calimero.link.KNXNetworkLinkIP.sendRequestWait(KNXNetworkLinkIP.java:222) ~[?:?]
at tuwien.auto.calimero.process.ProcessCommunicatorImpl.readFromGroup(ProcessCommunicatorImpl.java:418) ~[?:?]
at tuwien.auto.calimero.process.ProcessCommunicatorImpl.read(ProcessCommunicatorImpl.java:346) ~[?:?]
at org.openhab.binding.knx.internal.client.AbstractKNXClient.readNextQueuedDatapoint(AbstractKNXClient.java:284) ~[?:?]
at org.openhab.binding.knx.internal.client.AbstractKNXClient.lambda$1(AbstractKNXClient.java:199) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [?:?]
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) [?:?]
2019-02-02 03:04:11.275 [ERROR] [KNXnet/IP Tunneling 192.168.0.8:3671] - establishing connection failed, null
It happened again today. All knx Things where offline. This time I restarted only the knx binding bundle and all started working again. Any suggestions about what I can do to figure out this problem?
same here works for a while end crashes. looks like the binding crash and can’t continue. restarting the binding fixes the problem…is there a way to schedule a script so that it can restart the service automatically until the problem fixed ? can be time based as well.