Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. IoBroker - Neustart, Javascript keine Funktion

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    IoBroker - Neustart, Javascript keine Funktion

    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      mike2712 @paul53 last edited by

      @paul53
      das hat ein gelbes Pause Zeichen ?
      Inhalt ist so wie aus dem Forum:

      /*  System Homematic Servicemeldungen
      Skript erstellt Variablen Service.Homematic.*
      http://forum.iobroker.org/viewtopic.php?f=21&t=914#p9153
      
      erstellt: 04.08.2015 von paul53
      angepasst von pix
      05.10.2015 STICKY UNREACH wird jetzt auf true gesetzt und damit gelöscht http://forum.iobroker.org/viewtopic.php?f=21&t=914&p=9200&hilit=sticky#p9173
      04.02.2016 Instanz Variable
      */
      
      instanz = 'javascript.1.';
      
      // Service Meldungen
      
      createState('Servicemeldungen.Homematic.Anzahl', 0, {
          name: 'Homematic Servicemeldungen Anzahl',
          desc: 'Zahl der Homematic Servicemeldungen',
          type: 'number'
      });
      createState('Servicemeldungen.Homematic.Text', "", {
          name: 'Homematic Servicemeldungen Text',
          desc: 'Liste der Geräte, die Servicemeldungen produzieren',
          type: 'string'
      });
      
      var idAnzahl = instanz + 'Servicemeldungen.Homematic.Anzahl',
          idText =   instanz + 'Servicemeldungen.Homematic.Text';
      
      var SelectorUNREACH = $('channel[state.id=*.UNREACH]');
      var SelectorSTICKY_UNREACH = $('channel[state.id=*.STICKY_UNREACH]');
      var SelectorLOWBAT = $('channel[state.id=*.LOWBAT]');
      var SelectorCONFIG_PENDING = $('channel[state.id=*.CONFIG_PENDING]');
      
      function countService(obj) {
          var anzahl    = 0;
          var text      = "";
      
         function count(id) {
              var status = getState(id).val;                // Zustand abfragen (jedes Element)
              if (status) {                        // wenn Zustand = true, dann wird die Anzahl der Geräte hochgezählt
                  var temptext = getObject(id).common.name;
                  var Geraet = temptext.split(':');
                  text = text + Geraet[0] + " ==> ";
                  temptext = Geraet[1];
                  Geraet = temptext.split('.');
                  text = text + Geraet[1] + "<br>";
                  ++anzahl;                                  // Zählt die Anzahl der Service-Alarme
              }
          }
       
          SelectorUNREACH.each(function (id, i) {
              count(id);
           });
            
          SelectorSTICKY_UNREACH.each(function (id, i) {
              var status = getState(id).val;                // Zustand abfragen (jedes Element)
              if (status) {                        // wenn Zustand = true, dann wird die Anzahl der Geräte hochgezählt
                  log('STICKY_UNREACH Meldung: ' + id + ' wurde auf <true> gesetzt. Das Homematic Gerät ist wieder uneingeschränkt erreichbar.');
                  setState(id, false); // STICKY_UNREACH werden gelöscht
              }
          });
            
          SelectorLOWBAT.each(function (id, i) {
              count(id);
          });
            
          SelectorCONFIG_PENDING.each(function (id, i) {
              count(id);
          });
            
      
          // Schleife ist durchlaufen. Im Log wird der aktuelle Status (Anzahl, davon Service zutreffend) ausgegeben
          log("Homematic-Servicemeldungen: " + text);
          log("Anzahl Homematic-Servicemeldungen: " + anzahl);
      
          // die ermittelten Werte werden als javascript.0. Variable in ioBroker gespeichert 
          if (!anzahl) { 
              text = "keine Servicemeldungen";
          }
          setState(idText, text);          // Schreibt die IDs der Datenpunkte mit Service Meldung
          setState(idAnzahl, anzahl);      // Schreibt die aktuelle Anzahl der Service Meldungen
      }   
      
      SelectorUNREACH.on(function(obj) {          // bei Zustandänderung *.UNREACH in allen Gewerken
          countService(obj);
      });
      
      SelectorSTICKY_UNREACH.on(function(obj) {   // bei Zustandänderung *.STICKY_UNREACH in allen Gewerken
          countService(obj);
      });
      
      SelectorLOWBAT.on(function(obj) {          // bei Zustandänderung *.LOWBAT in allen Gewerken
          countService(obj);
      });
      
      SelectorCONFIG_PENDING.on(function(obj) {   // bei Zustandänderung *.CONFIG_PENDING in allen Gewerken
          countService(obj);
      });
      
      // alternative Abfrage jede Minute
      schedule("*/15 * * * *", function () {
          countService();
      });
      
      // Ausführung bei Scriptstart
      countService();
      
      paul53 1 Reply Last reply Reply Quote 0
      • paul53
        paul53 @mike2712 last edited by paul53

        @mike2712

                    var Geraet = temptext.split(':');
        

        Das Skript erwartet, dass der Datenpunkt-Name einen Doppelpunkt enthält.
        Bau mal nach Zeile 41 ein Log ein, um die Namen zu sehen.

        log(temptext);
        
        M 1 Reply Last reply Reply Quote 0
        • M
          mike2712 @paul53 last edited by

          @paul53 sagte in IoBroker - Neustart, Javascript keine Funktion:

          log(temptext);
          Danach kommt folgender LOG, das Script wird angehalten und steht auf Pause, das kann doch dann meine eigentlichen Probleme gar nicht verursachen, oder, wenn das Script angehalten ist?

          19:59:06.306	info	javascript.1 Stop script script.js.Allgemein.Servicemeldungen
          19:59:08.911	info	javascript.1 Start javascript script.js.Allgemein.Servicemeldungen
          19:59:08.911	info	javascript.1 script.js.Allgemein.Servicemeldungen: Badezimmer Fenster:0.UNREACH
          19:59:08.911	info	javascript.1 script.js.Allgemein.Servicemeldungen: UNREACH
          19:59:08.911	error	javascript.1 script.js.Allgemein.Servicemeldungen: script.js.Allgemein.Servicemeldungen:46
          19:59:08.911	error	javascript.1 at count (script.js.Allgemein.Servicemeldungen:46:31)
          19:59:08.911	error	javascript.1 at script.js.Allgemein.Servicemeldungen:53:9
          19:59:08.911	error	javascript.1 at countService (script.js.Allgemein.Servicemeldungen:52:21)
          19:59:08.911	error	javascript.1 at script.js.Allgemein.Servicemeldungen:107:1
          
          paul53 1 Reply Last reply Reply Quote 0
          • paul53
            paul53 @mike2712 last edited by paul53

            @mike2712

            19:59:08.911	info	javascript.1 script.js.Allgemein.Servicemeldungen: UNREACH
            

            Es scheint einen Datenpunkt mit Zustand UNREACH = true zu geben, der nur den Namen UNREACH hat.
            Ändere mal das Log in Zeile 42 nach

            log(id + ': ' + temptext);
            

            um zu sehen, welcher Datenpunkt es ist.

            M 1 Reply Last reply Reply Quote 0
            • M
              mike2712 @paul53 last edited by

              @paul53 kann es sein das dieses mit den Homematic Fenterdrehgriff Kontakten zusammenhängt?
              Da musste ich vor kurzen einen ablernen und neu anlernen, ich vermute das es dann vielleicht in iobroker noch drin steckt? Wenn ich etwas in der CCU ändere, werden ja nur zusätzliche Sachen automatisch zugefügt, aber keine Datenpunkte gelöscht, oder?

              Kann den das mein allgemeines Problem sein, was passiert den da, das Script wird doch automatisch pausiert, aber die Probleme sind weiterhin da.

              paul53 1 Reply Last reply Reply Quote 0
              • paul53
                paul53 @mike2712 last edited by

                @mike2712 sagte:

                das Script wird doch automatisch pausiert

                Wieso wird es automatisch pausiert ?

                M 1 Reply Last reply Reply Quote 1
                • M
                  mike2712 @paul53 last edited by

                  @paul53 kannte ich so auch noch nicht, das Script startet und aufgrund der Fehler im Script kommt ein gelbes Pause Zeichen.
                  2ad37853-c7c9-4dc8-bcec-1d960059f028-image.png
                  Hier der neue LOG:

                  20:29:39.540	info	javascript.1 Stop script script.js.Allgemein.Servicemeldungen
                  20:29:43.034	info	javascript.1 Start javascript script.js.Allgemein.Servicemeldungen
                  20:29:43.034	info	javascript.1 script.js.Allgemein.Servicemeldungen: hm-rpc.0.MEQ0214836.0.UNREACH: Badezimmer Fenster:0.UNREACH
                  20:29:43.034	info	javascript.1 script.js.Allgemein.Servicemeldungen: iqontrol.0.Views.Tanel.0000__Tanel Licht.UNREACH: UNREACH
                  20:29:43.034	error	javascript.1 script.js.Allgemein.Servicemeldungen: script.js.Allgemein.Servicemeldungen:50
                  20:29:43.034	error	javascript.1 at count (script.js.Allgemein.Servicemeldungen:50:31)
                  20:29:43.034	error	javascript.1 at script.js.Allgemein.Servicemeldungen:57:9
                  20:29:43.034	error	javascript.1 at countService (script.js.Allgemein.Servicemeldungen:56:21)
                  20:29:43.034	error	javascript.1 at script.js.Allgemein.Servicemeldungen:111:1
                  
                  paul53 1 Reply Last reply Reply Quote 0
                  • paul53
                    paul53 @mike2712 last edited by paul53

                    @mike2712: Dieser Datenpunkt erzeugt den Fehler:

                    iqontrol.0.Views.Tanel.0000__Tanel Licht.UNREACH

                    Ändere den UNREACH-Selektor (s.u.).

                    M 1 Reply Last reply Reply Quote 0
                    • M
                      mike2712 @paul53 last edited by

                      @paul53 Das sind die Datenpunkte aus Qontrol, richtig ?

                      die sind aber an jedem Qontrol so angebunden, warum macht nur der eine Fehler, wo kann ich den ändern?

                      86ed0cca-4a6c-4d22-bcc5-8eb64df0b4ea-image.png

                      paul53 2 Replies Last reply Reply Quote 0
                      • paul53
                        paul53 @mike2712 last edited by

                        @mike2712 Was ist Qontrol ?

                        M 1 Reply Last reply Reply Quote 0
                        • paul53
                          paul53 @mike2712 last edited by

                          @mike2712 sagte:

                          wo kann ich den ändern?

                          Du solltest die Selektoren ändern:

                          var SelectorUNREACH = $('channel[state.id=hm-rpc.*.UNREACH]');
                          
                          M 1 Reply Last reply Reply Quote 0
                          • M
                            mike2712 @paul53 last edited by

                            @paul53 Jetzt habe ich den rausgelöscht, wie vermutet kommt jetzt der nächste, nicht Licht, sondern Jalousie.

                            20:42:07.108	info	javascript.1 Stop script script.js.Allgemein.Servicemeldungen
                            20:42:11.398	info	javascript.1 Start javascript script.js.Allgemein.Servicemeldungen
                            20:42:11.398	info	javascript.1 script.js.Allgemein.Servicemeldungen: hm-rpc.0.MEQ0214836.0.UNREACH: Badezimmer Fenster:0.UNREACH
                            20:42:11.398	info	javascript.1 script.js.Allgemein.Servicemeldungen: iqontrol.0.Views.Tanel.0001__Tanel Jalousie.UNREACH: UNREACH
                            20:42:11.413	error	javascript.1 script.js.Allgemein.Servicemeldungen: script.js.Allgemein.Servicemeldungen:50
                            20:42:11.413	error	javascript.1 at count (script.js.Allgemein.Servicemeldungen:50:31)
                            20:42:11.413	error	javascript.1 at script.js.Allgemein.Servicemeldungen:57:9
                            20:42:11.413	error	javascript.1 at countService (script.js.Allgemein.Servicemeldungen:56:21)
                            20:42:11.413	error	javascript.1 at script.js.Allgemein.Servicemeldungen:111:1
                            

                            Sorry iQontrol
                            https://forum.iobroker.net/topic/22039/neuer-adapter-visualisierung-iqontrol

                            1 Reply Last reply Reply Quote 0
                            • M
                              mike2712 @paul53 last edited by

                              @paul53
                              Da habe ich was falsch verstanden? Habe den hier bei unreach den Wert rausgenommen.

                              b024cc2e-cc7d-45c2-90cc-3954f6a36249-image.png

                              Das Script kommt doch sogar von Dir, ist mein Script noch aktuell, ich kann leider nichts anderes finden.

                              paul53 1 Reply Last reply Reply Quote 0
                              • paul53
                                paul53 @mike2712 last edited by paul53

                                @mike2712 sagte:

                                Das Script kommt doch sogar von Dir

                                Das ist eines meiner ersten Skripte gewesen. Damals gab es noch kein iQontrol. Nur HomeMatic hatte Datenpunkte mit UNREACH am Ende. Deshalb erweitere den Selektor um hm-rpc. vor dem Sternchen:

                                var SelectorUNREACH = $('channel[state.id=hm-rpc.*.UNREACH]');
                                
                                M 1 Reply Last reply Reply Quote 0
                                • M
                                  mike2712 @paul53 last edited by

                                  @paul53 ok, ist das weiter entwickelt worden, scheinbar nicht, schade finde das sehr gut und nützlich.

                                  Was genau muss ich den in dieser Zeile ändern ?

                                  var SelectorUNREACH = $('channel[state.id=hm-rpc.*.UNREACH]');

                                  Ich kann leider kein Java, dann würden die Homematic Unreach auch nicht mehr funktionieren? Das wäre auch blöd.

                                  paul53 1 Reply Last reply Reply Quote 0
                                  • paul53
                                    paul53 @mike2712 last edited by

                                    @mike2712 sagte:

                                    dann würden die Homematic Unreach auch nicht mehr funktionieren?

                                    Der Zusatz hm-rpc. begrenzt die Gültigkeit auf HomeMatic.

                                    M 1 Reply Last reply Reply Quote 1
                                    • M
                                      mike2712 @paul53 last edited by

                                      @paul53 super, vielen Dank, das läuft jetzt ohne Probleme durch.

                                      Aber nochmal, kann das meine Probleme verursacht haben da dieses Script ja auf Pause stand?
                                      Obwohl was dafür spricht, ist ja das ich das Gefühl hatte das es mit testen von iQontrol zusammenhängt. Aber verstehe es nicht, da das Script ja pausiert. Was passiert den durch diesen Fehler, die wichtigen Funktionen waren ja eigentlich im Javascript 0.

                                      paul53 1 Reply Last reply Reply Quote 0
                                      • paul53
                                        paul53 @mike2712 last edited by

                                        @mike2712 sagte:

                                        kann das meine Probleme verursacht haben da dieses Script ja auf Pause stand?

                                        Wirklich ? Wenn das Skript nicht aktiviert ist, kann es auch keine Logeinträge erzeugen.

                                        M 1 Reply Last reply Reply Quote 0
                                        • M
                                          mike2712 @paul53 last edited by

                                          @paul53 hmm? Das stimmt wohl, komisch. Ich warte jetzt mal ab ob die Probleme ausgestanden sind, vielen Dank nochmal.

                                          1 Reply Last reply Reply Quote 0
                                          • M
                                            mike2712 last edited by mike2712

                                            Ich habe weiterhin Probleme das Javascript mit der Instanz 0 nicht ausgeführt wird, ich habe weiterhin sehr viele Warnungen und Fehler im LOG.
                                            Wie kann ich den den Fehler finden, Fehlermeldungen zum Javascript fallen mir nicht auf.
                                            Das System läuft total instabil.

                                            Javascript scheint einfach nicht zu laufen, obwohl im Adapter alles grün ist, die Funktionen funktionieren nach einem Neustart ohne Probleme, wie kann ich den Fehler eingrenzen?

                                            2019-05-26 00:00:00.156 - warn: javascript.0 Cannot calculate "night" for 52.133751464629825, 7.540483474731443
                                            2019-05-26 00:00:01.186 - warn: javascript.0 Cannot calculate "nightEnd" for 52.133751464629825, 7.540483474731443
                                            2019-05-26 00:10:20.881 - warn: sonoff.0 Old client Sonoff-Steckdose-14 with secret 1558822182333_9671 sends publish. Ignore! Actual secret is 1558822217589_8185
                                            2019-05-26 00:10:20.881 - warn: sonoff.0 Old client Sonoff-Steckdose-14 with secret 1558822182333_9671 sends pingreq. Ignore! Actual secret is 1558822217589_8185
                                            2019-05-26 00:10:24.750 - warn: sonoff.0 Old client Sonoff-Steckdose-17 with secret 1558822048485_8304 sends pingreq. Ignore! Actual secret is 1558822213034_9291
                                            
                                            2019-05-26 01:01:35.126 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:01:35.126 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:01:42.895 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:01:42.895 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:01:42.895 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/wlan/guest_access.lua?0=0&sid=e5d517fc26e675b2"}}
                                            2019-05-26 01:01:42.895 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:01:52.894 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:01:52.894 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:02:00.023 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/wlan/guest_access.lua?0=0&sid=e5d517fc26e675b2"}}
                                            2019-05-26 01:02:00.023 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:02:02.893 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:02:02.893 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:02:02.893 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:02:02.893 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:02:12.721 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:02:12.721 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:02:12.721 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:02:12.721 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:02:22.923 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:02:22.923 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:02:22.923 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:02:22.923 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:02:32.782 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:02:32.782 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:02:32.923 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:02:32.923 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:02:42.782 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:02:42.782 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:02:42.782 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:02:42.782 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:02:49.833 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/wlan/guest_access.lua?0=0&sid=e5d517fc26e675b2"}}
                                            2019-05-26 01:02:49.833 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:02:52.922 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:02:52.922 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:03:02.781 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:03:02.781 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:03:02.781 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:03:02.781 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:03:09.693 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/wlan/guest_access.lua?0=0&sid=e5d517fc26e675b2"}}
                                            2019-05-26 01:03:09.693 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:03:12.922 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:03:12.922 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:03:12.922 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:03:12.922 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:03:19.693 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/wlan/guest_access.lua?0=0&sid=e5d517fc26e675b2"}}
                                            2019-05-26 01:03:19.693 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:03:22.781 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:03:22.781 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:03:32.984 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:03:32.984 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:03:39.988 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/wlan/guest_access.lua?0=0&sid=e5d517fc26e675b2"}}
                                            2019-05-26 01:03:39.988 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:03:42.983 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:03:42.983 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:03:42.983 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:03:42.983 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:03:52.921 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:03:52.921 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:03:52.921 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:03:52.921 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:04:02.889 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:04:02.889 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:04:02.983 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:04:02.983 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:04:09.924 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:04:09.924 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:04:09.924 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/wlan/guest_access.lua?0=0&sid=e5d517fc26e675b2"}}
                                            2019-05-26 01:04:09.924 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:04:12.919 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:04:12.919 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:04:20.032 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/wlan/guest_access.lua?0=0&sid=e5d517fc26e675b2"}}
                                            2019-05-26 01:04:20.032 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:04:22.778 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:04:22.778 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:04:30.032 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/wlan/guest_access.lua?0=0&sid=e5d517fc26e675b2"}}
                                            2019-05-26 01:04:30.032 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:04:32.934 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:04:32.934 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:04:42.980 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:04:42.980 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:04:50.328 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/wlan/guest_access.lua?0=0&sid=e5d517fc26e675b2"}}
                                            2019-05-26 01:04:50.328 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:04:52.980 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:04:52.980 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:04:52.980 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:04:52.980 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:04:59.922 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/wlan/guest_access.lua?0=0&sid=e5d517fc26e675b2"}}
                                            2019-05-26 01:04:59.922 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:05:02.839 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:05:02.839 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:05:02.839 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:05:02.839 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:05:10.031 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/wlan/guest_access.lua?0=0&sid=e5d517fc26e675b2"}}
                                            2019-05-26 01:05:10.031 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:05:12.824 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:05:12.824 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:05:12.824 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:05:12.824 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:05:20.125 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/wlan/guest_access.lua?0=0&sid=e5d517fc26e675b2"}}
                                            2019-05-26 01:05:20.125 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:05:22.823 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:05:22.823 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:05:22.823 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}}
                                            2019-05-26 01:05:22.823 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:05:30.031 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/wlan/guest_access.lua?0=0&sid=e5d517fc26e675b2"}}
                                            2019-05-26 01:05:30.031 - error: fritzdect.0 no response part in returned message
                                            2019-05-26 01:30:46.927 - info: javascript.0 script.js.Steckdosen.PV-Leistung: 209
                                            2019-05-26 01:31:46.768 - error: cloud.0 Socket error: Error: websocket error
                                            2019-05-26 01:31:46.768 - info: cloud.0 Connection changed: transport error
                                            2019-05-26 01:31:46.768 - info: cloud.0 Connection lost
                                            2019-05-26 01:31:57.346 - error: host.Home-ioBroker instance system.adapter.cloud.0 terminated with code 4294967196 ()
                                            2019-05-26 01:31:57.346 - info: host.Home-ioBroker Restart adapter system.adapter.cloud.0 because enabled
                                            2019-05-26 01:31:58.375 - info: host.Home-ioBroker instance system.adapter.cloud.0 started with pid 20996
                                            2019-05-26 01:32:18.187 - info: alexa2.0 Alexa-Push-Connection disconnected - retry: Retry Connection in 5s
                                            2019-05-26 01:32:23.132 - warn: alexa2.0 Disabling some commands for device because of unknown type. Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
                                            2019-05-26 01:32:23.132 - warn: alexa2.0 Device-type:AKPGW064GI9HE (MICROPHONE,PERSISTENT_CONNECTION,FLASH_BRIEFING,ACTIVE_AFTER_FRO,CHANGE_NAME,VOLUME_SETTING,SUPPORTS_SOFTWARE_VERSION,ARTHUR_TARGET,SUPPORTS_CONNECTED_HOME_CLOUD_ONLY,ALLOW_LOG_UPLOAD)
                                            2019-05-26 01:32:24.973 - info: alexa2.0 Alexa-Push-Connection established. Disable Polling
                                            2019-05-26 01:32:28.686 - warn: alexa2.0 Disabling some commands for device because of unknown type. Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
                                            2019-05-26 01:32:28.686 - warn: alexa2.0 Device-type:AKPGW064GI9HE (MICROPHONE,FLASH_BRIEFING,ARTHUR_TARGET,ACTIVE_AFTER_FRO,SUPPORTS_SOFTWARE_VERSION,VOLUME_SETTING,SUPPORTS_CONNECTED_HOME_CLOUD_ONLY,CHANGE_NAME,PERSISTENT_CONNECTION,ALLOW_LOG_UPLOAD)
                                            2019-05-26 01:32:53.147 - info: cloud.0 starting. Version 2.6.2 in C:/iobroker/node_modules/iobroker.cloud, node: v10.15.1
                                            2019-05-26 01:32:53.381 - info: cloud.0 Connecting with https://iobroker.pro:10555 with "@pro_mike@mike-holtgrefe.de_b621e8a0-23d2-11e8-8035-a92015b605a4"
                                            2019-05-26 01:32:58.841 - info: cloud.0 Trying to connect as system.user.admin
                                            2019-05-26 01:33:40.228 - error: iot.0 read ECONNRESET
                                            2019-05-26 01:33:40.244 - info: iot.0 Connection changed: disconnect
                                            2019-05-26 01:33:40.244 - info: iot.0 Connection lost
                                            2019-05-26 01:33:41.352 - error: host.Home-ioBroker instance system.adapter.sonoff.0 terminated with code 7 (Adapter already running)
                                            2019-05-26 01:33:41.352 - info: host.Home-ioBroker Restart adapter system.adapter.sonoff.0 because enabled
                                            2019-05-26 01:33:45.657 - info: iot.0 Connection changed: connect
                                            2019-05-26 01:33:55.874 - warn: alexa2.0 Reconnection to DB.
                                            2019-05-26 01:33:55.890 - warn: alexa2.0 Reconnection to DB.
                                            2019-05-26 01:33:55.907 - warn: hm-rpc.0 Reconnection to DB.
                                            2019-05-26 01:33:55.922 - warn: hm-rpc.0 Reconnection to DB.
                                            2019-05-26 01:33:55.984 - warn: tradfri.0 Reconnection to DB.
                                            2019-05-26 01:33:56.000 - warn: tradfri.0 Reconnection to DB.
                                            2019-05-26 01:34:01.443 - warn: pushover.0 Reconnection to DB.
                                            2019-05-26 01:34:01.443 - warn: pushover.0 Reconnection to DB.
                                            2019-05-26 01:34:11.725 - info: host.Home-ioBroker instance system.adapter.sonoff.0 started with pid 26720
                                            2019-05-26 01:34:12.941 - warn: hm-rega.0 Reconnection to DB.
                                            2019-05-26 01:34:12.957 - warn: hm-rega.0 Reconnection to DB.
                                            2019-05-26 01:34:13.174 - warn: web.0 Reconnection to DB.
                                            2019-05-26 01:34:13.174 - warn: web.0 Reconnection to DB.
                                            2019-05-26 01:34:13.721 - warn: hm-rpc.2 Reconnection to DB.
                                            2019-05-26 01:34:13.737 - warn: hm-rpc.2 Reconnection to DB.
                                            2019-05-26 01:34:13.689 - warn: admin.0 Reconnection to DB.
                                            2019-05-26 01:34:13.705 - warn: admin.0 Reconnection to DB.
                                            2019-05-26 01:34:16.528 - warn: fritzdect.0 Reconnection to DB.
                                            2019-05-26 01:34:16.528 - warn: fritzdect.0 Reconnection to DB.
                                            2019-05-26 01:34:19.696 - info: cloud.0 Trying to connect as system.user.admin
                                            2019-05-26 01:34:26.778 - warn: tr-064.0 Reconnection to DB.
                                            2019-05-26 01:34:26.794 - warn: tr-064.0 Reconnection to DB.
                                            2019-05-26 01:34:27.590 - warn: hm-rpc.0 Reconnection to DB.
                                            2019-05-26 01:34:27.590 - warn: hm-rpc.0 Reconnection to DB.
                                            2019-05-26 01:34:27.620 - warn: alexa2.0 Reconnection to DB.
                                            2019-05-26 01:34:27.620 - warn: alexa2.0 Reconnection to DB.
                                            2019-05-26 01:34:28.230 - warn: tradfri.0 Reconnection to DB.
                                            2019-05-26 01:34:28.230 - warn: tradfri.0 Reconnection to DB.
                                            2019-05-26 01:34:28.729 - warn: iot.0 Reconnection to DB.
                                            2019-05-26 01:34:28.729 - warn: iot.0 Reconnection to DB.
                                            2019-05-26 01:34:29.289 - warn: fritzdect.0 Reconnection to DB.
                                            2019-05-26 01:34:29.289 - warn: fritzdect.0 Reconnection to DB.
                                            2019-05-26 01:34:29.492 - error: pushover.0 already running
                                            2019-05-26 01:34:29.727 - error: host.Home-ioBroker instance system.adapter.pushover.0 terminated with code 7 (Adapter already running)
                                            2019-05-26 01:34:29.727 - info: host.Home-ioBroker Restart adapter system.adapter.pushover.0 because enabled
                                            2019-05-26 01:34:30.804 - error: host.Home-ioBroker instance system.adapter.sayit.0 terminated with code 7 (Adapter already running)
                                            2019-05-26 01:34:30.804 - info: host.Home-ioBroker Restart adapter system.adapter.sayit.0 because enabled
                                            2019-05-26 01:34:32.628 - warn: text2command.0 Reconnection to DB.
                                            2019-05-26 01:34:32.628 - warn: text2command.0 Reconnection to DB.
                                            2019-05-26 01:34:33.112 - warn: fullcalendar.0 Reconnection to DB.
                                            2019-05-26 01:34:33.127 - warn: fullcalendar.0 Reconnection to DB.
                                            2019-05-26 01:34:33.299 - warn: sql.0 Reconnection to DB.
                                            2019-05-26 01:34:33.299 - warn: sql.0 Reconnection to DB.
                                            2019-05-26 01:34:33.658 - warn: backitup.0 Reconnection to DB.
                                            2019-05-26 01:34:33.658 - warn: backitup.0 Reconnection to DB.
                                            2019-05-26 01:34:39.087 - error: backitup.0 already running
                                            2019-05-26 01:34:39.587 - error: host.Home-ioBroker instance system.adapter.backitup.0 terminated with code 7 (Adapter already running)
                                            2019-05-26 01:34:39.587 - info: host.Home-ioBroker Restart adapter system.adapter.backitup.0 because enabled
                                            2019-05-26 01:34:47.105 - error: fullcalendar.0 already running
                                            2019-05-26 01:34:39.617 - info: sonoff.0 starting. Version 2.2.2 in C:/iobroker/node_modules/iobroker.sonoff, node: v10.15.1
                                            2019-05-26 01:34:52.129 - error: host.Home-ioBroker instance system.adapter.fullcalendar.0 terminated with code 7 (Adapter already running)
                                            2019-05-26 01:34:52.409 - info: sonoff.0 Starting MQTT server on port 1883
                                            2019-05-26 01:34:52.425 - error: text2command.0 already running
                                            2019-05-26 01:34:52.580 - info: sonoff.0 Client [Sonoff-Steckdose-51] connected with secret 1558827292565_1702
                                            2019-05-26 01:34:52.814 - info: sonoff.0 Client [Sonoff-Steckdose-14] connected with secret 1558827292799_4363
                                            2019-05-26 01:34:52.814 - info: sonoff.0 Client [Sonoff-Steckdose-13] connected with secret 1558827292814_6594
                                            2019-05-26 01:34:52.129 - info: host.Home-ioBroker Restart adapter system.adapter.fullcalendar.0 because enabled
                                            2019-05-26 01:34:53.173 - info: sonoff.0 Client [Sonoff-Steckdose-17] connected with secret 1558827293173_3992
                                            2019-05-26 01:34:53.173 - info: sonoff.0 Client [Sonoff-Steckdose-11] connected with secret 1558827293173_2187
                                            2019-05-26 01:34:53.189 - info: sonoff.0 Client [Sonoff-Steckdose-15] connected with secret 1558827293173_4843
                                            2019-05-26 01:34:53.190 - error: host.Home-ioBroker instance system.adapter.text2command.0 terminated with code 7 (Adapter already running)
                                            2019-05-26 01:34:53.190 - info: host.Home-ioBroker Restart adapter system.adapter.text2command.0 because enabled
                                            2019-05-26 01:34:53.204 - error: cloud.0 already running
                                            2019-05-26 01:34:53.251 - info: sonoff.0 Client [Sonoff-Steckdose-53] connected with secret 1558827293251_9534
                                            2019-05-26 01:34:53.314 - info: sonoff.0 Client [Sonoff-Steckdose-12] connected with secret 1558827293298_9981
                                            2019-05-26 01:34:53.345 - info: sonoff.0 Client [Sonoff-Steckdose-16] connected with secret 1558827293345_3055
                                            2019-05-26 01:34:53.439 - error: host.Home-ioBroker instance system.adapter.cloud.0 terminated with code 7 (Adapter already running)
                                            2019-05-26 01:41:51.160 - warn: iqontrol.0 Reconnection to DB.
                                            2019-05-26 01:41:51.441 - error: fritzdect.0 already running
                                            2019-05-26 01:41:51.472 - error: text2command.0 already running
                                            2019-05-26 01:41:51.487 - error: tradfri.0 already running
                                            2019-05-26 01:41:51.503 - error: backitup.0 already running
                                            2019-05-26 01:41:51.784 - warn: sql.0 Reconnection to DB.
                                            2019-05-26 01:41:51.784 - warn: sql.0 Reconnection to DB.
                                            2019-05-26 01:41:52.237 - error: pushover.0 already running
                                            2019-05-26 01:41:52.267 - error: tr-064.0 already running
                                            2019-05-26 01:41:52.283 - error: alexa2.0 already running
                                            2019-05-26 01:41:52.283 - error: hm-rpc.0 already running
                                            2019-05-26 01:41:52.314 - error: iqontrol.0 already running
                                            2019-05-26 01:41:52.704 - error: host.Home-ioBroker instance system.adapter.fullcalendar.0 terminated with code 7 (Adapter already running)
                                            2019-05-26 01:41:52.704 - info: host.Home-ioBroker Restart adapter system.adapter.fullcalendar.0 because enabled
                                            2019-05-26 01:41:52.720 - error: host.Home-ioBroker instance system.adapter.backitup.0 terminated with code 7 (Adapter already running)
                                            2019-05-26 01:41:52.720 - info: host.Home-ioBroker Restart adapter system.adapter.backitup.0 because enabled
                                            2019-05-26 01:41:52.766 - error: host.Home-ioBroker instance system.adapter.text2command.0 terminated with code 7 (Adapter already running)
                                            2019-05-26 01:41:52.766 - info: host.Home-ioBroker Restart adapter system.adapter.text2command.0 because enabled
                                            2019-05-26 01:41:53.079 - warn: javascript.0 Reconnection to DB.
                                            2019-05-26 01:41:53.484 - error: host.Home-ioBroker instance system.adapter.tr-064.0 terminated with code 7 (Adapter already running)
                                            2019-05-26 01:41:53.781 - warn: javascript.0 Reconnection to DB.
                                            2019-05-26 01:41:53.484 - info: host.Home-ioBroker Restart adapter system.adapter.tr-064.0 because enabled
                                            2019-05-26 01:41:53.546 - error: host.Home-ioBroker instance system.adapter.sayit.0 terminated with code 7 (Adapter already running)
                                            2019-05-26 01:41:53.546 - info: host.Home-ioBroker Restart adapter system.adapter.sayit.0 because enabled
                                            2019-05-26 01:41:53.593 - error: host.Home-ioBroker instance system.adapter.fritzdect.0 terminated with code 7 (Adapter already running)
                                            2019-05-26 01:41:53.593 - info: host.Home-ioBroker Restart adapter system.adapter.fritzdect.0 because enabled
                                            2019-05-26 01:41:53.702 - error: host.Home-ioBroker instance system.adapter.pushover.0 terminated with code 7 (Adapter already running)
                                            2019-05-26 01:41:53.702 - info: host.Home-ioBroker Restart adapter system.adapter.pushover.0 because enabled
                                            2019-05-26 01:41:53.718 - error: host.Home-ioBroker instance system.adapter.tradfri.0 terminated with code 7 (Adapter already running)
                                            2019-05-26 01:41:53.718 - info: host.Home-ioBroker Restart adapter system.adapter.tradfri.0 because enabled
                                            2019-05-26 01:41:54.498 - info: host.Home-ioBroker instance system.adapter.tr-064.0 started with pid 6832
                                            2019-05-26 01:41:55.684 - error: host.Home-ioBroker instance system.adapter.iqontrol.0 terminated with code 7 (Adapter already running)
                                            2019-05-26 01:41:55.684 - info: host.Home-ioBroker Restart adapter system.adapter.iqontrol.0 because enabled
                                            2019-05-26 01:41:55.699 - error: host.Home-ioBroker instance system.adapter.javascript.1 terminated with code 7 (Adapter already running)
                                            2019-05-26 01:41:55.699 - info: host.Home-ioBroker Restart adapter system.adapter.javascript.1 because enabled
                                            2019-05-26 01:41:55.793 - error: host.Home-ioBroker instance system.adapter.hm-rpc.0 terminated with code 7 (Adapter already running)
                                            2019-05-26 01:41:55.793 - info: host.Home-ioBroker Restart adapter system.adapter.hm-rpc.0 because enabled
                                            2019-05-26 01:41:55.808 - error: host.Home-ioBroker instance system.adapter.alexa2.0 terminated with code 7 (Adapter already running)
                                            
                                            
                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate
                                            FAQ Cloud / IOT
                                            HowTo: Node.js-Update
                                            HowTo: Backup/Restore
                                            Downloads
                                            BLOG

                                            523
                                            Online

                                            31.8k
                                            Users

                                            80.0k
                                            Topics

                                            1.3m
                                            Posts

                                            iobroker iobroker log javascript javaskript adapter
                                            2
                                            22
                                            1366
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo