Ankündigung

Einklappen
Keine Ankündigung bisher.

OH 2.3/ KNX2 - IP Gateway geht immer offline

Einklappen
X
 
  • Filter
  • Zeit
  • Anzeigen
Alles löschen
neue Beiträge

    #31
    Hallo Ich hatte heute den nächsten Ausfall.

    allerdings habe ich diesmal nicht Openhab komplett neu gestartet sonder nur die KNX Bridge in der Things auskommentiert. Dann gewartet bis im Tail alles Unkonwn war dann wieder einkommentiert und alles lief wieder.

    Code:
     
           2018-11-15 07:52:14.923 [COLOR=orange][WARN ][/COLOR] [alimero.mgmt.MC 192.168.179.177:3671] - problem reading property (response 43 d6 00 09 00 01)
     
    tuwien.auto.calimero.KNXRemoteException: property access OI 0 PID 9 failed/forbidden
     
    at tuwien.auto.calimero.mgmt.ManagementClientImpl.extractPropertyElements(ManagementClientImpl.java:986) ~[?:?]
     
    at tuwien.auto.calimero.mgmt.ManagementClientImpl.lambda$readProperty$0(ManagementClientImpl.java:570) ~[?:?]
     
    at tuwien.auto.calimero.mgmt.ManagementClientImpl.waitForResponses(ManagementClientImpl.java:905) ~[?:?]
     
    at tuwien.auto.calimero.mgmt.ManagementClientImpl.readProperty(ManagementClientImpl.java:568) ~[?:?]
     
    at tuwien.auto.calimero.mgmt.ManagementClientImpl.readProperty(ManagementClientImpl.java:535) ~[?:?]
     
    at org.openhab.binding.knx.internal.client.DeviceInfoClientImpl.lambda$2(DeviceInfoClientImpl.java:107) ~[?:?]
     
    at org.openhab.binding.knx.internal.client.DeviceInfoClientImpl.readFromManagementClient(DeviceInfoClientImpl.java:56) ~[?:?]
     
    at org.openhab.binding.knx.internal.client.DeviceInfoClientImpl.readDeviceProperties(DeviceInfoClientImpl.java:105) ~[?:?]
     
    at org.openhab.binding.knx.internal.client.DeviceInspector.readDeviceProperties(DeviceInspector.java:111) ~[?:?]
     
    at org.openhab.binding.knx.internal.client.DeviceInspector.readDeviceInfo(DeviceInspector.java:88) ~[?:?]
     
    at org.openhab.binding.knx.handler.AbstractKNXThingHandler.describeDevice(AbstractKNXThingHandler.java:89) ~[?:?]
     
    at org.openhab.binding.knx.handler.AbstractKNXThingHandler.lambda$0(AbstractKNXThingHandler.java:153) ~[?:?]
     
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
     
    at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
     
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:?]
     
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:?]
     
    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) [?:?]
    ich hatte auch diese Fehlermeldung im Tail kann jemand damit etwas anfangen ?
    Zuletzt geändert von Höhlenbär; 15.11.2018, 08:01. Grund: Fehler hinzugefügt
    Gruß

    Guido

    Kommentar


      #32
      Das Log sagt aus, dass versucht wurde einen ungültigen Wert auf den knx Bus zu schreiben. Um näheres sagen zu können fehlen die direkten Zeilen vorher, irgendwas wie:
      Code:
      2018-06-30 20:46:29.162 [WARN ] [rest.core.internal.item.ItemResource] - Received HTTP POST request at ...
      Wie hier beschrieben:
      https://github.com/openhab/openhab2-addons/issues/3842

      Ändere mal Deine Devices, lösche den "fetch" parameter oder setze ihn auf "fetch=false". Dann sollten diese Fehler unterbleiben.
      Zuletzt geändert von 4media; 16.11.2018, 09:34.

      Kommentar


        #33
        Ok dann schau ich mal wenn das wieder auftritt. Scheint aber immer beim Neustart der Verbindung zu sein.
        Gruß

        Guido

        Kommentar


          #34
          Zitat von Höhlenbär Beitrag anzeigen
          Ok dann schau ich mal wenn das wieder auftritt. Scheint aber immer beim Neustart der Verbindung zu sein.
          Definitiv holt das Binding die Geräte infos nur nur beim Neustart! Auslesen der Geräteparameter und Adress- / Kommunikationsobjekttabellen (erfordert die Adresse)

          Und für den Betrieb sind diese nicht erforderlich. Also weg damit!

          Kommentar


            #35
            Hallo,

            bei mir war gestern und heute erneut die Verbindung weg.

            im log stand leider nur das
            Code:
            2018-11-24 10:29:19.000 [hingStatusInfoChangedEvent] - 'knx:ip:bridge' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR)
            2018-11-24 10:29:19.015 [hingStatusInfoChangedEvent] - 'knx:device:bridge:UVRHeizung' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.017 [hingStatusInfoChangedEvent] - 'knx:device:bridge:Klemme1' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.023 [hingStatusInfoChangedEvent] - 'knx:device:bridge:KG_Aktor_ABB_8fach_Eing' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.025 [hingStatusInfoChangedEvent] - 'knx:device:bridge:PM_Decke_Waschh' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.028 [hingStatusInfoChangedEvent] - 'knx:device:bridge:EG_6933Jal_SchlafzimmerFewo' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.042 [hingStatusInfoChangedEvent] - 'knx:device:bridge:Klemme2' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.044 [hingStatusInfoChangedEvent] - 'knx:device:bridge:EG_6124SoloRTR_SchlafzimmerFewo' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.047 [hingStatusInfoChangedEvent] - 'knx:device:bridge:EG_6131USoloTaster2SchlafzimmerFewo' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.048 [hingStatusInfoChangedEvent] - 'knx:device:bridge:EG_6131USoloTaster1SchlafzimmerFewo' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.050 [hingStatusInfoChangedEvent] - 'knx:device:bridge:EG_6124SoloRTR_KuecheFewo' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.052 [hingStatusInfoChangedEvent] - 'knx:device:bridge:EG_6933Jal_WohnzimmerFewo' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.054 [hingStatusInfoChangedEvent] - 'knx:device:bridge:EG_6133UHeizungSchlafzimmerfewo' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.056 [hingStatusInfoChangedEvent] - 'knx:device:bridge:PM_Decke_Keller' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.059 [hingStatusInfoChangedEvent] - 'knx:device:bridge:EG_6933Jal_KuecheFewo' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.061 [hingStatusInfoChangedEvent] - 'knx:device:bridge:EG_6133USoloTaster1Kuechefewo' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.063 [hingStatusInfoChangedEvent] - 'knx:device:bridge:EG_6133UHeizungKuechefewo' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.066 [hingStatusInfoChangedEvent] - 'knx:device:bridge:EG_6133USoloTaster2Wohnfewo' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.069 [hingStatusInfoChangedEvent] - 'knx:device:bridge:KG_Aktor_Gira_8fach_Schalt' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.072 [hingStatusInfoChangedEvent] - 'knx:device:bridge:EG_6133USoloBM_Flur1fewo' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.074 [hingStatusInfoChangedEvent] - 'knx:device:bridge:EG_6133UHeizungFlurfewo' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.079 [hingStatusInfoChangedEvent] - 'knx:device:bridge:EG_6133UHeizungWohnzimmerfewo' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.081 [hingStatusInfoChangedEvent] - 'knx:device:bridge:EG_6124SoloRTR_Flurfewo' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.084 [hingStatusInfoChangedEvent] - 'knx:device:bridge:EG_AKUKombi8Kanal' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.088 [hingStatusInfoChangedEvent] - 'knx:device:bridge:EG_6133USoloTaster1Wohnfewo' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.091 [hingStatusInfoChangedEvent] - 'knx:device:bridge:EG_6124SoloRTR_Wohnzimmerfewo' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.094 [hingStatusInfoChangedEvent] - 'knx:device:bridge:EG_MDT4Jal0410_4Kanal' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.097 [hingStatusInfoChangedEvent] - 'knx:device:bridge:EG_AKKSchaltaktor_8Kanal' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.098 [hingStatusInfoChangedEvent] - 'knx:device:bridge:EG_Hager_Flur_WYT61' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.100 [hingStatusInfoChangedEvent] - 'knx:device:bridge:EG_HeizungsAkt8fachUV' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.102 [hingStatusInfoChangedEvent] - 'knx:device:bridge:OG1_6935SoloRTRFlur' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.104 [hingStatusInfoChangedEvent] - 'knx:device:bridge:OG1_LEDTreiber4fachAP' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.105 [hingStatusInfoChangedEvent] - 'knx:device:bridge:OG1_MDT4Jal0410_4Kanal' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.107 [hingStatusInfoChangedEvent] - 'knx:device:bridge:OG1_6933Jal_Wohnzimmerhinten' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.109 [hingStatusInfoChangedEvent] - 'knx:device:bridge:OG1_6997_Wohnzimmerhinten' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.110 [hingStatusInfoChangedEvent] - 'knx:device:bridge:OG1_6933Triton2_Wohnzimmervorn' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.112 [hingStatusInfoChangedEvent] - 'knx:device:bridge:OG1_6133UHeizungWohnzimmervorn' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.114 [hingStatusInfoChangedEvent] - 'knx:device:bridge:DG_BinEing8KanalUV' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.117 [hingStatusInfoChangedEvent] - 'knx:device:bridge:DG_WC_Prasenz' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.119 [hingStatusInfoChangedEvent] - 'knx:device:bridge:EG_Hager_WYT61' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.120 [hingStatusInfoChangedEvent] - 'knx:device:bridge:OG1_HeizungsAkt8fachUV' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.122 [hingStatusInfoChangedEvent] - 'knx:device:bridge:OG1_BinEing8KanalUVKueche' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.124 [hingStatusInfoChangedEvent] - 'knx:device:bridge:OG1_6935Triton_Wohnzimmerhinten' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.126 [hingStatusInfoChangedEvent] - 'knx:device:bridge:OG1_6933_Wohnzimmerhinten' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.128 [hingStatusInfoChangedEvent] - 'knx:device:bridge:OG1_6933Jal_Wohnzimmervorn' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.130 [hingStatusInfoChangedEvent] - 'knx:device:bridge:OG1_6933Schalt_Wohnzimmervorn' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.131 [hingStatusInfoChangedEvent] - 'knx:device:bridge:DG_MDT4Jal0410_4Kanal' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.133 [hingStatusInfoChangedEvent] - 'knx:device:bridge:DG_HeizungsAkt8fachUV' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.135 [hingStatusInfoChangedEvent] - 'knx:device:bridge:DG_FlurPrasenz' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.138 [hingStatusInfoChangedEvent] - 'knx:device:bridge:DG_PaulaRTR5fach' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.140 [hingStatusInfoChangedEvent] - 'knx:device:bridge:DG_WilliRTR5fach' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.141 [hingStatusInfoChangedEvent] - 'knx:device:bridge:DG_SchlafDimmAkt1fach' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.143 [hingStatusInfoChangedEvent] - 'knx:device:bridge:Fewo2_WohnRTR2fach' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.146 [hingStatusInfoChangedEvent] - 'knx:device:bridge:OG1_AKKSchaltaktor_8Kanal' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.148 [hingStatusInfoChangedEvent] - 'knx:device:bridge:OG1_6935SoloRTRKueche' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.149 [hingStatusInfoChangedEvent] - 'knx:device:bridge:OG1_6932_DimmerWohnzimmerhinten' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.151 [hingStatusInfoChangedEvent] - 'knx:device:bridge:OG1_6133UHeizungWohnzimmerhinten' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.153 [hingStatusInfoChangedEvent] - 'knx:device:bridge:OG1_6935Triton_Wohnzimmervorn' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.155 [hingStatusInfoChangedEvent] - 'knx:device:bridge:DG_MDT2Jal0206_2Kanal' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.156 [hingStatusInfoChangedEvent] - 'knx:device:bridge:DG_SchaltAkt4fachUV' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.159 [hingStatusInfoChangedEvent] - 'knx:device:bridge:DG_6933Jal_WC' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.161 [hingStatusInfoChangedEvent] - 'knx:device:bridge:DG_PaulaDimAkt4fach' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.163 [hingStatusInfoChangedEvent] - 'knx:device:bridge:DG_WilliDimaktvorraum1fach' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.166 [hingStatusInfoChangedEvent] - 'knx:device:bridge:DG_SchlafSchaltAkt2fach' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.169 [hingStatusInfoChangedEvent] - 'knx:device:bridge:Fewo2_SchlafRTR2fach' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.171 [hingStatusInfoChangedEvent] - 'knx:device:bridge:Nebengeb_BinEing4KanalUV' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.173 [hingStatusInfoChangedEvent] - 'knx:device:bridge:EG_BinEing8KanalUVEB' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.175 [hingStatusInfoChangedEvent] - 'knx:device:bridge:DG_PaulaSchaltAkt2fach' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.228 [hingStatusInfoChangedEvent] - 'knx:device:bridge:DG_WilliDimaktraum1fach' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.231 [hingStatusInfoChangedEvent] - 'knx:device:bridge:DG_SchlafRTR5fach' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.233 [hingStatusInfoChangedEvent] - 'knx:device:bridge:Nebengeb_MDT4KombiHMG4_12Kanal' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.235 [hingStatusInfoChangedEvent] - 'knx:device:bridge:Wetterstation' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.237 [hingStatusInfoChangedEvent] - 'knx:device:bridge:DG_FlurRTR2fach' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            2018-11-24 10:29:19.239 [hingStatusInfoChangedEvent] - 'knx:device:bridge:OG1_LEDTreiber4fachDecke' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
            kann ich irgendwie auswerten wenn das passiert und die Verbindung neu starten?

            Im Moment öffne ich nur die Things Datei kommentiere die Zeile mit der Bridge aus speichere ab
            Warte bis OH das eingelesen hat.,dann kommentiere ich das wieder ein und alles läuft wieder..

            Hast da ne Idee zu das zu Automatisieren? Ist dann zwar ne "Hilfskrücke" mindert aber das Leiden.
            Gruß

            Guido

            Kommentar


              #36
              Der automatische Reconnect ist ja implementiert! Nur scheint dort noch etwas zu fehlen.
              Von dem Effekt berichten noch weitere zwei drei Nutzer. Nur die Ursache haben wir noch nicht finden können.

              Vergleiche mal Deine Parameter. Die "autoReconnectPeriod", nicht zu klein einstellen.
              Wenn möglich mode ROUTER nutzen, dort kann es Prinzipbedingt keine Verbindung abbrechen, weil es keine feste Verbindung gibt.

              Du kannst mir per PM gerne auch mal Deine Bridge samt Things und Channels schicken, dann schau ich mal ob mir was auffällt.

              Bridge knx:ip:bridge [
              ...
              readingPause=50,
              responseTimeout=10,
              readRetriesLimit=3,
              autoReconnectPeriod=60
              ]

              Wenn Du die Konsole nutzen kannst, dann stelle bitte calimero und das knx binding auf einen höheren debug mode. Dann kommen zwar sehr viele Einträge ins log, aber wir finden eher die Ursache:

              log:set TRACE org.openhab.binding.knx
              log:set TRACE calimero

              Kommentar


                #37
                Hallo Danke für Deine Hilfe,

                der autoReconect ist bei mir definitiv zu kurz das ändere ich sofort.
                Router Mode funktioniert leider nicht dann tanzen die Aktoren auf dem Powernet Lambada warum kann ich nicht sagen.
                Den Log stelle ich selbstverständlich ein möchte gern so gut es geht helfen den Fehler zu finden. Wenn Du noch was brauchst sag Bescheid.
                Die Bridge und die Things habe ich Dir gesendet allerdings nicht komplett. Die Anzahl der Zeichen war überschritten.
                Gruß

                Guido

                Kommentar


                  #38
                  Hallo Höhlenbär,

                  also wenn Du ein Routing fähiges KNX-IP Interface hast, dann ist diese Verbindung die bessere Wahl!

                  Zitat von Höhlenbär Beitrag anzeigen
                  Router Mode funktioniert leider nicht dann tanzen die Aktoren auf dem Powernet Lambada
                  dass darf aber nicht sein! Was bedeutet das bzw. wie äußert sich das?

                  Der ROUTER mode ist eine broadcast Kommunikation, das bedeutet es kann keine Verbindungsabbrüche geben, weil es gar keine gibt. ;-)


                  Code:
                  Bridge knx:ip:bridge "XXXXX" @ "KNX" [
                     //ipAddress="224.0.23.12", //<- das ist die standard Broadcast Addresse die im ROUTER mode verwendet wird. Muß aber nicht explizit angegeben werden.
                     ipAddress="xxx.xxx.xxx.xxx",
                     portNumber=3671,
                     localIp="xxx.xxx.xxx.xxx ", //<- Bitte das Leerzeichen entfernen! Die lokale Adresse mußt Du nicht angeben, nur wenn die IP vom Binding nicht automatisch erkannt wird. (ZB zwei Netzwerkkarten)
                     type="TUNNEL",
                     readingPause=50,
                     responseTimeout=10,
                     readRetriesLimit=3,
                     autoReconnectPeriod=1, //<- würde ich auf 60 sek einstellen. EIn Verbindungsabbruch kommt im Normalfall ja hoffentlich sehr selten vor und hat ja einen Grund, dehalb eher etwas Zeit lassen um die anderen Komponenten sich auch stabilisieren können.
                     localSourceAddr="0.0.0" //<- 0.0.0 ist der Standardwert und berechtigt das Hardware Interface selbst eine Adresse zu wählen. Im Normalfall nicht nötig das anzugeben, außer Du hast mehrere openHAB oder/und möchtest eine spezielle Hardwareadresse mit dem sich openHAB im KNX meldet.
                  ] {
                  Sonst ist mir nichts ungewöhnliches aufgefallen.
                  Zuletzt geändert von 4media; 25.11.2018, 11:27.

                  Kommentar


                    #39
                    Ja woran das liegt kann ich auch nicht sagen. Jedenfalls scheinen die Aktoren auf dem Powernet mit irgendwelchen Telegrammen geflutet zu werden. Diese sind nach dem umstellen auf den Routermodus nicht mehr ansprechbar und die Kommunikation auch zwischen den Powernetaktoren kommt zum erliegen. Die Aktoren sind dann nur durch einen Neustart wiederzubeleben. Leider konnte ich noch nicht rausbekommen warum das so ist. Ev. kommen sich der Router und der Medienkoppler der ja auch als Router fungiert in die Quere. Da die Wohnung vermietet ist sind logischer weise die Mieter jedes mal etwas genervt wenn ich teste. Darum lasse ich das vorerst mal.
                    Gruß

                    Guido

                    Kommentar


                      #40
                      Darf ich mich mit dem gleichen Problem hier einklinken?
                      Ich verwende OH 2.3.0 auf einem Raspberry Pi und ein Enertex® KNXnet/IP Interface. Dieses verliert teilweise mehrmals täglich die Verbindung, wobei manchmal erst ein Reboot des Raspberry Pi das Problem löst. Durch den Hinweis von 4media logge ich seit gestern mit. Hier Informationen vom letzten Ausfall, wobei der Reconnect hier rasch von alleine wieder kam.
                      Code:
                      knx.things:
                      Bridge knx:ip:knx-ip-gateway "KNX/IP Gateway" @ "EG Vorzimmer" [ 
                          ipAddress="192.168.1.55", 
                          portNumber=3671, 
                          localIp="192.168.1.44", 
                          type="TUNNEL", 
                          readingPause=50, 
                          responseTimeout=10, 
                          readRetriesLimit=3, 
                          autoReconnectPeriod=60,
                          localSourceAddr="0.0.0"
                      ] {
                          Thing device knx "KNX dummy for openHAB" @ "KNX" [
                              address="1.1.254",
                              fetch=false,
                              pingInterval=300,
                              readInterval=0
                          ] {
                              // --- KG Keller ---
                              Type switch        : KG_Keller_Licht            "KG_Keller_Licht"           [ ga="2/1/9+<2/1/10" ]
                              Type switch        : KG_Keller_Stiege            "KG_Keller_Stiege"           [ ga="2/1/13+<2/1/14" ]
                              Type switch        : KG_Keller_Steckdose            "KG_Keller_Steckdose"           [ ga="2/1/17+<2/1/18" ]
                              Type number        : KG_Keller_Temperatur   "KG_Keller_Temperatur" [ ga="5/3/2" ]
                      ...
                      Code:
                      events.log:
                      2018-11-29 14:54:18.627 [ome.event.ItemCommandEvent] - Item 'EG_WC_Temperatur_Menu' received command 19.84
                      2018-11-29 14:54:25.477 [hingStatusInfoChangedEvent] - 'knx:ip:knx-ip-gateway' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): server request
                      2018-11-29 14:54:25.511 [hingStatusInfoChangedEvent] - 'knx:device:knx-ip-gateway:knx' changed from OFFLINE to OFFLINE (BRIDGE_OFFLINE)
                      2018-11-29 14:54:25.591 [hingStatusInfoChangedEvent] - 'knx:ip:knx-ip-gateway' changed from OFFLINE (COMMUNICATION_ERROR): server request to OFFLINE (COMMUNICATION_ERROR)
                      2018-11-29 14:54:25.637 [hingStatusInfoChangedEvent] - 'knx:ip:knx-ip-gateway' changed from OFFLINE (COMMUNICATION_ERROR) to ONLINE
                      2018-11-29 14:54:25.647 [hingStatusInfoChangedEvent] - 'knx:device:knx-ip-gateway:knx' changed from OFFLINE (BRIDGE_OFFLINE) to UNKNOWN
                      2018-11-29 14:54:43.485 [hingStatusInfoChangedEvent] - 'knx:device:knx-ip-gateway:knx' changed from UNKNOWN to OFFLINE
                      2018-11-29 14:54:56.436 [vent.ItemStateChangedEvent] - KG_Keller_Stiege changed from OFF to ON
                      Code:
                      openhab.log:
                      2018-11-29 14:54:18.677 [DEBUG] [nx.internal.client.AbstractKNXClient] - Wrote value '19.84' to datapoint 'command DP 5/3/11 'knx:ip:knx-ip-gateway', DPT id 9.001, low priority' (0. attempt).
                      2018-11-29 14:54:25.421 [TRACE] [NXnet/IP Tunneling 192.168.1.55:3671] - sending connection state request, attempt 1
                      2018-11-29 14:54:25.430 [TRACE] [NXnet/IP Tunneling 192.168.1.55:3671] - received request seq 98 (channel 65) cEMI 29 00 bc e0 11 20 39 01 04 00 80 8e 36 18
                      2018-11-29 14:54:25.433 [DEBUG] [calimero.link.192.168.1.55:3671     ] - indication 1.1.32->7/1/1 L_Data.ind, low priority hop count 6, tpdu 00 80 8e 36 18
                      2018-11-29 14:54:25.433 [TRACE] [nx.internal.client.AbstractKNXClient] - Received a Group Write telegram from '1.1.32' to '7/1/1'
                      2018-11-29 14:54:25.435 [DEBUG] [NXnet/IP Tunneling 192.168.1.55:3671] - skip tunneling request with rcv-seq 98 (already received)
                      2018-11-29 14:54:25.440 [INFO ] [NXnet/IP Tunneling 192.168.1.55:3671] - close connection - server request
                      2018-11-29 14:54:25.444 [INFO ] [calimero.mgmt.TL 192.168.1.55:3671  ] - attached link was closed
                      2018-11-29 14:54:25.447 [INFO ] [calimero.mgmt.MC 192.168.1.55:3671  ] - attached link was closed
                      2018-11-29 14:54:25.452 [INFO ] [calimero.mgmt.TL 192.168.1.55:3671  ] - attached link was closed
                      2018-11-29 14:54:25.456 [INFO ] [calimero.mgmt.MC 192.168.1.55:3671  ] - attached link was closed
                      2018-11-29 14:54:25.458 [INFO ] [ro.process.process 192.168.1.55:3671] - attached link was closed
                      2018-11-29 14:54:25.467 [DEBUG] [nx.internal.client.AbstractKNXClient] - The KNX network link was detached from the process communicator
                      2018-11-29 14:54:25.470 [INFO ] [ro.process.process 192.168.1.55:3671] - detached from 192.168.1.55:3671
                      2018-11-29 14:54:25.481 [DEBUG] [nx.internal.client.AbstractKNXClient] - Bridge knx:ip:knx-ip-gateway is disconnecting from the KNX bus
                      2018-11-29 14:54:25.483 [DEBUG] [calimero.mgmt.TL 192.168.1.55:3671  ] - detached from 192.168.1.55:3671
                      2018-11-29 14:54:25.485 [DEBUG] [calimero.mgmt.MC 192.168.1.55:3671  ] - detached from 192.168.1.55:3671
                      2018-11-29 14:54:25.487 [DEBUG] [nx.internal.client.AbstractKNXClient] - KNX link has been lost (reason: server request on object tunneling link (closed) 192.168.1.55:3671 TP1 medium, device 0.0.0, hopcount 6)
                      2018-11-29 14:54:25.487 [DEBUG] [calimero.mgmt.TL 192.168.1.55:3671  ] - detached from 192.168.1.55:3671
                      2018-11-29 14:54:25.489 [DEBUG] [calimero.mgmt.MC 192.168.1.55:3671  ] - detached from 192.168.1.55:3671
                      2018-11-29 14:54:25.510 [INFO ] [ero.device.process 192.168.1.55:3671] - detached from 192.168.1.55:3671
                      2018-11-29 14:54:25.512 [INFO ] [calimero.link.192.168.1.55:3671     ] - link closed
                      2018-11-29 14:54:25.515 [DEBUG] [nx.internal.client.AbstractKNXClient] - Bridge knx:ip:knx-ip-gateway is connecting to the KNX bus
                      2018-11-29 14:54:25.518 [DEBUG] [binding.knx.internal.client.IPClient] - Establishing connection to KNX bus on 192.168.1.55:3671 in mode TUNNEL.
                      2018-11-29 14:54:25.528 [INFO ] [NXnet/IP Tunneling 192.168.1.55:3671] - establish connection from /192.168.1.44:60867 to /192.168.1.55:3671
                      2018-11-29 14:54:25.533 [DEBUG] [NXnet/IP Tunneling 192.168.1.55:3671] - wait for connect response from /192.168.1.55:3671 ...
                      2018-11-29 14:54:25.543 [ERROR] [NXnet/IP Tunneling 192.168.1.55:3671] - establishing connection failed, null
                      2018-11-29 14:54:25.546 [DEBUG] [nx.internal.client.AbstractKNXClient] - Error connecting to the bus: null
                      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.ClientConnection.connect(ClientConnection.java:190) ~[?:?]
                          at tuwien.auto.calimero.knxnetip.KNXnetIPTunnel.<init>(KNXnetIPTunnel.java:159) ~[?:?]
                          at org.openhab.binding.knx.internal.client.IPClient.getConnection(IPClient.java:107) ~[?:?]
                          at org.openhab.binding.knx.internal.client.IPClient.createKNXNetworkLinkIP(IPClient.java:90) ~[?:?]
                          at org.openhab.binding.knx.internal.client.IPClient.establishConnection(IPClient.java:77) ~[?:?]
                          at org.openhab.binding.knx.internal.client.AbstractKNXClient.connect(AbstractKNXClient.java:178) ~[?:?]
                          at org.openhab.binding.knx.internal.client.AbstractKNXClient.connectIfNotAutomatic(AbstractKNXClient.java:164) ~[?:?]
                          at org.openhab.binding.knx.internal.client.AbstractKNXClient.readNextQueuedDatapoint(AbstractKNXClient.java:272) ~[?:?]
                          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) [?:?]
                      2018-11-29 14:54:25.583 [DEBUG] [nx.internal.client.AbstractKNXClient] - Bridge knx:ip:knx-ip-gateway is disconnecting from the KNX bus
                      2018-11-29 14:54:25.598 [DEBUG] [nx.internal.client.AbstractKNXClient] - Bridge knx:ip:knx-ip-gateway is disconnecting from the KNX bus
                      2018-11-29 14:54:25.601 [DEBUG] [nx.internal.client.AbstractKNXClient] - Bridge knx:ip:knx-ip-gateway is connecting to the KNX bus
                      2018-11-29 14:54:25.603 [DEBUG] [binding.knx.internal.client.IPClient] - Establishing connection to KNX bus on 192.168.1.55:3671 in mode TUNNEL.
                      2018-11-29 14:54:25.606 [INFO ] [NXnet/IP Tunneling 192.168.1.55:3671] - establish connection from /192.168.1.44:51042 to /192.168.1.55:3671
                      2018-11-29 14:54:25.609 [DEBUG] [NXnet/IP Tunneling 192.168.1.55:3671] - wait for connect response from /192.168.1.55:3671 ...
                      2018-11-29 14:54:25.624 [DEBUG] [NXnet/IP Tunneling 192.168.1.55:3671] - using server-assigned data endpoint /192.168.1.55:3671
                      2018-11-29 14:54:25.628 [INFO ] [NXnet/IP Tunneling 192.168.1.55:3671] - connection established (channel 243)
                      2018-11-29 14:54:25.638 [DEBUG] [.knx.handler.AbstractKNXThingHandler] - 'knx:device:knx-ip-gateway:knx' will be polled every 300s
                      Vorschläge werde ich gerne ausprobieren.
                      Liebe Grüße aus Wien
                      Peter

                      Kommentar


                        #41
                        So bei mir war es auch wieder soweit.
                        Code:
                        2018-12-01 06:11:20.441 [INFO ] [et/IP Tunneling 192.168.179.177:3671] - close connection - server request
                        2018-12-01 06:11:20.457 [INFO ] [alimero.mgmt.TL 192.168.179.177:3671] - attached link was closed
                        2018-12-01 06:11:20.465 [DEBUG] [nx.internal.client.AbstractKNXClient] - Bridge knx:ip:bridge is disconnecting from the KNX bus
                        2018-12-01 06:11:20.468 [DEBUG] [alimero.mgmt.TL 192.168.179.177:3671] - detached from 192.168.179.177:3671
                        2018-12-01 06:11:20.470 [DEBUG] [alimero.mgmt.MC 192.168.179.177:3671] - detached from 192.168.179.177:3671
                        2018-12-01 06:11:20.473 [DEBUG] [alimero.mgmt.TL 192.168.179.177:3671] - detached from 192.168.179.177:3671
                        2018-12-01 06:11:20.464 [INFO ] [alimero.mgmt.MC 192.168.179.177:3671] - attached link was closed
                        2018-12-01 06:11:20.493 [DEBUG] [alimero.mgmt.MC 192.168.179.177:3671] - detached from 192.168.179.177:3671
                        2018-12-01 06:11:20.496 [INFO ] [process.process 192.168.179.177:3671] - detached from 192.168.179.177:3671
                        2018-12-01 06:11:20.498 [INFO ] [alimero.mgmt.TL 192.168.179.177:3671] - attached link was closed
                        2018-12-01 06:11:20.510 [INFO ] [.device.process 192.168.179.177:3671] - detached from 192.168.179.177:3671
                        2018-12-01 06:11:20.510 [INFO ] [alimero.mgmt.MC 192.168.179.177:3671] - attached link was closed
                        2018-12-01 06:11:20.543 [DEBUG] [nx.internal.client.AbstractKNXClient] - Bridge knx:ip:bridge is connecting to the KNX bus
                        2018-12-01 06:11:20.546 [INFO ] [process.process 192.168.179.177:3671] - attached link was closed
                        2018-12-01 06:11:20.555 [INFO ] [calimero.link.192.168.179.177:3671 ] - link closed
                        2018-12-01 06:11:20.545 [DEBUG] [binding.knx.internal.client.IPClient] - Establishing connection to KNX bus on 192.168.179.177:3671 in mode TUNNEL.
                        2018-12-01 06:11:20.562 [INFO ] [et/IP Tunneling 192.168.179.177:3671] - establish connection from /192.168.179.176:49008 to /192.168.179.177:3671
                        2018-12-01 06:11:20.567 [DEBUG] [et/IP Tunneling 192.168.179.177:3671] - wait for connect response from /192.168.179.177:3671 ...
                        2018-12-01 06:11:20.580 [ERROR] [et/IP Tunneling 192.168.179.177:3671] - establishing connection failed, null
                        2018-12-01 06:11:20.581 [DEBUG] [nx.internal.client.AbstractKNXClient] - Error connecting to the bus: null
                        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.ClientConnection.connect(ClientConnection.java:190) ~[?:?]
                            at tuwien.auto.calimero.knxnetip.KNXnetIPTunnel.<init>(KNXnetIPTunnel.java:159) ~[?:?]
                            at org.openhab.binding.knx.internal.client.IPClient.getConnection(IPClient.java:107) ~[?:?]
                            at org.openhab.binding.knx.internal.client.IPClient.createKNXNetworkLinkIP(IPClient.java:90) ~[?:?]
                            at org.openhab.binding.knx.internal.client.IPClient.establishConnection(IPClient.java:77) ~[?:?]
                            at org.openhab.binding.knx.internal.client.AbstractKNXClient.connect(AbstractKNXClient.java:178) ~[?:?]
                            at org.openhab.binding.knx.internal.client.AbstractKNXClient.connectIfNotAutomatic(AbstractKNXClient.java:164) ~[?:?]
                            at org.openhab.binding.knx.internal.client.AbstractKNXClient.readNextQueuedDatapoint(AbstractKNXClient.java:272) ~[?:?]
                            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) [?:?]
                        2018-12-01 06:11:20.642 [DEBUG] [nx.internal.client.AbstractKNXClient] - Bridge knx:ip:bridge is disconnecting from the KNX bus
                        Wenn ich das richtig aus dem log lese wird der Reconnect nur ein mal durchgeführt oder ?

                        Vielleicht ist es eine Lösung dies so oft zu versuchen bis die Verbindung wieder aufgebaut ist natürlich in gewissen Zeit abständen. Dann könnte sogar über einen Parameter die Anzahl vorgegeben werden.
                        Gruß

                        Guido

                        Kommentar


                          #42
                          Zitat von Höhlenbär Beitrag anzeigen
                          Wenn ich das richtig aus dem log lese wird der Reconnect nur ein mal durchgeführt oder ?
                          Das sollte definitiv nicht so sein, openHAB sollte den Reconnect so lange erneut versuchen, bis die Verbindung wieder steht. Kann ja sein, dass der knx-Bus mal für ein paar Minuten gestört ist. Auch der Name des Parameters autoReconnectPeriod legt nahe, dass hier ein periodischer Verbindungsversuch gemeint ist. Ein weiterer Grund, diesen Parameter nicht zu niedrig einzustellen, eventuell kommt sonst ein Gateway auf die Idee und blacklistet openHAB, weil es ständig versucht, Kontakt herzustellen Ich habe keine Ahnung, wie "schlau" manche Gateways - insbesondere knx/IP-Router - da inzwischen sind, schließlich könnte es sich hier auch um einen Angriff handeln, um das System lahmzulegen.

                          Kommentar


                            #43
                            Hallo zusammen ,

                            hab das gleiche Problem bei mir ist es das MDT KNX Gateway

                            Code:
                            Bridge knx:ip:knxgw [
                                ipAddress="192.168.90.7",
                                portNumber=3671,
                                type="TUNNEL",
                                readingPause=50,
                                responseTimeout=10,
                                readRetriesLimit=3,
                                autoReconnectPeriod=60,
                                localSourceAddr="1.0.156"
                            
                            ] {
                            Log :
                            Code:
                            018-11-29 21:16:30.576 [TRACE] [g.knx.internal.dpt.KNXCoreTypeMapper] - toType datapoint DPT = 16.001
                            2018-11-29 21:16:30.741 [TRACE] [NXnet/IP Tunneling 192.168.90.7:3671] - received request seq 106 (channel 11) cEMI 29 00 bc e0 11 0a 18 1a 0f 00 80 4d 35 20 53 30 20 41 32 39 33 20 45 30 30
                            2018-11-29 21:16:30.745 [DEBUG] [calimero.link.192.168.90.7:3671 ] - indication 1.1.10->3/0/26 L_Data.ind, low priority hop count 6, tpdu 00 80 4d 35 20 53 30 20 41 32 39 33 20 45 30 30
                            2018-11-29 21:16:30.745 [TRACE] [nx.internal.client.AbstractKNXClient] - Received a Group Write telegram from '1.1.10' to '3/0/26'
                            2018-11-29 21:16:30.748 [DEBUG] [.internal.handler.DeviceThingHandler] - Thing 'knx:device:knxgw:1-1-45' received a Group Write telegram from '1.1.10' for destination '3/0/26'
                            2018-11-29 21:16:30.784 [TRACE] [.internal.handler.DeviceThingHandler] - Thing 'knx:device:knxgw:1-1-45' processes a Group Write telegram for destination '3/0/26' for channel 'knx:device:knxgw:1-1-45:ZENTRAL-Obergeschoss-Z-J-Jalousie-Beschattung-State'
                            2018-11-29 21:16:30.787 [TRACE] [g.knx.internal.dpt.KNXCoreTypeMapper] - toType datapoint DPT = 16.001
                            2018-11-29 21:16:53.594 [TRACE] [NXnet/IP Tunneling 192.168.90.7:3671] - received request seq 107 (channel 11) cEMI 29 00 bc e0 11 03 23 00 03 00 80 07 b2
                            2018-11-29 21:16:53.600 [DEBUG] [calimero.link.192.168.90.7:3671 ] - indication 1.1.3->4/3/0 L_Data.ind, low priority hop count 6, tpdu 00 80 07 b2
                            2018-11-29 21:16:53.604 [TRACE] [nx.internal.client.AbstractKNXClient] - Received a Group Write telegram from '1.1.3' to '4/3/0'
                            2018-11-29 21:16:53.609 [DEBUG] [.internal.handler.DeviceThingHandler] - Thing 'knx:device:knxgw:1-1-45' received a Group Write telegram from '1.1.3' for destination '4/3/0'
                            2018-11-29 21:16:53.603 [DEBUG] [NXnet/IP Tunneling 192.168.90.7:3671] - skip tunneling request with rcv-seq 107 (already received)
                            2018-11-29 21:16:53.619 [INFO ] [NXnet/IP Tunneling 192.168.90.7:3671] - close connection - server request
                            2018-11-29 21:16:53.625 [INFO ] [calimero.mgmt.TL 192.168.90.7:3671 ] - attached link was closed
                            2018-11-29 21:16:53.628 [INFO ] [calimero.mgmt.MC 192.168.90.7:3671 ] - attached link was closed
                            2018-11-29 21:16:53.631 [INFO ] [calimero.mgmt.TL 192.168.90.7:3671 ] - attached link was closed
                            2018-11-29 21:16:53.644 [DEBUG] [nx.internal.client.AbstractKNXClient] - Bridge knx:ip:knxgw is disconnecting from the KNX bus
                            2018-11-29 21:16:53.648 [DEBUG] [calimero.mgmt.TL 192.168.90.7:3671 ] - detached from 192.168.90.7:3671
                            2018-11-29 21:16:53.651 [DEBUG] [calimero.mgmt.MC 192.168.90.7:3671 ] - detached from 192.168.90.7:3671
                            2018-11-29 21:16:53.653 [INFO ] [calimero.mgmt.MC 192.168.90.7:3671 ] - attached link was closed
                            2018-11-29 21:16:53.654 [DEBUG] [calimero.mgmt.TL 192.168.90.7:3671 ] - detached from 192.168.90.7:3671
                            2018-11-29 21:16:53.656 [INFO ] [ro.process.process 192.168.90.7:3671] - attached link was closed
                            2018-11-29 21:16:53.657 [DEBUG] [calimero.mgmt.MC 192.168.90.7:3671 ] - detached from 192.168.90.7:3671
                            2018-11-29 21:16:53.668 [DEBUG] [nx.internal.client.AbstractKNXClient] - The KNX network link was detached from the process communicator
                            2018-11-29 21:16:53.669 [INFO ] [ero.device.process 192.168.90.7:3671] - detached from 192.168.90.7:3671
                            2018-11-29 21:16:53.672 [INFO ] [ro.process.process 192.168.90.7:3671] - detached from 192.168.90.7:3671
                            2018-11-29 21:16:53.672 [DEBUG] [nx.internal.client.AbstractKNXClient] - Bridge knx:ip:knxgw is connecting to the KNX bus
                            2018-11-29 21:16:53.675 [INFO ] [calimero.link.192.168.90.7:3671 ] - link closed
                            2018-11-29 21:16:53.681 [DEBUG] [binding.knx.internal.client.IPClient] - Establishing connection to KNX bus on 192.168.90.7:3671 in mode TUNNEL.
                            2018-11-29 21:16:53.686 [INFO ] [NXnet/IP Tunneling 192.168.90.7:3671] - establish connection from /192.168.90.3:36837 to /192.168.90.7:3671
                            2018-11-29 21:16:53.689 [DEBUG] [NXnet/IP Tunneling 192.168.90.7:3671] - wait for connect response from /192.168.90.7:3671 ...
                            2018-11-29 21:16:53.689 [TRACE] [.internal.handler.DeviceThingHandler] - Thing 'knx:device:knxgw:1-1-45' processes a Group Write telegram for destination '4/3/0' for channel 'knx:device:knxgw:1-1-45:Eltern-HMDT-Heizen-MDT-Temperaturmesswert'
                            2018-11-29 21:16:53.698 [TRACE] [g.knx.internal.dpt.KNXCoreTypeMapper] - toType datapoint DPT = 9.001
                            2018-11-29 21:16:53.698 [ERROR] [NXnet/IP Tunneling 192.168.90.7:3671] - establishing connection failed, null
                            2018-11-29 21:16:53.701 [DEBUG] [nx.internal.client.AbstractKNXClient] - Error connecting to the bus: null
                            java.lang.InterruptedException: null
                            at java.lang.Object.wait(Native Method) ~[?:?]
                            at tuwien.auto.calimero.knxnetip.ConnectionBase.waitF orStateChange(ConnectionBase.java:541) ~[?:?]
                            at tuwien.auto.calimero.knxnetip.ClientConnection.con nect(ClientConnection.java:190) ~[?:?]
                            at tuwien.auto.calimero.knxnetip.KNXnetIPTunnel.<init >(KNXnetIPTunnel.java:159) ~[?:?]
                            at org.openhab.binding.knx.internal.client.IPClient.g etConnection(IPClient.java:107) ~[?:?]
                            at org.openhab.binding.knx.internal.client.IPClient.c reateKNXNetworkLinkIP(IPClient.java:90) ~[?:?]
                            at org.openhab.binding.knx.internal.client.IPClient.e stablishConnection(IPClient.java:77) ~[?:?]
                            at org.openhab.binding.knx.internal.client.AbstractKN XClient.connect(AbstractKNXClient.java:178) ~[?:?]
                            at org.openhab.binding.knx.internal.client.AbstractKN XClient.connectIfNotAutomatic(AbstractKNXClient.ja va:164) ~[?:?]
                            at org.openhab.binding.knx.internal.client.AbstractKN XClient.readNextQueuedDatapoint(AbstractKNXClient. java:272) ~[?:?]
                            at org.openhab.binding.knx.internal.client.AbstractKN XClient.lambda$1(AbstractKNXClient.java:199) ~[?:?]
                            at java.util.concurrent.Executors$RunnableAdapter.cal l(Executors.java:511) [?:?]
                            at java.util.concurrent.FutureTask.runAndReset(Future Task.java:308) [?:?]
                            at java.util.concurrent.ScheduledThreadPoolExecutor$S cheduledFutureTask.access$301(ScheduledThreadPoolE xecutor.java:180) [?:?]
                            at java.util.concurrent.ScheduledThreadPoolExecutor$S cheduledFutureTask.run(ScheduledThreadPoolExecutor .java:294) [?:?]
                            at java.util.concurrent.ThreadPoolExecutor.runWorker( ThreadPoolExecutor.java:1142) [?:?]
                            at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:617) [?:?]
                            at java.lang.Thread.run(Thread.java:745) [?:?]
                            2018-11-29 21:16:53.867 [DEBUG] [nx.internal.client.AbstractKNXClient] - Bridge knx:ip:knxgw is disconnecting from the KNX bus
                            2018-11-29 21:16:53.954 [ERROR] [eclipse.smarthome.model.script.Debug] - Library Rules | OFFLINE

                            Kommentar


                              #44
                              Ich habe auch einen Ausfall mitgeloggt. Verbindung stand erst wieder nach "sudo systemctl restart openhab2.service". "openhab.log" entspricht dem, was Höhlenbär und theneon gepostet haben:
                              Code:
                              2018-12-01 10:54:08.438 [INFO ] [calimero.link.192.168.1.55:3671     ] - link closed
                              2018-12-01 10:54:08.442 [INFO ] [ero.device.process 192.168.1.55:3671] - detached from 192.168.1.55:3671
                              2018-12-01 10:54:08.444 [DEBUG] [nx.internal.client.AbstractKNXClient] - Bridge knx:ip:knx-ip-gateway is connecting to the KNX bus
                              2018-12-01 10:54:08.446 [DEBUG] [binding.knx.internal.client.IPClient] - Establishing connection to KNX bus on 192.168.1.55:3671 in mode TUNNEL.
                              2018-12-01 10:54:08.449 [INFO ] [NXnet/IP Tunneling 192.168.1.55:3671] - establish connection from /192.168.1.44:38135 to /192.168.1.55:3671
                              2018-12-01 10:54:08.451 [DEBUG] [NXnet/IP Tunneling 192.168.1.55:3671] - wait for connect response from /192.168.1.55:3671 ...
                              2018-12-01 10:54:08.472 [DEBUG] [NXnet/IP Tunneling 192.168.1.55:3671] - using server-assigned data endpoint /192.168.1.55:3671
                              2018-12-01 10:54:08.478 [ERROR] [NXnet/IP Tunneling 192.168.1.55:3671] - establishing connection failed, null
                              2018-12-01 10:54:08.481 [DEBUG] [nx.internal.client.AbstractKNXClient] - Error connecting to the bus: null
                              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.ClientConnection.connect(ClientConnection.java:190) ~[?:?]
                                  at tuwien.auto.calimero.knxnetip.KNXnetIPTunnel.<init>(KNXnetIPTunnel.java:159) ~[?:?]
                                  at org.openhab.binding.knx.internal.client.IPClient.getConnection(IPClient.java:107) ~[?:?]
                                  at org.openhab.binding.knx.internal.client.IPClient.createKNXNetworkLinkIP(IPClient.java:90) ~[?:?]
                                  at org.openhab.binding.knx.internal.client.IPClient.establishConnection(IPClient.java:77) ~[?:?]
                                  at org.openhab.binding.knx.internal.client.AbstractKNXClient.connect(AbstractKNXClient.java:178) ~[?:?]
                                  at org.openhab.binding.knx.internal.client.AbstractKNXClient.connectIfNotAutomatic(AbstractKNXClient.java:164) ~[?:?]
                                  at org.openhab.binding.knx.internal.client.AbstractKNXClient.readNextQueuedDatapoint(AbstractKNXClient.java:272) ~[?:?]
                                  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) [?:?]
                              2018-12-01 10:54:08.533 [DEBUG] [nx.internal.client.AbstractKNXClient] - Bridge knx:ip:knx-ip-gateway is disconnecting from the KNX bus

                              Kommentar


                                #45
                                Zitat von udo1toni Beitrag anzeigen
                                Das sollte definitiv nicht so sein, openHAB sollte den Reconnect so lange erneut versuchen, bis die Verbindung wieder steht. Kann ja sein, dass der knx-Bus mal für ein paar Minuten gestört ist. Auch der Name des Parameters autoReconnectPeriod legt nahe, dass hier ein periodischer Verbindungsversuch gemeint ist.
                                Wenn dem so ist, sollte dann nicht im Log die gleiche Sequenz zyklisch zu sehen sein ?
                                Gruß

                                Guido

                                Kommentar

                                Lädt...
                                X