[Gelöst] [V1.5 RC 8] - KNX-Problem aus OpenHAB Container - Ausbleibende Confirmations

[peti69]

Hallo,

im Log meiner OpenHAB 1 Installation erhalte ich KNX-Fehlermeldungen.

Das ist die erste Auffälligkeit:

Code: Alles auswählen

2019-10-18 14:00:03.508 [WARN ] [.b.knx.internal.bus.KNXBinding] - Value 'OFF' could not be sent to the KNX bus using datapoint 'command DP 1/1/10 Licht_EG_Wohnen_Vitrine, DPT main 0 id 1.001, low priority' - retrying one time: no confirmation reply received

Ab hier geht es weiter:

Code: Alles auswählen

2019-10-18 15:35:03.010 [WARN ] [.b.knx.internal.bus.KNXBinding] - Value 'OFF' could not be sent to the KNX bus using datapoint 'command DP 0/1/60 Licht_Garage, DPT main 0 id 1.001, low priority' - retrying one time: no confirmation reply received
2019-10-18 15:35:06.011 [WARN ] [.b.knx.internal.bus.KNXBinding] - Value 'OFF' could not be sent to the KNX bus using datapoint 'command DP 3/6/4 Zirkulationspumpe, DPT main 0 id 1.001, low priority' - retrying one time: no confirmation reply received
2019-10-18 15:35:09.013 [ERROR] [.b.knx.internal.bus.KNXBinding] - Value 'OFF' could not be sent to the KNX bus using datapoint 'command DP 0/1/60 Licht_Garage, DPT main 0 id 1.001, low priority' - giving up after second try: no confirmation reply received
2019-10-18 15:35:12.014 [ERROR] [.b.knx.internal.bus.KNXBinding] - Value 'OFF' could not be sent to the KNX bus using datapoint 'command DP 3/6/4 Zirkulationspumpe, DPT main 0 id 1.001, low priority' - giving up after second try: no confirmation reply received
2019-10-18 15:35:13.426 [WARN ] [tuwien.auto.calimero          ] - KNXnet/IP Tunneling 192.168.25.9:3674: connection state response status: server detected error concerning the KNX bus/subsystem connection
2019-10-18 15:35:15.016 [WARN ] [.b.knx.internal.bus.KNXBinding] - Value 'CLOSED' could not be sent to the KNX bus using datapoint 'state DP 3/6/7 WW_ZPA_Pumpenlauf_Notwendig, DPT main 0 id 1.019, low priority' - retrying one time: no confirmation reply received
2019-10-18 15:35:18.018 [WARN ] [.b.knx.internal.bus.KNXBinding] - Value 'OFF' could not be sent to the KNX bus using datapoint 'command DP 3/1/4 Windalarm, DPT main 0 id 1.001, low priority' - retrying one time: no confirmation reply received
2019-10-18 15:35:21.019 [WARN ] [.b.knx.internal.bus.KNXBinding] - Value 'OFF' could not be sent to the KNX bus using datapoint 'command DP 3/1/3 Regenalarm, DPT main 0 id 1.001, low priority' - retrying one time: no confirmation reply received
2019-10-18 15:35:23.426 [WARN ] [tuwien.auto.calimero          ] - KNXnet/IP Tunneling 192.168.25.9:3674: connection state response status: server detected error concerning the KNX bus/subsystem connection
2019-10-18 15:35:24.021 [ERROR] [.b.knx.internal.bus.KNXBinding] - Value 'CLOSED' could not be sent to the KNX bus using datapoint 'state DP 3/6/7 WW_ZPA_Pumpenlauf_Notwendig, DPT main 0 id 1.019, low priority' - giving up after second try: no confirmation reply received
2019-10-18 15:35:27.023 [ERROR] [.b.knx.internal.bus.KNXBinding] - Value 'OFF' could not be sent to the KNX bus using datapoint 'command DP 3/1/4 Windalarm, DPT main 0 id 1.001, low priority' - giving up after second try: no confirmation reply received
2019-10-18 15:35:30.024 [ERROR] [.b.knx.internal.bus.KNXBinding] - Value 'OFF' could not be sent to the KNX bus using datapoint 'command DP 3/1/3 Regenalarm, DPT main 0 id 1.001, low priority' - giving up after second try: no confirmation reply received
2019-10-18 15:35:33.026 [WARN ] [.b.knx.internal.bus.KNXBinding] - Value 'OFF' could not be sent to the KNX bus using datapoint 'command DP 1/1/13 Steckdose_EG_Wohnen_Schrank, DPT main 0 id 1.001, low priority' - retrying one time: no confirmation reply received
2019-10-18 15:35:33.427 [WARN ] [tuwien.auto.calimero          ] - KNXnet/IP Tunneling 192.168.25.9:3674: connection state response status: server detected error concerning the KNX bus/subsystem connection
2019-10-18 15:35:36.027 [WARN ] [.b.knx.internal.bus.KNXBinding] - Value '2' could not be sent to the KNX bus using datapoint 'command DP 3/6/33 FBH_Modus, DPT main 0 id 5.010, low priority' - retrying one time: no confirmation reply received
2019-10-18 15:35:39.029 [ERROR] [.b.knx.internal.bus.KNXBinding] - Value 'OFF' could not be sent to the KNX bus using datapoint 'command DP 1/1/13 Steckdose_EG_Wohnen_Schrank, DPT main 0 id 1.001, low priority' - giving up after second try: no confirmation reply received
2019-10-18 15:35:42.031 [ERROR] [.b.knx.internal.bus.KNXBinding] - Value '2' could not be sent to the KNX bus using datapoint 'command DP 3/6/33 FBH_Modus, DPT main 0 id 5.010, low priority' - giving up after second try: no confirmation reply received
2019-10-18 15:35:43.428 [WARN ] [tuwien.auto.calimero          ] - KNXnet/IP Tunneling 192.168.25.9:3674: connection state response status: server detected error concerning the KNX bus/subsystem connection
2019-10-18 15:35:45.032 [WARN ] [.b.knx.internal.bus.KNXBinding] - Value 'OFF' could not be sent to the KNX bus using datapoint 'command DP 1/1/10 Licht_EG_Wohnen_Vitrine, DPT main 0 id 1.001, low priority' - retrying one time: no confirmation reply received
2019-10-18 15:35:48.034 [ERROR] [.b.knx.internal.bus.KNXBinding] - Value 'OFF' could not be sent to the KNX bus using datapoint 'command DP 1/1/10 Licht_EG_Wohnen_Vitrine, DPT main 0 id 1.001, low priority' - giving up after second try: no confirmation reply received
2019-10-18 15:35:51.053 [WARN ] [.b.knx.internal.bus.KNXBinding] - Value 'OFF' could not be sent to the KNX bus using datapoint 'command DP 1/1/50 Steckdose_DG_Flur_Fenster, DPT main 0 id 1.001, low priority' - retrying one time: no confirmation reply received
2019-10-18 15:35:53.432 [WARN ] [tuwien.auto.calimero          ] - KNXnet/IP Tunneling 192.168.25.9:3674: close connection - no heartbeat response
2019-10-18 15:35:53.437 [WARN ] [b.k.i.connection.KNXConnection] - KNX link has been lost (reason: no heartbeat response on object link 192.168.25.9:3674 tunneling mode (closed), TP1 hopcount 6)
2019-10-18 15:35:53.437 [INFO ] [b.k.i.connection.KNXConnection] - KNX link will be retried in 30 seconds
2019-10-18 15:36:23.439 [INFO ] [b.k.i.connection.KNXConnection] - Trying to (re-)connect to KNX...
2019-10-18 15:36:23.460 [INFO ] [b.k.i.connection.KNXConnection] - Established connection to KNX bus on 192.168.25.9:3674 in mode TUNNEL.
2019-10-18 15:36:23.502 [INFO ] [b.k.i.connection.KNXConnection] - Connected to KNX
2019-10-18 15:36:26.509 [WARN ] [.KNXBindingDatapointReaderTask] - Autorefresh: Cannot read value for item 'FBH_Absenktemperatur' from KNX bus: no confirmation reply received: timeout

Das Problem bleibt ab diesem Zeitpunkt bestehen. Nach einem Neustart des TWS ist dann wieder alles in Ordnung.

Eine zweiter Tunnel Client (meine Eigenentwicklung) hat ähnliche Probleme und meldet ebenfalls fehlende Confirmations.

Mit dem Wiregate hatte ich diese Probleme nicht.

Viele Grüße,
Peter

[StefanW]

Hallo Peter,

der WireGate Server war auch kein zertifizierter KNX Stack und hat unter anderem viele Restriktionen überhaupt nicht eingehalten, die der Standard aber vorsieht. Dazu gehören auch u.a. Timeouts bei fehlerhaften Tunnel-Verbindungen wie zum Beispiel nicht eingehaltene Timeouts.

Der Stack des Timberwolf Servers ist von einem akkreditierten Labor zertifiziert worden, entsprechend werden dort auch solche Verhalten überprüft.

Es besteht daher die Möglichkeit - und so ließt sich auch das Log - dass der verwendete eibd / knxd sich nicht an das Protokoll hält, den Heartbeat nicht sendet und daher die Tunneling Verbindung beendet wird.

Ich fürchte, hier können wir nicht groß helfen.

lg

Stefan

[StefanW]

Hallo Peter,

ich sehe gerade, Du schreibst im Titel RC5?

==> Wir haben derzeit RC8, bitte grundsätzlich vor Beiträgen auf die jeweils aktuelle Version updaten

lg

Stefan

[peti69]

Hallo Stefan,

danke für die schnelle Rückmeldung.

Update auf das letzte Release ist erfolgt.

Ich werde das weiter beobachten und beim nächsten Aussetzer von OpenHAB mal mit der ETS die Tunnelverbindung zum TWS prüfen.

Viele Grüße,
Peter

[StefanW]

Hallo Peter,

womöglich kann man auch das Logging im eibd / knxd (keine Ahnung welcher hier verwendet wird) hochdrehen

Stefan

[peti69]

Hallo Stefan,

OpenHAB verbindet sich (unter Nutzung der Calimero Library) über einen Tunnel direkt zum TWS. Es wird kein knxd oder eibd verwendet. Daher verstehe ich nicht was Du meinst.

Viele Grüße
Peter

[Matze76]

im Log meiner OpenHAB 1 Installation

In meiner openHAB 2 Installation (mit dem aktuellen KNX 2 Binding) habe ich solche Log-Einträge noch nicht vorgefunden. Vielleicht wurde da inzwischen mal etwas gefixed...

[Dragonos2000]

Kenne das Verhalten aus meinen beiden OpenHAB 2 Dockern auch nicht...

[peti69]

Hallo,

ich habe jetzt aktuell einen Zustand bei der ich mit der ETS 5.7.2 über den TWS (mit RC 8) die KNX-Geräte nicht mehr programmieren kann:

ETS-Fehler.PNG

Im TWS-Busmonitor werden alle Telegramme des KNX-Bus 4-fach angezeigt:

TWS-Fehler.PNG

Im Log von OpenHAB 1 sieht es so aus:

Code: Alles auswählen

2019-10-21 17:00:00.911 [WARN ] [tuwien.auto.calimero          ] - Data-unit builder: unknown APCI service code 0x216
2019-10-21 17:00:36.891 [WARN ] [tuwien.auto.calimero          ] - KNXnet/IP Tunneling 192.168.25.9:3674: connection state response status: server detected error concerning the KNX bus/subsystem connection
2019-10-21 17:00:46.891 [WARN ] [tuwien.auto.calimero          ] - KNXnet/IP Tunneling 192.168.25.9:3674: connection state response status: server detected error concerning the KNX bus/subsystem connection
2019-10-21 17:00:56.892 [WARN ] [tuwien.auto.calimero          ] - KNXnet/IP Tunneling 192.168.25.9:3674: connection state response status: server detected error concerning the KNX bus/subsystem connection
2019-10-21 17:01:06.893 [WARN ] [tuwien.auto.calimero          ] - KNXnet/IP Tunneling 192.168.25.9:3674: connection state response status: server detected error concerning the KNX bus/subsystem connection
2019-10-21 17:01:16.898 [WARN ] [tuwien.auto.calimero          ] - KNXnet/IP Tunneling 192.168.25.9:3674: close connection - no heartbeat response
2019-10-21 17:01:16.909 [WARN ] [b.k.i.connection.KNXConnection] - KNX link has been lost (reason: no heartbeat response on object link 192.168.25.9:3674 tunneling mode (closed), TP1 hopcount 6)
2019-10-21 17:01:16.915 [INFO ] [b.k.i.connection.KNXConnection] - KNX link will be retried in 30 seconds
2019-10-21 17:01:46.917 [INFO ] [b.k.i.connection.KNXConnection] - Trying to (re-)connect to KNX...
2019-10-21 17:01:46.935 [INFO ] [b.k.i.connection.KNXConnection] - Established connection to KNX bus on 192.168.25.9:3674 in mode TUNNEL.
2019-10-21 17:01:46.984 [INFO ] [b.k.i.connection.KNXConnection] - Connected to KNX
2019-10-21 17:02:46.933 [WARN ] [tuwien.auto.calimero          ] - KNXnet/IP Tunneling 192.168.25.9:3674: connection state response status: server detected error concerning the KNX bus/subsystem connection
2019-10-21 17:02:56.933 [WARN ] [tuwien.auto.calimero          ] - KNXnet/IP Tunneling 192.168.25.9:3674: connection state response status: server detected error concerning the KNX bus/subsystem connection
2019-10-21 17:03:06.933 [WARN ] [tuwien.auto.calimero          ] - KNXnet/IP Tunneling 192.168.25.9:3674: connection state response status: server detected error concerning the KNX bus/subsystem connection
2019-10-21 17:03:16.933 [WARN ] [tuwien.auto.calimero          ] - KNXnet/IP Tunneling 192.168.25.9:3674: connection state response status: server detected error concerning the KNX bus/subsystem connection
2019-10-21 17:03:26.936 [WARN ] [tuwien.auto.calimero          ] - KNXnet/IP Tunneling 192.168.25.9:3674: close connection - no heartbeat response
2019-10-21 17:03:26.937 [WARN ] [b.k.i.connection.KNXConnection] - KNX link has been lost (reason: no heartbeat response on object link 192.168.25.9:3674 tunneling mode (closed), TP1 hopcount 6)
2019-10-21 17:03:26.940 [INFO ] [b.k.i.connection.KNXConnection] - KNX link will be retried in 30 seconds
2019-10-21 17:03:56.944 [INFO ] [b.k.i.connection.KNXConnection] - Trying to (re-)connect to KNX...
2019-10-21 17:03:56.959 [INFO ] [b.k.i.connection.KNXConnection] - Established connection to KNX bus on 192.168.25.9:3674 in mode TUNNEL.
2019-10-21 17:03:57.001 [INFO ] [b.k.i.connection.KNXConnection] - Connected to KNX
2019-10-21 17:04:56.957 [WARN ] [tuwien.auto.calimero          ] - KNXnet/IP Tunneling 192.168.25.9:3674: connection state response status: server detected error concerning the KNX bus/subsystem connection
2019-10-21 17:05:03.054 [WARN ] [.b.knx.internal.bus.KNXBinding] - Value 'OFF' could not be sent to the KNX bus using datapoint 'command DP 3/1/4 Windalarm, DPT main 0 id 1.001, low priority' - retrying one time: no confirmation reply received
2019-10-21 17:05:06.057 [WARN ] [.b.knx.internal.bus.KNXBinding] - Value 'OFF' could not be sent to the KNX bus using datapoint 'command DP 0/1/60 Licht_Garage, DPT main 0 id 1.001, low priority' - retrying one time: no confirmation reply received
2019-10-21 17:05:06.957 [WARN ] [tuwien.auto.calimero          ] - KNXnet/IP Tunneling 192.168.25.9:3674: connection state response status: server detected error concerning the KNX bus/subsystem connection
2019-10-21 17:05:09.058 [ERROR] [.b.knx.internal.bus.KNXBinding] - Value 'OFF' could not be sent to the KNX bus using datapoint 'command DP 3/1/4 Windalarm, DPT main 0 id 1.001, low priority' - giving up after second try: no confirmation reply received
2019-10-21 17:05:12.060 [ERROR] [.b.knx.internal.bus.KNXBinding] - Value 'OFF' could not be sent to the KNX bus using datapoint 'command DP 0/1/60 Licht_Garage, DPT main 0 id 1.001, low priority' - giving up after second try: no confirmation reply received
2019-10-21 17:05:15.062 [WARN ] [.b.knx.internal.bus.KNXBinding] - Value 'CLOSED' could not be sent to the KNX bus using datapoint 'state DP 3/6/7 WW_ZPA_Pumpenlauf_Notwendig, DPT main 0 id 1.019, low priority' - retrying one time: no confirmation reply received
2019-10-21 17:05:16.957 [WARN ] [tuwien.auto.calimero          ] - KNXnet/IP Tunneling 192.168.25.9:3674: connection state response status: server detected error concerning the KNX bus/subsystem connection
2019-10-21 17:05:18.064 [WARN ] [.b.knx.internal.bus.KNXBinding] - Value 'OFF' could not be sent to the KNX bus using datapoint 'command DP 3/1/3 Regenalarm, DPT main 0 id 1.001, low priority' - retrying one time: no confirmation reply received
2019-10-21 17:05:21.066 [ERROR] [.b.knx.internal.bus.KNXBinding] - Value 'CLOSED' could not be sent to the KNX bus using datapoint 'state DP 3/6/7 WW_ZPA_Pumpenlauf_Notwendig, DPT main 0 id 1.019, low priority' - giving up after second try: no confirmation reply received
2019-10-21 17:05:24.068 [WARN ] [.b.knx.internal.bus.KNXBinding] - Value 'OFF' could not be sent to the KNX bus using datapoint 'command DP 1/1/13 Steckdose_EG_Wohnen_Schrank, DPT main 0 id 1.001, low priority' - retrying one time: no confirmation reply received
2019-10-21 17:05:26.957 [WARN ] [tuwien.auto.calimero          ] - KNXnet/IP Tunneling 192.168.25.9:3674: connection state response status: server detected error concerning the KNX bus/subsystem connection
2019-10-21 17:05:27.070 [ERROR] [.b.knx.internal.bus.KNXBinding] - Value 'OFF' could not be sent to the KNX bus using datapoint 'command DP 3/1/3 Regenalarm, DPT main 0 id 1.001, low priority' - giving up after second try: no confirmation reply received
2019-10-21 17:05:30.074 [ERROR] [.b.knx.internal.bus.KNXBinding] - Value 'OFF' could not be sent to the KNX bus using datapoint 'command DP 1/1/13 Steckdose_EG_Wohnen_Schrank, DPT main 0 id 1.001, low priority' - giving up after second try: no confirmation reply received
2019-10-21 17:05:33.090 [WARN ] [.b.knx.internal.bus.KNXBinding] - Value 'OFF' could not be sent to the KNX bus using datapoint 'command DP 1/1/10 Licht_EG_Wohnen_Vitrine, DPT main 0 id 1.001, low priority' - retrying one time: no confirmation reply received
2019-10-21 17:05:36.094 [ERROR] [.b.knx.internal.bus.KNXBinding] - Value 'OFF' could not be sent to the KNX bus using datapoint 'command DP 1/1/10 Licht_EG_Wohnen_Vitrine, DPT main 0 id 1.001, low priority' - giving up after second try: no confirmation reply received
2019-10-21 17:05:36.957 [WARN ] [tuwien.auto.calimero          ] - KNXnet/IP Tunneling 192.168.25.9:3674: close connection - no heartbeat response
2019-10-21 17:05:36.958 [WARN ] [b.k.i.connection.KNXConnection] - KNX link has been lost (reason: no heartbeat response on object link 192.168.25.9:3674 tunneling mode (closed), TP1 hopcount 6)
2019-10-21 17:05:36.969 [INFO ] [b.k.i.connection.KNXConnection] - KNX link will be retried in 30 seconds
2019-10-21 17:06:06.970 [INFO ] [b.k.i.connection.KNXConnection] - Trying to (re-)connect to KNX...
2019-10-21 17:06:06.986 [INFO ] [b.k.i.connection.KNXConnection] - Established connection to KNX bus on 192.168.25.9:3674 in mode TUNNEL.
2019-10-21 17:06:07.035 [INFO ] [b.k.i.connection.KNXConnection] - Connected to KNX

Ich vermute das irgendein Busteilnehmer den TWS aus dem Tritt bringt. Möglicherweise handelt es sich um ein Gerät das die KNX-Spezifikation nicht 100% erfüllt. Durch einen Neustart des TWS kann das Problem dann (vorläufig) wieder behoben werden.

Viele Grüße,
Peter

[peti69]

Ich würde gerne im Titel RC 5 durch RC 8 ersetzen. Allerdings weiß ich nicht wie.