Meross nur noch unidirektional

[MyzerAT]

@apollon77

das Problem, war das in den Objekten beim besagten Gerät nur zwei Zeilen sichtbar waren, nicht wie jetzt :

ist auch immer anders! einmal erkannte er das Gerät und beim nächsten mal wieder nicht! Momentan, auch wenn ich mehrmals die Instanz starte, funktioniert es ohne Probleme

[apollon77]

@myzerat Also die Objekte sollten kommen sobald das Gerät initialisiert wurde

[MyzerAT]

@apollon77

ja das tun sie, aber vor tagen nicht immer! zur zeit funktioniert es ohne probs !

[MyzerAT]

@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

[apollon77]

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

[MyzerAT]

@apollon77

sieht so aus als wäre es das doch nicht

[apollon77]

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

[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

[MyzerAT]

@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

[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

[MCU]

@myzerat Ok, mach ich mal. Danke.

[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?

[MCU]

@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

[apollon77]

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]

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

[apollon77]

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

[andiko2]

@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]

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

[andiko2]

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

System:

Spoiler

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.

Spoiler

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

[apollon77]

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