Dear all,
I’m trying to upgrade from KNX1 to KNX2, but this just drives me crazy…
In principle, I managed to control the KNX also with KNX2 quite fast, but I can’t get rid of the “response timeout waiting for confirmation” warning, no matter what I try.
My HW/SW configuration is OH2 2.4.0 on raspbian, the KNX-IF is a MDT SCN-IP000.01.
The .things file looks like
Bridge knx:ip:SCN-IP "KNX/IP Gateway" @ "KNX" [
type="TUNNEL",
ipAddress="192.168.178.27",
portNumber=3671,
localIp="192.168.178.41",
readingPause=500,
responseTimeout=500,
readRetriesLimit=3,
autoReconnectPeriod=0,
localSourceAddr="1.0.1"
] {
Thing device AKD-0401_1 "Dimmer 1 (4 Ch)" @ "KNX" [
address="1.0.11",
fetch=false,
pingInterval=600,
readInterval=0
] {
Type dimmer : Ch_1 "Dimmer 1.1" [ switch="2/1/17+<2/2/17", position="2/4/17+<2/5/17", increaseDecrease="2/3/17" ]
Type dimmer : Ch_2 "Dimmer 1.2" [ switch="2/1/18+<2/2/18", position="2/4/18+<2/5/18", increaseDecrease="2/3/18" ]
Type dimmer : Ch_3 "Dimmer 1.3" [ switch="2/1/16+<2/2/16", position="2/4/16+<2/5/16", increaseDecrease="2/3/16" ]
Type dimmer : Ch_4 "Dimmer 1.4" [ switch="2/1/19+<2/2/19", position="2/4/19+<2/5/19", increaseDecrease="2/3/19" ]
}
}
Soon as OH2 is starting, I get continuous WARNings like
2019-02-10 17:06:28.882 [WARN ] [net/IP Tunneling 192.168.178.27:3671] - response timeout waiting for confirmation
tuwien.auto.calimero.KNXTimeoutException: no confirmation reply received for 1.0.1->2/5/18 L_Data.req, low priority hop count 6 repeat, tpdu 00 00
at tuwien.auto.calimero.knxnetip.ClientConnection.doExtraBlockingModes(ClientConnection.java:244) ~[?:?]
at tuwien.auto.calimero.knxnetip.ConnectionBase.send(ConnectionBase.java:258) ~[?:?]
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) [?:?]
As I did not find any solution for this issue, I decided to ignore the warnings by setting the log-level for the KNX-IF to ERROR, but with no success.
Logger │ Level
─────────────────────────────────────┼──────
ROOT │ WARN
...
org.openhab │ INFO
org.openhab.binding.knx │ ERROR
...
tuwien.auto.calimero │ ERROR
But still the WARNings appear in the log file.
Has anyone got a clue
- If the MDT KNX-IP000.01is not fully supported?
- If I’ve got an issue in my Things file?
- How to change the Log-Level for the above warnings?
For the time beeing I will switch back to KNX1.
Regards,
Dirk