NEWS
Test Adapter mihome-vacuum v2.0.x
-
@schwabe installiere den aktuellen Adapter, Stelle den Adapter mal auf debug und poste das hier. Denk dran, das es manchmal dauern kann, bis er sich connected. Oft hilft es auch, wenn man gleichzeitig in die mihome App geht
@dirkhe Danke für die Hilfe.
Ich habe den Adapter aktualisiert und auf Debug gestellt. Dann habe ich ein paar Einstellungen vorgenommen und den Adapter einmal neu gestartet. Zudem ist seit über 12 Stunden der Adapter auf dem TinkerBoardS deaktiviert. Der Adpater bleibt weiterhin "Gelb".
Hier der LOG:mihome-vacuum.0 2021-02-19 08:05:06.261 debug (8721) Xiaomi Cloud: Login successful mihome-vacuum.0 2021-02-19 08:05:04.771 info (8721) set nächster Timer: Nicht verfügbar mihome-vacuum.0 2021-02-19 08:05:04.264 debug (8721) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) } mihome-vacuum.0 2021-02-19 08:05:04.253 debug (8721) server started on 0.0.0.0:53421 mihome-vacuum.0 2021-02-19 08:05:04.250 info (8721) Create state clean_home for controlling by cloud adapter mihome-vacuum.0 2021-02-19 08:05:04.250 info (8721) Expert mode enabled, states created mihome-vacuum.0 2021-02-19 08:05:04.247 debug (8721) Xiaomi Cloud: Logging in mihome-vacuum.0 2021-02-19 08:05:04.247 debug (8721) load Map creator... true mihome-vacuum.0 2021-02-19 08:05:04.209 info (8721) starting. Version 2.1.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v12.20.2, js-controller: 3.1.6 mihome-vacuum.0 2021-02-19 08:05:04.107 debug (8721) statesDB connected mihome-vacuum.0 2021-02-19 08:05:04.107 debug (8721) States connected to redis: 127.0.0.1:9000 mihome-vacuum.0 2021-02-19 08:05:04.102 debug (8721) States create System PubSub Client mihome-vacuum.0 2021-02-19 08:05:04.102 debug (8721) States create User PubSub Client mihome-vacuum.0 2021-02-19 08:05:04.099 debug (8721) Redis States: Use Redis connection: 127.0.0.1:9000 mihome-vacuum.0 2021-02-19 08:05:04.098 debug (8721) objectDB connected mihome-vacuum.0 2021-02-19 08:05:04.097 debug (8721) Objects connected to redis: 127.0.0.1:9001 mihome-vacuum.0 2021-02-19 08:05:04.088 debug (8721) Objects client initialize lua scripts mihome-vacuum.0 2021-02-19 08:05:04.088 debug (8721) Objects create User PubSub Client mihome-vacuum.0 2021-02-19 08:05:04.088 debug (8721) Objects create System PubSub Client mihome-vacuum.0 2021-02-19 08:05:04.087 debug (8721) Objects client ready ... initialize now mihome-vacuum.0 2021-02-19 08:05:04.077 debug (8721) Redis Objects: Use Redis connection: 127.0.0.1:9001 host.Server 2021-02-19 08:05:03.708 info instance system.adapter.mihome-vacuum.0 started with pid 8721 host.Server 2021-02-19 08:05:01.434 info instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) host.Server 2021-02-19 08:05:01.201 info instance system.adapter.mihome-vacuum.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) dwd.0 2021-02-19 08:05:00.926 info (8706) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason mihome-vacuum.0 2021-02-19 08:05:00.688 info (8691) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason mihome-vacuum.0 2021-02-19 08:05:00.688 info (8691) terminating mihome-vacuum.0 2021-02-19 08:05:00.687 info (8691) Got terminate signal TERMINATE_YOURSELF host.Server 2021-02-19 08:05:00.686 info stopInstance system.adapter.mihome-vacuum.0 send kill signal host.Server 2021-02-19 08:05:00.686 info stopInstance system.adapter.mihome-vacuum.0 (force=false, process=true) dwd.0 2021-02-19 08:05:00.613 info (8706) starting. Version 2.5.2 in /opt/iobroker/node_modules/iobroker.dwd, node: v12.20.2, js-controller: 3.1.6 host.Server 2021-02-19 08:05:00.033 info instance system.adapter.dwd.0 started with pid 8706 mihome-vacuum.0 2021-02-19 08:04:56.597 debug (8691) Xiaomi Cloud: Login successful mihome-vacuum.0 2021-02-19 08:04:55.360 info (8691) set nächster Timer: Nicht verfügbar mihome-vacuum.0 2021-02-19 08:04:54.857 debug (8691) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) } mihome-vacuum.0 2021-02-19 08:04:54.846 debug (8691) server started on 0.0.0.0:53421 mihome-vacuum.0 2021-02-19 08:04:54.843 info (8691) Create state clean_home for controlling by cloud adapter mihome-vacuum.0 2021-02-19 08:04:54.842 info (8691) Expert mode enabled, states created mihome-vacuum.0 2021-02-19 08:04:54.840 debug (8691) Xiaomi Cloud: Logging in mihome-vacuum.0 2021-02-19 08:04:54.840 debug (8691) load Map creator... true mihome-vacuum.0 2021-02-19 08:04:54.799 info (8691) starting. Version 2.1.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v12.20.2, js-controller: 3.1.6 mihome-vacuum.0 2021-02-19 08:04:54.700 debug (8691) statesDB connected mihome-vacuum.0 2021-02-19 08:04:54.700 debug (8691) States connected to redis: 127.0.0.1:9000 mihome-vacuum.0 2021-02-19 08:04:54.694 debug (8691) States create System PubSub Client mihome-vacuum.0 2021-02-19 08:04:54.693 debug (8691) States create User PubSub Client mihome-vacuum.0 2021-02-19 08:04:54.691 debug (8691) Redis States: Use Redis connection: 127.0.0.1:9000 mihome-vacuum.0 2021-02-19 08:04:54.690 debug (8691) objectDB connected mihome-vacuum.0 2021-02-19 08:04:54.689 debug (8691) Objects connected to redis: 127.0.0.1:9001 mihome-vacuum.0 2021-02-19 08:04:54.681 debug (8691) Objects client initialize lua scripts mihome-vacuum.0 2021-02-19 08:04:54.681 debug (8691) Objects create User PubSub Client mihome-vacuum.0 2021-02-19 08:04:54.681 debug (8691) Objects create System PubSub Client mihome-vacuum.0 2021-02-19 08:04:54.680 debug (8691) Objects client ready ... initialize now mihome-vacuum.0 2021-02-19 08:04:54.670 debug (8691) Redis Objects: Use Redis connection: 127.0.0.1:9001 host.Server 2021-02-19 08:04:54.303 info instance system.adapter.mihome-vacuum.0 started with pid 8691 host.Server 2021-02-19 08:04:51.842 info instance system.adapter.mihome-vacuum.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) mihome-vacuum.0 2021-02-19 08:04:51.284 info (8676) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason mihome-vacuum.0 2021-02-19 08:04:51.283 info (8676) terminating mihome-vacuum.0 2021-02-19 08:04:51.283 info (8676) Got terminate signal TERMINATE_YOURSELF host.Server 2021-02-19 08:04:51.280 info stopInstance system.adapter.mihome-vacuum.0 send kill signal host.Server 2021-02-19 08:04:51.279 info stopInstance system.adapter.mihome-vacuum.0 (force=false, process=true) mihome-vacuum.0 2021-02-19 08:04:42.923 debug (8676) Xiaomi Cloud: Login successful mihome-vacuum.0 2021-02-19 08:04:40.900 info (8676) set nächster Timer: Nicht verfügbar mihome-vacuum.0 2021-02-19 08:04:40.394 debug (8676) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) } mihome-vacuum.0 2021-02-19 08:04:40.383 debug (8676) server started on 0.0.0.0:53421 mihome-vacuum.0 2021-02-19 08:04:40.380 info (8676) Create state clean_home for controlling by cloud adapter mihome-vacuum.0 2021-02-19 08:04:40.380 info (8676) Expert mode enabled, states created mihome-vacuum.0 2021-02-19 08:04:40.377 debug (8676) Xiaomi Cloud: Logging in mihome-vacuum.0 2021-02-19 08:04:40.377 debug (8676) load Map creator... true mihome-vacuum.0 2021-02-19 08:04:40.280 info (8676) starting. Version 2.1.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v12.20.2, js-controller: 3.1.6 mihome-vacuum.0 2021-02-19 08:04:40.188 debug (8676) statesDB connected mihome-vacuum.0 2021-02-19 08:04:40.188 debug (8676) States connected to redis: 127.0.0.1:9000 mihome-vacuum.0 2021-02-19 08:04:40.183 debug (8676) States create System PubSub Client mihome-vacuum.0 2021-02-19 08:04:40.182 debug (8676) States create User PubSub Client mihome-vacuum.0 2021-02-19 08:04:40.179 debug (8676) Redis States: Use Redis connection: 127.0.0.1:9000 mihome-vacuum.0 2021-02-19 08:04:40.179 debug (8676) objectDB connected mihome-vacuum.0 2021-02-19 08:04:40.178 debug (8676) Objects connected to redis: 127.0.0.1:9001 mihome-vacuum.0 2021-02-19 08:04:40.170 debug (8676) Objects client initialize lua scripts mihome-vacuum.0 2021-02-19 08:04:40.170 debug (8676) Objects create User PubSub Client mihome-vacuum.0 2021-02-19 08:04:40.169 debug (8676) Objects create System PubSub Client mihome-vacuum.0 2021-02-19 08:04:40.167 debug (8676) Objects client ready ... initialize now mihome-vacuum.0 2021-02-19 08:04:40.157 debug (8676) Redis Objects: Use Redis connection: 127.0.0.1:9001 host.Server 2021-02-19 08:04:39.786 info instance system.adapter.mihome-vacuum.0 started with pid 8676 host.Server 2021-02-19 08:04:37.278 info instance system.adapter.mihome-vacuum.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) mihome-vacuum.0 2021-02-19 08:04:36.764 info (6066) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason mihome-vacuum.0 2021-02-19 08:04:36.764 info (6066) terminating mihome-vacuum.0 2021-02-19 08:04:36.763 info (6066) Got terminate signal TERMINATE_YOURSELF host.Server 2021-02-19 08:04:36.761 info stopInstance system.adapter.mihome-vacuum.0 send kill signal host.Server 2021-02-19 08:04:36.760 info stopInstance system.adapter.mihome-vacuum.0 (force=false, process=true) tr-064.0 2021-02-19 08:04:34.434 info (726) forEachConfiguredDevice: in GetSpecificHostEntry 1(Mandy/ A8:DB:03:65:DB:6F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpec mihome-vacuum.0 2021-02-19 08:04:08.726 debug (6066) sendTo "discovery" to system.adapter.admin.0 from system.adapter.mihome-vacuum.0 mihome-vacuum.0 2021-02-19 08:04:08.726 debug (6066) discover__[{"did":"259591246","token":"3657354e664a5a4b4b74306d524c6f52","longitude":"0.00000000","latitude":"0.00000000","name":"Eltern","pid":"0","localip":"192.168.1.135","mac":"04:CF:8C:F8 mihome-vacuum.0 2021-02-19 08:04:08.724 debug (6066) {"code":0,"message":"ok","result":{"list":[{"did":"259591246","token":"3657354e664a5a4b4b74306d524c6f52","longitude":"0.00000000","latitude":"0.00000000","name":"Eltern","pid":"0","localip":"1 mihome-vacuum.0 2021-02-19 08:04:08.564 debug (6066) GET devices from:https://de.api.io.mi.com/app/home/device_list mihome-vacuum.0 2021-02-19 08:04:08.546 debug (6066) Xiaomi Cloud: Login successful mihome-vacuum.0 2021-02-19 08:04:06.695 debug (6066) Xiaomi Cloud: Logging in mihome-vacuum.0 2021-02-19 08:03:51.246 debug (6066) system.adapter.admin.0: logging true mihome-vacuum.0 2021-02-19 08:03:47.255 debug (6066) system.adapter.admin.0: logging false -
@dirkhe Danke für die Hilfe.
Ich habe den Adapter aktualisiert und auf Debug gestellt. Dann habe ich ein paar Einstellungen vorgenommen und den Adapter einmal neu gestartet. Zudem ist seit über 12 Stunden der Adapter auf dem TinkerBoardS deaktiviert. Der Adpater bleibt weiterhin "Gelb".
Hier der LOG:mihome-vacuum.0 2021-02-19 08:05:06.261 debug (8721) Xiaomi Cloud: Login successful mihome-vacuum.0 2021-02-19 08:05:04.771 info (8721) set nächster Timer: Nicht verfügbar mihome-vacuum.0 2021-02-19 08:05:04.264 debug (8721) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) } mihome-vacuum.0 2021-02-19 08:05:04.253 debug (8721) server started on 0.0.0.0:53421 mihome-vacuum.0 2021-02-19 08:05:04.250 info (8721) Create state clean_home for controlling by cloud adapter mihome-vacuum.0 2021-02-19 08:05:04.250 info (8721) Expert mode enabled, states created mihome-vacuum.0 2021-02-19 08:05:04.247 debug (8721) Xiaomi Cloud: Logging in mihome-vacuum.0 2021-02-19 08:05:04.247 debug (8721) load Map creator... true mihome-vacuum.0 2021-02-19 08:05:04.209 info (8721) starting. Version 2.1.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v12.20.2, js-controller: 3.1.6 mihome-vacuum.0 2021-02-19 08:05:04.107 debug (8721) statesDB connected mihome-vacuum.0 2021-02-19 08:05:04.107 debug (8721) States connected to redis: 127.0.0.1:9000 mihome-vacuum.0 2021-02-19 08:05:04.102 debug (8721) States create System PubSub Client mihome-vacuum.0 2021-02-19 08:05:04.102 debug (8721) States create User PubSub Client mihome-vacuum.0 2021-02-19 08:05:04.099 debug (8721) Redis States: Use Redis connection: 127.0.0.1:9000 mihome-vacuum.0 2021-02-19 08:05:04.098 debug (8721) objectDB connected mihome-vacuum.0 2021-02-19 08:05:04.097 debug (8721) Objects connected to redis: 127.0.0.1:9001 mihome-vacuum.0 2021-02-19 08:05:04.088 debug (8721) Objects client initialize lua scripts mihome-vacuum.0 2021-02-19 08:05:04.088 debug (8721) Objects create User PubSub Client mihome-vacuum.0 2021-02-19 08:05:04.088 debug (8721) Objects create System PubSub Client mihome-vacuum.0 2021-02-19 08:05:04.087 debug (8721) Objects client ready ... initialize now mihome-vacuum.0 2021-02-19 08:05:04.077 debug (8721) Redis Objects: Use Redis connection: 127.0.0.1:9001 host.Server 2021-02-19 08:05:03.708 info instance system.adapter.mihome-vacuum.0 started with pid 8721 host.Server 2021-02-19 08:05:01.434 info instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) host.Server 2021-02-19 08:05:01.201 info instance system.adapter.mihome-vacuum.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) dwd.0 2021-02-19 08:05:00.926 info (8706) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason mihome-vacuum.0 2021-02-19 08:05:00.688 info (8691) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason mihome-vacuum.0 2021-02-19 08:05:00.688 info (8691) terminating mihome-vacuum.0 2021-02-19 08:05:00.687 info (8691) Got terminate signal TERMINATE_YOURSELF host.Server 2021-02-19 08:05:00.686 info stopInstance system.adapter.mihome-vacuum.0 send kill signal host.Server 2021-02-19 08:05:00.686 info stopInstance system.adapter.mihome-vacuum.0 (force=false, process=true) dwd.0 2021-02-19 08:05:00.613 info (8706) starting. Version 2.5.2 in /opt/iobroker/node_modules/iobroker.dwd, node: v12.20.2, js-controller: 3.1.6 host.Server 2021-02-19 08:05:00.033 info instance system.adapter.dwd.0 started with pid 8706 mihome-vacuum.0 2021-02-19 08:04:56.597 debug (8691) Xiaomi Cloud: Login successful mihome-vacuum.0 2021-02-19 08:04:55.360 info (8691) set nächster Timer: Nicht verfügbar mihome-vacuum.0 2021-02-19 08:04:54.857 debug (8691) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) } mihome-vacuum.0 2021-02-19 08:04:54.846 debug (8691) server started on 0.0.0.0:53421 mihome-vacuum.0 2021-02-19 08:04:54.843 info (8691) Create state clean_home for controlling by cloud adapter mihome-vacuum.0 2021-02-19 08:04:54.842 info (8691) Expert mode enabled, states created mihome-vacuum.0 2021-02-19 08:04:54.840 debug (8691) Xiaomi Cloud: Logging in mihome-vacuum.0 2021-02-19 08:04:54.840 debug (8691) load Map creator... true mihome-vacuum.0 2021-02-19 08:04:54.799 info (8691) starting. Version 2.1.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v12.20.2, js-controller: 3.1.6 mihome-vacuum.0 2021-02-19 08:04:54.700 debug (8691) statesDB connected mihome-vacuum.0 2021-02-19 08:04:54.700 debug (8691) States connected to redis: 127.0.0.1:9000 mihome-vacuum.0 2021-02-19 08:04:54.694 debug (8691) States create System PubSub Client mihome-vacuum.0 2021-02-19 08:04:54.693 debug (8691) States create User PubSub Client mihome-vacuum.0 2021-02-19 08:04:54.691 debug (8691) Redis States: Use Redis connection: 127.0.0.1:9000 mihome-vacuum.0 2021-02-19 08:04:54.690 debug (8691) objectDB connected mihome-vacuum.0 2021-02-19 08:04:54.689 debug (8691) Objects connected to redis: 127.0.0.1:9001 mihome-vacuum.0 2021-02-19 08:04:54.681 debug (8691) Objects client initialize lua scripts mihome-vacuum.0 2021-02-19 08:04:54.681 debug (8691) Objects create User PubSub Client mihome-vacuum.0 2021-02-19 08:04:54.681 debug (8691) Objects create System PubSub Client mihome-vacuum.0 2021-02-19 08:04:54.680 debug (8691) Objects client ready ... initialize now mihome-vacuum.0 2021-02-19 08:04:54.670 debug (8691) Redis Objects: Use Redis connection: 127.0.0.1:9001 host.Server 2021-02-19 08:04:54.303 info instance system.adapter.mihome-vacuum.0 started with pid 8691 host.Server 2021-02-19 08:04:51.842 info instance system.adapter.mihome-vacuum.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) mihome-vacuum.0 2021-02-19 08:04:51.284 info (8676) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason mihome-vacuum.0 2021-02-19 08:04:51.283 info (8676) terminating mihome-vacuum.0 2021-02-19 08:04:51.283 info (8676) Got terminate signal TERMINATE_YOURSELF host.Server 2021-02-19 08:04:51.280 info stopInstance system.adapter.mihome-vacuum.0 send kill signal host.Server 2021-02-19 08:04:51.279 info stopInstance system.adapter.mihome-vacuum.0 (force=false, process=true) mihome-vacuum.0 2021-02-19 08:04:42.923 debug (8676) Xiaomi Cloud: Login successful mihome-vacuum.0 2021-02-19 08:04:40.900 info (8676) set nächster Timer: Nicht verfügbar mihome-vacuum.0 2021-02-19 08:04:40.394 debug (8676) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) } mihome-vacuum.0 2021-02-19 08:04:40.383 debug (8676) server started on 0.0.0.0:53421 mihome-vacuum.0 2021-02-19 08:04:40.380 info (8676) Create state clean_home for controlling by cloud adapter mihome-vacuum.0 2021-02-19 08:04:40.380 info (8676) Expert mode enabled, states created mihome-vacuum.0 2021-02-19 08:04:40.377 debug (8676) Xiaomi Cloud: Logging in mihome-vacuum.0 2021-02-19 08:04:40.377 debug (8676) load Map creator... true mihome-vacuum.0 2021-02-19 08:04:40.280 info (8676) starting. Version 2.1.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v12.20.2, js-controller: 3.1.6 mihome-vacuum.0 2021-02-19 08:04:40.188 debug (8676) statesDB connected mihome-vacuum.0 2021-02-19 08:04:40.188 debug (8676) States connected to redis: 127.0.0.1:9000 mihome-vacuum.0 2021-02-19 08:04:40.183 debug (8676) States create System PubSub Client mihome-vacuum.0 2021-02-19 08:04:40.182 debug (8676) States create User PubSub Client mihome-vacuum.0 2021-02-19 08:04:40.179 debug (8676) Redis States: Use Redis connection: 127.0.0.1:9000 mihome-vacuum.0 2021-02-19 08:04:40.179 debug (8676) objectDB connected mihome-vacuum.0 2021-02-19 08:04:40.178 debug (8676) Objects connected to redis: 127.0.0.1:9001 mihome-vacuum.0 2021-02-19 08:04:40.170 debug (8676) Objects client initialize lua scripts mihome-vacuum.0 2021-02-19 08:04:40.170 debug (8676) Objects create User PubSub Client mihome-vacuum.0 2021-02-19 08:04:40.169 debug (8676) Objects create System PubSub Client mihome-vacuum.0 2021-02-19 08:04:40.167 debug (8676) Objects client ready ... initialize now mihome-vacuum.0 2021-02-19 08:04:40.157 debug (8676) Redis Objects: Use Redis connection: 127.0.0.1:9001 host.Server 2021-02-19 08:04:39.786 info instance system.adapter.mihome-vacuum.0 started with pid 8676 host.Server 2021-02-19 08:04:37.278 info instance system.adapter.mihome-vacuum.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) mihome-vacuum.0 2021-02-19 08:04:36.764 info (6066) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason mihome-vacuum.0 2021-02-19 08:04:36.764 info (6066) terminating mihome-vacuum.0 2021-02-19 08:04:36.763 info (6066) Got terminate signal TERMINATE_YOURSELF host.Server 2021-02-19 08:04:36.761 info stopInstance system.adapter.mihome-vacuum.0 send kill signal host.Server 2021-02-19 08:04:36.760 info stopInstance system.adapter.mihome-vacuum.0 (force=false, process=true) tr-064.0 2021-02-19 08:04:34.434 info (726) forEachConfiguredDevice: in GetSpecificHostEntry 1(Mandy/ A8:DB:03:65:DB:6F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpec mihome-vacuum.0 2021-02-19 08:04:08.726 debug (6066) sendTo "discovery" to system.adapter.admin.0 from system.adapter.mihome-vacuum.0 mihome-vacuum.0 2021-02-19 08:04:08.726 debug (6066) discover__[{"did":"259591246","token":"3657354e664a5a4b4b74306d524c6f52","longitude":"0.00000000","latitude":"0.00000000","name":"Eltern","pid":"0","localip":"192.168.1.135","mac":"04:CF:8C:F8 mihome-vacuum.0 2021-02-19 08:04:08.724 debug (6066) {"code":0,"message":"ok","result":{"list":[{"did":"259591246","token":"3657354e664a5a4b4b74306d524c6f52","longitude":"0.00000000","latitude":"0.00000000","name":"Eltern","pid":"0","localip":"1 mihome-vacuum.0 2021-02-19 08:04:08.564 debug (6066) GET devices from:https://de.api.io.mi.com/app/home/device_list mihome-vacuum.0 2021-02-19 08:04:08.546 debug (6066) Xiaomi Cloud: Login successful mihome-vacuum.0 2021-02-19 08:04:06.695 debug (6066) Xiaomi Cloud: Logging in mihome-vacuum.0 2021-02-19 08:03:51.246 debug (6066) system.adapter.admin.0: logging true mihome-vacuum.0 2021-02-19 08:03:47.255 debug (6066) system.adapter.admin.0: logging false -
@schwabe was ich da sehe, ist das der Adapter ständig neu startet. Normalerweise sollte man sehen, wie er versucht sich zu verbinden. Da stimmt irgendwas gar nicht.
@dirkhe die Neustarts habe ich initialisiert, damit Logs geschrieben werden. Bei jedem Neustart sollte der Adapter ja alle Phasen durchlaufen, oder? Mittlerweile sind weitere 16 Stunden vorbei, der ThinkerBoardS Adapter ist noch immer deaktiviert, ich habe mehrfach die App geöffnet, doch der Adapter bleibt "gelb"
Das ist der einzige Eintrag, welcher durch den Adapter in der letzten Stunde gemacht wurde:mihome-vacuum.0 2021-02-19 23:54:16.473 debug (13884) system.adapter.admin.0: logging true -
@dirkhe die Neustarts habe ich initialisiert, damit Logs geschrieben werden. Bei jedem Neustart sollte der Adapter ja alle Phasen durchlaufen, oder? Mittlerweile sind weitere 16 Stunden vorbei, der ThinkerBoardS Adapter ist noch immer deaktiviert, ich habe mehrfach die App geöffnet, doch der Adapter bleibt "gelb"
Das ist der einzige Eintrag, welcher durch den Adapter in der letzten Stunde gemacht wurde:mihome-vacuum.0 2021-02-19 23:54:16.473 debug (13884) system.adapter.admin.0: logging true -
@schwabe also in Zeile 61 hat er sich connected und nach 9 Sekunden schaltest du den Adapter wieder aus?
@dirkhe Der Adapter bleibt aber "gelb" auch wenn im Log steht "logging true".
Der folgende Log zeigt das ich den Adapter neu gestartet habe, er war vorher "gelb", wurde dann natürlich "rot" und blieb wieder bei "gelb" stehen, obwohl er auch hier "logging true" verzeichnet. Ich kann mir da überhaupt keinen Reim drauf machen. Ich habe ihn auch bereits mehrfach deinstalliert und wieder installiert, in verschiedenen Versionen. Die Version im TinkerBoardS läuft wieder in der Version 1.1.5 ohne Probleme.mihome-vacuum.0 2021-02-22 01:18:36.409 debug (10379) system.adapter.admin.0: logging true mihome-vacuum.0 2021-02-22 01:18:03.941 debug (10379) system.adapter.admin.0: logging false tr-064.0 2021-02-22 01:17:48.515 info (851) forEachConfiguredDevice: in GetSpecificHostEntry 1(Mandy/ A8:DB:03:65:DB:6F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpec mihome-vacuum.0 2021-02-22 01:17:17.398 debug (10379) system.adapter.admin.0: logging true tr-064.0 2021-02-22 01:16:46.898 info (851) forEachConfiguredDevice: in GetSpecificHostEntry 1(Mandy/ A8:DB:03:65:DB:6F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpec host.Server 2021-02-22 01:16:27.509 info iobroker exit 0 host.Server 2021-02-22 01:16:26.468 info iobroker Adapter "upnp" updated host.Server 2021-02-22 01:16:26.370 info iobroker upload [0] upnp.admin /opt/iobroker/node_modules/iobroker.upnp/admin/custom_m.html custom_m.html text/html host.Server 2021-02-22 01:16:26.303 info iobroker upload [1] upnp.admin /opt/iobroker/node_modules/iobroker.upnp/admin/i18n/de/translations.json i18n/de/translations.json application/json host.Server 2021-02-22 01:16:26.241 info iobroker upload [2] upnp.admin /opt/iobroker/node_modules/iobroker.upnp/admin/i18n/en/translations.json i18n/en/translations.json application/json host.Server 2021-02-22 01:16:26.180 info iobroker upload [3] upnp.admin /opt/iobroker/node_modules/iobroker.upnp/admin/i18n/es/translations.json i18n/es/translations.json application/json host.Server 2021-02-22 01:16:26.119 info iobroker upload [4] upnp.admin /opt/iobroker/node_modules/iobroker.upnp/admin/i18n/fr/translations.json i18n/fr/translations.json application/json host.Server 2021-02-22 01:16:26.053 info iobroker upload [5] upnp.admin /opt/iobroker/node_modules/iobroker.upnp/admin/i18n/it/translations.json i18n/it/translations.json application/json host.Server 2021-02-22 01:16:25.996 info iobroker upload [6] upnp.admin /opt/iobroker/node_modules/iobroker.upnp/admin/i18n/nl/translations.json i18n/nl/translations.json application/json host.Server 2021-02-22 01:16:25.931 info iobroker upload [7] upnp.admin /opt/iobroker/node_modules/iobroker.upnp/admin/i18n/pl/translations.json i18n/pl/translations.json application/json host.Server 2021-02-22 01:16:25.868 info iobroker upload [8] upnp.admin /opt/iobroker/node_modules/iobroker.upnp/admin/i18n/pt/translations.json i18n/pt/translations.json application/json host.Server 2021-02-22 01:16:25.807 info iobroker upload [9] upnp.admin /opt/iobroker/node_modules/iobroker.upnp/admin/i18n/ru/translations.json i18n/ru/translations.json application/json host.Server 2021-02-22 01:16:25.731 info iobroker upload [10] upnp.admin /opt/iobroker/node_modules/iobroker.upnp/admin/i18n/zh-cn/translations.json i18n/zh-cn/translations.json application/json host.Server 2021-02-22 01:16:25.638 info iobroker upload [11] upnp.admin /opt/iobroker/node_modules/iobroker.upnp/admin/index_m.html index_m.html text/html host.Server 2021-02-22 01:16:25.576 info iobroker upload [12] upnp.admin /opt/iobroker/node_modules/iobroker.upnp/admin/upnp.png upnp.png image/png host.Server 2021-02-22 01:16:25.514 info iobroker Update "system.adapter.upnp.0" host.Server 2021-02-22 01:16:25.500 info iobroker upload [13] upnp.admin /opt/iobroker/node_modules/iobroker.upnp/admin/words.js words.js application/javascript host.Server 2021-02-22 01:16:15.531 info iobroker npm install iobroker.upnp@1.0.17 --loglevel error --prefix "/opt/iobroker" (System call) host.Server 2021-02-22 01:16:15.531 info iobroker NPM version: 6.14.11 host.Server 2021-02-22 01:16:14.187 info iobroker Update upnp from @1.0.16 to @1.0.17 host.Server 2021-02-22 01:16:12.674 info iobroker upgrade upnp mihome-vacuum.0 2021-02-22 01:15:55.227 debug (10379) Xiaomi Cloud: Login successful mihome-vacuum.0 2021-02-22 01:15:53.763 info (10379) set nächster Timer: Nicht verfügbar mihome-vacuum.0 2021-02-22 01:15:53.264 debug (10379) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) } mihome-vacuum.0 2021-02-22 01:15:53.263 info (10379) New generation or new fw(3.5.8,2652) detected, create new states goto and zoneclean mihome-vacuum.0 2021-02-22 01:15:53.262 info (10379) extend state mop for State control.fan_power mihome-vacuum.0 2021-02-22 01:15:53.262 info (10379) change states from State control.fan_power mihome-vacuum.0 2021-02-22 01:15:53.249 debug (10379) server started on 0.0.0.0:53421 mihome-vacuum.0 2021-02-22 01:15:53.247 info (10379) Create state clean_home for controlling by cloud adapter mihome-vacuum.0 2021-02-22 01:15:53.247 info (10379) Expert mode enabled, states created mihome-vacuum.0 2021-02-22 01:15:53.244 debug (10379) Xiaomi Cloud: Logging in mihome-vacuum.0 2021-02-22 01:15:53.244 debug (10379) load Map creator... false mihome-vacuum.0 2021-02-22 01:15:52.921 info (10379) starting. Version 2.1.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.15.5, js-controller: 3.2.16 mihome-vacuum.0 2021-02-22 01:15:52.811 debug (10379) statesDB connected mihome-vacuum.0 2021-02-22 01:15:52.811 debug (10379) States connected to redis: 127.0.0.1:9000 mihome-vacuum.0 2021-02-22 01:15:52.805 debug (10379) States create User PubSub Client mihome-vacuum.0 2021-02-22 01:15:52.805 debug (10379) States create System PubSub Client mihome-vacuum.0 2021-02-22 01:15:52.801 debug (10379) Redis States: Use Redis connection: 127.0.0.1:9000 mihome-vacuum.0 2021-02-22 01:15:52.801 debug (10379) objectDB connected mihome-vacuum.0 2021-02-22 01:15:52.799 debug (10379) Objects connected to redis: 127.0.0.1:9001 mihome-vacuum.0 2021-02-22 01:15:52.793 debug (10379) Objects client initialize lua scripts mihome-vacuum.0 2021-02-22 01:15:52.792 debug (10379) Objects create User PubSub Client mihome-vacuum.0 2021-02-22 01:15:52.792 debug (10379) Objects create System PubSub Client mihome-vacuum.0 2021-02-22 01:15:52.791 debug (10379) Objects client ready ... initialize now mihome-vacuum.0 2021-02-22 01:15:52.780 debug (10379) Redis Objects: Use Redis connection: 127.0.0.1:9001 host.Server 2021-02-22 01:15:52.365 info instance system.adapter.mihome-vacuum.0 started with pid 10379 host.Server 2021-02-22 01:15:49.885 info instance system.adapter.mihome-vacuum.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) mihome-vacuum.0 2021-02-22 01:15:49.343 info (866) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason mihome-vacuum.0 2021-02-22 01:15:49.342 info (866) terminating mihome-vacuum.0 2021-02-22 01:15:49.337 info (866) Got terminate signal TERMINATE_YOURSELF -
es scheint auch so, als würde mein Adapter abschmieren, wenn ich den Befehl get map v1 sende.
@bjoegibbard said in Test Adapter mihome-vacuum v2.0.x:
Hallo,
ich habe seit kurzem exakt den gleichen Fehler wie oben im Bild zu sehen, wenn ich per Skript ein Kommando senden will (sitze gerade nicht zu Hause, daher hab ich mal auf den schon hier geposteten Screenshot zurückgegriffen).
Hat jemand eine Idee, wie man das beheben kann? Der Fehler tritt bei mir auf, seitdem ich den js-controller auf 3.2.16 geupdated habe. Vielen Dank schonmal! :) -
@bjoegibbard said in Test Adapter mihome-vacuum v2.0.x:
Hallo,
ich habe seit kurzem exakt den gleichen Fehler wie oben im Bild zu sehen, wenn ich per Skript ein Kommando senden will (sitze gerade nicht zu Hause, daher hab ich mal auf den schon hier geposteten Screenshot zurückgegriffen).
Hat jemand eine Idee, wie man das beheben kann? Der Fehler tritt bei mir auf, seitdem ich den js-controller auf 3.2.16 geupdated habe. Vielen Dank schonmal! :) -
@dirkhe Der Adapter bleibt aber "gelb" auch wenn im Log steht "logging true".
Der folgende Log zeigt das ich den Adapter neu gestartet habe, er war vorher "gelb", wurde dann natürlich "rot" und blieb wieder bei "gelb" stehen, obwohl er auch hier "logging true" verzeichnet. Ich kann mir da überhaupt keinen Reim drauf machen. Ich habe ihn auch bereits mehrfach deinstalliert und wieder installiert, in verschiedenen Versionen. Die Version im TinkerBoardS läuft wieder in der Version 1.1.5 ohne Probleme.mihome-vacuum.0 2021-02-22 01:18:36.409 debug (10379) system.adapter.admin.0: logging true mihome-vacuum.0 2021-02-22 01:18:03.941 debug (10379) system.adapter.admin.0: logging false tr-064.0 2021-02-22 01:17:48.515 info (851) forEachConfiguredDevice: in GetSpecificHostEntry 1(Mandy/ A8:DB:03:65:DB:6F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpec mihome-vacuum.0 2021-02-22 01:17:17.398 debug (10379) system.adapter.admin.0: logging true tr-064.0 2021-02-22 01:16:46.898 info (851) forEachConfiguredDevice: in GetSpecificHostEntry 1(Mandy/ A8:DB:03:65:DB:6F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpec host.Server 2021-02-22 01:16:27.509 info iobroker exit 0 host.Server 2021-02-22 01:16:26.468 info iobroker Adapter "upnp" updated host.Server 2021-02-22 01:16:26.370 info iobroker upload [0] upnp.admin /opt/iobroker/node_modules/iobroker.upnp/admin/custom_m.html custom_m.html text/html host.Server 2021-02-22 01:16:26.303 info iobroker upload [1] upnp.admin /opt/iobroker/node_modules/iobroker.upnp/admin/i18n/de/translations.json i18n/de/translations.json application/json host.Server 2021-02-22 01:16:26.241 info iobroker upload [2] upnp.admin /opt/iobroker/node_modules/iobroker.upnp/admin/i18n/en/translations.json i18n/en/translations.json application/json host.Server 2021-02-22 01:16:26.180 info iobroker upload [3] upnp.admin /opt/iobroker/node_modules/iobroker.upnp/admin/i18n/es/translations.json i18n/es/translations.json application/json host.Server 2021-02-22 01:16:26.119 info iobroker upload [4] upnp.admin /opt/iobroker/node_modules/iobroker.upnp/admin/i18n/fr/translations.json i18n/fr/translations.json application/json host.Server 2021-02-22 01:16:26.053 info iobroker upload [5] upnp.admin /opt/iobroker/node_modules/iobroker.upnp/admin/i18n/it/translations.json i18n/it/translations.json application/json host.Server 2021-02-22 01:16:25.996 info iobroker upload [6] upnp.admin /opt/iobroker/node_modules/iobroker.upnp/admin/i18n/nl/translations.json i18n/nl/translations.json application/json host.Server 2021-02-22 01:16:25.931 info iobroker upload [7] upnp.admin /opt/iobroker/node_modules/iobroker.upnp/admin/i18n/pl/translations.json i18n/pl/translations.json application/json host.Server 2021-02-22 01:16:25.868 info iobroker upload [8] upnp.admin /opt/iobroker/node_modules/iobroker.upnp/admin/i18n/pt/translations.json i18n/pt/translations.json application/json host.Server 2021-02-22 01:16:25.807 info iobroker upload [9] upnp.admin /opt/iobroker/node_modules/iobroker.upnp/admin/i18n/ru/translations.json i18n/ru/translations.json application/json host.Server 2021-02-22 01:16:25.731 info iobroker upload [10] upnp.admin /opt/iobroker/node_modules/iobroker.upnp/admin/i18n/zh-cn/translations.json i18n/zh-cn/translations.json application/json host.Server 2021-02-22 01:16:25.638 info iobroker upload [11] upnp.admin /opt/iobroker/node_modules/iobroker.upnp/admin/index_m.html index_m.html text/html host.Server 2021-02-22 01:16:25.576 info iobroker upload [12] upnp.admin /opt/iobroker/node_modules/iobroker.upnp/admin/upnp.png upnp.png image/png host.Server 2021-02-22 01:16:25.514 info iobroker Update "system.adapter.upnp.0" host.Server 2021-02-22 01:16:25.500 info iobroker upload [13] upnp.admin /opt/iobroker/node_modules/iobroker.upnp/admin/words.js words.js application/javascript host.Server 2021-02-22 01:16:15.531 info iobroker npm install iobroker.upnp@1.0.17 --loglevel error --prefix "/opt/iobroker" (System call) host.Server 2021-02-22 01:16:15.531 info iobroker NPM version: 6.14.11 host.Server 2021-02-22 01:16:14.187 info iobroker Update upnp from @1.0.16 to @1.0.17 host.Server 2021-02-22 01:16:12.674 info iobroker upgrade upnp mihome-vacuum.0 2021-02-22 01:15:55.227 debug (10379) Xiaomi Cloud: Login successful mihome-vacuum.0 2021-02-22 01:15:53.763 info (10379) set nächster Timer: Nicht verfügbar mihome-vacuum.0 2021-02-22 01:15:53.264 debug (10379) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) } mihome-vacuum.0 2021-02-22 01:15:53.263 info (10379) New generation or new fw(3.5.8,2652) detected, create new states goto and zoneclean mihome-vacuum.0 2021-02-22 01:15:53.262 info (10379) extend state mop for State control.fan_power mihome-vacuum.0 2021-02-22 01:15:53.262 info (10379) change states from State control.fan_power mihome-vacuum.0 2021-02-22 01:15:53.249 debug (10379) server started on 0.0.0.0:53421 mihome-vacuum.0 2021-02-22 01:15:53.247 info (10379) Create state clean_home for controlling by cloud adapter mihome-vacuum.0 2021-02-22 01:15:53.247 info (10379) Expert mode enabled, states created mihome-vacuum.0 2021-02-22 01:15:53.244 debug (10379) Xiaomi Cloud: Logging in mihome-vacuum.0 2021-02-22 01:15:53.244 debug (10379) load Map creator... false mihome-vacuum.0 2021-02-22 01:15:52.921 info (10379) starting. Version 2.1.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.15.5, js-controller: 3.2.16 mihome-vacuum.0 2021-02-22 01:15:52.811 debug (10379) statesDB connected mihome-vacuum.0 2021-02-22 01:15:52.811 debug (10379) States connected to redis: 127.0.0.1:9000 mihome-vacuum.0 2021-02-22 01:15:52.805 debug (10379) States create User PubSub Client mihome-vacuum.0 2021-02-22 01:15:52.805 debug (10379) States create System PubSub Client mihome-vacuum.0 2021-02-22 01:15:52.801 debug (10379) Redis States: Use Redis connection: 127.0.0.1:9000 mihome-vacuum.0 2021-02-22 01:15:52.801 debug (10379) objectDB connected mihome-vacuum.0 2021-02-22 01:15:52.799 debug (10379) Objects connected to redis: 127.0.0.1:9001 mihome-vacuum.0 2021-02-22 01:15:52.793 debug (10379) Objects client initialize lua scripts mihome-vacuum.0 2021-02-22 01:15:52.792 debug (10379) Objects create User PubSub Client mihome-vacuum.0 2021-02-22 01:15:52.792 debug (10379) Objects create System PubSub Client mihome-vacuum.0 2021-02-22 01:15:52.791 debug (10379) Objects client ready ... initialize now mihome-vacuum.0 2021-02-22 01:15:52.780 debug (10379) Redis Objects: Use Redis connection: 127.0.0.1:9001 host.Server 2021-02-22 01:15:52.365 info instance system.adapter.mihome-vacuum.0 started with pid 10379 host.Server 2021-02-22 01:15:49.885 info instance system.adapter.mihome-vacuum.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) mihome-vacuum.0 2021-02-22 01:15:49.343 info (866) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason mihome-vacuum.0 2021-02-22 01:15:49.342 info (866) terminating mihome-vacuum.0 2021-02-22 01:15:49.337 info (866) Got terminate signal TERMINATE_YOURSELF@schwabe load Map creator... false steht da, das sieht so aus, als wenn das canvas nicht installiert ist, obwohl da eigentlich noch andere Fehlermeldungen kommen müssten.
Unabhängig davon fehlen mir die ganzen Versuche, sich mit dem robbi zu verbinden. Steht da vlt. Noch irgendwo was im System Log? Hast du die ip Adresse korrekt eingetragen? -
@schwabe load Map creator... false steht da, das sieht so aus, als wenn das canvas nicht installiert ist, obwohl da eigentlich noch andere Fehlermeldungen kommen müssten.
Unabhängig davon fehlen mir die ganzen Versuche, sich mit dem robbi zu verbinden. Steht da vlt. Noch irgendwo was im System Log? Hast du die ip Adresse korrekt eingetragen?@dirkhe danke noch mal für die Hilfe. Ich kann es zwar nicht erklären, jedoch ist der Adapter jetzt, ohne das ich was am System, dem Adapter oder ioBroker geändert habe auf "grün" gesprungen.
Die Canvas-Gauges Style Widgets sind bei mir installiert oder meinst du was anderes? -
@dirkhe danke noch mal für die Hilfe. Ich kann es zwar nicht erklären, jedoch ist der Adapter jetzt, ohne das ich was am System, dem Adapter oder ioBroker geändert habe auf "grün" gesprungen.
Die Canvas-Gauges Style Widgets sind bei mir installiert oder meinst du was anderes? -
guten Tag ich habe leider das Problem das sobald ich eine Zimmerreinigung starte, der Adapter die Verbindung verliert, er fängt dann an zu saugen aber steuern ist nicht mehr möglich, bis ich den Adapter einmal von Hand neu starte. Das zeigt mir der Log:
Hat jemand eine idee woran das liegen kann ?
-
guten Tag ich habe leider das Problem das sobald ich eine Zimmerreinigung starte, der Adapter die Verbindung verliert, er fängt dann an zu saugen aber steuern ist nicht mehr möglich, bis ich den Adapter einmal von Hand neu starte. Das zeigt mir der Log:
Hat jemand eine idee woran das liegen kann ?
-
@serial13579 schau mal, ob deine Räume im ioBroker die saugstärke definiert haben
@dirkhe vielen Dank!! das war es !
-
Hat schon jemand bei seinem Xiaomi 1S Saugroboter das Firmware Update auf 3.5.4_1342 gemacht und kann bestätigen dass danach die Verbindung zum Adapter noch funktioniert?
..:: So long! Tom ::..
NUC7i3 (Ubuntu Proxmox VM) | Echo Dots 2+3. Gen | Xiaomi Sensoren | Mi Robot 1S | Yeelight | Sonoff | Shelly | H801 RGB | Gosund SP1 | NodeMCU+ESP32 | Kostal Plenticore PV+BYD | openWB
-
Hat schon jemand bei seinem Xiaomi 1S Saugroboter das Firmware Update auf 3.5.4_1342 gemacht und kann bestätigen dass danach die Verbindung zum Adapter noch funktioniert?
@diginix Auf meinem Robi der ersten Generation (heißt der 1S?) läuft 3.5.8_004028 und alles funktioniert.
-
@diginix Auf meinem Robi der ersten Generation (heißt der 1S?) läuft 3.5.8_004028 und alles funktioniert.
@thomas-braun Ne der 1S war der Nachfolger mit Kartenspeicherung und Raumaufteilung. Der hat zusätzlich einen TOF-Sensor im Deckel
Das Update gibt es erst ein paar Tage. Davor war 3.5.4_0948 die aktuelle Version.
Vom Roboter Forum haben schon welche aktualisiert und bei mind. einem mit OpenHAB funktioniert noch alles. Ich warte mal noch bissel. Wirkliche Mehrwerte bringt das Update ohnehin nicht.Edit: Update erfolgreich durchgeführt und 1S weiterhin über Adapter wie zuvor nutzbar.
-
Moin!
Nachdem einige Wochen der Adapter problemlos funktionierte, stürzt er nun an einem erfolgreich Übermittelten Befehl ab. Hat dazu jemand einen Tipp?
Neuinstallation des Adpaters und Reboot des Saugroboters haben nichts gebracht...
mihome-vacuum.0 2020-11-18 13:45:13.301 debug (22494) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0 mihome-vacuum.0 2020-11-18 13:45:13.300 info (22494) connecting, this can take up to 10 minutes ... mihome-vacuum.0 2020-11-18 13:45:13.296 debug (22494) Receive <<< Helo <<< 213100200000000013272a775fb51759ffffffffffffffffffffffffffffffff mihome-vacuum.0 2020-11-18 13:45:13.285 info (22494) New generation or new fw(3.5.8,2516) detected, create new states goto and zoneclean mihome-vacuum.0 2020-11-18 13:45:13.283 info (22494) extend state mop for State control.fan_power mihome-vacuum.0 2020-11-18 13:45:13.271 info (22494) change states from State control.fan_power mihome-vacuum.0 2020-11-18 13:45:13.239 debug (22494) server started on 0.0.0.0:53421 mihome-vacuum.0 2020-11-18 13:45:13.232 info (22494) Cloud control disabled mihome-vacuum.0 2020-11-18 13:45:13.231 info (22494) Expert mode disabled, states deleted mihome-vacuum.0 2020-11-18 13:45:13.226 debug (22494) Xiaomi Cloud: Logging in mihome-vacuum.0 2020-11-18 13:45:13.224 debug (22494) load Map creator... true mihome-vacuum.0 2020-11-18 13:45:13.169 info (22494) starting. Version 2.1.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v12.19.1, js-controller: 3.1.6 mihome-vacuum.0 2020-11-18 13:44:40.465 info (22435) Terminated (NO_ERROR): Without reason mihome-vacuum.0 2020-11-18 13:44:40.464 info (22435) terminating mihome-vacuum.0 2020-11-18 13:44:40.457 error (22435) TypeError: Cannot read property 'val' of null at /opt/iobroker/node_modules/iobroker.mihome-vacuum/main.js:187:68 at /opt/iobroker/node_modules/iobroker.js-controller/lib/states/states mihome-vacuum.0 2020-11-18 13:44:40.456 error (22435) uncaught exception: Cannot read property 'val' of null mihome-vacuum.0 2020-11-18 13:44:40.454 debug (22435) sendMsg[1] >>> {"id":29,"method":"app_segment_clean","params":[19]} mihome-vacuum.0 2020-11-18 13:44:40.453 info (22435) trigger cleaning segment 19 mihome-vacuum.0 2020-11-18 13:44:40.449 debug (22435) sendTo "cleanSegments" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0 mihome-vacuum.0 2020-11-18 13:44:40.447 debug (22435) stateChange mihome-vacuum.0.rooms.717001010826.roomClean {"val":true,"ack":false,"ts":1605703480443,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1605684698520} mihome-vacuum.0 2020-11-18 13:44:33.763 debug (22435) CLEAN_LOGGING[{"Datum":"18.11","Start":"13:12","Saugzeit":"4 min","Fläche":"7.46 m²","Error":0,"Ende":false},{"Datum":"18.11","Start":"13:01","Saugzeit":"11 min","Fläche":"15.31 m²","Error":0,Nach einem neuem Befehl wieder direkter Absturz...
mihome-vacuum.0 2020-11-18 13:49:20.617 info (22494) Terminated (NO_ERROR): Without reason mihome-vacuum.0 2020-11-18 13:49:20.616 info (22494) terminating mihome-vacuum.0 2020-11-18 13:49:20.608 error (22494) TypeError: Cannot read property 'val' of null at /opt/iobroker/node_modules/iobroker.mihome-vacuum/main.js:187:68 at /opt/iobroker/node_modules/iobroker.js-controller/lib/states/states mihome-vacuum.0 2020-11-18 13:49:20.607 error (22494) uncaught exception: Cannot read property 'val' of null mihome-vacuum.0 2020-11-18 13:49:20.605 debug (22494) sendMsg[1] >>> {"id":14,"method":"app_segment_clean","params":[19]} mihome-vacuum.0 2020-11-18 13:49:20.604 info (22494) trigger cleaning segment 19EDIT:
Auch ein komplettes Update nach dieser Anleitung
https://forum.iobroker.net/topic/37020/nodejs-update-iobroker-installation-via-curl-nicht-möglich/51
hat nichts geändert...@maeuseking sagte in Test Adapter mihome-vacuum v2.0.x:
Moin!
Nachdem einige Wochen der Adapter problemlos funktionierte, stürzt er nun an einem erfolgreich Übermittelten Befehl ab. Hat dazu jemand einen Tipp?
Neuinstallation des Adpaters und Reboot des Saugroboters haben nichts gebracht...
mihome-vacuum.0 2020-11-18 13:45:13.301 debug (22494) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0 mihome-vacuum.0 2020-11-18 13:45:13.300 info (22494) connecting, this can take up to 10 minutes ... mihome-vacuum.0 2020-11-18 13:45:13.296 debug (22494) Receive <<< Helo <<< 213100200000000013272a775fb51759ffffffffffffffffffffffffffffffff mihome-vacuum.0 2020-11-18 13:45:13.285 info (22494) New generation or new fw(3.5.8,2516) detected, create new states goto and zoneclean mihome-vacuum.0 2020-11-18 13:45:13.283 info (22494) extend state mop for State control.fan_power mihome-vacuum.0 2020-11-18 13:45:13.271 info (22494) change states from State control.fan_power mihome-vacuum.0 2020-11-18 13:45:13.239 debug (22494) server started on 0.0.0.0:53421 mihome-vacuum.0 2020-11-18 13:45:13.232 info (22494) Cloud control disabled mihome-vacuum.0 2020-11-18 13:45:13.231 info (22494) Expert mode disabled, states deleted mihome-vacuum.0 2020-11-18 13:45:13.226 debug (22494) Xiaomi Cloud: Logging in mihome-vacuum.0 2020-11-18 13:45:13.224 debug (22494) load Map creator... true mihome-vacuum.0 2020-11-18 13:45:13.169 info (22494) starting. Version 2.1.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v12.19.1, js-controller: 3.1.6 mihome-vacuum.0 2020-11-18 13:44:40.465 info (22435) Terminated (NO_ERROR): Without reason mihome-vacuum.0 2020-11-18 13:44:40.464 info (22435) terminating mihome-vacuum.0 2020-11-18 13:44:40.457 error (22435) TypeError: Cannot read property 'val' of null at /opt/iobroker/node_modules/iobroker.mihome-vacuum/main.js:187:68 at /opt/iobroker/node_modules/iobroker.js-controller/lib/states/states mihome-vacuum.0 2020-11-18 13:44:40.456 error (22435) uncaught exception: Cannot read property 'val' of null mihome-vacuum.0 2020-11-18 13:44:40.454 debug (22435) sendMsg[1] >>> {"id":29,"method":"app_segment_clean","params":[19]} mihome-vacuum.0 2020-11-18 13:44:40.453 info (22435) trigger cleaning segment 19 mihome-vacuum.0 2020-11-18 13:44:40.449 debug (22435) sendTo "cleanSegments" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0 mihome-vacuum.0 2020-11-18 13:44:40.447 debug (22435) stateChange mihome-vacuum.0.rooms.717001010826.roomClean {"val":true,"ack":false,"ts":1605703480443,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1605684698520} mihome-vacuum.0 2020-11-18 13:44:33.763 debug (22435) CLEAN_LOGGING[{"Datum":"18.11","Start":"13:12","Saugzeit":"4 min","Fläche":"7.46 m²","Error":0,"Ende":false},{"Datum":"18.11","Start":"13:01","Saugzeit":"11 min","Fläche":"15.31 m²","Error":0,Nach einem neuem Befehl wieder direkter Absturz...
mihome-vacuum.0 2020-11-18 13:49:20.617 info (22494) Terminated (NO_ERROR): Without reason mihome-vacuum.0 2020-11-18 13:49:20.616 info (22494) terminating mihome-vacuum.0 2020-11-18 13:49:20.608 error (22494) TypeError: Cannot read property 'val' of null at /opt/iobroker/node_modules/iobroker.mihome-vacuum/main.js:187:68 at /opt/iobroker/node_modules/iobroker.js-controller/lib/states/states mihome-vacuum.0 2020-11-18 13:49:20.607 error (22494) uncaught exception: Cannot read property 'val' of null mihome-vacuum.0 2020-11-18 13:49:20.605 debug (22494) sendMsg[1] >>> {"id":14,"method":"app_segment_clean","params":[19]} mihome-vacuum.0 2020-11-18 13:49:20.604 info (22494) trigger cleaning segment 19EDIT:
Auch ein komplettes Update nach dieser Anleitung
https://forum.iobroker.net/topic/37020/nodejs-update-iobroker-installation-via-curl-nicht-möglich/51
hat nichts geändert...Das Problem besteht bei mir noch immer. Hat jemand dazu eine Idee?
Loxone Miniserver Gen 1 / 1 Relay Extension / 2 Extension / 1 Air Extension / 1 1-Wire-Extension / 1 RS485 Extension
1 Pi4 als ioBroker-Server und zur Visualisierung an einem HP E230t Monitor
-
@maeuseking sagte in Test Adapter mihome-vacuum v2.0.x:
Moin!
Nachdem einige Wochen der Adapter problemlos funktionierte, stürzt er nun an einem erfolgreich Übermittelten Befehl ab. Hat dazu jemand einen Tipp?
Neuinstallation des Adpaters und Reboot des Saugroboters haben nichts gebracht...
mihome-vacuum.0 2020-11-18 13:45:13.301 debug (22494) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0 mihome-vacuum.0 2020-11-18 13:45:13.300 info (22494) connecting, this can take up to 10 minutes ... mihome-vacuum.0 2020-11-18 13:45:13.296 debug (22494) Receive <<< Helo <<< 213100200000000013272a775fb51759ffffffffffffffffffffffffffffffff mihome-vacuum.0 2020-11-18 13:45:13.285 info (22494) New generation or new fw(3.5.8,2516) detected, create new states goto and zoneclean mihome-vacuum.0 2020-11-18 13:45:13.283 info (22494) extend state mop for State control.fan_power mihome-vacuum.0 2020-11-18 13:45:13.271 info (22494) change states from State control.fan_power mihome-vacuum.0 2020-11-18 13:45:13.239 debug (22494) server started on 0.0.0.0:53421 mihome-vacuum.0 2020-11-18 13:45:13.232 info (22494) Cloud control disabled mihome-vacuum.0 2020-11-18 13:45:13.231 info (22494) Expert mode disabled, states deleted mihome-vacuum.0 2020-11-18 13:45:13.226 debug (22494) Xiaomi Cloud: Logging in mihome-vacuum.0 2020-11-18 13:45:13.224 debug (22494) load Map creator... true mihome-vacuum.0 2020-11-18 13:45:13.169 info (22494) starting. Version 2.1.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v12.19.1, js-controller: 3.1.6 mihome-vacuum.0 2020-11-18 13:44:40.465 info (22435) Terminated (NO_ERROR): Without reason mihome-vacuum.0 2020-11-18 13:44:40.464 info (22435) terminating mihome-vacuum.0 2020-11-18 13:44:40.457 error (22435) TypeError: Cannot read property 'val' of null at /opt/iobroker/node_modules/iobroker.mihome-vacuum/main.js:187:68 at /opt/iobroker/node_modules/iobroker.js-controller/lib/states/states mihome-vacuum.0 2020-11-18 13:44:40.456 error (22435) uncaught exception: Cannot read property 'val' of null mihome-vacuum.0 2020-11-18 13:44:40.454 debug (22435) sendMsg[1] >>> {"id":29,"method":"app_segment_clean","params":[19]} mihome-vacuum.0 2020-11-18 13:44:40.453 info (22435) trigger cleaning segment 19 mihome-vacuum.0 2020-11-18 13:44:40.449 debug (22435) sendTo "cleanSegments" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0 mihome-vacuum.0 2020-11-18 13:44:40.447 debug (22435) stateChange mihome-vacuum.0.rooms.717001010826.roomClean {"val":true,"ack":false,"ts":1605703480443,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1605684698520} mihome-vacuum.0 2020-11-18 13:44:33.763 debug (22435) CLEAN_LOGGING[{"Datum":"18.11","Start":"13:12","Saugzeit":"4 min","Fläche":"7.46 m²","Error":0,"Ende":false},{"Datum":"18.11","Start":"13:01","Saugzeit":"11 min","Fläche":"15.31 m²","Error":0,Nach einem neuem Befehl wieder direkter Absturz...
mihome-vacuum.0 2020-11-18 13:49:20.617 info (22494) Terminated (NO_ERROR): Without reason mihome-vacuum.0 2020-11-18 13:49:20.616 info (22494) terminating mihome-vacuum.0 2020-11-18 13:49:20.608 error (22494) TypeError: Cannot read property 'val' of null at /opt/iobroker/node_modules/iobroker.mihome-vacuum/main.js:187:68 at /opt/iobroker/node_modules/iobroker.js-controller/lib/states/states mihome-vacuum.0 2020-11-18 13:49:20.607 error (22494) uncaught exception: Cannot read property 'val' of null mihome-vacuum.0 2020-11-18 13:49:20.605 debug (22494) sendMsg[1] >>> {"id":14,"method":"app_segment_clean","params":[19]} mihome-vacuum.0 2020-11-18 13:49:20.604 info (22494) trigger cleaning segment 19EDIT:
Auch ein komplettes Update nach dieser Anleitung
https://forum.iobroker.net/topic/37020/nodejs-update-iobroker-installation-via-curl-nicht-möglich/51
hat nichts geändert...Das Problem besteht bei mir noch immer. Hat jemand dazu eine Idee?
@maeuseking System inkl. NodeJS und ioBroker auf Stand bringen, beobachten, dann ggf. nochmal fragen.
-
heute hatte ich folgendes Problem:
- aus mir nicht erfindlichen Gründen hatte sich der Staubsauger selbstständig auf die Werkseinstellungen zurückgesetzt
- ich mußte ihn in der APP komplett neu installieren
- dabei war natürlich der alte Token verloren gegangen
- es gelang mir nicht, den "Xiaomi cloud login" ans Laufen zu bekommen
- es blieb dann nur der sehr umständliche Weg über das iphone Backup den neuen Token zu finden
Daher zwei Fragen:
Hattet ihr das auch schon mal, daß sich der Sauger selstständig auf die Werkseinstellungen zurückgesetzt hat?Funktioniert momentan der Cloud Login nicht?
PS: installierte Version ist die 2.1.1
Support us
590
Online32.5k
Benutzer81.6k
Themen1.3m
Beiträge