Meross nur noch unidirektional
-
ich habe seit Tagen ein Ähnliches Problem.
habe jetzt auch die Version 1.11.0 installiert, aber es ändert nichts an dem Problem!
Meine Meross Instanz startet mehrmals aus unerfindlichen Grund neu und es werden dann immer einige Geräte nicht gefunden, per Handy App geht aber alles. Selbst wenn ich auf dem Handy ein Gerät das per Iobroker nicht geschaltet werden kann --> einschalte, sieht man es dann im Iobroker true aber am iobroker selbst lässt es sich nicht schalten, wenn diese Meldung in den Logs steht :
meross.0 2022-06-09 12:41:12.828 warn Can not get Data for Device 1809013215340225180534298f166a51: undefined meross.0 2022-06-09 12:41:12.828 info Can not get Data for Device 1809013215340225180534298f166a51: Error: Timeout meross.0 2022-06-09 12:41:12.785 warn Can not get Data for Device 1810224092789329085334298f16f18d: undefined meross.0 2022-06-09 12:41:12.785 info Can not get Data for Device 1810224092789329085334298f16f18d: Error: Timeouthier ein Log, wo man sieht das die Instanz immer neustartet
2022-06-08 00:00:00.044 - [32minfo[39m: meross.0 (3683) Scheduled restart. 2022-06-08 00:00:00.096 - [32minfo[39m: javascript.0 (448) script.js.common.Heizung.WC_E-Heizung: getState(id=#Eigene.0.Heizung.Heizen_WC, timerId=undefined) => {"val":false,"ack":true,"ts":1654635661286,"q":0,"c":"script.js.common.Heizung.WC_E-Heizung","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1654624861280} 2022-06-08 00:00:00.100 - [32minfo[39m: meross.0 (3683) Device: 19011898369667251h0434298f1a6462 closed: null 2022-06-08 00:00:00.101 - [32minfo[39m: meross.0 (3683) Device: 1811305641257125182134298f187fdd closed: null 2022-06-08 00:00:00.101 - [32minfo[39m: meross.0 (3683) Device: 18122163520756258h0334298f144240 closed: null 2022-06-08 00:00:00.102 - [32minfo[39m: meross.0 (3683) Device: 21020338573116251h6148e1e94abdc7 closed: null 2022-06-08 00:00:00.103 - [32minfo[39m: meross.0 (3683) Device: 21020300990383251h6148e1e94acdf8 closed: null 2022-06-08 00:00:00.103 - [32minfo[39m: meross.0 (3683) Device: 2001192419504425188548e1e9171db0 closed: null 2022-06-08 00:00:00.104 - [32minfo[39m: meross.0 (3683) Device: 1809016208959425180534298f1665ca closed: null 2022-06-08 00:00:00.104 - [32minfo[39m: meross.0 (3683) Device: 19011820035814251h0334298f1a0745 closed: null 2022-06-08 00:00:00.105 - [32minfo[39m: meross.0 (3683) Device: 19011818986476251h0434298f1a5b94 closed: null 2022-06-08 00:00:00.106 - [32minfo[39m: meross.0 (3683) Device: 2001191193736125188548e1e9171e9a closed: null 2022-06-08 00:00:00.106 - [32minfo[39m: meross.0 (3683) Device: 2001194310463525188548e1e9172324 closed: null 2022-06-08 00:00:00.107 - [32minfo[39m: meross.0 (3683) Device: 2001192823402125188548e1e9172387 closed: null 2022-06-08 00:00:00.107 - [32minfo[39m: meross.0 (3683) Device: 1812178320463025182834298f19ca1c closed: null 2022-06-08 00:00:00.108 - [32minfo[39m: meross.0 (3683) Device: 19011832535820251h0334298f1a090a closed: null 2022-06-08 00:00:00.108 - [32minfo[39m: meross.0 (3683) Device: 1809015737278325180534298f16671f closed: null 2022-06-08 00:00:00.109 - [32minfo[39m: meross.0 (3683) Device: 1809010653847025180534298f16668c closed: null 2022-06-08 00:00:00.109 - [32minfo[39m: meross.0 (3683) Device: 19011849037183251h0434298f1a5d0d closed: null 2022-06-08 00:00:00.110 - [32minfo[39m: meross.0 (3683) Device: 19011863874770251h0434298f1a5666 closed: null 2022-06-08 00:00:00.111 - [32minfo[39m: meross.0 (3683) Device: 1812174950278625182834298f19c365 closed: null 2022-06-08 00:00:00.112 - [32minfo[39m: meross.0 (3683) Device: 19011873123850251h0334298f1a09a6 closed: null 2022-06-08 00:00:00.112 - [32minfo[39m: meross.0 (3683) Device: 1812179492140325182834298f19d01f closed: null 2022-06-08 00:00:00.113 - [32minfo[39m: meross.0 (3683) Device: 19011882830659251h0334298f1a0625 closed: null 2022-06-08 00:00:00.113 - [32minfo[39m: meross.0 (3683) Device: 1811301845905925182134298f1880f5 closed: null 2022-06-08 00:00:00.114 - [32minfo[39m: meross.0 (3683) Device: 1809014572480225180534298f166ab5 closed: null 2022-06-08 00:00:00.114 - [32minfo[39m: meross.0 (3683) Device: 1810224092789329085334298f16f18d closed: null 2022-06-08 00:00:00.115 - [32minfo[39m: meross.0 (3683) Device: 1811305787614825182134298f187da6 closed: null 2022-06-08 00:00:00.115 - [32minfo[39m: meross.0 (3683) Device: 1810221956507129085334298f16f380 closed: null 2022-06-08 00:00:00.116 - [32minfo[39m: meross.0 (3683) Device: 1809012709631425180534298f16660a closed: null 2022-06-08 00:00:00.116 - [32minfo[39m: meross.0 (3683) Device: 1809017394109425180534298f166544 closed: null 2022-06-08 00:00:00.117 - [32minfo[39m: meross.0 (3683) Device: 1809014813536325180534298f166a87 closed: null 2022-06-08 00:00:00.117 - [32minfo[39m: meross.0 (3683) Device: 1809013215340225180534298f166a51 closed: null 2022-06-08 00:00:00.118 - [32minfo[39m: meross.0 (3683) Device: 1811301259073025182134298f187dd9 closed: null 2022-06-08 00:00:00.118 - [32minfo[39m: meross.0 (3683) Device: 1811302076928625182134298f188306 closed: null 2022-06-08 00:00:00.119 - [32minfo[39m: meross.0 (3683) Device: 1811306089340925182134298f187b61 closed: null 2022-06-08 00:00:00.119 - [32minfo[39m: meross.0 (3683) Device: 1811303935030425182134298f187dde closed: null 2022-06-08 00:00:00.119 - [32minfo[39m: meross.0 (3683) Device: 1811304781456425182134298f1882c8 closed: null 2022-06-08 00:00:00.113 - [32minfo[39m: javascript.0 (448) script.js.common.Heizung.WC_E-Heizung: setForeignState(id=#Eigene.0.WC.SollTempWC, state={"val":18,"ack":true,"c":"script.js.common.Heizung.WC_E-Heizung"}) 2022-06-08 00:00:00.170 - [33mwarn[39m: javascript.0 (448) script.js.common.#Tulln.PV_Anlage.Generator_Start_Stop: ********* Lärmzeit 9-11 + 16-19 AUS 2022-06-08 00:00:00.171 - [33mwarn[39m: javascript.0 (448) script.js.common.#Tulln.PV_Anlage.Generator_Start_Stop: ********* Lärmzeit AUS 2022-06-08 00:00:00.209 - [33mwarn[39m: javascript.0 (448) script.js.common.#Tulln.PV_Anlage.Generator_Start_Stop: ********* Sonntag ist FALSCH 2022-06-08 00:00:00.297 - [32minfo[39m: javascript.0 (448) script.js.common.Heizung.WC_E-Heizung: getState(id=#Eigene.0.Heizung.Intervall.WC.00, timerId=undefined) => {"val":false,"ack":false,"ts":1575274291656,"q":0,"from":"system.adapter.admin.0","lc":1575274291656} 2022-06-08 00:00:00.298 - [32minfo[39m: javascript.0 (448) script.js.common.Heizung.WC_E-Heizung: setStateDelayed(id=#Eigene.0.Heizung.Heizen_WC, state=false, isAck=true, delay=61000, clearRunning=false) 2022-06-08 00:00:03.408 - [32minfo[39m: meross.0 (3683) terminating 2022-06-08 00:00:03.410 - [32minfo[39m: meross.0 (3683) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2022-06-08 00:00:04.059 - [32minfo[39m: host.RDJLHome instance system.adapter.meross.0 scheduled normal terminated and will be restarted on schedule. 2022-06-08 00:00:04.075 - [32minfo[39m: host.RDJLHome Restart adapter system.adapter.meross.0 because enabled 2022-06-08 00:00:05.229 - [32minfo[39m: host.RDJLHome instance system.adapter.meross.0 started with pid 27629 2022-06-08 00:00:08.161 - [32minfo[39m: meross.0 (27629) starting. Version 1.10.5 (non-npm: Apollon77/ioBroker.meross#ae71235c96c0beedf83869967a87b881c9e7e152) in /opt/iobroker/node_modules/iobroker.meross, node: v12.22.1, js-controller: 4.0.21 2022-06-08 00:00:08.992 - [32minfo[39m: meross.0 (27629) Device 19011898369667251h0434298f1a6462 initialized 2022-06-08 00:00:09.107 - [32minfo[39m: meross.0 (27629) Device 1811305641257125182134298f187fdd initialized 2022-06-08 00:00:09.108 - [32minfo[39m: meross.0 (27629) Device 18122163520756258h0334298f144240 initialized 2022-06-08 00:00:09.109 - [32minfo[39m: meross.0 (27629) Device 21020338573116251h6148e1e94abdc7 initialized 2022-06-08 00:00:09.110 - [32minfo[39m: meross.0 (27629) Device 21020300990383251h6148e1e94acdf8 initialized 2022-06-08 00:00:09.112 - [32minfo[39m: meross.0 (27629) Device 2001192419504425188548e1e9171db0 initialized 2022-06-08 00:00:09.113 - [32minfo[39m: meross.0 (27629) Device 1809016208959425180534298f1665ca initialized 2022-06-08 00:00:09.113 - [32minfo[39m: meross.0 (27629) Device 19011820035814251h0334298f1a0745 initialized 2022-06-08 00:00:09.114 - [32minfo[39m: meross.0 (27629) Device 19011818986476251h0434298f1a5b94 initialized 2022-06-08 00:00:09.115 - [32minfo[39m: meross.0 (27629) Device 2001191193736125188548e1e9171e9a initialized 2022-06-08 00:00:09.116 - [32minfo[39m: meross.0 (27629) Device 2001194310463525188548e1e9172324 initialized 2022-06-08 00:00:09.117 - [32minfo[39m: meross.0 (27629) Device 2001192823402125188548e1e9172387 initialized 2022-06-08 00:00:09.118 - [32minfo[39m: meross.0 (27629) Device 1812178320463025182834298f19ca1c initialized 2022-06-08 00:00:09.119 - [32minfo[39m: meross.0 (27629) Device 19011832535820251h0334298f1a090a initialized 2022-06-08 00:00:09.120 - [32minfo[39m: meross.0 (27629) Device 1809015737278325180534298f16671f initialized 2022-06-08 00:00:09.121 - [32minfo[39m: meross.0 (27629) Device 1809010653847025180534298f16668c initialized 2022-06-08 00:00:09.122 - [32minfo[39m: meross.0 (27629) Device 19011849037183251h0434298f1a5d0d initialized 2022-06-08 00:00:09.123 - [32minfo[39m: meross.0 (27629) Device 19011863874770251h0434298f1a5666 initialized 2022-06-08 00:00:09.123 - [32minfo[39m: meross.0 (27629) Device 1812174950278625182834298f19c365 initialized 2022-06-08 00:00:09.124 - [32minfo[39m: meross.0 (27629) Device 19011873123850251h0334298f1a09a6 initialized 2022-06-08 00:00:09.125 - [32minfo[39m: meross.0 (27629) Device 1812179492140325182834298f19d01f initialized 2022-06-08 00:00:09.126 - [32minfo[39m: meross.0 (27629) Device 19011882830659251h0334298f1a0625 initialized 2022-06-08 00:00:09.127 - [32minfo[39m: meross.0 (27629) Device 1811301845905925182134298f1880f5 initialized 2022-06-08 00:00:09.128 - [32minfo[39m: meross.0 (27629) Device 1809014572480225180534298f166ab5 initialized 2022-06-08 00:00:09.129 - [32minfo[39m: meross.0 (27629) Device 1810224092789329085334298f16f18d initialized 2022-06-08 00:00:09.130 - [32minfo[39m: meross.0 (27629) Device 1811305787614825182134298f187da6 initialized 2022-06-08 00:00:09.131 - [32minfo[39m: meross.0 (27629) Device 1810221956507129085334298f16f380 initialized 2022-06-08 00:00:09.131 - [32minfo[39m: meross.0 (27629) Device 1809012709631425180534298f16660a initialized 2022-06-08 00:00:09.132 - [32minfo[39m: meross.0 (27629) Device 1809017394109425180534298f166544 initialized 2022-06-08 00:00:09.133 - [32minfo[39m: meross.0 (27629) Device 1809014813536325180534298f166a87 initialized 2022-06-08 00:00:09.134 - [32minfo[39m: meross.0 (27629) Device 1809013215340225180534298f166a51 initialized 2022-06-08 00:00:09.134 - [32minfo[39m: meross.0 (27629) Device 1811301259073025182134298f187dd9 initialized 2022-06-08 00:00:09.135 - [32minfo[39m: meross.0 (27629) Device 1811302076928625182134298f188306 initialized 2022-06-08 00:00:09.136 - [32minfo[39m: meross.0 (27629) Device 1811306089340925182134298f187b61 initialized 2022-06-08 00:00:09.137 - [32minfo[39m: meross.0 (27629) Device 1811303935030425182134298f187dde initialized 2022-06-08 00:00:09.138 - [32minfo[39m: meross.0 (27629) Device 1811304781456425182134298f1882c8 initialized 2022-06-08 00:00:09.365 - [32minfo[39m: meross.0 (27629) Device: 19011898369667251h0434298f1a6462 connected 2022-06-08 00:00:09.369 - [32minfo[39m: meross.0 (27629) Device: 1811305641257125182134298f187fdd connected 2022-06-08 00:00:09.371 - [32minfo[39m: meross.0 (27629) Device: 18122163520756258h0334298f144240 connected 2022-06-08 00:00:09.373 - [32minfo[39m: meross.0 (27629) Device: 21020338573116251h6148e1e94abdc7 connected 2022-06-08 00:00:09.375 - [32minfo[39m: meross.0 (27629) Device: 21020300990383251h6148e1e94acdf8 connected 2022-06-08 00:00:09.378 - [32minfo[39m: meross.0 (27629) Device: 2001192419504425188548e1e9171db0 connected 2022-06-08 00:00:09.380 - [32minfo[39m: meross.0 (27629) Device: 1809016208959425180534298f1665ca connected 2022-06-08 00:00:09.382 - [32minfo[39m: meross.0 (27629) Device: 19011820035814251h0334298f1a0745 connected 2022-06-08 00:00:09.384 - [32minfo[39m: meross.0 (27629) Device: 19011818986476251h0434298f1a5b94 connected 2022-06-08 00:00:09.386 - [32minfo[39m: meross.0 (27629) Device: 2001191193736125188548e1e9171e9a connected 2022-06-08 00:00:09.388 - [32minfo[39m: meross.0 (27629) Device: 2001194310463525188548e1e9172324 connected 2022-06-08 00:00:09.390 - [32minfo[39m: meross.0 (27629) Device: 2001192823402125188548e1e9172387 connected 2022-06-08 00:00:09.392 - [32minfo[39m: meross.0 (27629) Device: 1812178320463025182834298f19ca1c connected 2022-06-08 00:00:09.394 - [32minfo[39m: meross.0 (27629) Device: 19011832535820251h0334298f1a090a connected 2022-06-08 00:00:09.395 - [32minfo[39m: meross.0 (27629) Device: 1809015737278325180534298f16671f connected 2022-06-08 00:00:09.397 - [32minfo[39m: meross.0 (27629) Device: 1809010653847025180534298f16668c connected 2022-06-08 00:00:09.399 - [32minfo[39m: meross.0 (27629) Device: 19011849037183251h0434298f1a5d0d connected 2022-06-08 00:00:09.402 - [32minfo[39m: meross.0 (27629) Device: 19011863874770251h0434298f1a5666 connected 2022-06-08 00:00:09.408 - [32minfo[39m: meross.0 (27629) Device: 1812174950278625182834298f19c365 connected 2022-06-08 00:00:09.410 - [32minfo[39m: meross.0 (27629) Device: 19011873123850251h0334298f1a09a6 connected 2022-06-08 00:00:09.411 - [32minfo[39m: meross.0 (27629) Device: 1812179492140325182834298f19d01f connected 2022-06-08 00:00:09.412 - [32minfo[39m: meross.0 (27629) Device: 19011882830659251h0334298f1a0625 connected 2022-06-08 00:00:09.414 - [32minfo[39m: meross.0 (27629) Device: 1811301845905925182134298f1880f5 connected 2022-06-08 00:00:09.415 - [32minfo[39m: meross.0 (27629) Device: 1809014572480225180534298f166ab5 connected 2022-06-08 00:00:09.417 - [32minfo[39m: meross.0 (27629) Device: 1810224092789329085334298f16f18d connected 2022-06-08 00:00:09.418 - [32minfo[39m: meross.0 (27629) Device: 1811305787614825182134298f187da6 connected 2022-06-08 00:00:09.419 - [32minfo[39m: meross.0 (27629) Device: 1810221956507129085334298f16f380 connected 2022-06-08 00:00:09.421 - [32minfo[39m: meross.0 (27629) Device: 1809012709631425180534298f16660a connected 2022-06-08 00:00:09.422 - [32minfo[39m: meross.0 (27629) Device: 1809017394109425180534298f166544 connected 2022-06-08 00:00:09.424 - [32minfo[39m: meross.0 (27629) Device: 1809014813536325180534298f166a87 connected 2022-06-08 00:00:09.425 - [32minfo[39m: meross.0 (27629) Device: 1809013215340225180534298f166a51 connected 2022-06-08 00:00:09.426 - [32minfo[39m: meross.0 (27629) Device: 1811301259073025182134298f187dd9 connected 2022-06-08 00:00:09.428 - [32minfo[39m: meross.0 (27629) Device: 1811302076928625182134298f188306 connected 2022-06-08 00:00:09.429 - [32minfo[39m: meross.0 (27629) Device: 1811306089340925182134298f187b61 connected 2022-06-08 00:00:09.431 - [32minfo[39m: meross.0 (27629) Device: 1811303935030425182134298f187dde connected 2022-06-08 00:00:09.432 - [32minfo[39m: meross.0 (27629) Device: 1811304781456425182134298f1882c8 connected 2022-06-08 00:00:16.414 - [32minfo[39m: meross.0 (27629) Devices initialized 2022-06-08 00:00:23.981 - [32minfo[39m: javascript.0 (448) script.js.common.Sonstige.#Sonnenzeiten: neue Tagezeit: Abend 2022-06-08 00:01:00.026 - [32minfo[39m: meross.0 (27629) Scheduled restart. 2022-06-08 00:01:00.029 - [32minfo[39m: javascript.0 (448) script.js.common.Heizung.WC_E-Heizung: getState(id=#Eigene.0.Heizung.Heizen_WC, timerId=[object Object]) => {"val":false,"ack":true,"ts":1654635661286,"q":0,"c":"script.js.common.Heizung.WC_E-Heizung","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1654624861280} 2022-06-08 00:01:00.030 - [32minfo[39m: javascript.0 (448) script.js.common.Heizung.WC_E-Heizung: setForeignState(id=#Eigene.0.WC.SollTempWC, state={"val":18,"ack":true,"c":"script.js.common.Heizung.WC_E-Heizung"}) 2022-06-08 00:01:00.042 - [32minfo[39m: meross.0 (27629) Device: 19011898369667251h0434298f1a6462 closed: null 2022-06-08 00:01:00.044 - [32minfo[39m: meross.0 (27629) Device: 1811305641257125182134298f187fdd closed: null 2022-06-08 00:01:00.045 - [32minfo[39m: meross.0 (27629) Device: 18122163520756258h0334298f144240 closed: null 2022-06-08 00:01:00.045 - [32minfo[39m: meross.0 (27629) Device: 21020338573116251h6148e1e94abdc7 closed: null 2022-06-08 00:01:00.048 - [32minfo[39m: meross.0 (27629) Device: 21020300990383251h6148e1e94acdf8 closed: null 2022-06-08 00:01:00.049 - [32minfo[39m: meross.0 (27629) Device: 2001192419504425188548e1e9171db0 closed: null 2022-06-08 00:01:00.050 - [32minfo[39m: meross.0 (27629) Device: 1809016208959425180534298f1665ca closed: null 2022-06-08 00:01:00.051 - [32minfo[39m: meross.0 (27629) Device: 19011820035814251h0334298f1a0745 closed: null 2022-06-08 00:01:00.052 - [32minfo[39m: meross.0 (27629) Device: 19011818986476251h0434298f1a5b94 closed: null 2022-06-08 00:01:00.053 - [32minfo[39m: meross.0 (27629) Device: 2001191193736125188548e1e9171e9a closed: null 2022-06-08 00:01:00.053 - [32minfo[39m: meross.0 (27629) Device: 2001194310463525188548e1e9172324 closed: null 2022-06-08 00:01:00.054 - [32minfo[39m: meross.0 (27629) Device: 2001192823402125188548e1e9172387 closed: null 2022-06-08 00:01:00.055 - [32minfo[39m: meross.0 (27629) Device: 1812178320463025182834298f19ca1c closed: null 2022-06-08 00:01:00.056 - [32minfo[39m: meross.0 (27629) Device: 19011832535820251h0334298f1a090a closed: null 2022-06-08 00:01:00.057 - [32minfo[39m: meross.0 (27629) Device: 1809015737278325180534298f16671f closed: null 2022-06-08 00:01:00.057 - [32minfo[39m: meross.0 (27629) Device: 1809010653847025180534298f16668c closed: null 2022-06-08 00:01:00.058 - [32minfo[39m: meross.0 (27629) Device: 19011849037183251h0434298f1a5d0d closed: null 2022-06-08 00:01:00.059 - [32minfo[39m: meross.0 (27629) Device: 19011863874770251h0434298f1a5666 closed: null 2022-06-08 00:01:00.059 - [32minfo[39m: meross.0 (27629) Device: 1812174950278625182834298f19c365 closed: null 2022-06-08 00:01:00.060 - [32minfo[39m: meross.0 (27629) Device: 19011873123850251h0334298f1a09a6 closed: null 2022-06-08 00:01:00.061 - [32minfo[39m: meross.0 (27629) Device: 1812179492140325182834298f19d01f closed: null 2022-06-08 00:01:00.061 - [32minfo[39m: meross.0 (27629) Device: 19011882830659251h0334298f1a0625 closed: null 2022-06-08 00:01:00.062 - [32minfo[39m: meross.0 (27629) Device: 1811301845905925182134298f1880f5 closed: null 2022-06-08 00:01:00.063 - [32minfo[39m: meross.0 (27629) Device: 1809014572480225180534298f166ab5 closed: null 2022-06-08 00:01:00.070 - [32minfo[39m: meross.0 (27629) Device: 1810224092789329085334298f16f18d closed: null 2022-06-08 00:01:00.070 - [32minfo[39m: meross.0 (27629) Device: 1811305787614825182134298f187da6 closed: null 2022-06-08 00:01:00.071 - [32minfo[39m: meross.0 (27629) Device: 1810221956507129085334298f16f380 closed: null 2022-06-08 00:01:00.072 - [32minfo[39m: meross.0 (27629) Device: 1809012709631425180534298f16660a closed: null 2022-06-08 00:01:00.073 - [32minfo[39m: meross.0 (27629) Device: 1809017394109425180534298f166544 closed: null 2022-06-08 00:01:00.073 - [32minfo[39m: meross.0 (27629) Device: 1809014813536325180534298f166a87 closed: null 2022-06-08 00:01:00.074 - [32minfo[39m: meross.0 (27629) Device: 1809013215340225180534298f166a51 closed: null 2022-06-08 00:01:00.075 - [32minfo[39m: meross.0 (27629) Device: 1811301259073025182134298f187dd9 closed: null 2022-06-08 00:01:00.076 - [32minfo[39m: meross.0 (27629) Device: 1811302076928625182134298f188306 closed: null 2022-06-08 00:01:00.076 - [32minfo[39m: meross.0 (27629) Device: 1811306089340925182134298f187b61 closed: null 2022-06-08 00:01:00.077 - [32minfo[39m: meross.0 (27629) Device: 1811303935030425182134298f187dde closed: null 2022-06-08 00:01:00.077 - [32minfo[39m: meross.0 (27629) Device: 1811304781456425182134298f1882c8 closed: null 2022-06-08 00:01:01.299 - [32minfo[39m: javascript.0 (448) script.js.common.Heizung.WC_E-Heizung: setForeignState(id=#Eigene.0.Heizung.Heizen_WC, state={"val":false,"ack":true,"c":"script.js.common.Heizung.WC_E-Heizung"}) 2022-06-08 00:01:03.342 - [32minfo[39m: meross.0 (27629) terminating 2022-06-08 00:01:03.345 - [32minfo[39m: meross.0 (27629) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2022-06-08 00:01:03.992 - [32minfo[39m: host.RDJLHome instance system.adapter.meross.0 scheduled normal terminated and will be restarted on schedule. 2022-06-08 00:01:03.993 - [32minfo[39m: host.RDJLHome Restart adapter system.adapter.meross.0 because enabled 2022-06-08 00:01:05.122 - [32minfo[39m: host.RDJLHome instance system.adapter.meross.0 started with pid 29105 2022-06-08 00:01:05.824 - [32minfo[39m: web.0 (12288) <== Disconnect system.user.admin from ::ffff:192.168.0.103 vis.0 2022-06-08 00:01:07.955 - [32minfo[39m: meross.0 (29105) starting. Version 1.10.5 (non-npm: Apollon77/ioBroker.meross#ae71235c96c0beedf83869967a87b881c9e7e152) in /opt/iobroker/node_modules/iobroker.meross, node: v12.22.1, js-controller: 4.0.21 2022-06-08 00:01:09.101 - [32minfo[39m: meross.0 (29105) Device 19011898369667251h0434298f1a6462 initialized 2022-06-08 00:01:09.216 - [32minfo[39m: meross.0 (29105) Device 1811305641257125182134298f187fdd initialized 2022-06-08 00:01:09.217 - [32minfo[39m: meross.0 (29105) Device 18122163520756258h0334298f144240 initialized 2022-06-08 00:01:09.218 - [32minfo[39m: meross.0 (29105) Device 21020338573116251h6148e1e94abdc7 initialized 2022-06-08 00:01:09.219 - [32minfo[39m: meross.0 (29105) Device 21020300990383251h6148e1e94acdf8 initialized 2022-06-08 00:01:09.220 - [32minfo[39m: meross.0 (29105) Device 2001192419504425188548e1e9171db0 initialized 2022-06-08 00:01:09.221 - [32minfo[39m: meross.0 (29105) Device 1809016208959425180534298f1665ca initialized 2022-06-08 00:01:09.223 - [32minfo[39m: meross.0 (29105) Device 19011820035814251h0334298f1a0745 initialized 2022-06-08 00:01:09.224 - [32minfo[39m: meross.0 (29105) Device 19011818986476251h0434298f1a5b94 initialized 2022-06-08 00:01:09.225 - [32minfo[39m: meross.0 (29105) Device 2001191193736125188548e1e9171e9a initialized 2022-06-08 00:01:09.227 - [32minfo[39m: meross.0 (29105) Device 2001194310463525188548e1e9172324 initialized 2022-06-08 00:01:09.228 - [32minfo[39m: meross.0 (29105) Device 2001192823402125188548e1e9172387 initialized 2022-06-08 00:01:09.230 - [32minfo[39m: meross.0 (29105) Device 1812178320463025182834298f19ca1c initialized 2022-06-08 00:01:09.231 - [32minfo[39m: meross.0 (29105) Device 19011832535820251h0334298f1a090a initialized 2022-06-08 00:01:09.233 - [32minfo[39m: meross.0 (29105) Device 1809015737278325180534298f16671f initialized 2022-06-08 00:01:09.235 - [32minfo[39m: meross.0 (29105) Device 1809010653847025180534298f16668c initialized 2022-06-08 00:01:09.236 - [32minfo[39m: meross.0 (29105) Device 19011849037183251h0434298f1a5d0d initialized 2022-06-08 00:01:09.237 - [32minfo[39m: meross.0 (29105) Device 19011863874770251h0434298f1a5666 initialized 2022-06-08 00:01:09.238 - [32minfo[39m: meross.0 (29105) Device 1812174950278625182834298f19c365 initialized 2022-06-08 00:01:09.239 - [32minfo[39m: meross.0 (29105) Device 19011873123850251h0334298f1a09a6 initialized 2022-06-08 00:01:09.240 - [32minfo[39m: meross.0 (29105) Device 1812179492140325182834298f19d01f initialized 2022-06-08 00:01:09.240 - [32minfo[39m: meross.0 (29105) Device 19011882830659251h0334298f1a0625 initialized 2022-06-08 00:01:09.241 - [32minfo[39m: meross.0 (29105) Device 1811301845905925182134298f1880f5 initialized 2022-06-08 00:01:09.242 - [32minfo[39m: meross.0 (29105) Device 1809014572480225180534298f166ab5 initialized 2022-06-08 00:01:09.243 - [32minfo[39m: meross.0 (29105) Device 1810224092789329085334298f16f18d initialized 2022-06-08 00:01:09.244 - [32minfo[39m: meross.0 (29105) Device 1811305787614825182134298f187da6 initialized 2022-06-08 00:01:09.245 - [32minfo[39m: meross.0 (29105) Device 1810221956507129085334298f16f380 initialized 2022-06-08 00:01:09.246 - [32minfo[39m: meross.0 (29105) Device 1809012709631425180534298f16660a initialized 2022-06-08 00:01:09.246 - [32minfo[39m: meross.0 (29105) Device 1809017394109425180534298f166544 initialized 2022-06-08 00:01:09.247 - [32minfo[39m: meross.0 (29105) Device 1809014813536325180534298f166a87 initialized 2022-06-08 00:01:09.248 - [32minfo[39m: meross.0 (29105) Device 1809013215340225180534298f166a51 initialized 2022-06-08 00:01:09.249 - [32minfo[39m: meross.0 (29105) Device 1811301259073025182134298f187dd9 initialized 2022-06-08 00:01:09.250 - [32minfo[39m: meross.0 (29105) Device 1811302076928625182134298f188306 initialized 2022-06-08 00:01:09.250 - [32minfo[39m: meross.0 (29105) Device 1811306089340925182134298f187b61 initialized 2022-06-08 00:01:09.251 - [32minfo[39m: meross.0 (29105) Device 1811303935030425182134298f187dde initialized 2022-06-08 00:01:09.252 - [32minfo[39m: meross.0 (29105) Device 1811304781456425182134298f1882c8 initialized 2022-06-08 00:01:09.481 - [32minfo[39m: meross.0 (29105) Device: 19011898369667251h0434298f1a6462 connected 2022-06-08 00:01:09.484 - [32minfo[39m: meross.0 (29105) Device: 1811305641257125182134298f187fdd connected 2022-06-08 00:01:09.485 - [32minfo[39m: meross.0 (29105) Device: 18122163520756258h0334298f144240 connected 2022-06-08 00:01:09.487 - [32minfo[39m: meross.0 (29105) Device: 21020338573116251h6148e1e94abdc7 connected 2022-06-08 00:01:09.489 - [32minfo[39m: meross.0 (29105) Device: 21020300990383251h6148e1e94acdf8 connected 2022-06-08 00:01:09.490 - [32minfo[39m: meross.0 (29105) Device: 2001192419504425188548e1e9171db0 connected 2022-06-08 00:01:09.492 - [32minfo[39m: meross.0 (29105) Device: 1809016208959425180534298f1665ca connected 2022-06-08 00:01:09.493 - [32minfo[39m: meross.0 (29105) Device: 19011820035814251h0334298f1a0745 connected 2022-06-08 00:01:09.495 - [32minfo[39m: meross.0 (29105) Device: 19011818986476251h0434298f1a5b94 connected 2022-06-08 00:01:09.496 - [32minfo[39m: meross.0 (29105) Device: 2001191193736125188548e1e9171e9a connected 2022-06-08 00:01:09.498 - [32minfo[39m: meross.0 (29105) Device: 2001194310463525188548e1e9172324 connected 2022-06-08 00:01:09.499 - [32minfo[39m: meross.0 (29105) Device: 2001192823402125188548e1e9172387 connected 2022-06-08 00:01:09.500 - [32minfo[39m: meross.0 (29105) Device: 1812178320463025182834298f19ca1c connected 2022-06-08 00:01:09.502 - [32minfo[39m: meross.0 (29105) Device: 19011832535820251h0334298f1a090a connected 2022-06-08 00:01:09.503 - [32minfo[39m: meross.0 (29105) Device: 1809015737278325180534298f16671f connected 2022-06-08 00:01:09.504 - [32minfo[39m: meross.0 (29105) Device: 1809010653847025180534298f16668c connected 2022-06-08 00:01:09.506 - [32minfo[39m: meross.0 (29105) Device: 19011849037183251h0434298f1a5d0d connected 2022-06-08 00:01:09.507 - [32minfo[39m: meross.0 (29105) Device: 19011863874770251h0434298f1a5666 connected 2022-06-08 00:01:09.509 - [32minfo[39m: meross.0 (29105) Device: 1812174950278625182834298f19c365 connected 2022-06-08 00:01:09.510 - [32minfo[39m: meross.0 (29105) Device: 19011873123850251h0334298f1a09a6 connected 2022-06-08 00:01:09.511 - [32minfo[39m: meross.0 (29105) Device: 1812179492140325182834298f19d01f connected 2022-06-08 00:01:09.513 - [32minfo[39m: meross.0 (29105) Device: 19011882830659251h0334298f1a0625 connected 2022-06-08 00:01:09.514 - [32minfo[39m: meross.0 (29105) Device: 1811301845905925182134298f1880f5 connected 2022-06-08 00:01:09.516 - [32minfo[39m: meross.0 (29105) Device: 1809014572480225180534298f166ab5 connected 2022-06-08 00:01:09.517 - [32minfo[39m: meross.0 (29105) Device: 1810224092789329085334298f16f18d connected 2022-06-08 00:01:09.518 - [32minfo[39m: meross.0 (29105) Device: 1811305787614825182134298f187da6 connected 2022-06-08 00:01:09.520 - [32minfo[39m: meross.0 (29105) Device: 1810221956507129085334298f16f380 connected 2022-06-08 00:01:09.521 - [32minfo[39m: meross.0 (29105) Device: 1809012709631425180534298f16660a connected 2022-06-08 00:01:09.522 - [32minfo[39m: meross.0 (29105) Device: 1809017394109425180534298f166544 connected 2022-06-08 00:01:09.524 - [32minfo[39m: meross.0 (29105) Device: 1809014813536325180534298f166a87 connected 2022-06-08 00:01:09.525 - [32minfo[39m: meross.0 (29105) Device: 1809013215340225180534298f166a51 connected 2022-06-08 00:01:09.527 - [32minfo[39m: meross.0 (29105) Device: 1811301259073025182134298f187dd9 connected 2022-06-08 00:01:09.528 - [32minfo[39m: meross.0 (29105) Device: 1811302076928625182134298f188306 connected 2022-06-08 00:01:09.529 - [32minfo[39m: meross.0 (29105) Device: 1811306089340925182134298f187b61 connected 2022-06-08 00:01:09.531 - [32minfo[39m: meross.0 (29105) Device: 1811303935030425182134298f187dde connected 2022-06-08 00:01:09.532 - [32minfo[39m: meross.0 (29105) Device: 1811304781456425182134298f1882c8 connected 2022-06-08 00:01:11.147 - [32minfo[39m: web.0 (12288) <== Disconnect system.user.admin from ::ffff:192.168.0.103 vis.0 2022-06-08 00:01:11.973 - [32minfo[39m: meross.0 (29105) Devices initialized 2022-06-08 00:02:00.020 - [32minfo[39m: meross.0 (29105) Scheduled restart. 2022-06-08 00:02:00.038 - [32minfo[39m: meross.0 (29105) Device: 19011898369667251h0434298f1a6462 closed: null 2022-06-08 00:02:00.039 - [32minfo[39m: meross.0 (29105) Device: 1811305641257125182134298f187fdd closed: null 2022-06-08 00:02:00.044 - [32minfo[39m: meross.0 (29105) Device: 18122163520756258h0334298f144240 closed: null 2022-06-08 00:02:00.047 - [32minfo[39m: meross.0 (29105) Device: 21020338573116251h6148e1e94abdc7 closed: null 2022-06-08 00:02:00.048 - [32minfo[39m: meross.0 (29105) Device: 21020300990383251h6148e1e94acdf8 closed: null 2022-06-08 00:02:00.049 - [32minfo[39m: meross.0 (29105) Device: 2001192419504425188548e1e9171db0 closed: null 2022-06-08 00:02:00.051 - [32minfo[39m: meross.0 (29105) Device: 1809016208959425180534298f1665ca closed: null 2022-06-08 00:02:00.051 - [32minfo[39m: meross.0 (29105) Device: 19011820035814251h0334298f1a0745 closed: null 2022-06-08 00:02:00.053 - [32minfo[39m: meross.0 (29105) Device: 19011818986476251h0434298f1a5b94 closed: null 2022-06-08 00:02:00.053 - [32minfo[39m: meross.0 (29105) Device: 2001191193736125188548e1e9171e9a closed: null 2022-06-08 00:02:00.055 - [32minfo[39m: meross.0 (29105) Device: 2001194310463525188548e1e9172324 closed: null 2022-06-08 00:02:00.056 - [32minfo[39m: meross.0 (29105) Device: 2001192823402125188548e1e9172387 closed: null 2022-06-08 00:02:00.057 - [32minfo[39m: meross.0 (29105) Device: 1812178320463025182834298f19ca1c closed: null 2022-06-08 00:02:00.058 - [32minfo[39m: meross.0 (29105) Device: 19011832535820251h0334298f1a090a closed: null 2022-06-08 00:02:00.059 - [32minfo[39m: meross.0 (29105) Device: 1809015737278325180534298f16671f closed: null 2022-06-08 00:02:00.060 - [32minfo[39m: meross.0 (29105) Device: 1809010653847025180534298f16668c closed: null 2022-06-08 00:02:00.061 - [32minfo[39m: meross.0 (29105) Device: 19011849037183251h0434298f1a5d0d closed: null 2022-06-08 00:02:00.062 - [32minfo[39m: meross.0 (29105) Device: 19011863874770251h0434298f1a5666 closed: null 2022-06-08 00:02:00.063 - [32minfo[39m: meross.0 (29105) Device: 1812174950278625182834298f19c365 closed: null 2022-06-08 00:02:00.064 - [32minfo[39m: meross.0 (29105) Device: 19011873123850251h0334298f1a09a6 closed: null 2022-06-08 00:02:00.065 - [32minfo[39m: meross.0 (29105) Device: 1812179492140325182834298f19d01f closed: null 2022-06-08 00:02:00.066 - [32minfo[39m: meross.0 (29105) Device: 19011882830659251h0334298f1a0625 closed: null 2022-06-08 00:02:00.067 - [32minfo[39m: meross.0 (29105) Device: 1811301845905925182134298f1880f5 closed: null 2022-06-08 00:02:00.068 - [32minfo[39m: meross.0 (29105) Device: 1809014572480225180534298f166ab5 closed: null 2022-06-08 00:02:00.069 - [32minfo[39m: meross.0 (29105) Device: 1810224092789329085334298f16f18d closed: null 2022-06-08 00:02:00.070 - [32minfo[39m: meross.0 (29105) Device: 1811305787614825182134298f187da6 closed: null 2022-06-08 00:02:00.071 - [32minfo[39m: meross.0 (29105) Device: 1810221956507129085334298f16f380 closed: null 2022-06-08 00:02:00.072 - [32minfo[39m: meross.0 (29105) Device: 1809012709631425180534298f16660a closed: null 2022-06-08 00:02:00.073 - [32minfo[39m: meross.0 (29105) Device: 1809017394109425180534298f166544 closed: null 2022-06-08 00:02:00.074 - [32minfo[39m: meross.0 (29105) Device: 1809014813536325180534298f166a87 closed: null 2022-06-08 00:02:00.075 - [32minfo[39m: meross.0 (29105) Device: 1809013215340225180534298f166a51 closed: null 2022-06-08 00:02:00.076 - [32minfo[39m: meross.0 (29105) Device: 1811301259073025182134298f187dd9 closed: null 2022-06-08 00:02:00.077 - [32minfo[39m: meross.0 (29105) Device: 1811302076928625182134298f188306 closed: null 2022-06-08 00:02:00.078 - [32minfo[39m: meross.0 (29105) Device: 1811306089340925182134298f187b61 closed: null 2022-06-08 00:02:00.079 - [32minfo[39m: meross.0 (29105) Device: 1811303935030425182134298f187dde closed: null 2022-06-08 00:02:00.080 - [32minfo[39m: meross.0 (29105) Device: 1811304781456425182134298f1882c8 closed: null 2022-06-08 00:02:00.138 - [32minfo[39m: javascript.0 (448) script.js.common.Heizung.WC_E-Heizung: getState(id=#Eigene.0.Heizung.Heizen_WC, timerId=undefined) => {"val":false,"ack":true,"ts":1654639261303,"q":0,"c":"script.js.common.Heizung.WC_E-Heizung","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1654624861280} 2022-06-08 00:02:00.139 - [32minfo[39m: javascript.0 (448) script.js.common.Heizung.WC_E-Heizung: setForeignState(id=#Eigene.0.WC.SollTempWC, state={"val":18,"ack":true,"c":"script.js.common.Heizung.WC_E-Heizung"}) 2022-06-08 00:02:03.349 - [32minfo[39m: meross.0 (29105) terminating 2022-06-08 00:02:03.351 - [32minfo[39m: meross.0 (29105) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2022-06-08 00:02:03.965 - [32minfo[39m: host.RDJLHome instance system.adapter.meross.0 scheduled normal terminated and will be restarted on schedule. 2022-06-08 00:02:03.967 - [32minfo[39m: host.RDJLHome Restart adapter system.adapter.meross.0 because enabled 2022-06-08 00:02:05.090 - [32minfo[39m: host.RDJLHome instance system.adapter.meross.0 started with pid 30408 2022-06-08 00:02:07.933 - [32minfo[39m: meross.0 (30408) starting. Version 1.10.5 (non-npm: Apollon77/ioBroker.meross#ae71235c96c0beedf83869967a87b881c9e7e152) in /opt/iobroker/node_modules/iobroker.meross, node: v12.22.1, js-controller: 4.0.21 -
@myzerat sagte in Meross nur noch unidirektional:
2022-06-08 00:02:00.020 - [32minfo[39m: meross.0 (29105) Scheduled restart.
Hm .. neee Du hast ein anderes Problem ... Du hast scheinbar einen minütliche Restart-Schedule im Admin gesetzt und genau das wird getan. Falls Du es nur täglich wolltest idt der cCron String falsch
-
-
@myzerat Aber irgendwo isser ... dann Admin - expertenmodus - Objekte und schau mal das JSON des system.adapter.meross.0 Objetcs an was da in common.restartSchedule steht. Oder klick im Admin mal auf den Restart Schedule und schau was drin steht
-
@apollon77 sagte in Meross nur noch unidirektional:
system.adapter.meross.0
hmmm, ich finde die datei system.adapter.meross.0 Objetcs nicht, die sollte ja hier am ende der Objekte sein
-
@myzerat Such oben den ordner system und dann aufklappen
-
den Ordner System, habe ich eh gefunden, aber nach was suche ich darin? habe mir den Ordner Meross angesehen, seh da aber nichts mit schedule?
nach was muss ich suchen?!
-
@myzerat auf das Objekt mit der 0 unterhalb von Meros bitte klicken und dann auf den Stift rechts in genau der Zeile
In der Zeile wo "instance" als Typ steht
-
ja habe ich
{ "_id": "system.adapter.meross.0", "type": "instance", "common": { "name": "meross", "version": "1.11.0", "news": { "1.0.0": { "en": "Added mss310 devices and electricity value handling including polling interval", "de": "Mss310-Geräte und Stromwertverarbeitung einschließlich Abfrageintervall hinzugefügt", "ru": "Добавлены устройства mss310 и обработка стоимости электроэнергии, включая интервал опроса", "pt": "Adicionado dispositivos mss310 e manipulação de valor de eletricidade, incluindo intervalo de pesquisa", "nl": "Mss310-apparaten en afhandeling van elektriciteitswaarde toegevoegd, inclusief polling-interval", "fr": "Ajout de périphériques mss310 et de la gestion de la valeur électrique, y compris l'intervalle d'interrogation", "it": "Aggiunti dispositivi mss310 e gestione del valore dell'elettricità compreso l'intervallo di polling", "es": "Se agregaron dispositivos mss310 y manejo del valor de la electricidad, incluido el intervalo de sondeo", "pl": "Dodano urządzenia mss310 i obsługę wartości elektrycznej, w tym interwał sondowania" }, "0.1.0": { "en": "Initial release", "de": "Erstveröffentlichung", "ru": "Первый выпуск", "pt": "lançamento inicial", "nl": "Eerste uitgave", "fr": "Première version", "it": "Versione iniziale", "es": "Versión inicial", "pl": "Pierwsze wydanie" }, "1.3.7": { "en": "some error cases are handled better", "de": "Einige Fehlerfälle werden besser behandelt", "ru": "некоторые ошибки обрабатываются лучше", "pt": "alguns casos de erro são tratados melhor", "nl": "sommige foutgevallen worden beter afgehandeld", "fr": "certains cas d'erreur sont mieux gérés", "it": "alcuni casi di errore sono gestiti meglio", "es": "algunos casos de error se manejan mejor", "pl": "niektóre przypadki błędów są obsługiwane lepiej", "zh-cn": "一些错误情况得到更好的处理" }, "1.3.6": { "en": "some error cases are handled better", "de": "Einige Fehlerfälle werden besser behandelt", "ru": "некоторые ошибки обрабатываются лучше", "pt": "alguns casos de erro são tratados melhor", "nl": "sommige foutgevallen worden beter afgehandeld", "fr": "certains cas d'erreur sont mieux gérés", "it": "alcuni casi di errore sono gestiti meglio", "es": "algunos casos de error se manejan mejor", "pl": "niektóre przypadki błędów są obsługiwane lepiej", "zh-cn": "一些错误情况得到更好的处理" }, "1.3.5": { "en": "some error cases are handled better", "de": "Einige Fehlerfälle werden besser behandelt", "ru": "некоторые ошибки обрабатываются лучше", "pt": "alguns casos de erro são tratados melhor", "nl": "sommige foutgevallen worden beter afgehandeld", "fr": "certains cas d'erreur sont mieux gérés", "it": "alcuni casi di errore sono gestiti meglio", "es": "algunos casos de error se manejan mejor", "pl": "niektóre przypadki błędów są obsługiwane lepiej", "zh-cn": "一些错误情况得到更好的处理" }, "1.3.4": { "en": "names for hub sub devices added", "de": "Namen für Hub-Sub-Geräte hinzugefügt", "ru": "добавлены имена для вспомогательных устройств-концентраторов", "pt": "nomes para sub-dispositivos de hub adicionados", "nl": "namen voor hub-subapparaten toegevoegd", "fr": "noms des sous-concentrateurs ajoutés", "it": "nomi per i dispositivi secondari hub aggiunti", "es": "nombres para dispositivos secundarios de concentrador agregados", "pl": "dodano nazwy urządzeń podrzędnych koncentratora", "zh-cn": "集线器子设备的名称已添加" }, "1.3.0": { "en": "New devices and compact mode added, see README.md for details", "de": "Neue Geräte und Kompaktmodus hinzugefügt. Weitere Informationen finden Sie in README.md", "ru": "Добавлены новые устройства и компактный режим, подробнее см. README.md", "pt": "Novos dispositivos e modo compacto adicionados, consulte README.md para obter detalhes", "nl": "Nieuwe apparaten en compacte modus toegevoegd, zie README.md voor details", "fr": "Nouveaux appareils et mode compact ajouté, voir README.md pour plus de détails", "it": "Nuovi dispositivi e modalità compatta aggiunti, vedere README.md per i dettagli", "es": "Nuevos dispositivos y modo compacto agregados, vea README.md para más detalles", "pl": "Dodano nowe urządzenia i tryb kompaktowy, zobacz README.md, aby uzyskać szczegółowe informacje", "zh-cn": "添加了新设备和紧凑模式，有关详细信息，请参见README.md" }, "1.0.1": { "en": "Added mss310 devices and electricity value handling including polling interval", "de": "Mss310-Geräte und Stromwertverarbeitung einschließlich Abfrageintervall hinzugefügt", "ru": "Добавлены устройства mss310 и обработка стоимости электроэнергии, включая интервал опроса", "pt": "Adicionado dispositivos mss310 e manipulação de valor de eletricidade, incluindo intervalo de pesquisa", "nl": "Mss310-apparaten en afhandeling van elektriciteitswaarde toegevoegd, inclusief polling-interval", "fr": "Ajout de périphériques mss310 et de la gestion de la valeur électrique, y compris l'intervalle d'interrogation", "it": "Aggiunti dispositivi mss310 e gestione del valore dell'elettricità compreso l'intervallo di polling", "es": "Se agregaron dispositivos mss310 y manejo del valor de la electricidad, incluido el intervalo de sondeo", "pl": "Dodano urządzenia mss310 i obsługę wartości elektrycznej, w tym interwał sondowania" }, "1.3.8": { "en": "update dependecies", "de": "Abhängigkeiten aktualisiert", "ru": "обновить зависимости", "pt": "atualizar dependências", "nl": "update afhankelijkheden", "fr": "mettre à jour les dépendances", "it": "aggiorna le dipendenze", "es": "actualizar dependencias", "pl": "aktualizować zależności", "zh-cn": "更新依赖" }, "1.3.11": { "en": "fixes and optimizations. Switched to iobroker own Sentry instance for reporting of crashes", "de": "Korrekturen und Optimierungen. Zur Meldung von Abstürzen auf die iobroker-eigene Sentry-Instanz umgestellt", "ru": "исправления и оптимизации. Переключен на собственный экземпляр Sentry iobroker для сообщения о сбоях", "pt": "correções e otimizações. Mudou para a instância Sentry do iobroker para relatar falhas", "nl": "fixes en optimalisaties. Overgeschakeld naar iobroker eigen Sentry-instantie voor het melden van crashes", "fr": "corrections et optimisations. Passé à l'instance Sentry d'iobroker pour le signalement des plantages", "it": "correzioni e ottimizzazioni. Passato alla propria istanza Sentry di iobroker per la segnalazione di arresti anomali", "es": "correcciones y optimizaciones. Se cambió a la instancia de Sentry propia de iobroker para informar sobre bloqueos", "pl": "poprawki i optymalizacje. Przełączono na własną instancję Sentry iobroker w celu zgłaszania awarii", "zh-cn": "修复和优化。切换到iobroker自己的Sentry实例以报告崩溃" }, "1.3.9": { "en": "some error cases are handled better", "de": "Einige Fehlerfälle werden besser behandelt", "ru": "некоторые ошибки обрабатываются лучше", "pt": "alguns casos de erro são tratados melhor", "nl": "sommige foutgevallen worden beter afgehandeld", "fr": "certains cas d'erreur sont mieux gérés", "it": "alcuni casi di errore sono gestiti meglio", "es": "algunos casos de error se manejan mejor", "pl": "niektóre przypadki błędów są obsługiwane lepiej", "zh-cn": "一些错误情况得到更好的处理" }, "1.5.1": { "en": "generate an unique uuid for each connection, fixes the \"Server not available\"", "de": "Generieren Sie eine eindeutige UUID für jede Verbindung, behebt den \"Server nicht verfügbar\"", "ru": "генерировать уникальный uuid для каждого подключения, исправляет \"Сервер недоступен\"", "pt": "gerar um uuid exclusivo para cada conexão, corrige o \"Servidor não disponível\"", "nl": "genereer een unieke uuid voor elke verbinding, repareert de \"Server niet beschikbaar\"", "fr": "générer un uuid unique pour chaque connexion, corrige le \"Serveur non disponible\"", "it": "genera un uuid univoco per ogni connessione, corregge il \"Server non disponibile\"", "es": "genera un uuid único para cada conexión, corrige el \"Servidor no disponible\"", "pl": "wygeneruje unikalny identyfikator użytkownika dla każdego połączenia, naprawia błąd „Serwer niedostępny”", "zh-cn": "为每个连接生成唯一的uuid，修复“服务器不可用”" }, "1.5.0": { "en": "Prevent crash cases (Sentry IOBROKER-MEROSS-G, IOBROKER-MEROSS-F)\nAdd warning about poll interval and cloud deactivation and reset poll interval to 30s for now", "de": "Verhindern Sie Absturzfälle (Sentry IOBROKER-MEROSS-G, IOBROKER-MEROSS-F)\nFügen Sie eine Warnung zum Abfrageintervall und zur Deaktivierung der Cloud hinzu und setzen Sie das Abfrageintervall vorerst auf 30 Sekunden zurück", "ru": "Предотвращение аварийных ситуаций (Sentry IOBROKER-MEROSS-G, IOBROKER-MEROSS-F)\nДобавить предупреждение об интервале опроса и облачной деактивации и сбросить интервал опроса до 30 с.", "pt": "Evitar casos de falha (Sentry IOBROKER-MEROSS-G, IOBROKER-MEROSS-F)\nAdicione um aviso sobre o intervalo de pesquisa e desativação da nuvem e redefina o intervalo de pesquisa para 30s por enquanto", "nl": "Voorkom crashgevallen (Sentry IOBROKER-MEROSS-G, IOBROKER-MEROSS-F)\nVoeg een waarschuwing toe over het pollinterval en de deactivering van de cloud en reset het pollinterval voorlopig naar 30 seconden", "fr": "Prévenir les cas de crash (Sentry IOBROKER-MEROSS-G, IOBROKER-MEROSS-F)\nAjouter un avertissement sur l'intervalle d'interrogation et la désactivation du cloud et réinitialiser l'intervalle d'interrogation à 30 secondes pour l'instant", "it": "Prevenire i casi di crash (Sentry IOBROKER-MEROSS-G, IOBROKER-MEROSS-F)\nAggiungi un avviso sull'intervallo di polling e la disattivazione del cloud e reimposta l'intervallo di poll su 30s per ora", "es": "Prevención de casos de bloqueo (Sentry IOBROKER-MEROSS-G, IOBROKER-MEROSS-F)\nAgregue advertencia sobre el intervalo de sondeo y la desactivación de la nube y restablezca el intervalo de sondeo a 30 segundos por ahora", "pl": "Zapobiegaj awariom (Sentry IOBROKER-MEROSS-G, IOBROKER-MEROSS-F)\nDodaj ostrzeżenie o interwale odpytywania i dezaktywacji chmury i na razie zresetuj interwał odpytywania do 30s", "zh-cn": "防止发生崩溃情况（哨兵IOBROKER-MEROSS-G，IOBROKER-MEROSS-F）\n添加有关轮询间隔和云停用的警告，并将轮询间隔暂时重置为30s" }, "1.4.1": { "en": "Fix Admin finally", "de": "Fix Admin endlich", "ru": "Исправить Admin наконец", "pt": "Corrigir Admin finalmente", "nl": "Fix Admin eindelijk", "fr": "Fix Admin enfin", "it": "Risolto il problema con Admin", "es": "Fix Admin finalmente", "pl": "Napraw administratora w końcu", "zh-cn": "最终修复管理员" }, "1.4.0": { "en": "Fix Admin\nRemove the automatic cutting of passwords to 15 characters, but log info message", "de": "Fix Admin\nEntfernen Sie das automatische Schneiden von Passwörtern auf 15 Zeichen, protokollieren Sie jedoch die Infomeldung", "ru": "Исправить админ\nУбрать автоматическую обрезку паролей до 15 символов, но записать в лог сообщение", "pt": "Fix Admin\nRemova o corte automático de senhas para 15 caracteres, mas registre a mensagem informativa", "nl": "Beheerder repareren\nVerwijder het automatisch knippen van wachtwoorden tot 15 tekens, maar log infobericht", "fr": "Fix Admin\nSupprimez la découpe automatique des mots de passe à 15 caractères, mais enregistrez le message d'information", "it": "Fix Admin\nRimuovi il taglio automatico delle password a 15 caratteri, ma registra il messaggio informativo", "es": "Fix Admin\nElimine el corte automático de contraseñas a 15 caracteres, pero registre el mensaje de información", "pl": "Napraw administratora\nUsuń automatyczne przycinanie haseł do 15 znaków, ale wiadomość z logami", "zh-cn": "修复管理员\n删除自动切成15个字符的密码，但记录信息消息" }, "1.3.13": { "en": "compatibility for js-controller 3.0 added, dependencies updated and optimizations/fixes", "de": "Kompatibilität für js-controller 3.0 hinzugefügt, Abhängigkeiten aktualisiert und Optimierungen / Korrekturen", "ru": "добавлена совместимость для js-controller 3.0, обновлены зависимости и оптимизированы / исправлены", "pt": "compatibilidade com o js-controller 3.0 adicionada, dependências atualizadas e otimizações / correções", "nl": "compatibiliteit voor js-controller 3.0 toegevoegd, afhankelijkheden bijgewerkt en optimalisaties / fixes", "fr": "compatibilité pour js-controller 3.0 ajoutée, dépendances mises à jour et optimisations / correctifs", "it": "compatibilità per js-controller 3.0 aggiunta, dipendenze aggiornate e ottimizzazioni / correzioni", "es": "compatibilidad para js-controller 3.0 agregado, dependencias actualizadas y optimizaciones / arreglos", "pl": "dodano kompatybilność dla js-kontrolera 3.0, zaktualizowano zależności i optymalizacje / poprawki", "zh-cn": "添加了与js-controller 3.0的兼容性，更新了依赖项以及优化/修复" }, "1.3.12": { "en": "update dependecies", "de": "Abhängigkeiten aktualisiert", "ru": "обновить зависимости", "pt": "atualizar dependências", "nl": "update afhankelijkheden", "fr": "mettre à jour les dépendances", "it": "aggiorna le dipendenze", "es": "actualizar dependencias", "pl": "aktualizować zależności", "zh-cn": "更新依赖" }, "1.6.2": { "en": "optimize for js-controller 3.3", "de": "optimieren für js-controller 3.3", "ru": "оптимизировать под js-controller 3.3", "pt": "otimizar para js-controller 3.3", "nl": "optimaliseren voor js-controller 3.3", "fr": "optimiser pour js-controller 3.3", "it": "ottimizzare per js-controller 3.3", "es": "optimizar para js-controller 3.3", "pl": "optymalizacja dla kontrolera js 3.3", "zh-cn": "针对js-controller 3.3进行优化" }, "1.6.1": { "en": "prevent crash case (Sentry IOBROKER-MEROSS-Z)", "de": "Absturz verhindern (Sentry IOBROKER-MEROSS-Z)", "ru": "случай предотвращения сбоя (Sentry IOBROKER-MEROSS-Z)", "pt": "evitar caso de travamento (Sentry IOBROKER-MEROSS-Z)", "nl": "crashgeval voorkomen (Sentry IOBROKER-MEROSS-Z)", "fr": "éviter les cas de crash (Sentry IOBROKER-MEROSS-Z)", "it": "prevenire crash case (Sentry IOBROKER-MEROSS-Z)", "es": "prevenir caso de choque (Sentry IOBROKER-MEROSS-Z)", "pl": "zapobiegać awariom (Sentry IOBROKER-MEROSS-Z)", "zh-cn": "防止发生崩溃情况（Sentry IOBROKER-MEROSS-Z）" }, "1.6.0": { "en": "add MOD100 Diffuser Spray device", "de": "MOD100 Diffusor Spray Gerät hinzufügen", "ru": "добавить устройство распыления диффузора MOD100", "pt": "adicionar dispositivo difusor de spray MOD100", "nl": "voeg MOD100 Diffuser Spray-apparaat toe", "fr": "ajouter le dispositif de pulvérisation de diffuseur MOD100", "it": "aggiungere il dispositivo di spruzzatura diffusore MOD100", "es": "añadir dispositivo de pulverización difusor MOD100", "pl": "dodaj urządzenie rozpylające z dyfuzorem MOD100", "zh-cn": "添加MOD100扩散喷雾器" }, "1.6.3": { "en": "Update translations", "de": "Übersetzungen aktualisieren", "ru": "Обновить переводы", "pt": "Atualizar traduções", "nl": "Vertalingen bijwerken", "fr": "Mettre à jour les traductions", "it": "Aggiorna traduzioni", "es": "Actualizar traducciones", "pl": "Zaktualizuj tłumaczenia", "zh-cn": "更新翻译" }, "1.10.1": { "en": "Fix pot. crash case", "de": "Topf fixieren. Crash-Fall", "ru": "Починить горшок. аварийный случай", "pt": "Conserte o pote. caso de acidente", "nl": "Pot repareren. crashgeval", "fr": "Casserole fixe. cas d'accident", "it": "Riparare la pentola. caso di incidente", "es": "Arreglar olla. caso de accidente", "pl": "Napraw garnek. wypadek wypadku", "zh-cn": "修锅。车祸案例" }, "1.10.0": { "en": "Optimize Meross Communication to first try to communicate with the device locally before sending data to MQTT - enabled by default, you can disable it in settings!\nOptimize Meross Communication by using only one MQTT connection instead of one per device when cloud is used\nAdd new state \"disabled\" to ignore connection error of a device; reconnections are still tried, but no error are logged if not successful\nAdd support for Online status reports from MTS100 hub devices\nAutomatically logout from meross cloud on adapter end; next start will do a new Login\nAutomatically delete old devices if no longer existing (when js-controller >=2.2)\nOptimize MTS200 handling", "de": "Optimieren Sie die Meross-Kommunikation, um zuerst zu versuchen, lokal mit dem Gerät zu kommunizieren, bevor Sie Daten an MQTT senden - standardmäßig aktiviert, Sie können es in den Einstellungen deaktivieren!\nOptimieren Sie die Meross-Kommunikation, indem Sie nur eine MQTT-Verbindung statt einer pro Gerät verwenden, wenn die Cloud verwendet wird\nNeuen Zustand „deaktiviert“ hinzufügen, um Verbindungsfehler eines Geräts zu ignorieren; Wiederverbindungen werden immer noch versucht, aber es werden keine Fehler protokolliert, wenn sie nicht erfolgreich sind\nUnterstützung für Online-Statusberichte von MTS100-Hub-Geräten hinzugefügt\nAutomatisches Abmelden von der Meross-Cloud am Adapterende; Beim nächsten Start wird ein neuer Login durchgeführt\nAlte Geräte automatisch löschen, wenn nicht mehr vorhanden (wenn js-controller >=2.2)\nOptimieren Sie die Handhabung des MTS200", "ru": "Оптимизируйте связь Meross, чтобы сначала попытаться связаться с устройством локально перед отправкой данных в MQTT — включено по умолчанию, вы можете отключить его в настройках!\nОптимизируйте связь Meross, используя только одно соединение MQTT вместо одного на устройство при использовании облака.\nДобавлено новое состояние «отключено», чтобы игнорировать ошибку подключения устройства; повторные подключения все еще предпринимаются, но в случае неудачи не регистрируется никаких ошибок\nДобавлена поддержка онлайн-отчетов о состоянии с узловых устройств MTS100.\nАвтоматический выход из облака meross на стороне адаптера; при следующем запуске будет выполнен новый вход в систему\nАвтоматически удалять старые устройства, если они больше не существуют (когда js-controller>=2.2)\nОптимизация работы с MTS200", "pt": "Otimize a comunicação Meross para primeiro tentar se comunicar com o dispositivo localmente antes de enviar dados para o MQTT - ativado por padrão, você pode desativá-lo nas configurações!\nOtimize a comunicação Meross usando apenas uma conexão MQTT em vez de uma por dispositivo quando a nuvem é usada\nAdicionar novo estado \"desabilitado\" para ignorar erro de conexão de um dispositivo; as reconexões ainda são tentadas, mas nenhum erro é registrado se não for bem-sucedida\nAdicione suporte para relatórios de status online de dispositivos de hub MTS100\nLogout automaticamente da nuvem meross na extremidade do adaptador; próxima partida fará um novo Login\nExclua automaticamente dispositivos antigos se não existirem mais (quando js-controller >=2.2)\nOtimize o manuseio do MTS200", "nl": "Optimaliseer Meross-communicatie om eerst lokaal met het apparaat te communiceren voordat u gegevens naar MQTT verzendt - standaard ingeschakeld, u kunt dit uitschakelen in de instellingen!\nOptimaliseer Meross-communicatie door slechts één MQTT-verbinding te gebruiken in plaats van één per apparaat wanneer de cloud wordt gebruikt\nVoeg een nieuwe status \"uitgeschakeld\" toe om de verbindingsfout van een apparaat te negeren; er wordt nog steeds geprobeerd om opnieuw verbinding te maken, maar er wordt geen fout geregistreerd als dit niet lukt\nOndersteuning toevoegen voor online statusrapporten van MTS100-hubapparaten\nAutomatisch uitloggen van meross cloud aan het uiteinde van de adapter; volgende start zal een nieuwe login doen\nVerwijder automatisch oude apparaten als ze niet meer bestaan (wanneer js-controller >=2.2)\nOptimaliseer de afhandeling van de MTS200", "fr": "Optimisez la communication Meross pour essayer d'abord de communiquer avec l'appareil localement avant d'envoyer des données à MQTT - activé par défaut, vous pouvez le désactiver dans les paramètres !\nOptimisez la communication Meross en utilisant une seule connexion MQTT au lieu d'une par appareil lorsque le cloud est utilisé\nAjouter un nouvel état \"désactivé\" pour ignorer l'erreur de connexion d'un appareil ; les reconnexions sont toujours tentées, mais aucune erreur n'est consignée en cas d'échec\nAjout de la prise en charge des rapports d'état en ligne des périphériques concentrateurs MTS100\nSe déconnecte automatiquement du cloud meross à l'extrémité de l'adaptateur ; le prochain démarrage fera une nouvelle connexion\nSupprimer automatiquement les anciens appareils s'ils n'existent plus (lorsque js-controller >=2.2)\nOptimiser la manipulation du MTS200", "it": "Ottimizza la comunicazione Meross per provare a comunicare con il dispositivo localmente prima di inviare i dati a MQTT - abilitato per impostazione predefinita, puoi disabilitarlo nelle impostazioni!\nOttimizza la comunicazione Meross utilizzando una sola connessione MQTT anziché una per dispositivo quando viene utilizzato il cloud\nAggiungi il nuovo stato \"disabilitato\" per ignorare l'errore di connessione di un dispositivo; le riconnessioni vengono ancora tentate, ma non vengono registrati errori se non hanno esito positivo\nAggiungi il supporto per i rapporti di stato online dai dispositivi hub MTS100\nDisconnettersi automaticamente dal cloud meross all'estremità dell'adattatore; il prossimo inizio eseguirà un nuovo accesso\nElimina automaticamente i vecchi dispositivi se non esistono più (quando js-controller >=2.2)\nOttimizza la gestione dell'MTS200", "es": "Optimice Meross Communication para intentar primero comunicarse con el dispositivo localmente antes de enviar datos a MQTT; habilitado de manera predeterminada, ¡puede deshabilitarlo en la configuración!\nOptimice Meross Communication usando solo una conexión MQTT en lugar de una por dispositivo cuando se usa la nube\nAgregar nuevo estado \"deshabilitado\" para ignorar el error de conexión de un dispositivo; las reconexiones aún se intentan, pero no se registra ningún error si no se realiza correctamente\nAgregue soporte para informes de estado en línea desde dispositivos concentradores MTS100\nCerrar sesión automáticamente desde la nube de meross en el extremo del adaptador; el próximo inicio hará un nuevo inicio de sesión\nEliminar automáticamente los dispositivos antiguos si ya no existen (cuando js-controller >=2.2)\nOptimizar el manejo de MTS200", "pl": "Zoptymalizuj komunikację Meross, aby najpierw spróbować komunikować się z urządzeniem lokalnie przed wysłaniem danych do MQTT - domyślnie włączone, można je wyłączyć w ustawieniach!\nZoptymalizuj komunikację Meross, używając tylko jednego połączenia MQTT zamiast jednego na urządzenie, gdy używana jest chmura\nDodaj nowy stan „wyłączony”, aby zignorować błąd połączenia urządzenia; próby ponownego połączenia są nadal próbowane, ale w przypadku niepowodzenia żaden błąd nie jest rejestrowany\nDodaj obsługę raportów o stanie online z urządzeń koncentratora MTS100\nAutomatycznie wyloguj się z chmury meross na końcu adaptera; następny start wykona nowe logowanie\nAutomatycznie usuwaj stare urządzenia, jeśli już nie istnieją (gdy js-controller >=2.2)\nZoptymalizuj obsługę MTS200", "zh-cn": "优化 Meross 通信，在向 MQTT 发送数据之前先尝试与设备本地通信 - 默认启用，您可以在设置中禁用它！\n使用云时，仅使用一个 MQTT 连接而不是每个设备一个，优化 Meross 通信\n添加新状态“禁用”以忽略设备的连接错误；仍然尝试重新连接，但如果不成功则不会记录错误\n添加对来自 MTS100 集线器设备的在线状态报告的支持\n适配器端自动退出meross云；下一次开始将做一个新的登录\n如果不再存在，则自动删除旧设备（当 js-controller >=2.2 时）\n优化 MTS200 处理" }, "1.8.0": { "en": "Add support for MTS200 Wifi Thermostat", "de": "Unterstützung für MTS200 Wifi Thermostat hinzufügen", "ru": "Добавить поддержку термостата MTS200 Wifi", "pt": "Adicionar suporte para termostato Wifi MTS200", "nl": "Ondersteuning toevoegen voor MTS200 Wifi-thermostaat", "fr": "Ajout de la prise en charge du thermostat Wifi MTS200", "it": "Aggiungi il supporto per il termostato Wi-Fi MTS200", "es": "Agregue soporte para el termostato Wifi MTS200", "pl": "Dodaj obsługę termostatu Wifi MTS200", "zh-cn": "添加对 MTS200 Wifi 恒温器的支持" }, "1.7.1": { "en": "Allow to enter passwords with more than 15 characters", "de": "Erlaube die Eingabe von Passwörtern mit mehr als 15 Zeichen", "ru": "Разрешить вводить пароли длиной более 15 символов", "pt": "Permite inserir senhas com mais de 15 caracteres", "nl": "Sta toe om wachtwoorden in te voeren met meer dan 15 tekens", "fr": "Autoriser la saisie de mots de passe de plus de 15 caractères", "it": "Consenti l'inserimento di password con più di 15 caratteri", "es": "Permitir ingresar contraseñas con más de 15 caracteres", "pl": "Zezwalaj na wprowadzanie haseł zawierających więcej niż 15 znaków", "zh-cn": "允许输入超过 15 个字符的密码" }, "1.7.0": { "en": "Add support for MTS150 Thermostats\nAdd support for MRS100 RollerShutter devices", "de": "Unterstützung für MTS150-Thermostate hinzufügen\nUnterstützung für MRS100 RollerShutter-Geräte hinzufügen", "ru": "Добавить поддержку термостатов MTS150\nДобавить поддержку устройств MRS100 RollerShutter", "pt": "Adicionar suporte para termostatos MTS150\nAdicionar suporte para dispositivos MRS100 RollerShutter", "nl": "Ondersteuning toevoegen voor MTS150-thermostaten\nOndersteuning toevoegen voor MRS100 RollerShutter-apparaten", "fr": "Ajout de la prise en charge des thermostats MTS150\nAjout de la prise en charge des dispositifs MRS100 RollerShutter", "it": "Aggiungi il supporto per i termostati MTS150\nAggiungi il supporto per i dispositivi RollerShutter MRS100", "es": "Agregar soporte para termostatos MTS150\nAgregue soporte para dispositivos RollerShutter MRS100", "pl": "Dodaj obsługę termostatów MTS150\nDodaj obsługę urządzeń MRS100 RollerShutter", "zh-cn": "添加对 MTS150 恒温器的支持\n添加对 MRS100 RollerShutter 设备的支持" } }, "title": "Meross Cloud", "titleLang": { "en": "Meross Cloud", "de": "Meross Cloud", "ru": "Meross Cloud", "pt": "Meross Cloud", "nl": "Meross Cloud", "fr": "Meross Cloud", "it": "Meross Cloud", "es": "Meross Cloud", "pl": "Meross Cloud", "zh-cn": "美洛斯云" }, "desc": { "en": "support for Meross Wifi devices", "de": "Unterstützung für Meross Wifi-Geräte", "ru": "поддержка устройств Meross Wifi", "pt": "suporte para dispositivos Wifi Meross", "nl": "ondersteuning voor Meross Wifi-apparaten", "fr": "support pour les appareils Meross Wifi", "it": "supporto per i dispositivi Meross Wifi", "es": "soporte para dispositivos wifi Meross", "pl": "obsługa urządzeń Wi-Fi firmy Meross", "zh-cn": "支持Meross Wifi设备" }, "authors": [ "Apollon77 <ingo@fischer-ka.de>" ], "platform": "Javascript/Node.js", "mode": "daemon", "icon": "meross.png", "materialize": true, "enabled": true, "extIcon": "https://raw.githubusercontent.com/Apollon77/ioBroker.meross/master/admin/meross.png", "keywords": [ "Meross" ], "readme": "https://github.com/Apollon77/ioBroker.meross/blob/master/README.md", "loglevel": "info", "type": "iot-systems", "installedVersion": "1.11.0", "host": "RDJLHome", "license": "MIT", "stopTimeout": 5000, "compact": true, "plugins": { "sentry": { "dsn": "https://4e753a8ae86d4ff89cb9ceda7c62855e@sentry.iobroker.net/4", "pathWhitelist": [ "@apollon", "meross-cloud" ], "errorBlacklist": [ "SyntaxError" ] } }, "connectionType": "cloud", "dataSource": "push", "installedFrom": "Apollon77/ioBroker.meross", "tier": 2, "dependencies": [ { "js-controller": ">=2.0.0" } ], "disableDataReporting": false, "adminUI": { "config": "materialize" } }, "native": { "user": "****", "password": "*****", "electricityPollingInterval": "120", "electricityPollingIntervalReChecked": true, "noDirectLocalCommunication": true }, "acl": { "object": 1636, "owner": "system.user.admin", "ownerGroup": "system.group.administrator" }, "protectedNative": [ "password" ], "encryptedNative": [ "password" ], "instanceObjects": [ { "_id": "info", "type": "channel", "common": { "name": "Information" }, "native": {} }, { "_id": "info.connection", "type": "state", "common": { "role": "indicator.connected", "name": "If connected to Meross Cloud", "type": "boolean", "read": true, "write": false, "def": false }, "native": {} } ], "objects": [], "notifications": [], "from": "system.adapter.admin.0", "user": "system.user.admin", "ts": 1654758611429 }steht nix drinnen von "restartSchedule" so wie ich beim Telegram Adapter es jeden Tag um 9:00 mache!
-
@myzerat sehr komisch, der js-controller denkt in jedem Fall das da was ist. am ebsten mal Reboot oder "iob stop" und "iob start"
-
hab ich schon heute sicher 2-3 mal gemacht!
ich werde mal morgen schauen ob es wieder passiert ist über Nacht , einstweilen tut sich nichts, mit reboot der Meross Instanz , außer das ich immer diese Meldung bekomme
meross.0 2022-06-09 14:58:22.730 warn Can not get Data for Device 1809013215340225180534298f166a51: undefined meross.0 2022-06-09 14:58:22.729 info Can not get Data for Device 1809013215340225180534298f166a51: Error: Timeout meross.0 2022-06-09 14:58:22.664 warn Can not get Data for Device 1810224092789329085334298f16f18d: undefined meross.0 2022-06-09 14:58:22.663 info Can not get Data for Device 1810224092789329085334298f16f18d: Error: TimeoutSind jedoch beide mit der Handy App schaltbar und man sieht es auch in den Objekten, das geschaltet wurde, nur von io aus geht es nicht zum schalten bei den beiden (bei einem Restart können es aber wieder andere Geräte sein, sind nicht immer die selben!)
! -
@myzerat Da würde mich mal ein vollstöäniges debug log interessieren bis dazu - aber bitte offizielle NPM version nehmen ... du hast iiirgendeine GitHub version drauf!
-
-
@myzerat Nein Meross Adapter version ... sonst hol nochmal neueste github
-
@apollon77
ich hatte die 1.11.0 von dir drauf --> https://github.com/Apollon77/ioBroker.meross
du meinst die 1.10.5 er version ? -
habe jetzt auf 1.10.5 den adapter wieder und nun spinnt er noch mehr! hier ein logfile , hoffe ers hilft, thx
er findet jetzt wieder mehrere nicht:
meross.0 2022-06-09 19:55:16.461 info Can not get Data for Device 1809013215340225180534298f166a51: Error: Timeout meross.0 2022-06-09 19:55:16.460 info Can not get Data for Device 1810224092789329085334298f16f18d: Error: Timeout meross.0 2022-06-09 19:55:16.458 info Can not get Data for Device 19011882830659251h0334298f1a0625: Error: Timeout meross.0 2022-06-09 19:55:16.457 info Can not get Data for Device 1812179492140325182834298f19d01f: Error: Timeout meross.0 2022-06-09 19:55:16.454 info Can not get Data for Device 19011873123850251h0334298f1a09a6: Error: Timeout meross.0 2022-06-09 19:55:16.453 info Can not get Data for Device 2001192823402125188548e1e9172387: Error: Timeout meross.0 2022-06-09 19:55:16.451 info Can not get Data for Device 2001192419504425188548e1e9171db0: Error: Timeout meross.0 2022-06-09 19:55:16.441 info Can not get Data for Device 19011898369667251h0434298f1a6462: Error: Timeout#######LOGFILE######
meross_Myzer.txtps: habe gerade eine nocxh nie benutze meross steckdose eingebunden, auch hier kommt diese meldung
Can not get Data for Device 21020323778036251h6148e1e94ad068: Error: Timeout -
@myzerat geh mal jetzt wieder auf die 1.11.0 (die von npm ... nicht GitHub)
-
Sorry für meine Unwissenheit, aber wie komme ich auf die 1.11.0 ohne Github, thx
-
@myzerat Admin - expertenmodus - Custom Install/GitHub Button - erster Tab "von NPM" ... ist immer die aktuelle Beta-Repo version
-
habe die npm versiopn 1.11.0 eingespielt und nach mehreren "closed:null, reconnected und Connection refused: Server unavailable" , hat es dann einige stunden funktioniert und es wurden auch alle geräte erkannt, dann kam aber wieder das selbe problem (das muss ich abere noch per debug aufzeichnen)
ich werde jetzt noch die instanz auf debug stellen und sobald der fehler wieder auftritt, dir hier das aktuelle log posten!
---->>>>>>>>>>>> meross_Myzer.txt
2022-06-10 13:56:11.506 - [32minfo[39m: meross.0 (2080) Device: 18122163520756258h0334298f144240 closed: null 2022-06-10 13:56:11.507 - [32minfo[39m: meross.0 (2080) Device: 21020338573116251h6148e1e94abdc7 closed: null 2022-06-10 13:56:11.507 - [32minfo[39m: meross.0 (2080) Device: 21020300990383251h6148e1e94acdf8 closed: null 2022-06-10 13:56:11.508 - [32minfo[39m: meross.0 (2080) Device: 1809016208959425180534298f1665ca closed: null 2022-06-10 13:56:11.508 - [32minfo[39m: meross.0 (2080) Device: 19011820035814251h0334298f1a0745 closed: null 2022-06-10 13:56:11.508 - [32minfo[39m: meross.0 (2080) Device: 2001191193736125188548e1e9171e9a closed: null 2022-06-10 13:56:11.508 - [32minfo[39m: meross.0 (2080) Device: 2001194310463525188548e1e9172324 closed: null 2022-06-10 13:56:11.509 - [32minfo[39m: meross.0 (2080) Device: 19011832535820251h0334298f1a090a closed: null 2022-06-10 13:56:11.509 - [32minfo[39m: meross.0 (2080) Device: 1809015737278325180534298f16671f closed: null 2022-06-10 13:56:11.509 - [32minfo[39m: meross.0 (2080) Device: 1809010653847025180534298f16668c closed: null 2022-06-10 13:56:11.509 - [32minfo[39m: meross.0 (2080) Device: 1809014572480225180534298f166ab5 closed: null 2022-06-10 13:56:11.510 - [32minfo[39m: meross.0 (2080) Device: 1811305787614825182134298f187da6 closed: null 2022-06-10 13:56:11.510 - [32minfo[39m: meross.0 (2080) Device: 1809012709631425180534298f16660a closed: null 2022-06-10 13:56:11.510 - [32minfo[39m: meross.0 (2080) Device: 1809017394109425180534298f166544 closed: null 2022-06-10 13:56:11.510 - [32minfo[39m: meross.0 (2080) Device: 1809014813536325180534298f166a87 closed: null 2022-06-10 13:56:16.507 - [32minfo[39m: meross.0 (2080) Device: 18122163520756258h0334298f144240 reconnected 2022-06-10 13:56:16.508 - [32minfo[39m: meross.0 (2080) Device: 21020338573116251h6148e1e94abdc7 reconnected 2022-06-10 13:56:16.508 - [32minfo[39m: meross.0 (2080) Device: 21020300990383251h6148e1e94acdf8 reconnected 2022-06-10 13:56:16.509 - [32minfo[39m: meross.0 (2080) Device: 1809016208959425180534298f1665ca reconnected 2022-06-10 13:56:16.509 - [32minfo[39m: meross.0 (2080) Device: 19011820035814251h0334298f1a0745 reconnected 2022-06-10 13:56:16.509 - [32minfo[39m: meross.0 (2080) Device: 2001191193736125188548e1e9171e9a reconnected 2022-06-10 13:56:16.509 - [32minfo[39m: meross.0 (2080) Device: 2001194310463525188548e1e9172324 reconnected 2022-06-10 13:56:16.509 - [32minfo[39m: meross.0 (2080) Device: 19011832535820251h0334298f1a090a reconnected 2022-06-10 13:56:16.510 - [32minfo[39m: meross.0 (2080) Device: 1809015737278325180534298f16671f reconnected 2022-06-10 13:56:16.510 - [32minfo[39m: meross.0 (2080) Device: 1809010653847025180534298f16668c reconnected 2022-06-10 13:56:16.510 - [32minfo[39m: meross.0 (2080) Device: 1809014572480225180534298f166ab5 reconnected 2022-06-10 13:56:16.510 - [32minfo[39m: meross.0 (2080) Device: 1811305787614825182134298f187da6 reconnected 2022-06-10 13:56:16.510 - [32minfo[39m: meross.0 (2080) Device: 1809012709631425180534298f16660a reconnected 2022-06-10 13:56:16.510 - [32minfo[39m: meross.0 (2080) Device: 1809017394109425180534298f166544 reconnected 2022-06-10 13:56:16.511 - [32minfo[39m: meross.0 (2080) Device: 1809014813536325180534298f166a87 reconnected 2022-06-10 13:56:16.746 - [32minfo[39m: meross.0 (2080) Device: 18122163520756258h0334298f144240 error: Error: Connection refused: Server unavailable 2022-06-10 13:56:16.747 - [32minfo[39m: meross.0 (2080) Device: 21020338573116251h6148e1e94abdc7 error: Error: Connection refused: Server unavailable 2022-06-10 13:56:16.747 - [32minfo[39m: meross.0 (2080) Device: 21020300990383251h6148e1e94acdf8 error: Error: Connection refused: Server unavailable 2022-06-10 13:56:16.747 - [32minfo[39m: meross.0 (2080) Device: 1809016208959425180534298f1665ca error: Error: Connection refused: Server unavailable 2022-06-10 13:56:16.748 - [32minfo[39m: meross.0 (2080) Device: 19011820035814251h0334298f1a0745 error: Error: Connection refused: Server unavailable 2022-06-10 13:56:16.749 - [32minfo[39m: meross.0 (2080) Device: 2001191193736125188548e1e9171e9a error: Error: Connection refused: Server unavailable 2022-06-10 13:56:16.750 - [32minfo[39m: meross.0 (2080) Device: 2001194310463525188548e1e9172324 error: Error: Connection refused: Server unavailable 2022-06-10 13:56:16.750 - [32minfo[39m: meross.0 (2080) Device: 19011832535820251h0334298f1a090a error: Error: Connection refused: Server unavailable 2022-06-10 13:56:16.750 - [32minfo[39m: meross.0 (2080) Device: 1809015737278325180534298f16671f error: Error: Connection refused: Server unavailable 2022-06-10 13:56:16.751 - [32minfo[39m: meross.0 (2080) Device: 1809010653847025180534298f16668c error: Error: Connection refused: Server unavailable 2022-06-10 13:56:16.751 - [32minfo[39m: meross.0 (2080) Device: 1809014572480225180534298f166ab5 error: Error: Connection refused: Server unavailable 2022-06-10 13:56:16.752 - [32minfo[39m: meross.0 (2080) Device: 1811305787614825182134298f187da6 error: Error: Connection refused: Server unavailable 2022-06-10 13:56:16.752 - [32minfo[39m: meross.0 (2080) Device: 1809012709631425180534298f16660a error: Error: Connection refused: Server unavailable 2022-06-10 13:56:16.752 - [32minfo[39m: meross.0 (2080) Device: 1809017394109425180534298f166544 error: Error: Connection refused: Server unavailable 2022-06-10 13:56:16.752 - [32minfo[39m: meross.0 (2080) Device: 1809014813536325180534298f166a87 error: Error: Connection refused: Server unavailable
