Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Zigbee Adapter - restart loop detected

    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

    Zigbee Adapter - restart loop detected

    This topic has been deleted. Only users with topic management privileges can see it.
    • Thomas Braun
      Thomas Braun Most Active @brokeling last edited by Thomas Braun

      @brokeling

      Im Terminal

      iobroker logs --watch
      

      und dann den Adapter neustarten. Neue Zeilen dann posten.

      Und halte das System auf Stand. Viele zu viele 'updateable' Adapters.

      sudo apt update
      

      liefert?

      1 Reply Last reply Reply Quote 0
      • B
        brokeling last edited by brokeling

        @thomas-braun

        pi@raspi:~ $ iobroker logs --watch
        Uncaught Rejection: Error: Cannot create a string longer than 0xffffff0 characters
            at Object.slice (buffer.js:609:37)
            at Buffer.toString (buffer.js:827:14)
            at CLILogs.execute (/opt/iobroker/node_modules/@iobroker/js-controller-cli/lib/cli/cliLogs.js:40:51)
            at processCommand (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:1137:25)
            at Object.module.exports.execute (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:3314:5)
            at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js:1:24)
            at Module._compile (internal/modules/cjs/loader.js:1085:14)
            at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
            at Module.load (internal/modules/cjs/loader.js:950:32)
            at Function.Module._load (internal/modules/cjs/loader.js:790:12)
        
        

        das kommt bereits als Antwort, bevor ich den Adapterneustart auslösen konnte.

        Thomas Braun 2 Replies Last reply Reply Quote 0
        • Thomas Braun
          Thomas Braun Most Active @brokeling last edited by

          @brokeling
          Wtf?
          Wie riesig ist bitte dein log?
          Das wären ja mehr als 268435440 Zeichen.

          B 1 Reply Last reply Reply Quote 0
          • Thomas Braun
            Thomas Braun Most Active @brokeling last edited by

            @brokeling

            Ich vermute du hast da noch ganz andere Probleme...

            Funktioniert

            tail -f /opt/iobroker/log/iobroker.current.log
            

            denn?

            1 Reply Last reply Reply Quote 0
            • B
              brokeling @Thomas Braun last edited by

              @thomas-braun
              Die vielen logs scheinen vom statistics-Adapter zu kommen.

              Thomas Braun B 2 Replies Last reply Reply Quote 0
              • Thomas Braun
                Thomas Braun Most Active @brokeling last edited by

                @brokeling

                Graf Zahl?
                Was loggst du da bitte alles?
                Dann schalt den Quasselkopp mal aus, damit der nicht dauernd in das Log reinblökt.

                1 Reply Last reply Reply Quote 0
                • B
                  brokeling @brokeling last edited by

                  2022-07-04 23:06:18.696  - debug: statistics.0 (1771) [STATE CHANGE] Increase temp.sumGroup.Stromverkauf.month on NaN to NaN
                  2022-07-04 23:06:18.699  - debug: statistics.0 (1771) [STATE CHANGE] Increase temp.sumGroup.Stromverkauf.quarter on NaN to NaN
                  2022-07-04 23:06:18.703  - debug: statistics.0 (1771) [STATE CHANGE] Increase temp.sumGroup.Stromverkauf.year on NaN to NaN
                  2022-07-04 23:06:18.712  - debug: statistics.0 (1771) [STATE CHANGE] Increase temp.sumDelta.0_userdata.0.Holger2.Energie_Haus.Strombezug_STAWA.15Min on 0 to 7157
                  2022-07-04 23:06:18.724  - debug: statistics.0 (1771) [STATE CHANGE] Increase temp.sumDelta.0_userdata.0.Holger2.Energie_Haus.Strombezug_STAWA.hour on 0 to 7157
                  2022-07-04 23:06:18.731  - debug: statistics.0 (1771) [STATE CHANGE] Increase temp.sumDelta.0_userdata.0.Holger2.Energie_Haus.Strombezug_STAWA.day on 0 to 1215739
                  2022-07-04 23:06:18.734  - debug: statistics.0 (1771) [STATE CHANGE] Increase temp.sumDelta.0_userdata.0.Holger2.Energie_Haus.Strombezug_STAWA.week on 0 to 1215739
                  2022-07-04 23:06:18.739  - debug: statistics.0 (1771) [STATE CHANGE] Increase temp.sumDelta.0_userdata.0.Holger2.Energie_Haus.Strombezug_STAWA.month on 0 to 3410906
                  2022-07-04 23:06:18.744  - debug: statistics.0 (1771) [STATE CHANGE] Increase temp.sumDelta.0_userdata.0.Holger2.Energie_Haus.Strombezug_STAWA.quarter on 0 to 3410906
                  2022-07-04 23:06:18.752  - debug: statistics.0 (1771) [STATE CHANGE] Increase temp.sumDelta.0_userdata.0.Holger2.Energie_Haus.Strombezug_STAWA.year on 0 to 86863699
                  2022-07-04 23:06:18.756  - debug: statistics.0 (1771) [STATE CHANGE] new last for "temp.avg.0_userdata.0.Holger2.Energie_Haus.Strombezug_STAWA.last: 0
                  2022-07-04 23:06:18.767  - debug: statistics.0 (1771) [STATE CHANGE] Increase temp.sumGroup.Strombezug.15Min on NaN to NaN
                  2022-07-04 23:06:18.771  - debug: statistics.0 (1771) [STATE CHANGE] Increase temp.sumGroup.Strombezug.hour on NaN to NaN
                  2022-07-04 23:06:18.775  - debug: statistics.0 (1771) [STATE CHANGE] Increase temp.sumGroup.Strombezug.day on NaN to NaN
                  2022-07-04 23:06:18.779  - debug: statistics.0 (1771) [STATE CHANGE] Increase temp.sumGroup.Strombezug.week on NaN to NaN
                  2022-07-04 23:06:18.784  - debug: statistics.0 (1771) [STATE CHANGE] Increase temp.sumGroup.Strombezug.month on NaN to NaN
                  2022-07-04 23:06:18.788  - debug: statistics.0 (1771) [STATE CHANGE] Increase temp.sumGroup.Strombezug.quarter on NaN to NaN
                  2022-07-04 23:06:18.792  - debug: statistics.0 (1771) [STATE CHANGE] Increase temp.sumGroup.Strombezug.year on NaN to NaN
                  2022-07-04 23:06:18.800  - debug: statistics.0 (1771) [STATE CHANGE] Increase temp.sumDelta.0_userdata.0.Holger2.Energie_Haus.Gesamtverbrauch_Haus.15Min on 0 to 22072
                  2022-07-04 23:06:18.803  - debug: statistics.0 (1771) [STATE CHANGE] Increase temp.sumDelta.0_userdata.0.Holger2.Energie_Haus.Gesamtverbrauch_Haus.hour on 0 to 22072
                  2022-07-04 23:06:18.806  - debug: statistics.0 (1771) [STATE CHANGE] Increase temp.sumDelta.0_userdata.0.Holger2.Energie_Haus.Gesamtverbrauch_Haus.day on 0 to 15671914
                  2022-07-04 23:06:18.809  - debug: statistics.0 (1771) [STATE CHANGE] Increase temp.sumDelta.0_userdata.0.Holger2.Energie_Haus.Gesamtverbrauch_Haus.week on 0 to 15671914
                  2022-07-04 23:06:18.812  - debug: statistics.0 (1771) [STATE CHANGE] Increase temp.sumDelta.0_userdata.0.Holger2.Energie_Haus.Gesamtverbrauch_Haus.month on 0 to 42252619
                  2022-07-04 23:06:18.815  - debug: statistics.0 (1771) [STATE CHANGE] Increase temp.sumDelta.0_userdata.0.Holger2.Energie_Haus.Gesamtverbrauch_Haus.quarter on 0 to 42252619
                  2022-07-04 23:06:18.819  - debug: statistics.0 (1771) [STATE CHANGE] Increase temp.sumDelta.0_userdata.0.Holger2.Energie_Haus.Gesamtverbrauch_Haus.year on 0 to 809781803
                  2022-07-04 23:06:18.823  - debug: statistics.0 (1771) [STATE CHANGE] new last for "temp.avg.0_userdata.0.Holger2.Energie_Haus.Gesamtverbrauch_Haus.last: 0
                  2022-07-04 23:06:18.837  - debug: statistics.0 (1771) [STATE CHANGE] Increase temp.sumGroup.Strombezug.15Min on NaN to NaN
                  2022-07-04 23:06:18.840  - debug: statistics.0 (1771) [STATE CHANGE] Increase temp.sumGroup.Strombezug.hour on NaN to NaN
                  2022-07-04 23:06:18.845  - debug: statistics.0 (1771) [STATE CHANGE] Increase temp.sumGroup.Strombezug.day on NaN to NaN
                  2022-07-04 23:06:18.849  - debug: statistics.0 (1771) [STATE CHANGE] Increase temp.sumGroup.Strombezug.week on NaN to NaN
                  2022-07-04 23:06:18.854  - debug: statistics.0 (1771) [STATE CHANGE] Increase temp.sumGroup.Strombezug.month on NaN to NaN
                  2022-07-04 23:06:18.858  - debug: statistics.0 (1771) [STATE CHANGE] Increase temp.sumGroup.Strombezug.quarter on NaN to NaN
                  2022-07-04 23:06:18.862  - debug: statistics.0 (1771) [STATE CHANGE] Increase temp.sumGroup.Strombezug.year on NaN to NaN
                  
                  
                  

                  ...ein Teil...

                  Thomas Braun 1 Reply Last reply Reply Quote 0
                  • Thomas Braun
                    Thomas Braun Most Active @brokeling last edited by Thomas Braun

                    @brokeling

                    Joh, in der Frequenz zu loggen dürfte irgendwann das System überlasten.
                    Außerdem steht der auf debug.

                    B 1 Reply Last reply Reply Quote 0
                    • B
                      brokeling @Thomas Braun last edited by

                      @thomas-braun
                      auf info umstellen?
                      dann geht es deutlich gemächlicher.

                      Thomas Braun 1 Reply Last reply Reply Quote 0
                      • Thomas Braun
                        Thomas Braun Most Active @brokeling last edited by

                        @brokeling

                        Natürlich. Was willste denn mit den Debug-Zeilen?

                        B 1 Reply Last reply Reply Quote 0
                        • B
                          brokeling @Thomas Braun last edited by

                          @thomas-braun

                          pi@raspi:~ $ iobroker logs --watch
                          Uncaught Rejection: Error: Cannot create a string longer than 0xffffff0 characters
                              at Object.slice (buffer.js:609:37)
                              at Buffer.toString (buffer.js:827:14)
                              at CLILogs.execute (/opt/iobroker/node_modules/@iobroker/js-controller-cli/lib/cli/cliLogs.js:40:51)
                              at processCommand (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:1137:25)
                              at Object.module.exports.execute (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:3314:5)
                              at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js:1:24)
                              at Module._compile (internal/modules/cjs/loader.js:1085:14)
                              at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
                              at Module.load (internal/modules/cjs/loader.js:950:32)
                              at Function.Module._load (internal/modules/cjs/loader.js:790:12)
                          
                          

                          Das bringt er jetzt immer noch, obwohl Adapter statistics aus.

                          Thomas Braun 1 Reply Last reply Reply Quote 0
                          • Thomas Braun
                            Thomas Braun Most Active @brokeling last edited by Thomas Braun

                            @brokeling sagte in Zigbee Adapter - restart loop detected:

                            Das bringt er jetzt immer noch, obwohl Adapter statistics aus.

                            Na klar, das file ist ja immer noch so riesig. Der alte Kram steht ja noch drin.

                            sudo apt update
                            tail -f /opt/iobroker/log/iobroker.current.log
                            
                            B 1 Reply Last reply Reply Quote 0
                            • B
                              brokeling @Thomas Braun last edited by

                              @thomas-braun
                              alles löschen?

                              B 1 Reply Last reply Reply Quote 0
                              • B
                                brokeling @brokeling last edited by

                                pi@raspi:~ $ sudo apt update
                                Holen:1 http://phoscon.de/apt/deconz buster InRelease [2.869 B]
                                Holen:2 http://archive.raspberrypi.org/debian buster InRelease [32,6 kB]
                                OK:3 https://deb.nodesource.com/node_12.x buster InRelease
                                Holen:4 http://raspbian.raspberrypi.org/raspbian buster InRelease [15,0 kB]
                                OK:5 https://deb.nodesource.com/node_14.x buster InRelease
                                Holen:6 http://phoscon.de/apt/deconz buster/main armhf Packages [734 B]
                                Holen:7 http://archive.raspberrypi.org/debian buster/main armhf Packages [391 kB]
                                Holen:8 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages [13,0 MB]
                                Es wurden 47,6 kB in 7 s geholt (7.063 B/s).
                                Paketlisten werden gelesen... Fertig
                                Abhängigkeitsbaum wird aufgebaut.
                                Statusinformationen werden eingelesen.... Fertig
                                Aktualisierung für 4 Pakete verfügbar. Führen Sie »apt list --upgradable« aus, um sie anzuzeigen.
                                
                                
                                pi@raspi:~ $ tail -f /opt/iobroker/log/iobroker.current.log
                                2022-07-04 23:15:39.626  - info: fritzdect.0 (2320) State value to set for "fritzdect.0.DECT_grpC786EA-3BDC033DC.boostactiveendtime" has to be type "number" but received type "string"
                                2022-07-04 23:15:39.627  - info: fritzdect.0 (2320) State value to set for "fritzdect.0.DECT_grpC786EA-3BDC033DC.endperiod" has to be type "number" but received type "string"
                                2022-07-04 23:15:39.629  - info: fritzdect.0 (2320) State value to set for "fritzdect.0.DECT_grpC786EA-3BDC03168.windowopenactiveendtime" has to be type "number" but received type "string"
                                2022-07-04 23:15:39.630  - info: fritzdect.0 (2320) State value to set for "fritzdect.0.DECT_grpC786EA-3BDC03168.boostactiveendtime" has to be type "number" but received type "string"
                                2022-07-04 23:15:39.631  - info: fritzdect.0 (2320) State value to set for "fritzdect.0.DECT_grpC786EA-3BDC03168.endperiod" has to be type "number" but received type "string"
                                2022-07-04 23:15:39.633  - info: fritzdect.0 (2320) State value to set for "fritzdect.0.DECT_grpC786EA-3BDC032FE.windowopenactiveendtime" has to be type "number" but received type "string"
                                2022-07-04 23:15:39.634  - info: fritzdect.0 (2320) State value to set for "fritzdect.0.DECT_grpC786EA-3BDC032FE.boostactiveendtime" has to be type "number" but received type "string"
                                2022-07-04 23:15:39.634  - info: fritzdect.0 (2320) State value to set for "fritzdect.0.DECT_grpC786EA-3BDC032FE.endperiod" has to be type "number" but received type "string"
                                2022-07-04 23:16:08.531  - info: javascript.0 (19239) script.js.common.Display.Display3_TFT.Alternativ.L8_CO2_WoZi1: 3
                                2022-07-04 23:17:08.491  - info: javascript.0 (19239) script.js.common.Display.Display3_TFT.Alternativ.L8_CO2_WoZi1: 3
                                
                                
                                Thomas Braun 1 Reply Last reply Reply Quote 0
                                • Thomas Braun
                                  Thomas Braun Most Active @brokeling last edited by

                                  @brokeling

                                  Dann jetzt den Adapter neustarten.

                                  B 1 Reply Last reply Reply Quote 0
                                  • B
                                    brokeling @Thomas Braun last edited by

                                    @thomas-braun
                                    läuft schon.

                                    Thomas Braun 1 Reply Last reply Reply Quote 0
                                    • Thomas Braun
                                      Thomas Braun Most Active @brokeling last edited by

                                      @brokeling

                                      Und?

                                      B 1 Reply Last reply Reply Quote 0
                                      • B
                                        brokeling @Thomas Braun last edited by

                                        @thomas-braun
                                        kann ich nicht sagen.
                                        Der zickt nur druchschnittlich einmal rum in 24 h.
                                        Da muss man jetzt abwarten.
                                        Ich muss mir den statistics Adapter nochmal anschauen, ob ich den anders konfigurieren kann. Der loggt wohl zu viel, oder?
                                        Die Adapter werde ich updaten oder rausschmeißen. Paar davon brauche ich garnicht. Doch das Löschen über die Admin Oberfläche hatte ich schon versucht, hat aber nicht geklappt. Blieb stehen. Muss ich nochmal probieren.

                                        Thomas Braun 1 Reply Last reply Reply Quote 0
                                        • Thomas Braun
                                          Thomas Braun Most Active @brokeling last edited by

                                          @brokeling

                                          Du sollst den zigbee-Adapter jetzt neustarten.

                                          B 1 Reply Last reply Reply Quote 0
                                          • B
                                            brokeling @Thomas Braun last edited by

                                            @thomas-braun
                                            ja ok, aber das ist unauffällig. Was dann?

                                            Thomas Braun 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

                                            843
                                            Online

                                            31.9k
                                            Users

                                            80.1k
                                            Topics

                                            1.3m
                                            Posts

                                            3
                                            66
                                            3699
                                            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