Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Meross nur noch unidirektional

    NEWS

    • Monatsrückblick - April 2025

    • Minor js-controller 7.0.7 Update in latest repo

    • Save The Date: ioBroker@Smart Living Forum Solingen, 14.06.

    Meross nur noch unidirektional

    This topic has been deleted. Only users with topic management privileges can see it.
    • MyzerAT
      MyzerAT @apollon77 last edited by

      @apollon77

      sag mal, die Einstellung Abfrageintervall für Stromwerte gilt ja für beide Zustände Cloud und Lokal! Kann ich, wenn ich nur Lokal nutze auch unter die besagten 15s gehen oder könnte es dann auch Probs mit Meross Betreiber geben ? THX

      4ca49d1d-feea-4f4c-987f-b7cd5c6c98d8-grafik.png

      apollon77 1 Reply Last reply Reply Quote 0
      • apollon77
        apollon77 @MyzerAT last edited by

        @myzerat lokal sollte (!!) es egal sein.

        MyzerAT 1 Reply Last reply Reply Quote 1
        • MyzerAT
          MyzerAT @apollon77 last edited by

          @apollon77

          sieht so aus als wäre es das doch nicht 😀

          00949f88-b0c4-44b2-9d31-bad57cb42299-grafik.png

          apollon77 1 Reply Last reply Reply Quote 0
          • apollon77
            apollon77 @MyzerAT last edited by

            @myzerat 😞 strange ... lass mal wieder freischalten und setzt wieder hoch

            M 1 Reply Last reply Reply Quote 1
            • M
              MCU @apollon77 last edited by MCU

              @apollon77 Habe auch eine Mail erhalten. Bei mir sind aber nur Geräte abgeschaltet und somit kommen immer die Meldungen, aber im Abstand von ca 90 Sekunden?: (Nr abgeschnitten)

              meross.0
              2022-07-11 15:29:30.199	warn	Can not get Data for Device 190807280368073908784: undefined
              
              meross.0
              2022-07-11 15:29:30.198	info	Can not get Data for Device 190807280368073908784: Error: Timeout
              
              meross.0
              2022-07-11 15:29:30.190	warn	Can not get Data for Device 1808176745879329083134: undefined
              
              meross.0
              2022-07-11 15:29:30.190	info	Can not get Data for Device 1808176745879329083134: Error: Timeout
              
              meross.0
              2022-07-11 15:28:53.602	warn	Can not get Data for Device 190611824229833908434: undefined
              
              meross.0
              2022-07-11 15:28:53.602	info	Can not get Data for Device 190611824229833908434: Error: Timeout
              

              a39031c3-fc69-4782-9801-225e8df9fe9d-image.png

              MyzerAT apollon77 3 Replies Last reply Reply Quote 0
              • MyzerAT
                MyzerAT @MCU last edited by

                @mcu

                damit @apollon77 mehr sieht, stell die instanz meross auf debug, starte die instanz neu und lass sie einige stunden laufen und dann stell das logfile hier online

                ffe9c390-14c3-4bfe-886b-987b571a4972-grafik.png

                1 Reply Last reply Reply Quote 1
                • MyzerAT
                  MyzerAT @MCU last edited by MyzerAT

                  @mcu

                  was meinst du mit abgeschaltet? --> sind die nicht eingesteckt?

                  abschalten kann man Meross Geräte auch mit der neuen Version, falls die zur Zeit nicht am Strom sein sollten, einfach das besagte Gerät auf "true" stellen
                  ee599188-9159-4313-b5c8-642115576bfe-grafik.png

                  M 1 Reply Last reply Reply Quote 0
                  • M
                    MCU @MyzerAT last edited by

                    @myzerat Ok, mach ich mal. Danke.

                    1 Reply Last reply Reply Quote 0
                    • apollon77
                      apollon77 @MCU last edited by apollon77

                      @mcu hm… also du fragst alle 15sec die Energiewerte ab. Und ja wenn er sie lokal nicht erreichen kann fragt er die Cloud. Und ja macht er auch wenn sie offline sind vllt. Da wäre ein debug log interessant. Richtig. Das könnte man mal ändern. Bitte github issue.

                      Edit: das Problem Ist das er nicht weiß ob das Gerät offline ist es sei denn er versucht mit ihm zu reden. Oder er bekommt aus der Cloud nen Push wegen einem Change. Und da beißt sich die katze in dem Schwanz.

                      Man könnte höchstens sagen „wenn keine Antwort kam dann frühestens 1-2 Minuten später neu versuchen Energiewerte abzuholen. Und so das Intervall quasi auszusetzen. Was meint ihr?

                      M 1 Reply Last reply Reply Quote 0
                      • M
                        MCU @apollon77 last edited by

                        @apollon77
                        https://github.com/Apollon77/ioBroker.meross/issues/290

                        mcuiobroker created this issue in Apollon77/ioBroker.meross

                        closed Datenabfrage nur wenn Gerät lokal erreichbar #290

                        1 Reply Last reply Reply Quote 0
                        • apollon77
                          apollon77 last edited by

                          Ok, habe jetzt etwas eingebaut um sicherzustellen das geräte nur lokal kontaktiert werden und kein Cloud Fallback stattfindet - auch wenn die Logs die ich gesehen haben jetzt keine Cloud Fallback bei den relevaten Geräten feststellen konnte.

                          Also müssen es weiter beobachten ob es mit "nur lokaler Modus" von den Limits her wirklich besser ist als per Cloud

                          MyzerAT 1 Reply Last reply Reply Quote 2
                          • MyzerAT
                            MyzerAT @apollon77 last edited by MyzerAT

                            @apollon77
                            ich nehme an du meinst die 1.13 auf github, habe die auch mal installiert zum testen!

                            apollon77 1 Reply Last reply Reply Quote 0
                            • apollon77
                              apollon77 @MyzerAT last edited by

                              @myzerat nee ich meine die 1.13 aus dem Beta Repo … GitHub install sind böse außer ich fordere explizit dazu auf.

                              andiko2 1 Reply Last reply Reply Quote 1
                              • andiko2
                                andiko2 @apollon77 last edited by

                                @apollon77 ich habe bei mir das gleiche Problem mit Meross. Das ist aus heiterem Himmel aufgetaucht ohne das ich etwas verändert habe. Cirka alle 2 Minuten verliert der Adapter bei den drei Grünen Punkten den "Verbunden mit Gerät oder Dienst" . Er verbindet sich gleich wieder und ist dann für ca. 2 Minuten wieder ok. Dann geht das wieder von vorne los. Hab mal Probiert einen Neustart für 3 Uhr zu setzen aber das hat nichts gebracht. Hab ich wieder gelöscht. Das Problem, wenn er für die ca. 5 Sekunden offline ist, und ein Schaltbefehl abgesetzt wir in der Zeit, wird er nicht ausgeführt. IoBroker Fixer hat auch nichts gebracht. Eventuell macht Meross wieder irgend was. Das einzigste was ich die letzten Tage gemacht habe, waren zwei neue Steckdosen anlernen. Habe hezte mal 4 Steckdosen und eine Farblampe die ich nicht mehr nutze aus dem System gelöscht und die Geräte resettet. Hat auch nichts geändert.

                                apollon77 1 Reply Last reply Reply Quote 0
                                • apollon77
                                  apollon77 @andiko2 last edited by

                                  @andiko2 Dann bitte Debug Log bereitstellen. Wird lokal oder per Cloud verbunden?

                                  andiko2 1 Reply Last reply Reply Quote 0
                                  • andiko2
                                    andiko2 @apollon77 last edited by andiko2

                                    @apollon77 jetzt hast du mich erwischt mit Debug Log bereitstellen. Wo und wie bekomme ich das?
                                    Einstellungen sind so:
                                    meross einstellung.png

                                    System:
                                    iob stand.png


                                    2023-01-27 16:30:50.929 - info: meross.0 (32041) Can not get Data for Device 1912126418405590806548e1e91310d7: Error: Timeout
                                    2023-01-27 16:30:50.929 - warn: meross.0 (32041) Can not get Data for Device 1912126418405590806548e1e91310d7: undefined
                                    2023-01-27 16:31:12.745 - info: hmip.0 (15121) Value unchanged, do not send this value
                                    2023-01-27 16:31:16.510 - info: meross.0 (32041) Can not get Data for Device 1812146710587929088434298f197e67: Error: Timeout
                                    2023-01-27 16:31:16.511 - warn: meross.0 (32041) Can not get Data for Device 1812146710587929088434298f197e67: undefined
                                    2023-01-27 16:31:31.422 - info: meross.0 (32041) Device: 2211011866779051080148e1e9ada63c closed: null
                                    2023-01-27 16:31:31.423 - info: meross.0 (32041) Device: 2211016259159251080148e1e9ad94ed closed: null
                                    2023-01-27 16:31:31.423 - info: meross.0 (32041) Device: 2211012131734251080148e1e9adac10 closed: null
                                    2023-01-27 16:31:31.423 - info: meross.0 (32041) Device: 1812146710587929088434298f197e67 closed: null
                                    2023-01-27 16:31:31.423 - info: meross.0 (32041) Device: 2102035620020190841348e1e94a832c closed: null
                                    2023-01-27 16:31:31.424 - info: meross.0 (32041) Device: 2102037387671590841348e1e94a9475 closed: null
                                    2023-01-27 16:31:31.424 - info: meross.0 (32041) Device: 2102036474864790841348e1e94a7d00 closed: null
                                    2023-01-27 16:31:31.424 - info: meross.0 (32041) Device: 20031733571410251h3648e1e918fb7c closed: null
                                    2023-01-27 16:31:31.424 - info: meross.0 (32041) Device: 1912242800955525188148e1e9146535 closed: null
                                    2023-01-27 16:31:31.424 - info: meross.0 (32041) Device: 1912248392224225188148e1e9147d1e closed: null
                                    2023-01-27 16:31:31.424 - info: meross.0 (32041) Device: 1912244502120725188148e1e9147ce4 closed: null
                                    2023-01-27 16:31:31.424 - info: meross.0 (32041) Device: 1912242390035525188148e1e9146525 closed: null
                                    2023-01-27 16:31:31.424 - info: meross.0 (32041) Device: 1911270495456425187448e1e9121431 closed: null
                                    2023-01-27 16:31:31.425 - info: meross.0 (32041) Device: 1911273580160125187448e1e91217b1 closed: null
                                    2023-01-27 16:31:31.425 - info: meross.0 (32041) Device: 1911271101958325187448e1e9121adc closed: null
                                    2023-01-27 16:31:31.425 - info: meross.0 (32041) Device: 1911276550451725187448e1e9121125 closed: null
                                    2023-01-27 16:31:31.425 - info: meross.0 (32041) Device: 1912248134073425188148e1e9146c1d closed: null
                                    2023-01-27 16:31:31.425 - info: meross.0 (32041) Device: 1912243266948225188148e1e914931b closed: null
                                    2023-01-27 16:31:31.425 - info: meross.0 (32041) Device: 1909121197501325186448e1e9037864 closed: null
                                    2023-01-27 16:31:31.426 - info: meross.0 (32041) Device: 1909125533830625186448e1e903758e closed: null
                                    2023-01-27 16:31:31.426 - info: meross.0 (32041) Device: 1909123280493825186448e1e9036048 closed: null
                                    2023-01-27 16:31:31.426 - info: meross.0 (32041) Device: 1909127841759725186448e1e9039ad5 closed: null
                                    2023-01-27 16:31:31.427 - info: meross.0 (32041) Device: 19060634960444251h0548e1e9001911 closed: null
                                    2023-01-27 16:31:31.427 - info: meross.0 (32041) Device: 19060619507324251h0548e1e90018fa closed: null
                                    2023-01-27 16:31:31.427 - info: meross.0 (32041) Device: 1812172967162725182734298f19a581 closed: null
                                    2023-01-27 16:31:31.427 - info: meross.0 (32041) Device: 1812170301856525182734298f1991d1 closed: null
                                    2023-01-27 16:31:31.427 - info: meross.0 (32041) Device: 1812178385914025182734298f19bb07 closed: null
                                    2023-01-27 16:31:31.427 - info: meross.0 (32041) Device: 1812171382435925182734298f19a8c4 closed: null
                                    2023-01-27 16:31:31.428 - info: meross.0 (32041) Device: 1812178389364925182734298f19b176 closed: null
                                    2023-01-27 16:31:31.428 - info: meross.0 (32041) Device: 1812172861029825182734298f19a5e3 closed: null
                                    2023-01-27 16:31:31.428 - info: meross.0 (32041) Device: 1812170548019025182734298f198eb2 closed: null
                                    2023-01-27 16:31:31.428 - info: meross.0 (32041) Device: 1812177950373925182734298f19b642 closed: null
                                    2023-01-27 16:31:31.428 - info: meross.0 (32041) Device: 1812171073231425182734298f19a473 closed: null
                                    2023-01-27 16:31:31.428 - info: meross.0 (32041) Device: 1812177841852625182834298f19d9ef closed: null
                                    2023-01-27 16:31:31.428 - info: meross.0 (32041) Device: 1812173452319625182834298f19c4b6 closed: null
                                    2023-01-27 16:31:31.428 - info: meross.0 (32041) Device: 1812179369749725182834298f19c865 closed: null
                                    2023-01-27 16:31:31.428 - info: meross.0 (32041) Device: 1812179610361425182834298f19e0f0 closed: null
                                    2023-01-27 16:31:35.628 - info: javascript.0 (15673) Stop script script.js.Bewegungsmelder.BWM_WZ
                                    2023-01-27 16:31:35.661 - info: javascript.0 (15673) Start javascript script.js.Bewegungsmelder.BWM_WZ
                                    2023-01-27 16:31:35.669 - info: javascript.0 (15673) script.js.Bewegungsmelder.BWM_WZ: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions
                                    2023-01-27 16:31:35.725 - info: javascript.0 (15673) Stop script script.js.Bewegungsmelder.BWM_WZ
                                    2023-01-27 16:31:35.731 - info: javascript.0 (15673) Stop script script.js.Bewegungsmelder.BWM_WZ
                                    2023-01-27 16:31:35.784 - info: javascript.0 (15673) Start javascript script.js.Bewegungsmelder.BWM_WZ
                                    2023-01-27 16:31:35.790 - info: javascript.0 (15673) script.js.Bewegungsmelder.BWM_WZ: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions
                                    2023-01-27 16:31:35.836 - info: javascript.0 (15673) Start javascript script.js.Bewegungsmelder.BWM_WZ
                                    2023-01-27 16:31:35.845 - info: javascript.0 (15673) script.js.Bewegungsmelder.BWM_WZ: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions
                                    2023-01-27 16:31:36.423 - info: meross.0 (32041) Device: 2211011866779051080148e1e9ada63c reconnected
                                    2023-01-27 16:31:36.424 - info: meross.0 (32041) Device: 2211016259159251080148e1e9ad94ed reconnected
                                    2023-01-27 16:31:36.424 - info: meross.0 (32041) Device: 2211012131734251080148e1e9adac10 reconnected
                                    2023-01-27 16:31:36.424 - info: meross.0 (32041) Device: 1812146710587929088434298f197e67 reconnected
                                    2023-01-27 16:31:36.424 - info: meross.0 (32041) Device: 2102035620020190841348e1e94a832c reconnected
                                    2023-01-27 16:31:36.425 - info: meross.0 (32041) Device: 2102037387671590841348e1e94a9475 reconnected
                                    2023-01-27 16:31:36.425 - info: meross.0 (32041) Device: 2102036474864790841348e1e94a7d00 reconnected
                                    2023-01-27 16:31:36.425 - info: meross.0 (32041) Device: 20031733571410251h3648e1e918fb7c reconnected
                                    2023-01-27 16:31:36.425 - info: meross.0 (32041) Device: 1912242800955525188148e1e9146535 reconnected
                                    2023-01-27 16:31:36.425 - info: meross.0 (32041) Device: 1912248392224225188148e1e9147d1e reconnected
                                    2023-01-27 16:31:36.425 - info: meross.0 (32041) Device: 1912244502120725188148e1e9147ce4 reconnected
                                    2023-01-27 16:31:36.425 - info: meross.0 (32041) Device: 1912242390035525188148e1e9146525 reconnected
                                    2023-01-27 16:31:36.426 - info: meross.0 (32041) Device: 1911270495456425187448e1e9121431 reconnected
                                    2023-01-27 16:31:36.426 - info: meross.0 (32041) Device: 1911273580160125187448e1e91217b1 reconnected
                                    2023-01-27 16:31:36.426 - info: meross.0 (32041) Device: 1911271101958325187448e1e9121adc reconnected
                                    2023-01-27 16:31:36.426 - info: meross.0 (32041) Device: 1911276550451725187448e1e9121125 reconnected
                                    2023-01-27 16:31:36.426 - info: meross.0 (32041) Device: 1912248134073425188148e1e9146c1d reconnected
                                    2023-01-27 16:31:36.426 - info: meross.0 (32041) Device: 1912243266948225188148e1e914931b reconnected
                                    2023-01-27 16:31:36.427 - info: meross.0 (32041) Device: 1909121197501325186448e1e9037864 reconnected
                                    2023-01-27 16:31:36.427 - info: meross.0 (32041) Device: 1909125533830625186448e1e903758e reconnected
                                    2023-01-27 16:31:36.427 - info: meross.0 (32041) Device: 1909123280493825186448e1e9036048 reconnected
                                    2023-01-27 16:31:36.427 - info: meross.0 (32041) Device: 1909127841759725186448e1e9039ad5 reconnected
                                    2023-01-27 16:31:36.427 - info: meross.0 (32041) Device: 19060634960444251h0548e1e9001911 reconnected
                                    2023-01-27 16:31:36.427 - info: meross.0 (32041) Device: 19060619507324251h0548e1e90018fa reconnected
                                    2023-01-27 16:31:36.428 - info: meross.0 (32041) Device: 1812172967162725182734298f19a581 reconnected
                                    2023-01-27 16:31:36.428 - info: meross.0 (32041) Device: 1812170301856525182734298f1991d1 reconnected
                                    2023-01-27 16:31:36.428 - info: meross.0 (32041) Device: 1812178385914025182734298f19bb07 reconnected
                                    2023-01-27 16:31:36.428 - info: meross.0 (32041) Device: 1812171382435925182734298f19a8c4 reconnected
                                    2023-01-27 16:31:36.428 - info: meross.0 (32041) Device: 1812178389364925182734298f19b176 reconnected
                                    2023-01-27 16:31:36.428 - info: meross.0 (32041) Device: 1812172861029825182734298f19a5e3 reconnected
                                    2023-01-27 16:31:36.428 - info: meross.0 (32041) Device: 1812170548019025182734298f198eb2 reconnected
                                    2023-01-27 16:31:36.429 - info: meross.0 (32041) Device: 1812177950373925182734298f19b642 reconnected
                                    2023-01-27 16:31:36.429 - info: meross.0 (32041) Device: 1812171073231425182734298f19a473 reconnected
                                    2023-01-27 16:31:36.429 - info: meross.0 (32041) Device: 1812177841852625182834298f19d9ef reconnected
                                    2023-01-27 16:31:36.429 - info: meross.0 (32041) Device: 1812173452319625182834298f19c4b6 reconnected
                                    2023-01-27 16:31:36.429 - info: meross.0 (32041) Device: 1812179369749725182834298f19c865 reconnected
                                    2023-01-27 16:31:36.429 - info: meross.0 (32041) Device: 1812179610361425182834298f19e0f0 reconnected
                                    2023-01-27 16:31:36.655 - info: meross.0 (32041) Device: 2211011866779051080148e1e9ada63c connected
                                    2023-01-27 16:31:36.656 - info: meross.0 (32041) Device: 2211016259159251080148e1e9ad94ed connected
                                    2023-01-27 16:31:36.656 - info: meross.0 (32041) Device: 2211012131734251080148e1e9adac10 connected
                                    2023-01-27 16:31:36.657 - info: meross.0 (32041) Device: 1812146710587929088434298f197e67 connected
                                    2023-01-27 16:31:36.658 - info: meross.0 (32041) Device: 2102035620020190841348e1e94a832c connected
                                    2023-01-27 16:31:36.659 - info: meross.0 (32041) Device: 2102037387671590841348e1e94a9475 connected
                                    2023-01-27 16:31:36.660 - info: meross.0 (32041) Device: 2102036474864790841348e1e94a7d00 connected
                                    2023-01-27 16:31:36.664 - info: meross.0 (32041) Device: 20031733571410251h3648e1e918fb7c connected
                                    2023-01-27 16:31:36.665 - info: meross.0 (32041) Device: 1912242800955525188148e1e9146535 connected
                                    2023-01-27 16:31:36.666 - info: meross.0 (32041) Device: 1912248392224225188148e1e9147d1e connected
                                    2023-01-27 16:31:36.667 - info: meross.0 (32041) Device: 1912244502120725188148e1e9147ce4 connected
                                    2023-01-27 16:31:36.668 - info: meross.0 (32041) Device: 1912242390035525188148e1e9146525 connected
                                    2023-01-27 16:31:36.668 - info: meross.0 (32041) Device: 1911270495456425187448e1e9121431 connected
                                    2023-01-27 16:31:36.669 - info: meross.0 (32041) Device: 1911273580160125187448e1e91217b1 connected
                                    2023-01-27 16:31:36.669 - info: meross.0 (32041) Device: 1911271101958325187448e1e9121adc connected
                                    2023-01-27 16:31:36.670 - info: meross.0 (32041) Device: 1911276550451725187448e1e9121125 connected
                                    2023-01-27 16:31:36.670 - info: meross.0 (32041) Device: 1912248134073425188148e1e9146c1d connected
                                    2023-01-27 16:31:36.671 - info: meross.0 (32041) Device: 1912243266948225188148e1e914931b connected
                                    2023-01-27 16:31:36.672 - info: meross.0 (32041) Device: 1909121197501325186448e1e9037864 connected
                                    2023-01-27 16:31:36.672 - info: meross.0 (32041) Device: 1909125533830625186448e1e903758e connected
                                    2023-01-27 16:31:36.673 - info: meross.0 (32041) Device: 1909123280493825186448e1e9036048 connected
                                    2023-01-27 16:31:36.673 - info: meross.0 (32041) Device: 1909127841759725186448e1e9039ad5 connected
                                    2023-01-27 16:31:36.674 - info: meross.0 (32041) Device: 19060634960444251h0548e1e9001911 connected
                                    2023-01-27 16:31:36.674 - info: meross.0 (32041) Device: 19060619507324251h0548e1e90018fa connected
                                    2023-01-27 16:31:36.675 - info: meross.0 (32041) Device: 1812172967162725182734298f19a581 connected
                                    2023-01-27 16:31:36.677 - info: meross.0 (32041) Device: 1812170301856525182734298f1991d1 connected
                                    2023-01-27 16:31:36.677 - info: meross.0 (32041) Device: 1812178385914025182734298f19bb07 connected
                                    2023-01-27 16:31:36.678 - info: meross.0 (32041) Device: 1812171382435925182734298f19a8c4 connected
                                    2023-01-27 16:31:36.678 - info: meross.0 (32041) Device: 1812178389364925182734298f19b176 connected
                                    2023-01-27 16:31:36.679 - info: meross.0 (32041) Device: 1812172861029825182734298f19a5e3 connected
                                    2023-01-27 16:31:36.679 - info: meross.0 (32041) Device: 1812170548019025182734298f198eb2 connected
                                    2023-01-27 16:31:36.680 - info: meross.0 (32041) Device: 1812177950373925182734298f19b642 connected
                                    2023-01-27 16:31:36.681 - info: meross.0 (32041) Device: 1812171073231425182734298f19a473 connected
                                    2023-01-27 16:31:36.681 - info: meross.0 (32041) Device: 1812177841852625182834298f19d9ef connected
                                    2023-01-27 16:31:36.682 - info: meross.0 (32041) Device: 1812173452319625182834298f19c4b6 connected
                                    2023-01-27 16:31:36.682 - info: meross.0 (32041) Device: 1812179369749725182834298f19c865 connected
                                    2023-01-27 16:31:36.683 - info: meross.0 (32041) Device: 1812179610361425182834298f19e0f0 connected
                                    2023-01-27 16:31:56.778 - info: meross.0 (32041) Can not get Data for Device 1812146710587929088434298f197e67: Error: Timeout
                                    2023-01-27 16:31:56.779 - warn: meross.0 (32041) Can not get Data for Device 1812146710587929088434298f197e67: undefined

                                    Ab da fing es an. Von 0 Uhr bist zum Start der Störung lief noch alles gut. Da war ich auch noch auf Arbeit. Also konnte ich auch nichts ändern in der Zeit.

                                    2023-01-27 15:10:19.228 - info: host.ioBrokerPC stopInstance system.adapter.meross.0 (force=false, process=true)
                                    2023-01-27 15:10:19.320 - info: host.ioBrokerPC stopInstance system.adapter.meross.0 send kill signal
                                    2023-01-27 15:10:19.321 - info: meross.0 (24447) Got terminate signal TERMINATE_YOURSELF
                                    2023-01-27 15:10:19.322 - info: meross.0 (24447) terminating
                                    2023-01-27 15:10:19.323 - info: meross.0 (24447) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                                    2023-01-27 15:10:19.972 - info: host.ioBrokerPC instance system.adapter.meross.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                    2023-01-27 15:10:20.421 - info: admin.1 (19056) <== Disconnect system.user.admin from ::ffff:192.168.178.119
                                    2023-01-27 15:10:26.988 - info: host.ioBrokerPC instance system.adapter.meross.0 started with pid 32041
                                    2023-01-27 15:10:29.394 - info: meross.0 (32041) starting. Version 1.14.0 in /opt/iobroker/node_modules/iobroker.meross, node: v16.19.0, js-controller: 4.0.24
                                    2023-01-27 15:10:30.042 - info: meross.0 (32041) Device 2211011866779051080148e1e9ada63c initialized
                                    2023-01-27 15:10:30.093 - info: meross.0 (32041) Device 2211016259159251080148e1e9ad94ed initialized
                                    2023-01-27 15:10:30.094 - info: meross.0 (32041) Device 2211012131734251080148e1e9adac10 initialized
                                    2023-01-27 15:10:30.095 - info: meross.0 (32041) Device 1812146710587929088434298f197e67 initialized
                                    2023-01-27 15:10:30.115 - info: meross.0 (32041) Device 2102035620020190841348e1e94a832c initialized
                                    2023-01-27 15:10:30.115 - info: meross.0 (32041) Device 2102037387671590841348e1e94a9475 initialized
                                    2023-01-27 15:10:30.116 - info: meross.0 (32041) Device 2102036474864790841348e1e94a7d00 initialized
                                    2023-01-27 15:10:30.117 - info: meross.0 (32041) Device 20031733571410251h3648e1e918fb7c initialized
                                    2023-01-27 15:10:30.118 - info: meross.0 (32041) Device 1912242800955525188148e1e9146535 initialized
                                    2023-01-27 15:10:30.119 - info: meross.0 (32041) Device 1912248392224225188148e1e9147d1e initialized
                                    2023-01-27 15:10:30.120 - info: meross.0 (32041) Device 1912244502120725188148e1e9147ce4 initialized
                                    2023-01-27 15:10:30.120 - info: meross.0 (32041) Device 1912242390035525188148e1e9146525 initialized
                                    2023-01-27 15:10:30.121 - info: meross.0 (32041) Device 1911270495456425187448e1e9121431 initialized
                                    2023-01-27 15:10:30.121 - info: meross.0 (32041) Device 1911273580160125187448e1e91217b1 initialized
                                    2023-01-27 15:10:30.122 - info: meross.0 (32041) Device 1911271101958325187448e1e9121adc initialized
                                    2023-01-27 15:10:30.123 - info: meross.0 (32041) Device 1912126418405590806548e1e91310d7 initialized
                                    2023-01-27 15:10:30.125 - info: meross.0 (32041) Device 1911276550451725187448e1e9121125 initialized
                                    2023-01-27 15:10:30.126 - info: meross.0 (32041) Device 1912248134073425188148e1e9146c1d initialized
                                    2023-01-27 15:10:30.127 - info: meross.0 (32041) Device 1912243266948225188148e1e914931b initialized
                                    2023-01-27 15:10:30.128 - info: meross.0 (32041) Device 1909121197501325186448e1e9037864 initialized
                                    2023-01-27 15:10:30.128 - info: meross.0 (32041) Device 1909125533830625186448e1e903758e initialized
                                    2023-01-27 15:10:30.128 - info: meross.0 (32041) Device 1909123280493825186448e1e9036048 initialized
                                    2023-01-27 15:10:30.129 - info: meross.0 (32041) Device 1909127841759725186448e1e9039ad5 initialized
                                    2023-01-27 15:10:30.129 - info: meross.0 (32041) Device 19060634960444251h0548e1e9001911 initialized
                                    2023-01-27 15:10:30.130 - info: meross.0 (32041) Device 19060619507324251h0548e1e90018fa initialized
                                    2023-01-27 15:10:30.130 - info: meross.0 (32041) Device 1812172967162725182734298f19a581 initialized
                                    2023-01-27 15:10:30.131 - info: meross.0 (32041) Device 1812170301856525182734298f1991d1 initialized
                                    2023-01-27 15:10:30.131 - info: meross.0 (32041) Device 1812178385914025182734298f19bb07 initialized
                                    2023-01-27 15:10:30.132 - info: meross.0 (32041) Device 1812171382435925182734298f19a8c4 initialized
                                    2023-01-27 15:10:30.132 - info: meross.0 (32041) Device 1812178389364925182734298f19b176 initialized
                                    2023-01-27 15:10:30.133 - info: meross.0 (32041) Device 1812172861029825182734298f19a5e3 initialized
                                    2023-01-27 15:10:30.133 - info: meross.0 (32041) Device 1812170548019025182734298f198eb2 initialized
                                    2023-01-27 15:10:30.134 - info: meross.0 (32041) Device 1812177950373925182734298f19b642 initialized
                                    2023-01-27 15:10:30.134 - info: meross.0 (32041) Device 1812171073231425182734298f19a473 initialized
                                    2023-01-27 15:10:30.135 - info: meross.0 (32041) Device 1812177841852625182834298f19d9ef initialized
                                    2023-01-27 15:10:30.135 - info: meross.0 (32041) Device 1812173452319625182834298f19c4b6 initialized
                                    2023-01-27 15:10:30.136 - info: meross.0 (32041) Device 1812179369749725182834298f19c865 initialized
                                    2023-01-27 15:10:30.137 - info: meross.0 (32041) Device 1812179610361425182834298f19e0f0 initialized
                                    2023-01-27 15:10:30.342 - info: meross.0 (32041) Device: 1912126418405590806548e1e91310d7 connected
                                    2023-01-27 15:10:30.349 - info: meross.0 (32041) Device: 2211011866779051080148e1e9ada63c connected
                                    2023-01-27 15:10:30.350 - info: meross.0 (32041) Device: 2211016259159251080148e1e9ad94ed connected
                                    2023-01-27 15:10:30.351 - info: meross.0 (32041) Device: 2211012131734251080148e1e9adac10 connected
                                    2023-01-27 15:10:30.352 - info: meross.0 (32041) Device: 1812146710587929088434298f197e67 connected
                                    2023-01-27 15:10:30.353 - info: meross.0 (32041) Device: 2102035620020190841348e1e94a832c connected
                                    2023-01-27 15:10:30.353 - info: meross.0 (32041) Device: 2102037387671590841348e1e94a9475 connected
                                    2023-01-27 15:10:30.354 - info: meross.0 (32041) Device: 2102036474864790841348e1e94a7d00 connected
                                    2023-01-27 15:10:30.356 - info: meross.0 (32041) Device: 20031733571410251h3648e1e918fb7c connected
                                    2023-01-27 15:10:30.357 - info: meross.0 (32041) Device: 1912242800955525188148e1e9146535 connected
                                    2023-01-27 15:10:30.358 - info: meross.0 (32041) Device: 1912248392224225188148e1e9147d1e connected
                                    2023-01-27 15:10:30.358 - info: meross.0 (32041) Device: 1912244502120725188148e1e9147ce4 connected
                                    2023-01-27 15:10:30.359 - info: meross.0 (32041) Device: 1912242390035525188148e1e9146525 connected
                                    2023-01-27 15:10:30.360 - info: meross.0 (32041) Device: 1911270495456425187448e1e9121431 connected
                                    2023-01-27 15:10:30.361 - info: meross.0 (32041) Device: 1911273580160125187448e1e91217b1 connected
                                    2023-01-27 15:10:30.362 - info: meross.0 (32041) Device: 1911271101958325187448e1e9121adc connected
                                    2023-01-27 15:10:30.363 - info: meross.0 (32041) Device: 1911276550451725187448e1e9121125 connected
                                    2023-01-27 15:10:30.364 - info: meross.0 (32041) Device: 1912248134073425188148e1e9146c1d connected
                                    2023-01-27 15:10:30.364 - info: meross.0 (32041) Device: 1912243266948225188148e1e914931b connected
                                    2023-01-27 15:10:30.366 - info: meross.0 (32041) Device: 1909121197501325186448e1e9037864 connected
                                    2023-01-27 15:10:30.367 - info: meross.0 (32041) Device: 1909125533830625186448e1e903758e connected
                                    2023-01-27 15:10:30.368 - info: meross.0 (32041) Device: 1909123280493825186448e1e9036048 connected
                                    2023-01-27 15:10:30.369 - info: meross.0 (32041) Device: 1909127841759725186448e1e9039ad5 connected
                                    2023-01-27 15:10:30.370 - info: meross.0 (32041) Device: 19060634960444251h0548e1e9001911 connected
                                    2023-01-27 15:10:30.370 - info: meross.0 (32041) Device: 19060619507324251h0548e1e90018fa connected
                                    2023-01-27 15:10:30.371 - info: meross.0 (32041) Device: 1812172967162725182734298f19a581 connected
                                    2023-01-27 15:10:30.372 - info: meross.0 (32041) Device: 1812170301856525182734298f1991d1 connected
                                    2023-01-27 15:10:30.373 - info: meross.0 (32041) Device: 1812178385914025182734298f19bb07 connected
                                    2023-01-27 15:10:30.373 - info: meross.0 (32041) Device: 1812171382435925182734298f19a8c4 connected
                                    2023-01-27 15:10:30.374 - info: meross.0 (32041) Device: 1812178389364925182734298f19b176 connected
                                    2023-01-27 15:10:30.375 - info: meross.0 (32041) Device: 1812172861029825182734298f19a5e3 connected
                                    2023-01-27 15:10:30.376 - info: meross.0 (32041) Device: 1812170548019025182734298f198eb2 connected
                                    2023-01-27 15:10:30.377 - info: meross.0 (32041) Device: 1812177950373925182734298f19b642 connected
                                    2023-01-27 15:10:30.377 - info: meross.0 (32041) Device: 1812171073231425182734298f19a473 connected
                                    2023-01-27 15:10:30.378 - info: meross.0 (32041) Device: 1812177841852625182834298f19d9ef connected
                                    2023-01-27 15:10:30.379 - info: meross.0 (32041) Device: 1812173452319625182834298f19c4b6 connected
                                    2023-01-27 15:10:30.380 - info: meross.0 (32041) Device: 1812179369749725182834298f19c865 connected
                                    2023-01-27 15:10:30.380 - info: meross.0 (32041) Device: 1812179610361425182834298f19e0f0 connected
                                    2023-01-27 15:10:30.474 - info: javascript.0 (15673) Stop script script.js.Bewegungsmelder.BWM_Küche
                                    2023-01-27 15:10:32.222 - info: virtualpowermeter.0 (4173) deinitilized meross.0.1812178389364925182734298f19b176.0-power
                                    2023-01-27 15:10:32.231 - info: virtualpowermeter.0 (4173) initial meross.0.1812178389364925182734298f19b176.0-power
                                    2023-01-27 15:10:32.421 - info: virtualpowermeter.0 (4173) initial done meross.0.1812178389364925182734298f19b176.0-power Destination Power: meross.0.1812178389364925182734298f19b176.Virtual_Energy_Power Destination EnergyTotal: meross.0.1812178389364925182734298f19b176.Virtual_Energy_Total Destination Group: virtualpowermeter.0.group_ioBroker.
                                    2023-01-27 15:10:32.749 - info: javascript.0 (15673) Start javascript script.js.Bewegungsmelder.BWM_Küche
                                    2023-01-27 15:10:32.760 - info: javascript.0 (15673) script.js.Bewegungsmelder.BWM_Küche: registered 16 subscriptions, 3 schedules, 0 messages, 0 logs and 0 file subscriptions
                                    2023-01-27 15:10:50.455 - info: meross.0 (32041) Can not get Data for Device 1912126418405590806548e1e91310d7: Error: Timeout
                                    2023-01-27 15:10:50.456 - warn: meross.0 (32041) Can not get Data for Device 1912126418405590806548e1e91310d7: undefined
                                    2023-01-27 15:10:50.459 - info: meross.0 (32041) Can not get Data for Device 1812146710587929088434298f197e67: Error: Timeout
                                    2023-01-27 15:10:50.460 - warn: meross.0 (32041) Can not get Data for Device 1812146710587929088434298f197e67: undefined
                                    2023-01-27 15:10:50.462 - info: meross.0 (32041) Devices initialized
                                    2023-01-27 15:10:52.772 - info: javascript.0 (15673) Stop script script.js.Nachrichten.Temperaturalarm_IoBroker_PC
                                    2023-01-27 15:10:52.820 - info: javascript.0 (15673) Start javascript script.js.Nachrichten.Temperaturalarm_IoBroker_PC
                                    2023-01-27 15:10:52.826 - info: javascript.0 (15673) script.js.Nachrichten.Temperaturalarm_IoBroker_PC: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions
                                    2023-01-27 15:11:52.748 - info: javascript.0 (15673) Stop script script.js.Nachrichten.Temperaturalarm_IoBroker_PC
                                    2023-01-27 15:11:52.806 - info: javascript.0 (15673) Start javascript script.js.Nachrichten.Temperaturalarm_IoBroker_PC
                                    2023-01-27 15:11:52.811 - info: javascript.0 (15673) script.js.Nachrichten.Temperaturalarm_IoBroker_PC: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions
                                    2023-01-27 15:12:10.465 - info: meross.0 (32041) Can not get Data for Device 1912126418405590806548e1e91310d7: Error: Timeout
                                    2023-01-27 15:12:10.466 - warn: meross.0 (32041) Can not get Data for Device 1912126418405590806548e1e91310d7: undefined
                                    2023-01-27 15:12:10.470 - info: meross.0 (32041) Can not get Data for Device 1812146710587929088434298f197e67: Error: Timeout
                                    2023-01-27 15:12:10.471 - warn: meross.0 (32041) Can not get Data for Device 1812146710587929088434298f197e67: undefined
                                    2023-01-27 15:12:24.296 - info: hmip.0 (15121) Value unchanged, do not send this value
                                    2023-01-27 15:12:25.341 - info: meross.0 (32041) Device: 2211011866779051080148e1e9ada63c closed: null
                                    2023-01-27 15:12:25.342 - info: meross.0 (32041) Device: 2211016259159251080148e1e9ad94ed closed: null
                                    2023-01-27 15:12:25.343 - info: meross.0 (32041) Device: 2211012131734251080148e1e9adac10 closed: null
                                    2023-01-27 15:12:25.343 - info: meross.0 (32041) Device: 1812146710587929088434298f197e67 closed: null
                                    2023-01-27 15:12:25.344 - info: meross.0 (32041) Device: 2102035620020190841348e1e94a832c closed: null
                                    2023-01-27 15:12:25.344 - info: meross.0 (32041) Device: 2102037387671590841348e1e94a9475 closed: null
                                    2023-01-27 15:12:25.345 - info: meross.0 (32041) Device: 2102036474864790841348e1e94a7d00 closed: null
                                    2023-01-27 15:12:25.345 - info: meross.0 (32041) Device: 20031733571410251h3648e1e918fb7c closed: null
                                    2023-01-27 15:12:25.346 - info: meross.0 (32041) Device: 1912242800955525188148e1e9146535 closed: null
                                    2023-01-27 15:12:25.346 - info: meross.0 (32041) Device: 1912248392224225188148e1e9147d1e closed: null
                                    2023-01-27 15:12:25.347 - info: meross.0 (32041) Device: 1912244502120725188148e1e9147ce4 closed: null
                                    2023-01-27 15:12:25.348 - info: meross.0 (32041) Device: 1912242390035525188148e1e9146525 closed: null
                                    2023-01-27 15:12:25.349 - info: meross.0 (32041) Device: 1911270495456425187448e1e9121431 closed: null
                                    2023-01-27 15:12:25.349 - info: meross.0 (32041) Device: 1911273580160125187448e1e91217b1 closed: null
                                    2023-01-27 15:12:25.350 - info: meross.0 (32041) Device: 1911271101958325187448e1e9121adc closed: null
                                    2023-01-27 15:12:25.350 - info: meross.0 (32041) Device: 1911276550451725187448e1e9121125 closed: null
                                    2023-01-27 15:12:25.351 - info: meross.0 (32041) Device: 1912248134073425188148e1e9146c1d closed: null
                                    2023-01-27 15:12:25.351 - info: meross.0 (32041) Device: 1912243266948225188148e1e914931b closed: null
                                    2023-01-27 15:12:25.352 - info: meross.0 (32041) Device: 1909121197501325186448e1e9037864 closed: null
                                    2023-01-27 15:12:25.352 - info: meross.0 (32041) Device: 1909125533830625186448e1e903758e closed: null
                                    2023-01-27 15:12:25.353 - info: meross.0 (32041) Device: 1909123280493825186448e1e9036048 closed: null
                                    2023-01-27 15:12:25.354 - info: meross.0 (32041) Device: 1909127841759725186448e1e9039ad5 closed: null
                                    2023-01-27 15:12:25.354 - info: meross.0 (32041) Device: 19060634960444251h0548e1e9001911 closed: null
                                    2023-01-27 15:12:25.354 - info: meross.0 (32041) Device: 19060619507324251h0548e1e90018fa closed: null
                                    2023-01-27 15:12:25.354 - info: meross.0 (32041) Device: 1812172967162725182734298f19a581 closed: null
                                    2023-01-27 15:12:25.354 - info: meross.0 (32041) Device: 1812170301856525182734298f1991d1 closed: null
                                    2023-01-27 15:12:25.355 - info: meross.0 (32041) Device: 1812178385914025182734298f19bb07 closed: null
                                    2023-01-27 15:12:25.355 - info: meross.0 (32041) Device: 1812171382435925182734298f19a8c4 closed: null
                                    2023-01-27 15:12:25.355 - info: meross.0 (32041) Device: 1812178389364925182734298f19b176 closed: null
                                    2023-01-27 15:12:25.355 - info: meross.0 (32041) Device: 1812172861029825182734298f19a5e3 closed: null
                                    2023-01-27 15:12:25.355 - info: meross.0 (32041) Device: 1812170548019025182734298f198eb2 closed: null
                                    2023-01-27 15:12:25.356 - info: meross.0 (32041) Device: 1812177950373925182734298f19b642 closed: null
                                    2023-01-27 15:12:25.356 - info: meross.0 (32041) Device: 1812171073231425182734298f19a473 closed: null
                                    2023-01-27 15:12:25.356 - info: meross.0 (32041) Device: 1812177841852625182834298f19d9ef closed: null
                                    2023-01-27 15:12:25.356 - info: meross.0 (32041) Device: 1812173452319625182834298f19c4b6 closed: null
                                    2023-01-27 15:12:25.356 - info: meross.0 (32041) Device: 1812179369749725182834298f19c865 closed: null
                                    2023-01-27 15:12:25.357 - info: meross.0 (32041) Device: 1812179610361425182834298f19e0f0 closed: null
                                    2023-01-27 15:12:30.342 - info: meross.0 (32041) Device: 2211011866779051080148e1e9ada63c reconnected
                                    2023-01-27 15:12:30.343 - info: meross.0 (32041) Device: 2211016259159251080148e1e9ad94ed reconnected
                                    2023-01-27 15:12:30.344 - info: meross.0 (32041) Device: 2211012131734251080148e1e9adac10 reconnected
                                    2023-01-27 15:12:30.344 - info: meross.0 (32041) Device: 1812146710587929088434298f197e67 reconnected
                                    2023-01-27 15:12:30.345 - info: meross.0 (32041) Device: 2102035620020190841348e1e94a832c reconnected
                                    2023-01-27 15:12:30.345 - info: meross.0 (32041) Device: 2102037387671590841348e1e94a9475 reconnected
                                    2023-01-27 15:12:30.346 - info: meross.0 (32041) Device: 2102036474864790841348e1e94a7d00 reconnected
                                    2023-01-27 15:12:30.346 - info: meross.0 (32041) Device: 20031733571410251h3648e1e918fb7c reconnected
                                    2023-01-27 15:12:30.347 - info: meross.0 (32041) Device: 1912242800955525188148e1e9146535 reconnected
                                    2023-01-27 15:12:30.347 - info: meross.0 (32041) Device: 1912248392224225188148e1e9147d1e reconnected
                                    2023-01-27 15:12:30.348 - info: meross.0 (32041) Device: 1912244502120725188148e1e9147ce4 reconnected
                                    2023-01-27 15:12:30.348 - info: meross.0 (32041) Device: 1912242390035525188148e1e9146525 reconnected
                                    2023-01-27 15:12:30.349 - info: meross.0 (32041) Device: 1911270495456425187448e1e9121431 reconnected
                                    2023-01-27 15:12:30.349 - info: meross.0 (32041) Device: 1911273580160125187448e1e91217b1 reconnected
                                    2023-01-27 15:12:30.349 - info: meross.0 (32041) Device: 1911271101958325187448e1e9121adc reconnected
                                    2023-01-27 15:12:30.350 - info: meross.0 (32041) Device: 1911276550451725187448e1e9121125 reconnected
                                    2023-01-27 15:12:30.350 - info: meross.0 (32041) Device: 1912248134073425188148e1e9146c1d reconnected
                                    2023-01-27 15:12:30.351 - info: meross.0 (32041) Device: 1912243266948225188148e1e914931b reconnected
                                    2023-01-27 15:12:30.351 - info: meross.0 (32041) Device: 1909121197501325186448e1e9037864 reconnected
                                    2023-01-27 15:12:30.352 - info: meross.0 (32041) Device: 1909125533830625186448e1e903758e reconnected
                                    2023-01-27 15:12:30.352 - info: meross.0 (32041) Device: 1909123280493825186448e1e9036048 reconnected
                                    2023-01-27 15:12:30.352 - info: meross.0 (32041) Device: 1909127841759725186448e1e9039ad5 reconnected
                                    2023-01-27 15:12:30.353 - info: meross.0 (32041) Device: 19060634960444251h0548e1e9001911 reconnected
                                    2023-01-27 15:12:30.353 - info: meross.0 (32041) Device: 19060619507324251h0548e1e90018fa reconnected
                                    2023-01-27 15:12:30.354 - info: meross.0 (32041) Device: 1812172967162725182734298f19a581 reconnected
                                    2023-01-27 15:12:30.354 - info: meross.0 (32041) Device: 1812170301856525182734298f1991d1 reconnected
                                    2023-01-27 15:12:30.355 - info: meross.0 (32041) Device: 1812178385914025182734298f19bb07 reconnected
                                    2023-01-27 15:12:30.355 - info: meross.0 (32041) Device: 1812171382435925182734298f19a8c4 reconnected
                                    2023-01-27 15:12:30.356 - info: meross.0 (32041) Device: 1812178389364925182734298f19b176 reconnected
                                    2023-01-27 15:12:30.356 - info: meross.0 (32041) Device: 1812172861029825182734298f19a5e3 reconnected
                                    2023-01-27 15:12:30.356 - info: meross.0 (32041) Device: 1812170548019025182734298f198eb2 reconnected
                                    2023-01-27 15:12:30.356 - info: meross.0 (32041) Device: 1812177950373925182734298f19b642 reconnected
                                    2023-01-27 15:12:30.356 - info: meross.0 (32041) Device: 1812171073231425182734298f19a473 reconnected
                                    2023-01-27 15:12:30.356 - info: meross.0 (32041) Device: 1812177841852625182834298f19d9ef reconnected
                                    2023-01-27 15:12:30.357 - info: meross.0 (32041) Device: 1812173452319625182834298f19c4b6 reconnected
                                    2023-01-27 15:12:30.357 - info: meross.0 (32041) Device: 1812179369749725182834298f19c865 reconnected
                                    2023-01-27 15:12:30.357 - info: meross.0 (32041) Device: 1812179610361425182834298f19e0f0 reconnected
                                    2023-01-27 15:12:30.555 - info: meross.0 (32041) Device: 2211011866779051080148e1e9ada63c connected
                                    2023-01-27 15:12:30.556 - info: meross.0 (32041) Device: 2211016259159251080148e1e9ad94ed connected
                                    2023-01-27 15:12:30.557 - info: meross.0 (32041) Device: 2211012131734251080148e1e9adac10 connected
                                    2023-01-27 15:12:30.558 - info: meross.0 (32041) Device: 1812146710587929088434298f197e67 connected
                                    2023-01-27 15:12:30.558 - info: meross.0 (32041) Device: 2102035620020190841348e1e94a832c connected
                                    2023-01-27 15:12:30.561 - info: meross.0 (32041) Device: 2102037387671590841348e1e94a9475 connected
                                    2023-01-27 15:12:30.562 - info: meross.0 (32041) Device: 2102036474864790841348e1e94a7d00 connected
                                    2023-01-27 15:12:30.562 - info: meross.0 (32041) Device: 20031733571410251h3648e1e918fb7c connected
                                    2023-01-27 15:12:30.563 - info: meross.0 (32041) Device: 1912242800955525188148e1e9146535 connected
                                    2023-01-27 15:12:30.565 - info: meross.0 (32041) Device: 1912248392224225188148e1e9147d1e connected
                                    2023-01-27 15:12:30.566 - info: meross.0 (32041) Device: 1912244502120725188148e1e9147ce4 connected
                                    2023-01-27 15:12:30.566 - info: meross.0 (32041) Device: 1912242390035525188148e1e9146525 connected
                                    2023-01-27 15:12:30.567 - info: meross.0 (32041) Device: 1911270495456425187448e1e9121431 connected
                                    2023-01-27 15:12:30.568 - info: meross.0 (32041) Device: 1911273580160125187448e1e91217b1 connected
                                    2023-01-27 15:12:30.569 - info: meross.0 (32041) Device: 1911271101958325187448e1e9121adc connected
                                    2023-01-27 15:12:30.570 - info: meross.0 (32041) Device: 1911276550451725187448e1e9121125 connected
                                    2023-01-27 15:12:30.570 - info: meross.0 (32041) Device: 1912248134073425188148e1e9146c1d connected
                                    2023-01-27 15:12:30.571 - info: meross.0 (32041) Device: 1912243266948225188148e1e914931b connected
                                    2023-01-27 15:12:30.572 - info: meross.0 (32041) Device: 1909121197501325186448e1e9037864 connected
                                    2023-01-27 15:12:30.572 - info: meross.0 (32041) Device: 1909125533830625186448e1e903758e connected
                                    2023-01-27 15:12:30.573 - info: meross.0 (32041) Device: 1909123280493825186448e1e9036048 connected
                                    2023-01-27 15:12:30.574 - info: meross.0 (32041) Device: 1909127841759725186448e1e9039ad5 connected
                                    2023-01-27 15:12:30.574 - info: meross.0 (32041) Device: 19060634960444251h0548e1e9001911 connected
                                    2023-01-27 15:12:30.575 - info: meross.0 (32041) Device: 19060619507324251h0548e1e90018fa connected
                                    2023-01-27 15:12:30.576 - info: meross.0 (32041) Device: 1812172967162725182734298f19a581 connected
                                    2023-01-27 15:12:30.576 - info: meross.0 (32041) Device: 1812170301856525182734298f1991d1 connected
                                    2023-01-27 15:12:30.577 - info: meross.0 (32041) Device: 1812178385914025182734298f19bb07 connected
                                    2023-01-27 15:12:30.577 - info: meross.0 (32041) Device: 1812171382435925182734298f19a8c4 connected
                                    2023-01-27 15:12:30.578 - info: meross.0 (32041) Device: 1812178389364925182734298f19b176 connected
                                    2023-01-27 15:12:30.579 - info: meross.0 (32041) Device: 1812172861029825182734298f19a5e3 connected
                                    2023-01-27 15:12:30.579 - info: meross.0 (32041) Device: 1812170548019025182734298f198eb2 connected
                                    2023-01-27 15:12:30.580 - info: meross.0 (32041) Device: 1812177950373925182734298f19b642 connected
                                    2023-01-27 15:12:30.581 - info: meross.0 (32041) Device: 1812171073231425182734298f19a473 connected
                                    2023-01-27 15:12:30.581 - info: meross.0 (32041) Device: 1812177841852625182834298f19d9ef connected
                                    2023-01-27 15:12:30.582 - info: meross.0 (32041) Device: 1812173452319625182834298f19c4b6 connected
                                    2023-01-27 15:12:30.583 - info: meross.0 (32041) Device: 1812179369749725182834298f19c865 connected
                                    2023-01-27 15:12:30.583 - info: meross.0 (32041) Device: 1812179610361425182834298f19e0f0 connected
                                    2023-01-27 15:12:50.694 - info: meross.0 (32041) Can not get Data for Device 1812146710587929088434298f197e67: Error: Timeout
                                    2023-01-27 15:12:50.695 - warn: meross.0 (32041) Can not get Data for Device 1812146710587929088434298f197e67: unde

                                    1 Reply Last reply Reply Quote 0
                                    • apollon77
                                      apollon77 last edited by

                                      1.) Warum nur Cloud kommunikation? Lokal geht viel besser in den meisten Fällen wenn Sie im gleichen Netzwerk erreichbar sind. Mit so vielen Geräten kann man da seeeehr schnell in meross Cloud Limits rennen.
                                      2.) "Timeout" heisst an sich das meross selbst auch die Geräte nicht erreichen kann ... sind die innder Meross App alle online?
                                      3.) Debug Log - siehe meine Forum Signatur

                                      andiko2 1 Reply Last reply Reply Quote 0
                                      • andiko2
                                        andiko2 @apollon77 last edited by

                                        @apollon77 über die App am Handy kann ich alles schalten. Hab gerade gesehen im Log von gestern, da war der fehler auch schon. Ich hatte das auf Cloud eingestellt heut, weil alle Steckdosen als ofline angezeigt wurden und auch keine schaltung über IoBroker ausgeführt wurde. Nach dem Umstellen waren sie erst mal wieder online. Wenn ich nach hause komme, wird mein Handy WLAN erkannt und meine Systeme also mini Rechner fahren hoch und meine Dashboards werde angezeigt. Das ist nicht mehr geschehen. Am Tablet wurde der Akku auf volle 100% geladen, obwohl die Steckdose bei 81% abschalten sollte. Der Fully war immer online. Das hab ich im Diagramm gesehen. Befehl wurde abgesetzt aber Meross hat nicht reagiert.

                                        apollon77 1 Reply Last reply Reply Quote 0
                                        • apollon77
                                          apollon77 @andiko2 last edited by

                                          @andiko2 Dann brauche ich ein volles Debug log bitte ... am besten versuche nochmal cloud bzw lokal beide optionen

                                          andiko2 1 Reply Last reply Reply Quote 0
                                          • andiko2
                                            andiko2 @apollon77 last edited by

                                            @apollon77 sorry bin gestern am PC eingeschlafen. War seid 4 Uhr auf den Beinen.
                                            Hier jetzt der Log.


                                            2023-01-28 01:16:57.069 - info: meross.0 (28469) Can not get Data for Device 1812146710587929088434298f197e67: Error: Timeout
                                            2023-01-28 01:16:57.069 - warn: meross.0 (28469) Can not get Data for Device 1812146710587929088434298f197e67: undefined
                                            2023-01-28 01:16:58.131 - info: javascript.0 (4010) Stop script script.js.Bewegungsmelder.BWM_WZ
                                            2023-01-28 01:16:58.288 - info: javascript.0 (4010) Start javascript script.js.Bewegungsmelder.BWM_WZ
                                            2023-01-28 01:16:58.292 - info: javascript.0 (4010) script.js.Bewegungsmelder.BWM_WZ: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions
                                            2023-01-28 01:16:58.551 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:17:06.931 - info: javascript.0 (4010) Stop script script.js.Bewegungsmelder.BWM_WZ
                                            2023-01-28 01:17:07.056 - info: javascript.0 (4010) Start javascript script.js.Bewegungsmelder.BWM_WZ
                                            2023-01-28 01:17:07.064 - info: javascript.0 (4010) script.js.Bewegungsmelder.BWM_WZ: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions
                                            2023-01-28 01:17:11.232 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:17:24.079 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:17:36.933 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:17:37.565 - info: javascript.0 (4010) Stop script script.js.Bewegungsmelder.BWM_WZ
                                            2023-01-28 01:17:37.662 - info: javascript.0 (4010) Start javascript script.js.Bewegungsmelder.BWM_WZ
                                            2023-01-28 01:17:37.669 - info: javascript.0 (4010) script.js.Bewegungsmelder.BWM_WZ: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions
                                            2023-01-28 01:17:49.630 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:18:03.006 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:18:15.830 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:18:17.130 - info: meross.0 (28469) Can not get Data for Device 1812146710587929088434298f197e67: Error: Timeout
                                            2023-01-28 01:18:17.131 - warn: meross.0 (28469) Can not get Data for Device 1812146710587929088434298f197e67: undefined
                                            2023-01-28 01:18:28.495 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:18:41.404 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:18:41.524 - info: javascript.0 (4010) Stop script script.js.Bewegungsmelder.BWM_WZ
                                            2023-01-28 01:18:41.622 - info: javascript.0 (4010) Start javascript script.js.Bewegungsmelder.BWM_WZ
                                            2023-01-28 01:18:41.629 - info: javascript.0 (4010) script.js.Bewegungsmelder.BWM_WZ: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions
                                            2023-01-28 01:18:47.409 - info: hmip.0 (4113) Value unchanged, do not send this value
                                            2023-01-28 01:18:54.232 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:19:07.183 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:19:12.110 - info: javascript.0 (4010) Stop script script.js.Bewegungsmelder.BWM_WZ
                                            2023-01-28 01:19:12.210 - info: javascript.0 (4010) Start javascript script.js.Bewegungsmelder.BWM_WZ
                                            2023-01-28 01:19:12.217 - info: javascript.0 (4010) script.js.Bewegungsmelder.BWM_WZ: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions
                                            2023-01-28 01:19:19.005 - info: meross.0 (28469) Device: 2211016259159251080148e1e9ad94ed closed: null
                                            2023-01-28 01:19:19.006 - info: meross.0 (28469) Device: 2211012131734251080148e1e9adac10 closed: null
                                            2023-01-28 01:19:19.007 - info: meross.0 (28469) Device: 1812146710587929088434298f197e67 closed: null
                                            2023-01-28 01:19:19.007 - info: meross.0 (28469) Device: 2102035620020190841348e1e94a832c closed: null
                                            2023-01-28 01:19:19.008 - info: meross.0 (28469) Device: 2102037387671590841348e1e94a9475 closed: null
                                            2023-01-28 01:19:19.008 - info: meross.0 (28469) Device: 2102036474864790841348e1e94a7d00 closed: null
                                            2023-01-28 01:19:19.008 - info: meross.0 (28469) Device: 20031733571410251h3648e1e918fb7c closed: null
                                            2023-01-28 01:19:19.008 - info: meross.0 (28469) Device: 1912242800955525188148e1e9146535 closed: null
                                            2023-01-28 01:19:19.009 - info: meross.0 (28469) Device: 1912248392224225188148e1e9147d1e closed: null
                                            2023-01-28 01:19:19.009 - info: meross.0 (28469) Device: 1912244502120725188148e1e9147ce4 closed: null
                                            2023-01-28 01:19:19.009 - info: meross.0 (28469) Device: 1912242390035525188148e1e9146525 closed: null
                                            2023-01-28 01:19:19.009 - info: meross.0 (28469) Device: 1911271101958325187448e1e9121adc closed: null
                                            2023-01-28 01:19:19.009 - info: meross.0 (28469) Device: 1911276550451725187448e1e9121125 closed: null
                                            2023-01-28 01:19:19.009 - info: meross.0 (28469) Device: 1912243266948225188148e1e914931b closed: null
                                            2023-01-28 01:19:19.010 - info: meross.0 (28469) Device: 1909121197501325186448e1e9037864 closed: null
                                            2023-01-28 01:19:19.010 - info: meross.0 (28469) Device: 1909125533830625186448e1e903758e closed: null
                                            2023-01-28 01:19:19.010 - info: meross.0 (28469) Device: 1909123280493825186448e1e9036048 closed: null
                                            2023-01-28 01:19:19.012 - info: meross.0 (28469) Device: 1909127841759725186448e1e9039ad5 closed: null
                                            2023-01-28 01:19:19.012 - info: meross.0 (28469) Device: 19060634960444251h0548e1e9001911 closed: null
                                            2023-01-28 01:19:19.012 - info: meross.0 (28469) Device: 19060619507324251h0548e1e90018fa closed: null
                                            2023-01-28 01:19:19.012 - info: meross.0 (28469) Device: 1812172967162725182734298f19a581 closed: null
                                            2023-01-28 01:19:19.012 - info: meross.0 (28469) Device: 1812170301856525182734298f1991d1 closed: null
                                            2023-01-28 01:19:19.013 - info: meross.0 (28469) Device: 1812171382435925182734298f19a8c4 closed: null
                                            2023-01-28 01:19:19.013 - info: meross.0 (28469) Device: 1812178389364925182734298f19b176 closed: null
                                            2023-01-28 01:19:19.013 - info: meross.0 (28469) Device: 1812172861029825182734298f19a5e3 closed: null
                                            2023-01-28 01:19:19.013 - info: meross.0 (28469) Device: 1812170548019025182734298f198eb2 closed: null
                                            2023-01-28 01:19:19.013 - info: meross.0 (28469) Device: 1812177950373925182734298f19b642 closed: null
                                            2023-01-28 01:19:19.014 - info: meross.0 (28469) Device: 1812171073231425182734298f19a473 closed: null
                                            2023-01-28 01:19:19.014 - info: meross.0 (28469) Device: 1812177841852625182834298f19d9ef closed: null
                                            2023-01-28 01:19:19.014 - info: meross.0 (28469) Device: 1812173452319625182834298f19c4b6 closed: null
                                            2023-01-28 01:19:19.014 - info: meross.0 (28469) Device: 1812179369749725182834298f19c865 closed: null
                                            2023-01-28 01:19:19.014 - info: meross.0 (28469) Device: 1812179610361425182834298f19e0f0 closed: null
                                            2023-01-28 01:19:20.031 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:19:24.005 - info: meross.0 (28469) Device: 2211016259159251080148e1e9ad94ed reconnected
                                            2023-01-28 01:19:24.006 - info: meross.0 (28469) Device: 2211012131734251080148e1e9adac10 reconnected
                                            2023-01-28 01:19:24.006 - info: meross.0 (28469) Device: 1812146710587929088434298f197e67 reconnected
                                            2023-01-28 01:19:24.007 - info: meross.0 (28469) Device: 2102035620020190841348e1e94a832c reconnected
                                            2023-01-28 01:19:24.007 - info: meross.0 (28469) Device: 2102037387671590841348e1e94a9475 reconnected
                                            2023-01-28 01:19:24.008 - info: meross.0 (28469) Device: 2102036474864790841348e1e94a7d00 reconnected
                                            2023-01-28 01:19:24.008 - info: meross.0 (28469) Device: 20031733571410251h3648e1e918fb7c reconnected
                                            2023-01-28 01:19:24.008 - info: meross.0 (28469) Device: 1912242800955525188148e1e9146535 reconnected
                                            2023-01-28 01:19:24.009 - info: meross.0 (28469) Device: 1912248392224225188148e1e9147d1e reconnected
                                            2023-01-28 01:19:24.009 - info: meross.0 (28469) Device: 1912244502120725188148e1e9147ce4 reconnected
                                            2023-01-28 01:19:24.009 - info: meross.0 (28469) Device: 1912242390035525188148e1e9146525 reconnected
                                            2023-01-28 01:19:24.010 - info: meross.0 (28469) Device: 1911271101958325187448e1e9121adc reconnected
                                            2023-01-28 01:19:24.010 - info: meross.0 (28469) Device: 1911276550451725187448e1e9121125 reconnected
                                            2023-01-28 01:19:24.010 - info: meross.0 (28469) Device: 1912243266948225188148e1e914931b reconnected
                                            2023-01-28 01:19:24.011 - info: meross.0 (28469) Device: 1909121197501325186448e1e9037864 reconnected
                                            2023-01-28 01:19:24.011 - info: meross.0 (28469) Device: 1909125533830625186448e1e903758e reconnected
                                            2023-01-28 01:19:24.011 - info: meross.0 (28469) Device: 1909123280493825186448e1e9036048 reconnected
                                            2023-01-28 01:19:24.012 - info: meross.0 (28469) Device: 1909127841759725186448e1e9039ad5 reconnected
                                            2023-01-28 01:19:24.012 - info: meross.0 (28469) Device: 19060634960444251h0548e1e9001911 reconnected
                                            2023-01-28 01:19:24.014 - info: meross.0 (28469) Device: 19060619507324251h0548e1e90018fa reconnected
                                            2023-01-28 01:19:24.015 - info: meross.0 (28469) Device: 1812172967162725182734298f19a581 reconnected
                                            2023-01-28 01:19:24.015 - info: meross.0 (28469) Device: 1812170301856525182734298f1991d1 reconnected
                                            2023-01-28 01:19:24.015 - info: meross.0 (28469) Device: 1812171382435925182734298f19a8c4 reconnected
                                            2023-01-28 01:19:24.015 - info: meross.0 (28469) Device: 1812178389364925182734298f19b176 reconnected
                                            2023-01-28 01:19:24.015 - info: meross.0 (28469) Device: 1812172861029825182734298f19a5e3 reconnected
                                            2023-01-28 01:19:24.016 - info: meross.0 (28469) Device: 1812170548019025182734298f198eb2 reconnected
                                            2023-01-28 01:19:24.016 - info: meross.0 (28469) Device: 1812177950373925182734298f19b642 reconnected
                                            2023-01-28 01:19:24.016 - info: meross.0 (28469) Device: 1812171073231425182734298f19a473 reconnected
                                            2023-01-28 01:19:24.016 - info: meross.0 (28469) Device: 1812177841852625182834298f19d9ef reconnected
                                            2023-01-28 01:19:24.016 - info: meross.0 (28469) Device: 1812173452319625182834298f19c4b6 reconnected
                                            2023-01-28 01:19:24.017 - info: meross.0 (28469) Device: 1812179369749725182834298f19c865 reconnected
                                            2023-01-28 01:19:24.017 - info: meross.0 (28469) Device: 1812179610361425182834298f19e0f0 reconnected
                                            2023-01-28 01:19:24.217 - info: meross.0 (28469) Device: 2211016259159251080148e1e9ad94ed connected
                                            2023-01-28 01:19:24.218 - info: meross.0 (28469) Device: 2211012131734251080148e1e9adac10 connected
                                            2023-01-28 01:19:24.219 - info: meross.0 (28469) Device: 1812146710587929088434298f197e67 connected
                                            2023-01-28 01:19:24.220 - info: meross.0 (28469) Device: 2102035620020190841348e1e94a832c connected
                                            2023-01-28 01:19:24.221 - info: meross.0 (28469) Device: 2102037387671590841348e1e94a9475 connected
                                            2023-01-28 01:19:24.222 - info: meross.0 (28469) Device: 2102036474864790841348e1e94a7d00 connected
                                            2023-01-28 01:19:24.223 - info: meross.0 (28469) Device: 20031733571410251h3648e1e918fb7c connected
                                            2023-01-28 01:19:24.223 - info: meross.0 (28469) Device: 1912242800955525188148e1e9146535 connected
                                            2023-01-28 01:19:24.224 - info: meross.0 (28469) Device: 1912248392224225188148e1e9147d1e connected
                                            2023-01-28 01:19:24.225 - info: meross.0 (28469) Device: 1912244502120725188148e1e9147ce4 connected
                                            2023-01-28 01:19:24.226 - info: meross.0 (28469) Device: 1912242390035525188148e1e9146525 connected
                                            2023-01-28 01:19:24.227 - info: meross.0 (28469) Device: 1911271101958325187448e1e9121adc connected
                                            2023-01-28 01:19:24.227 - info: meross.0 (28469) Device: 1911276550451725187448e1e9121125 connected
                                            2023-01-28 01:19:24.228 - info: meross.0 (28469) Device: 1912243266948225188148e1e914931b connected
                                            2023-01-28 01:19:24.228 - info: meross.0 (28469) Device: 1909121197501325186448e1e9037864 connected
                                            2023-01-28 01:19:24.229 - info: meross.0 (28469) Device: 1909125533830625186448e1e903758e connected
                                            2023-01-28 01:19:24.229 - info: meross.0 (28469) Device: 1909123280493825186448e1e9036048 connected
                                            2023-01-28 01:19:24.231 - info: meross.0 (28469) Device: 1909127841759725186448e1e9039ad5 connected
                                            2023-01-28 01:19:24.231 - info: meross.0 (28469) Device: 19060634960444251h0548e1e9001911 connected
                                            2023-01-28 01:19:24.232 - info: meross.0 (28469) Device: 19060619507324251h0548e1e90018fa connected
                                            2023-01-28 01:19:24.232 - info: meross.0 (28469) Device: 1812172967162725182734298f19a581 connected
                                            2023-01-28 01:19:24.233 - info: meross.0 (28469) Device: 1812170301856525182734298f1991d1 connected
                                            2023-01-28 01:19:24.233 - info: meross.0 (28469) Device: 1812171382435925182734298f19a8c4 connected
                                            2023-01-28 01:19:24.234 - info: meross.0 (28469) Device: 1812178389364925182734298f19b176 connected
                                            2023-01-28 01:19:24.234 - info: meross.0 (28469) Device: 1812172861029825182734298f19a5e3 connected
                                            2023-01-28 01:19:24.235 - info: meross.0 (28469) Device: 1812170548019025182734298f198eb2 connected
                                            2023-01-28 01:19:24.235 - info: meross.0 (28469) Device: 1812177950373925182734298f19b642 connected
                                            2023-01-28 01:19:24.236 - info: meross.0 (28469) Device: 1812171073231425182734298f19a473 connected
                                            2023-01-28 01:19:24.236 - info: meross.0 (28469) Device: 1812177841852625182834298f19d9ef connected
                                            2023-01-28 01:19:24.237 - info: meross.0 (28469) Device: 1812173452319625182834298f19c4b6 connected
                                            2023-01-28 01:19:24.237 - info: meross.0 (28469) Device: 1812179369749725182834298f19c865 connected
                                            2023-01-28 01:19:24.238 - info: meross.0 (28469) Device: 1812179610361425182834298f19e0f0 connected
                                            2023-01-28 01:19:24.387 - info: javascript.0 (4010) Stop script script.js.Bewegungsmelder.BWM_Küche
                                            2023-01-28 01:19:24.925 - info: javascript.0 (4010) Stop script script.js.Bewegungsmelder.BWM_WZ
                                            2023-01-28 01:19:25.048 - info: javascript.0 (4010) Start javascript script.js.Bewegungsmelder.BWM_WZ
                                            2023-01-28 01:19:25.055 - info: javascript.0 (4010) script.js.Bewegungsmelder.BWM_WZ: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions
                                            2023-01-28 01:19:26.331 - info: javascript.0 (4010) Start javascript script.js.Bewegungsmelder.BWM_Küche
                                            2023-01-28 01:19:26.337 - info: javascript.0 (4010) script.js.Bewegungsmelder.BWM_Küche: registered 16 subscriptions, 3 schedules, 0 messages, 0 logs and 0 file subscriptions
                                            2023-01-28 01:19:32.941 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:19:37.138 - info: meross.0 (28469) Can not get Data for Device 1812146710587929088434298f197e67: Error: Timeout
                                            2023-01-28 01:19:37.139 - warn: meross.0 (28469) Can not get Data for Device 1812146710587929088434298f197e67: undefined
                                            2023-01-28 01:19:44.327 - info: meross.0 (28469) Can not get Data for Device 1812146710587929088434298f197e67: Error: Timeout
                                            2023-01-28 01:19:44.327 - warn: meross.0 (28469) Can not get Data for Device 1812146710587929088434298f197e67: undefined
                                            2023-01-28 01:19:45.935 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:19:47.354 - info: hmip.0 (4113) Value unchanged, do not send this value
                                            2023-01-28 01:19:55.439 - info: javascript.0 (4010) Stop script script.js.Bewegungsmelder.BWM_WZ
                                            2023-01-28 01:19:55.487 - info: javascript.0 (4010) Start javascript script.js.Bewegungsmelder.BWM_WZ
                                            2023-01-28 01:19:55.492 - info: javascript.0 (4010) script.js.Bewegungsmelder.BWM_WZ: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions
                                            2023-01-28 01:19:58.611 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:20:00.055 - info: host.ioBrokerPC instance system.adapter.dwd.0 started with pid 16081
                                            2023-01-28 01:20:02.294 - info: dwd.0 (16081) starting. Version 2.8.3 in /opt/iobroker/node_modules/iobroker.dwd, node: v16.19.0, js-controller: 4.0.24
                                            2023-01-28 01:20:09.886 - info: dwd.0 (16081) State value to set for "dwd.0.warning1.begin" has to be type "string" but received type "number"
                                            2023-01-28 01:20:09.934 - info: dwd.0 (16081) State value to set for "dwd.0.warning1.end" has to be type "string" but received type "number"
                                            2023-01-28 01:20:10.038 - info: dwd.0 (16081) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                                            2023-01-28 01:20:10.569 - info: host.ioBrokerPC instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                            2023-01-28 01:20:11.231 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:20:20.802 - info: hmip.0 (4113) Value unchanged, do not send this value
                                            2023-01-28 01:20:22.803 - info: javascript.0 (4010) Stop script script.js.Bewegungsmelder.BWM_WZ
                                            2023-01-28 01:20:22.899 - info: javascript.0 (4010) Start javascript script.js.Bewegungsmelder.BWM_WZ
                                            2023-01-28 01:20:22.904 - info: javascript.0 (4010) script.js.Bewegungsmelder.BWM_WZ: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions
                                            2023-01-28 01:20:24.277 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:20:37.139 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:20:50.003 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:20:53.351 - info: javascript.0 (4010) Stop script script.js.Bewegungsmelder.BWM_WZ
                                            2023-01-28 01:20:53.449 - info: javascript.0 (4010) Start javascript script.js.Bewegungsmelder.BWM_WZ
                                            2023-01-28 01:20:53.460 - info: javascript.0 (4010) script.js.Bewegungsmelder.BWM_WZ: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions
                                            2023-01-28 01:21:02.962 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:21:04.335 - info: meross.0 (28469) Can not get Data for Device 1812146710587929088434298f197e67: Error: Timeout
                                            2023-01-28 01:21:04.335 - warn: meross.0 (28469) Can not get Data for Device 1812146710587929088434298f197e67: undefined
                                            2023-01-28 01:21:15.702 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:21:28.240 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:21:40.125 - info: javascript.0 (4010) Stop script script.js.Sonstiges.Kaffee_wird_gebrüht
                                            2023-01-28 01:21:40.177 - info: javascript.0 (4010) Start javascript script.js.Sonstiges.Kaffee_wird_gebrüht
                                            2023-01-28 01:21:40.185 - info: javascript.0 (4010) script.js.Sonstiges.Kaffee_wird_gebrüht: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions
                                            2023-01-28 01:21:41.350 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:21:53.184 - info: javascript.0 (4010) Stop script script.js.Bewegungsmelder.BWM_WZ
                                            2023-01-28 01:21:53.280 - info: javascript.0 (4010) Start javascript script.js.Bewegungsmelder.BWM_WZ
                                            2023-01-28 01:21:53.288 - info: javascript.0 (4010) script.js.Bewegungsmelder.BWM_WZ: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions
                                            2023-01-28 01:21:54.250 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:21:57.069 - info: hmip.0 (4113) Value unchanged, do not send this value
                                            2023-01-28 01:22:02.785 - info: web.0 (5022) <== Disconnect system.user.admin from ::ffff:192.168.178.95 vis.0
                                            2023-01-28 01:22:07.053 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:22:19.794 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:22:23.777 - info: javascript.0 (4010) Stop script script.js.Bewegungsmelder.BWM_WZ
                                            2023-01-28 01:22:23.801 - info: javascript.0 (4010) Start javascript script.js.Bewegungsmelder.BWM_WZ
                                            2023-01-28 01:22:23.807 - info: javascript.0 (4010) script.js.Bewegungsmelder.BWM_WZ: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions
                                            2023-01-28 01:22:23.866 - info: javascript.0 (4010) Stop script script.js.Bewegungsmelder.BWM_WZ
                                            2023-01-28 01:22:23.916 - info: javascript.0 (4010) Start javascript script.js.Bewegungsmelder.BWM_WZ
                                            2023-01-28 01:22:23.924 - info: javascript.0 (4010) script.js.Bewegungsmelder.BWM_WZ: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions
                                            2023-01-28 01:22:24.341 - info: meross.0 (28469) Can not get Data for Device 1812146710587929088434298f197e67: Error: Timeout
                                            2023-01-28 01:22:24.342 - warn: meross.0 (28469) Can not get Data for Device 1812146710587929088434298f197e67: undefined
                                            2023-01-28 01:22:32.775 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:22:36.528 - info: hmip.0 (4113) Value unchanged, do not send this value
                                            2023-01-28 01:22:45.455 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:22:58.142 - info: javascript.0 (4010) Stop script script.js.Nachrichten.Temperaturalarm_IoBroker_PC
                                            2023-01-28 01:22:58.153 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:22:58.248 - info: javascript.0 (4010) Start javascript script.js.Nachrichten.Temperaturalarm_IoBroker_PC
                                            2023-01-28 01:22:58.252 - info: javascript.0 (4010) script.js.Nachrichten.Temperaturalarm_IoBroker_PC: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions
                                            2023-01-28 01:23:00.058 - info: host.ioBrokerPC instance system.adapter.openweathermap.0 started with pid 25041
                                            2023-01-28 01:23:02.342 - info: openweathermap.0 (25041) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v16.19.0, js-controller: 4.0.24
                                            2023-01-28 01:23:10.887 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:23:23.440 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:23:33.958 - info: openweathermap.0 (25041) Terminated (NO_ERROR): Without reason
                                            2023-01-28 01:23:34.480 - info: host.ioBrokerPC instance system.adapter.openweathermap.0 terminated with code 0 (NO_ERROR)
                                            2023-01-28 01:23:36.238 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:23:44.348 - info: meross.0 (28469) Can not get Data for Device 1812146710587929088434298f197e67: Error: Timeout
                                            2023-01-28 01:23:44.348 - warn: meross.0 (28469) Can not get Data for Device 1812146710587929088434298f197e67: undefined
                                            2023-01-28 01:23:48.946 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:23:55.318 - info: web.0 (5022) <== Disconnect system.user.admin from ::ffff:192.168.178.95
                                            2023-01-28 01:24:01.823 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:24:10.698 - info: javascript.0 (4010) Stop script script.js.Sonstiges.Kaffee_wird_gebrüht
                                            2023-01-28 01:24:10.797 - info: javascript.0 (4010) Start javascript script.js.Sonstiges.Kaffee_wird_gebrüht
                                            2023-01-28 01:24:10.804 - info: javascript.0 (4010) script.js.Sonstiges.Kaffee_wird_gebrüht: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions
                                            2023-01-28 01:24:11.068 - info: hmip.0 (4113) Value unchanged, do not send this value
                                            2023-01-28 01:24:14.677 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:24:27.229 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:24:39.845 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:24:52.706 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:24:54.410 - info: hmip.0 (4113) Value unchanged, do not send this value
                                            2023-01-28 01:24:58.129 - info: javascript.0 (4010) Stop script script.js.Nachrichten.Temperaturalarm_IoBroker_PC
                                            2023-01-28 01:24:58.252 - info: javascript.0 (4010) Start javascript script.js.Nachrichten.Temperaturalarm_IoBroker_PC
                                            2023-01-28 01:24:58.266 - info: javascript.0 (4010) script.js.Nachrichten.Temperaturalarm_IoBroker_PC: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions
                                            2023-01-28 01:25:00.059 - info: host.ioBrokerPC instance system.adapter.dwd.0 started with pid 30909
                                            2023-01-28 01:25:02.214 - info: dwd.0 (30909) starting. Version 2.8.3 in /opt/iobroker/node_modules/iobroker.dwd, node: v16.19.0, js-controller: 4.0.24
                                            2023-01-28 01:25:04.353 - info: meross.0 (28469) Can not get Data for Device 1812146710587929088434298f197e67: Error: Timeout
                                            2023-01-28 01:25:04.354 - warn: meross.0 (28469) Can not get Data for Device 1812146710587929088434298f197e67: undefined
                                            2023-01-28 01:25:05.442 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:25:08.599 - info: dwd.0 (30909) State value to set for "dwd.0.warning1.begin" has to be type "string" but received type "number"
                                            2023-01-28 01:25:08.651 - info: dwd.0 (30909) State value to set for "dwd.0.warning1.end" has to be type "string" but received type "number"
                                            2023-01-28 01:25:08.760 - info: dwd.0 (30909) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                                            2023-01-28 01:25:09.232 - info: meross.0 (28469) Device: 2211016259159251080148e1e9ad94ed closed: null
                                            2023-01-28 01:25:09.233 - info: meross.0 (28469) Device: 2211012131734251080148e1e9adac10 closed: null
                                            2023-01-28 01:25:09.233 - info: meross.0 (28469) Device: 1812146710587929088434298f197e67 closed: null
                                            2023-01-28 01:25:09.234 - info: meross.0 (28469) Device: 2102035620020190841348e1e94a832c closed: null
                                            2023-01-28 01:25:09.234 - info: meross.0 (28469) Device: 2102037387671590841348e1e94a9475 closed: null
                                            2023-01-28 01:25:09.234 - info: meross.0 (28469) Device: 2102036474864790841348e1e94a7d00 closed: null
                                            2023-01-28 01:25:09.235 - info: meross.0 (28469) Device: 20031733571410251h3648e1e918fb7c closed: null
                                            2023-01-28 01:25:09.235 - info: meross.0 (28469) Device: 1912242800955525188148e1e9146535 closed: null
                                            2023-01-28 01:25:09.236 - info: meross.0 (28469) Device: 1912248392224225188148e1e9147d1e closed: null
                                            2023-01-28 01:25:09.236 - info: meross.0 (28469) Device: 1912244502120725188148e1e9147ce4 closed: null
                                            2023-01-28 01:25:09.236 - info: meross.0 (28469) Device: 1912242390035525188148e1e9146525 closed: null
                                            2023-01-28 01:25:09.237 - info: meross.0 (28469) Device: 1911271101958325187448e1e9121adc closed: null
                                            2023-01-28 01:25:09.237 - info: meross.0 (28469) Device: 1911276550451725187448e1e9121125 closed: null
                                            2023-01-28 01:25:09.237 - info: meross.0 (28469) Device: 1912243266948225188148e1e914931b closed: null
                                            2023-01-28 01:25:09.238 - info: meross.0 (28469) Device: 1909121197501325186448e1e9037864 closed: null
                                            2023-01-28 01:25:09.238 - info: meross.0 (28469) Device: 1909125533830625186448e1e903758e closed: null
                                            2023-01-28 01:25:09.239 - info: meross.0 (28469) Device: 1909123280493825186448e1e9036048 closed: null
                                            2023-01-28 01:25:09.239 - info: meross.0 (28469) Device: 1909127841759725186448e1e9039ad5 closed: null
                                            2023-01-28 01:25:09.239 - info: meross.0 (28469) Device: 19060634960444251h0548e1e9001911 closed: null
                                            2023-01-28 01:25:09.240 - info: meross.0 (28469) Device: 19060619507324251h0548e1e90018fa closed: null
                                            2023-01-28 01:25:09.240 - info: meross.0 (28469) Device: 1812172967162725182734298f19a581 closed: null
                                            2023-01-28 01:25:09.240 - info: meross.0 (28469) Device: 1812170301856525182734298f1991d1 closed: null
                                            2023-01-28 01:25:09.241 - info: meross.0 (28469) Device: 1812171382435925182734298f19a8c4 closed: null
                                            2023-01-28 01:25:09.241 - info: meross.0 (28469) Device: 1812178389364925182734298f19b176 closed: null
                                            2023-01-28 01:25:09.242 - info: meross.0 (28469) Device: 1812172861029825182734298f19a5e3 closed: null
                                            2023-01-28 01:25:09.242 - info: meross.0 (28469) Device: 1812170548019025182734298f198eb2 closed: null
                                            2023-01-28 01:25:09.242 - info: meross.0 (28469) Device: 1812177950373925182734298f19b642 closed: null
                                            2023-01-28 01:25:09.243 - info: meross.0 (28469) Device: 1812171073231425182734298f19a473 closed: null
                                            2023-01-28 01:25:09.243 - info: meross.0 (28469) Device: 1812177841852625182834298f19d9ef closed: null
                                            2023-01-28 01:25:09.243 - info: meross.0 (28469) Device: 1812173452319625182834298f19c4b6 closed: null
                                            2023-01-28 01:25:09.244 - info: meross.0 (28469) Device: 1812179369749725182834298f19c865 closed: null
                                            2023-01-28 01:25:09.244 - info: meross.0 (28469) Device: 1812179610361425182834298f19e0f0 closed: null
                                            2023-01-28 01:25:09.286 - info: host.ioBrokerPC instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                            2023-01-28 01:25:14.232 - info: meross.0 (28469) Device: 2211016259159251080148e1e9ad94ed reconnected
                                            2023-01-28 01:25:14.233 - info: meross.0 (28469) Device: 2211012131734251080148e1e9adac10 reconnected
                                            2023-01-28 01:25:14.233 - info: meross.0 (28469) Device: 1812146710587929088434298f197e67 reconnected
                                            2023-01-28 01:25:14.233 - info: meross.0 (28469) Device: 2102035620020190841348e1e94a832c reconnected
                                            2023-01-28 01:25:14.233 - info: meross.0 (28469) Device: 2102037387671590841348e1e94a9475 reconnected
                                            2023-01-28 01:25:14.234 - info: meross.0 (28469) Device: 2102036474864790841348e1e94a7d00 reconnected
                                            2023-01-28 01:25:14.234 - info: meross.0 (28469) Device: 20031733571410251h3648e1e918fb7c reconnected
                                            2023-01-28 01:25:14.234 - info: meross.0 (28469) Device: 1912242800955525188148e1e9146535 reconnected
                                            2023-01-28 01:25:14.234 - info: meross.0 (28469) Device: 1912248392224225188148e1e9147d1e reconnected
                                            2023-01-28 01:25:14.234 - info: meross.0 (28469) Device: 1912244502120725188148e1e9147ce4 reconnected
                                            2023-01-28 01:25:14.235 - info: meross.0 (28469) Device: 1912242390035525188148e1e9146525 reconnected
                                            2023-01-28 01:25:14.235 - info: meross.0 (28469) Device: 1911271101958325187448e1e9121adc reconnected
                                            2023-01-28 01:25:14.235 - info: meross.0 (28469) Device: 1911276550451725187448e1e9121125 reconnected
                                            2023-01-28 01:25:14.235 - info: meross.0 (28469) Device: 1912243266948225188148e1e914931b reconnected
                                            2023-01-28 01:25:14.235 - info: meross.0 (28469) Device: 1909121197501325186448e1e9037864 reconnected
                                            2023-01-28 01:25:14.235 - info: meross.0 (28469) Device: 1909125533830625186448e1e903758e reconnected
                                            2023-01-28 01:25:14.236 - info: meross.0 (28469) Device: 1909123280493825186448e1e9036048 reconnected
                                            2023-01-28 01:25:14.236 - info: meross.0 (28469) Device: 1909127841759725186448e1e9039ad5 reconnected
                                            2023-01-28 01:25:14.236 - info: meross.0 (28469) Device: 19060634960444251h0548e1e9001911 reconnected
                                            2023-01-28 01:25:14.236 - info: meross.0 (28469) Device: 19060619507324251h0548e1e90018fa reconnected
                                            2023-01-28 01:25:14.236 - info: meross.0 (28469) Device: 1812172967162725182734298f19a581 reconnected
                                            2023-01-28 01:25:14.237 - info: meross.0 (28469) Device: 1812170301856525182734298f1991d1 reconnected
                                            2023-01-28 01:25:14.237 - info: meross.0 (28469) Device: 1812171382435925182734298f19a8c4 reconnected
                                            2023-01-28 01:25:14.237 - info: meross.0 (28469) Device: 1812178389364925182734298f19b176 reconnected
                                            2023-01-28 01:25:14.237 - info: meross.0 (28469) Device: 1812172861029825182734298f19a5e3 reconnected
                                            2023-01-28 01:25:14.237 - info: meross.0 (28469) Device: 1812170548019025182734298f198eb2 reconnected
                                            2023-01-28 01:25:14.238 - info: meross.0 (28469) Device: 1812177950373925182734298f19b642 reconnected
                                            2023-01-28 01:25:14.238 - info: meross.0 (28469) Device: 1812171073231425182734298f19a473 reconnected
                                            2023-01-28 01:25:14.238 - info: meross.0 (28469) Device: 1812177841852625182834298f19d9ef reconnected
                                            2023-01-28 01:25:14.238 - info: meross.0 (28469) Device: 1812173452319625182834298f19c4b6 reconnected
                                            2023-01-28 01:25:14.238 - info: meross.0 (28469) Device: 1812179369749725182834298f19c865 reconnected
                                            2023-01-28 01:25:14.238 - info: meross.0 (28469) Device: 1812179610361425182834298f19e0f0 reconnected
                                            2023-01-28 01:25:14.452 - info: meross.0 (28469) Device: 2211016259159251080148e1e9ad94ed connected
                                            2023-01-28 01:25:14.453 - info: meross.0 (28469) Device: 2211012131734251080148e1e9adac10 connected
                                            2023-01-28 01:25:14.454 - info: meross.0 (28469) Device: 1812146710587929088434298f197e67 connected
                                            2023-01-28 01:25:14.455 - info: meross.0 (28469) Device: 2102035620020190841348e1e94a832c connected
                                            2023-01-28 01:25:14.455 - info: meross.0 (28469) Device: 2102037387671590841348e1e94a9475 connected
                                            2023-01-28 01:25:14.456 - info: meross.0 (28469) Device: 2102036474864790841348e1e94a7d00 connected
                                            2023-01-28 01:25:14.456 - info: meross.0 (28469) Device: 20031733571410251h3648e1e918fb7c connected
                                            2023-01-28 01:25:14.457 - info: meross.0 (28469) Device: 1912242800955525188148e1e9146535 connected
                                            2023-01-28 01:25:14.458 - info: meross.0 (28469) Device: 1912248392224225188148e1e9147d1e connected
                                            2023-01-28 01:25:14.458 - info: meross.0 (28469) Device: 1912244502120725188148e1e9147ce4 connected
                                            2023-01-28 01:25:14.459 - info: meross.0 (28469) Device: 1912242390035525188148e1e9146525 connected
                                            2023-01-28 01:25:14.459 - info: meross.0 (28469) Device: 1911271101958325187448e1e9121adc connected
                                            2023-01-28 01:25:14.460 - info: meross.0 (28469) Device: 1911276550451725187448e1e9121125 connected
                                            2023-01-28 01:25:14.461 - info: meross.0 (28469) Device: 1912243266948225188148e1e914931b connected
                                            2023-01-28 01:25:14.461 - info: meross.0 (28469) Device: 1909121197501325186448e1e9037864 connected
                                            2023-01-28 01:25:14.462 - info: meross.0 (28469) Device: 1909125533830625186448e1e903758e connected
                                            2023-01-28 01:25:14.462 - info: meross.0 (28469) Device: 1909123280493825186448e1e9036048 connected
                                            2023-01-28 01:25:14.463 - info: meross.0 (28469) Device: 1909127841759725186448e1e9039ad5 connected
                                            2023-01-28 01:25:14.464 - info: meross.0 (28469) Device: 19060634960444251h0548e1e9001911 connected
                                            2023-01-28 01:25:14.464 - info: meross.0 (28469) Device: 19060619507324251h0548e1e90018fa connected
                                            2023-01-28 01:25:14.465 - info: meross.0 (28469) Device: 1812172967162725182734298f19a581 connected
                                            2023-01-28 01:25:14.465 - info: meross.0 (28469) Device: 1812170301856525182734298f1991d1 connected
                                            2023-01-28 01:25:14.466 - info: meross.0 (28469) Device: 1812171382435925182734298f19a8c4 connected
                                            2023-01-28 01:25:14.466 - info: meross.0 (28469) Device: 1812178389364925182734298f19b176 connected
                                            2023-01-28 01:25:14.467 - info: meross.0 (28469) Device: 1812172861029825182734298f19a5e3 connected
                                            2023-01-28 01:25:14.468 - info: meross.0 (28469) Device: 1812170548019025182734298f198eb2 connected
                                            2023-01-28 01:25:14.468 - info: meross.0 (28469) Device: 1812177950373925182734298f19b642 connected
                                            2023-01-28 01:25:14.469 - info: meross.0 (28469) Device: 1812171073231425182734298f19a473 connected
                                            2023-01-28 01:25:14.470 - info: meross.0 (28469) Device: 1812177841852625182834298f19d9ef connected
                                            2023-01-28 01:25:14.470 - info: meross.0 (28469) Device: 1812173452319625182834298f19c4b6 connected
                                            2023-01-28 01:25:14.471 - info: meross.0 (28469) Device: 1812179369749725182834298f19c865 connected
                                            2023-01-28 01:25:14.471 - info: meross.0 (28469) Device: 1812179610361425182834298f19e0f0 connected
                                            2023-01-28 01:25:14.568 - info: javascript.0 (4010) Stop script script.js.Bewegungsmelder.BWM_Küche
                                            2023-01-28 01:25:16.526 - info: javascript.0 (4010) Start javascript script.js.Bewegungsmelder.BWM_Küche
                                            2023-01-28 01:25:16.533 - info: javascript.0 (4010) script.js.Bewegungsmelder.BWM_Küche: registered 16 subscriptions, 3 schedules, 0 messages, 0 logs and 0 file subscriptions
                                            2023-01-28 01:25:18.252 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:25:31.182 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117
                                            2023-01-28 01:25:34.500 - info: meross.0 (28469) Can not get Data for Device 1812146710587929088434298f197e67: Error: Timeout
                                            2023-01-28 01:25:34.500 - warn: meross.0 (28469) Can not get Data for Device 1812146710587929088434298f197e67: undefined
                                            2023-01-28 01:25:36.673 - info: javascript.0 (4010) Stop script script.js.Bewegungsmelder.BWM_WZ
                                            2023-01-28 01:25:36.716 - info: javascript.0 (4010) Start javascript script.js.Bewegungsmelder.BWM_WZ
                                            2023-01-28 01:25:36.720 - info: javascript.0 (4010) script.js.Bewegungsmelder.BWM_WZ: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions
                                            2023-01-28 01:25:43.790 - warn: fullybrowser.0 (6436) updateDeviceERROR 192.168.178.117

                                            Ich weiß nicht ob das so richtig ist. Ich selber kann damit nichts anfangen.

                                            apollon77 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

                                            1.1k
                                            Online

                                            31.6k
                                            Users

                                            79.4k
                                            Topics

                                            1.3m
                                            Posts

                                            9
                                            134
                                            9157
                                            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