search

mrbungle64 / ioBroker.ecovacs-deebot

Control your Ecovacs Deebot and yeedi vacuum cleaner with ioBroker
MIT License
65 stars 11 forks source link

Deebot Ozmo 950 #7

Closed gigasi closed 4 years ago

gigasi commented 4 years ago

Hallo, wird es irgendwann auch mal ein Support für Deebot Ozmo 950 geben?

mrbungle64 commented 4 years ago

pi@raspberrypi:~/ecovacs-deebot.js/example $ NODE_ENV=dev node app2.js eu [EcovacsAPI] Setting up EcovacsAPI ... /home/pi/ecovacs-deebot.js/library/ecovacsMQTT.js:335 let result = tools.xmlDocumentElement2Json(xml.documentElement); ^

TypeError: tools.xmlDocumentElement2Json is not a function

ok, danke @gigasi. Bugfix dafür steht bereit :)

gigasi commented 4 years ago

Kann ich mal die Beiträge von mir löschen (die so lang sind) ?

mrbungle64 commented 4 years ago

Kann ich mal die Beiträge von mir löschen (die so lang sind) ?

Ja kannst Du gerne machen.

Ich muss jetzt übrigens für heute hier Schluss machen - für mich geht es dann morgen weiter :)

gigasi commented 4 years ago

@mrbungle64 vielen dank!

krobipd commented 4 years ago

vielen dank für deine tolle arbeit und das schnelle hinzufügen. freut mich mega. hab jetzt einen git clone von deiner library und die alte ersetzt.

ich kann den roboter gar nicht damit steuern, wenn ich aber via app einen saugvorgang mache bekomme ich folgende fehlermeldung im iobroker log zusehen.

2020-02-08 22:35:03.679 - error: host.krobis-iotvm Caught by controller[0]: TypeError: Cannot read property 'nodeName' of null

2020-02-08 22:35:03.679 - error: host.krobis-iotvm Caught by controller[0]: at Object.xmlDocumentElement2Json (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/ecovacs-deebot/library/tools.js:11:18) 2020-02-08 22:35:03.679 - error: host.krobis-iotvm Caught by controller[0]: at EcovacsMQTT._ctl_to_dict_mqtt (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/ecovacs-deebot/library/ecovacsMQTT.js:335:28) 2020-02-08 22:35:03.680 - error: host.krobis-iotvm Caught by controller[0]: at EcovacsMQTT._handle_ctl_mqtt (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/ecovacs-deebot/library/ecovacsMQTT.js:317:28) 2020-02-08 22:35:03.680 - error: host.krobis-iotvm Caught by controller[0]: at MqttClient.EcovacsMQTT.client.on (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/ecovacs-deebot/library/ecovacsMQTT.js:83:18) 2020-02-08 22:35:03.680 - error: host.krobis-iotvm Caught by controller[0]: at MqttClient.emit (events.js:198:13) 2020-02-08 22:35:03.680 - error: host.krobis-iotvm Caught by controller[0]: at MqttClient._handlePublish (/opt/iobroker/node_modules/mqtt/lib/client.js:1162:12) 2020-02-08 22:35:03.680 - error: host.krobis-iotvm Caught by controller[0]: at MqttClient._handlePacket (/opt/iobroker/node_modules/mqtt/lib/client.js:351:12) 2020-02-08 22:35:03.680 - error: host.krobis-iotvm Caught by controller[0]: at work (/opt/iobroker/node_modules/mqtt/lib/client.js:283:12) 2020-02-08 22:35:03.680 - error: host.krobis-iotvm Caught by controller[0]: at Writable.writable._write (/opt/iobroker/node_modules/mqtt/lib/client.js:294:5) 2020-02-08 22:35:03.680 - error: host.krobis-iotvm Caught by controller[0]: at doWrite (/opt/iobroker/node_modules/mqtt/node_modules/readable-stream/lib/_stream_writable.js:428:64)

boriswerner commented 4 years ago

Hi, ich hab gerade mal versucht zu testen, aber nach jedem Kommando bricht er mit dem folgenden Fehler ab: 11 json[element.nodeName] = {};

TypeError: Cannot read property 'nodeName' of null at Object.xmlDocumentElement2Json (/home/myuser/ecovacs-deebot.js/library/tools.js:11:18) at EcovacsMQTT._message_to_dict (/home/myuser/ecovacs-deebot.js/library/ecovacsMQTT.js:363:32) at EcovacsMQTT._handle_message (/home/myuser/ecovacs-deebot.js/library/ecovacsMQTT.js:318:28) at MqttClient.EcovacsMQTT.client.on (/home/myuser/ecovacs-deebot.js/library/ecovacsMQTT.js:83:18) at MqttClient.emit (events.js:198:13) at MqttClient._handlePublish (/home/myuser/ecovacs-deebot.js/node_modules/mqtt/lib/client.js:1162:12) at MqttClient._handlePacket (/home/myuser/ecovacs-deebot.js/node_modules/mqtt/lib/client.js:351:12) at work (/home/myuser/ecovacs-deebot.js/node_modules/mqtt/lib/client.js:283:12) at Writable.writable._write (/home/myuser/ecovacs-deebot.js/node_modules/mqtt/lib/client.js:294:5) at doWrite (/home/myuser/ecovacs-deebot.js/node_modules/readable-stream/lib/_stream_writable.js:428:64)

Die messages kommen aber an. Folgendes hab ich getestet: Bereichsreinigung der Bereiche A und C auf aktueller Karte (Kartenname "EG", es sind 2 gespeichert) [EcovacsMQTT] message topic: iot/atr/onCleanInfo/e0bc19bb-8cb1-43e3-8503-e9f810e35d36/yna5xi/BTKk/j [EcovacsMQTT] message message: {"header":{"pri":1,"tzm":480,"ts":"1581236774889","ver":"0.0.1","fwVer":"1.7.6","hwVer":"0.1.1"},"body":{"data":{"trigger":"app","state":"clean",$ Dann hab ich den Bot pausiert, das Skript neugestartet und dann die Reinigung fortgesetzt: Reinigung nach Pause gestartet, da kam die gleiche Message (nur mit anderem Timestamp)

Während der Reinigung kam dann folgende Message mit der Position: [EcovacsMQTT] message topic: iot/atr/onPos/e0bc19bb-8cb1-43e3-8503-e9f810e35d36/yna5xi/BTKk/j [EcovacsMQTT] message message: {"header":{"pri":1,"tzm":480,"ts":"1581237274465","ver":"0.0.1","fwVer":"1.7.6","hwVer":"0.1.1"},"body":{"data":{"deebotPos":{"x":-3375,"y":-339,$

Da er die ständig schickt bricht immer wieder das Skript ab.

mrbungle64 commented 4 years ago

Hi, ich hab gerade mal versucht zu testen, aber nach jedem Kommando bricht er mit dem folgenden Fehler ab: 11 json[element.nodeName] = {};

TypeError: Cannot read property 'nodeName' of null at Object.xmlDocumentElement2Json (/home/myuser/ecovacs-deebot.js/library/tools.js:11:18)

Hi @boriswerner, vielen Dank!

Eigentllich dürfte der beim Ozmo 950 gar nicht zu dieser Stelle kommen ...

Kannst Du das noch mal mit den aktuellen Quellen von vor ein paar Minuten ausführen? Es wäre vor allem die Ausgabe interessant die folgendermaßen beginnt:

[EcovacsMQTT] _message_to_dict xmlOrJson:
boriswerner commented 4 years ago

Ich hatte in der API einfach mal den Part auskommentiert, damit er nur loggt: // this._handle_message(topic.toString(), message.toString()); // this.client.end(); Daraufhin bekomme ich die messages auf jeden Fall ausgegeben, das hier scheint das Update während eines laufenden Wischvorgangs zu sein, das wiederholt sich ständig: [EcovacsMQTT] message topic: iot/atr/onCleanInfo/e0bc19bb-8cb1-43e3-8503-e9f810e35d36/yna5xi/BTKk/j [EcovacsMQTT] message message: {"header":{"pri":1,"tzm":480,"ts":"1581239575607","ver":"0.0.1","fwVer":"1.7.6","hwVer":"0.1.1"},"body":{"data":{"trigger":"app","state":"clean","cleanState":{"id":"122","router":"plan","type":"spotArea","content":"2","motionState":"working"}}}} [EcovacsMQTT] message topic: iot/atr/onMapTrace/e0bc19bb-8cb1-43e3-8503-e9f810e35d36/yna5xi/BTKk/j [EcovacsMQTT] message message: {"header":{"pri":1,"tzm":480,"ts":"1581239575678","ver":"0.0.1","fwVer":"1.7.6","hwVer":"0.1.1"},"body":{"data":{"tid":"547838","totalCount":0,"traceStart":0,"pointCount":0,"traceValue":""}}} [EcovacsMQTT] message topic: iot/atr/onChargeState/e0bc19bb-8cb1-43e3-8503-e9f810e35d36/yna5xi/BTKk/j [EcovacsMQTT] message message: {"header":{"pri":1,"tzm":480,"ts":"1581239582532","ver":"0.0.1","fwVer":"1.7.6","hwVer":"0.1.1"},"body":{"data":{"isCharging":0,"mode":"slot"}}} [EcovacsMQTT] message topic: iot/atr/onMajorMap/e0bc19bb-8cb1-43e3-8503-e9f810e35d36/yna5xi/BTKk/j [EcovacsMQTT] message message: {"header":{"pri":1,"tzm":480,"ts":"1581239585682","ver":"0.0.1","fwVer":"1.7.6","hwVer":"0.1.1"},"body":{"data":{"mid":"1260001067","pieceWidth":100,"pieceHeight":100,"cellWidth":8,"cellHeight":8,"pixel":50,"value":"1295764014,1295764014,1295764014,1295764014,1295764014,1295764014,1295764014,1295764014,1295764014,1295764014,1295764014,1295764014,1295764014,1295764014,1295764014,1295764014,1295764014,1295764014,894020574,1295764014,1295764014,1295764014,1295764014,1295764014,1295764014,1295764014,2245315312,1907130790,1076237138,1295764014,1295764014,1295764014,1295764014,1295764014,620384341,3593048229,3091038444,1295764014,1295764014,1295764014,1295764014,1295764014,1295764014,1256977222,4109728410,1295764014,1295764014,1295764014,1295764014,1295764014,1295764014,1295764014,1295764014,1295764014,1295764014,1295764014,1295764014,1295764014,1295764014,1295764014,1295764014,1295764014,1295764014,1295764014","type":"ol"}}} [EcovacsMQTT] message topic: iot/atr/onMinorMap/e0bc19bb-8cb1-43e3-8503-e9f810e35d36/yna5xi/BTKk/j [EcovacsMQTT] message message: {"header":{"pri":1,"tzm":480,"ts":"1581239585686","ver":"0.0.1","fwVer":"1.7.6","hwVer":"0.1.1"},"body":{"data":{"mid":"1260001067","pieceIndex":27,"pieceValue":"XQAABAAQJwAAAABv/f//o7f/Rz5H/2awMpbj4Ee8DGbaGvRZLdo1lQETzBmf3qje4nki7Y7cJdSsOS0QbCLY0Rmj015GGkytuKZnt5zfQykaRA31aJVLru2DG+oIvFSEKdExQN9h9mH+MQ2cWFXfsh1O9YyRcjOipWWBLVwa9xX8G+BnAdZiaESStNkg0cB0MYEuMLp4IrbD04KrAPZMzgyhyQ1Y3S7R+SWSFy8IFI9uYezzvaPBYOrFetYvUIBh0cl48rV+dEvL/JEscHx2yZEjUmZBq2Fursv4g5P6xF9dA66L7/NPJpQJJnD55FLInJOTwCS98cjDnFWFbr9YjLM1gCP8f3NhhiXKLxkq5tAF2Eg4hmCWuYw7CFnSDqJtLHMP7UZ/0KQ1qggekcmObjDFgV7AEzvBdr294MEgEzw0X/owl37tjIGOZxc/RCcpVrcVCKBJpRFjgT3rMF9oZ0rhvb4ViNTApkTQI6/ObxYv0pZUkxo2Pi2G5VWaS8M3gByWY47TilEMxlFSN/ZgUmMFBoBuFDyjBZQBHD1j/rsZU+hptEv6SjtWmvfStUe5jZHbw8+u/1fdjThVuESyGXSeR4oM9P+tc6JUGVdSvPGthK8p7a7aMVAU67fA5xeDrLfRZiI81Lk6brTPIchJyN8+nF52bnsEP3+Lfkm+gQZoUsN5BuYm9Ph3Lguaz9R8q+LlRxg/XPWv8wZ3TK8HAeo8wHtsF36/pbDdHbV7/7nNF3CiHwyF3Pxa9chiMgxK2sfiwoaOXvaJzBQzq798qsWAUSQVNS+nnPinaaVK9F766Xw0dEaPkeMw07sJziaHc69zSynqJoYrlvArY3iisfAIjl6MRmoDbioCnhnWWal2SKF+7DfaOOo66VFwkJRD2HUbiJSRHOQqsMK1dwHSBeIJiF0ULOmmfPhShH2/no++Cvf9SUaPKuW4u4sPGcMso/ugpjIOSP5tbgTg5g=="}}} [EcovacsMQTT] message topic: iot/atr/onMinorMap/e0bc19bb-8cb1-43e3-8503-e9f810e35d36/yna5xi/BTKk/j [EcovacsMQTT] message message: {"header":{"pri":1,"tzm":480,"ts":"1581239585688","ver":"0.0.1","fwVer":"1.7.6","hwVer":"0.1.1"},"body":{"data":{"mid":"1260001067","pieceIndex":28,"pieceValue":"XQAABAAQJwAAAABv/f//o7f/Rz4LmtqRWy5jzE3bfGDyvWIN/oWGsdOKEQs7WgcXUt0M6kZI4hLPOpa8Q1erDbPZc+U62SEGJa8JQK6iCAuYwOaP+MN9cGx/6S+wf4BYvAGbWkwuwQbzMUkUBA3ahZPowza0yXxwnKQRhYc6VsUMrIXkxEAX9JWH7z+P7KmkQL6RUmC1ttjCNnAX5LRVvVle0tragZje1dInBmBl5vOsc4P8DybQ0r0scUw="}}} [EcovacsMQTT] message topic: iot/atr/reportStats/e0bc19bb-8cb1-43e3-8503-e9f810e35d36/yna5xi/BTKk/j

Mit deinem neuen Code kommt folgendes vor dem Fehler: [EcovacsMQTT] _message_to_dict topic: iot/atr/onCleanInfo/e0bc19bb-8cb1-43e3-8503-e9f810e35d36/yna5xi/BTKk/j [EcovacsMQTT] _message_to_dict xmlOrJson: {"header":{"pri":1,"tzm":480,"ts":"1581240014265","ver":"0.0.1","fwVer":"1.7.6","hwVer":"0.1.1"},"body":{"data":{"trigger":"app","state":"clean","cleanState":{"id":"122","router":"plan","type":"spotArea","content":"2","motionState":"working"}}}}

mrbungle64 commented 4 years ago

@boriswerner ok, ich denke dass man es mit dem gerade aktualisierten Code noch mal probieren könnte :)

Interessant wäre u.a. auch ob irgendwo die Ausgabe

[VacBot] Ozmo 950 detected

kommmt

boriswerner commented 4 years ago

Die Ausgabe kommt relativ oft (bei jedem Command) [VacBot] Sending command GetBatteryInfo [VacBot] deviceClass: yna5xi [VacBot] Ozmo 950 detected [EcovacsMQTT] c: {"auth":{"realm":"ecouser.net","resource":"REPLACED_RESOURCE","token":"REPLACED_TOKEN","userid":"REPLACED_USERID","with":"users"},"cmdName":"GetBatteryInfo","payload":[],"payloadType":"j","td":"q","toId":"e0bc19bb-8cb1-43e3-8503-e9f810e35d36","toRes":"BTKk","toType":"yna5xi"} [VacBot] deviceClass: yna5xi [VacBot] Ozmo 950 detected

Danach gibt es nach der ersten Message allerdings wieder einen Fehler: [EcovacsMQTT] message topic: iot/atr/onRelocationState/e0bc19bb-8cb1-43e3-8503-e9f810e35d36/yna5xi/BTKk/j [EcovacsMQTT] message message: {"header":{"pri":1,"tzm":480,"ts":"1581244396638","ver":"0.0.1","fwVer":"1.7.6","hwVer":"0.1.1"},"body":{"data":{"mode":"lift","state":"start","isHasMap":1}}} [EcovacsMQTT] _message_to_dict JSON: [object Object] /home/myuser/ecovacs-deebot.js/library/ecovacsMQTT.js:420 command = command.replace("Get", "").toLowerCase(); ^

TypeError: Cannot read property 'replace' of undefined at EcovacsMQTT._handle_command (/home/myuser/ecovacs-deebot.js/library/ecovacsMQTT.js:420:27) at EcovacsMQTT._handle_message (/home/myuser/ecovacs-deebot.js/library/ecovacsMQTT.js:329:18) at MqttClient.EcovacsMQTT.client.on (/home/myuser/ecovacs-deebot.js/library/ecovacsMQTT.js:83:18) at MqttClient.emit (events.js:198:13) at MqttClient._handlePublish (/home/myuser/ecovacs-deebot.js/node_modules/mqtt/lib/client.js:1162:12) at MqttClient._handlePacket (/home/myuser/ecovacs-deebot.js/node_modules/mqtt/lib/client.js:351:12) at work (/home/myuser/ecovacs-deebot.js/node_modules/mqtt/lib/client.js:283:12) at Writable.writable._write (/home/myuser/ecovacs-deebot.js/node_modules/mqtt/lib/client.js:294:5) at doWrite (/home/myuser/ecovacs-deebot.js/node_modules/readable-stream/lib/_stream_writable.js:428:64) at writeOrBuffer (/home/myuser/ecovacs-deebot.js/node_modules/readable-stream/lib/_stream_writable.js:417:5)

mrbungle64 commented 4 years ago

Danach gibt es nach der ersten Message allerdings wieder einen Fehler: [EcovacsMQTT] message topic: iot/atr/onRelocationState/e0bc19bb-8cb1-43e3-8503-e9f810e35d36/yna5xi/BTKk/j [EcovacsMQTT] message message: {"header":{"pri":1,"tzm":480,"ts":"1581244396638","ver":"0.0.1","fwVer":"1.7.6","hwVer":"0.1.1"},"body":{"data":{"mode":"lift","state":"start","isHasMap":1}}} [EcovacsMQTT] _message_to_dict JSON: [object Object] /home/myuser/ecovacs-deebot.js/library/ecovacsMQTT.js:420 command = command.replace("Get", "").toLowerCase(); ^

TypeError: Cannot read property 'replace' of undefined at EcovacsMQTT._handle_command (/home/myuser/ecovacs-deebot.js/library/ecovacsMQTT.js:420:27)

@boriswerner, der Fehler sollte jetzt behoben sein und werden hoffentlich die Werte zu (u.a.) CleanReport, ChargeState, BatteryInfo korrekt behandelt und auch ausgegeben :)

boriswerner commented 4 years ago

Hm, der Fehler ist leider immer noch da, nur 2 Zeilen weiter unten:

[EcovacsMQTT] _message_to_dict JSON: [object Object] [EcovacsMQTT] as_dict: [object Object] [EcovacsMQTT] command: undefined /home/pi/ecovacs-deebot.js/library/ecovacsMQTT.js:422 command = command.replace("Get", "").toLowerCase(); ^

TypeError: Cannot read property 'replace' of undefined at EcovacsMQTT._handle_command (/home/pi/ecovacs-deebot.js/library/ecovacsMQTT.js:422:27) at EcovacsMQTT._handle_message (/home/pi/ecovacs-deebot.js/library/ecovacsMQTT.js:331:18) at MqttClient.EcovacsMQTT.client.on (/home/pi/ecovacs-deebot.js/library/ecovacsMQTT.js:83:18) at MqttClient.emit (events.js:198:13) at MqttClient._handlePublish (/home/pi/ecovacs-deebot.js/node_modules/mqtt/lib/client.js:1162:12) at MqttClient._handlePacket (/home/pi/ecovacs-deebot.js/node_modules/mqtt/lib/client.js:351:12) at work (/home/pi/ecovacs-deebot.js/node_modules/mqtt/lib/client.js:283:12) at Writable.writable._write (/home/pi/ecovacs-deebot.js/node_modules/mqtt/lib/client.js:294:5) at doWrite (/home/pi/ecovacs-deebot.js/node_modules/readable-stream/lib/_stream_writable.js:428:64) at writeOrBuffer (/home/pi/ecovacs-deebot.js/node_modules/readable-stream/lib/_stream_writable.js:417:5)

mrbungle64 commented 4 years ago

Hm, der Fehler ist leider immer noch da, nur 2 Zeilen weiter unten:

@boriswerner, sorry - das sind alles Codestellen wo der bei meinen Geräten gar nicht hinkommt weil der MQTT-Server in diesem Fall nichts zurückliefert ;)

Ich habe das Logging noch mal verbessert/angepasst und den Laufzeitfehler auch (hoffentlich) abgefangen ...

Ich hoffe wir finden das jetzt mal raus wo es aktuell klemmt :)

Btw: kommt eigentlich der failure code 500 noch?

mrbungle64 commented 4 years ago

Es wäre übrigens auch interessant zu wissen, ob das Polling bei den MQTT Geräten (u.a. der Ozmo 950 und auch Ozmo 900) notwendig ist:

Das könnte man testen, in dem man das setInterval in der app2j.s entfernt:

        // let interval = setInterval(() => {
            vacbot.run('GetCleanState');
            vacbot.run('GetChargeState');
            vacbot.run('GetBatteryState');
        // }, 15000);

Danach sollte sich z.B. der BatteryState noch ändern, wenn das Gerät aktiv ist oder geräde lädt.

Vielleicht kann das ja einer von Euch mal testen :)

boriswerner commented 4 years ago

Vielen Dank weiterhin für die Mühe. Ich komme leider im Moment nicht dazu mich da weiter reinzuarbeiten, sonst würde ich auch selbst mal was anpassen und testen.

Der failure code 500 kommt weiterhin.

Das Logging scheint mir weniger geworden zu sein oder irgendwas funktioniert noch nicht so richtig. Ich bekomme eine Meldung, wenn ich die Reinigung starte, danach keine mehr: [EcovacsMQTT] _message_to_dict JSON: {"header":{"pri":1,"tzm":480,"ts":"1581252398406","ver":"0.0.1","fwVer":"1.7.6","hwVer":"0.1.1"},"body":{"data":{"trigger":"app","state":"clean","cleanState":{"id":"122","router":"plan","type":"customArea","content":"-841.000000,10.000000,295.000000,-1746.000000","count":1,"motionState":"working"}}}} [EcovacsMQTT] _message_to_dict body: {"data":{"trigger":"app","state":"clean","cleanState":{"id":"122","router":"plan","type":"customArea","content":"-841.000000,10.000000,295.000000,-1746.000000","count":1,"motionState":"working"}}} [EcovacsMQTT] _message_to_dict no command detected [EcovacsMQTT] as_dict: {"header":{"pri":1,"tzm":480,"ts":"1581252398406","ver":"0.0.1","fwVer":"1.7.6","hwVer":"0.1.1"},"body":{"data":{"trigger":"app","state":"clean","cleanState":{"id":"122","router":"plan","type":"customArea","content":"-841.000000,10.000000,295.000000,-1746.000000","count":1,"motionState":"working"}}}} [VacBot] action: GetCleanState //dann wieder weiter mit den Gets

Ich hatte vorhin zum Testen im this.client.on('message', (topic, message) auch mal das this.client.end(); auskommentiert, dann hatte er weiterhin messages ausgeworfen (s.o., u.a. mit der aktuellen Position). Muss der ggf. erst beim Schließen des Skripts geschlossen werden? Ich hatte versucht, da eine onStop-Methode reinzubringen, der den am Ende schließt, habs aber auf die schnelle nicht hinbekommen.

Ich kommentiere übrigens weiterhin vacbot.run('Clean'); in der Beispielapp aus, vor dem Start. Gehe ich richtig in der Annahme, dass der Befehl eigentlich eine Reinigung starten soll?

mrbungle64 commented 4 years ago

Ich hatte vorhin zum Testen im this.client.on('message', (topic, message) auch mal das this.client.end(); auskommentiert, dann hatte er weiterhin messages ausgeworfen (s.o., u.a. mit der aktuellen Position). Muss der ggf. erst beim Schließen des Skripts geschlossen werden? Ich hatte versucht, da eine onStop-Methode reinzubringen, der den am Ende schließt, habs aber auf die schnelle nicht hinbekommen.

Ja das hatte ich mir auch schon überlegt. In allen Code Beispielen für das mqtt Modul war das halt so drin. Es macht schon Sinn das mal rauszunehmen - allerdings muss man das ja auch irgendwann trotzdem ausführen - da muss ich mich noch mal schlau machen.

Ich hab's jetzt aber mal entfernt - mal schauen wie sich das dann verhält :)

Ich kommentiere übrigens weiterhin vacbot.run('Clean'); in der Beispielapp aus, vor dem Start. Gehe ich richtig in der Annahme, dass der Befehl eigentlich eine Reinigung starten soll?

Ja richtig - es wäre ganz gut wenn Du das mal wieder (zumindest zeitweise) einkommentieren würdest :)

Dir auch schon mal Vielen Dank für's fleißige Testen und für die wertvollen Rückmeldungen!

gigasi commented 4 years ago

Ich bin heute Abend auch wieder dabei 😊

mrbungle64 commented 4 years ago

@gigasi, @boriswerner, @krobipd, @rebel1985 An alle, die mal die aktuelle Version der Library mit dem ioBroker testen wollen Ich habe auf Github mal die aktuelle Version vom Adapter committed (nicht über "Latest Repo" verfügbar)

https://github.com/mrbungle64/ioBroker.ecovacs-deebot.git ("Adapter" => "Adapter aus beliebiger Quelle installieren oder aktualisieren") Nicht wundern: Ist immer noch Version 0.3.4

AudidriverA4 commented 4 years ago

Hallo,

hab gerade mal neu installiert und einen Test gemacht mit Deebot 900. Die Reinigung ist mal gestartet mit Button. Dann hab ich mal zurück zur Ladestation usw getestet da ging leider nichts. Hier mal ein paar Screenshots:

Screenshot 2020-02-09 20 24 33 Screenshot 2020-02-09 20 25 04 Screenshot 2020-02-09 20 24 53
mrbungle64 commented 4 years ago

Hallo @AudidriverA4,

Hotfix ist da - bitte noch mal über Github installieren :)

AudidriverA4 commented 4 years ago

Hab nochmal neu, irgendwie wenn der Deebot startet über Button wird die Instanz Rot und logisch geht dann nichts mehr. Wenn er es wieder schafft zu verbinden dann funktioniert auch der Button zur Ladestation.

Screenshot 2020-02-09 20 56 05 Screenshot 2020-02-09 20 56 15 Screenshot 2020-02-09 20 58 07 Screenshot 2020-02-09 20 58 12
mrbungle64 commented 4 years ago

@AudidriverA4

Leider wird in den Screenshots immer die Stelle rechts abgeschnitten die die für mich wichtig wäre ;) Siehe z.B. 19:53:45 und 19:57:35 - das was nach .../ecovacs-deebot/library/ecovacs... kommt

Kannst du mir die kompletten Zeilen bitte mal hier rein kopieren? Alles was .../ecovacs-deebot/... enthält und im Screenshot abgeschnitten ist. Dankeschön :)

AudidriverA4 commented 4 years ago

ecovacs-deebot.0 2020-02-09 21:09:18.224 info (4973) Dobby successfully connected ecovacs-deebot.0 2020-02-09 21:09:16.840 info (4973) Successfully connected to Ecovacs server ecovacs-deebot.0 2020-02-09 21:09:15.348 info (4973) reconnecting (11) ... ecovacs-deebot.0 2020-02-09 21:09:10.070 info (4973) reconnecting (10) ... ecovacs-deebot.0 2020-02-09 21:09:04.774 info (4973) reconnecting (9) ... ecovacs-deebot.0 2020-02-09 21:08:59.520 info (4973) reconnecting (8) ... ecovacs-deebot.0 2020-02-09 21:08:54.448 info (4973) reconnecting (7) ... ecovacs-deebot.0 2020-02-09 21:08:49.348 info (4973) reconnecting (6) ... ecovacs-deebot.0 2020-02-09 21:08:44.240 info (4973) reconnecting (5) ... ecovacs-deebot.0 2020-02-09 20:08:39.171 info (4973) reconnecting (4) ... ecovacs-deebot.0 2020-02-09 20:08:34.113 info (4973) reconnecting (3) ... ecovacs-deebot.0 2020-02-09 20:08:29.022 info (4973) reconnecting (2) ... ecovacs-deebot.0 2020-02-09 20:08:23.948 info (4973) reconnecting (1) ... ecovacs-deebot.0 2020-02-09 20:08:18.412 info (4973) starting. Version 0.3.4 in /opt/iobroker/node_modules/iobroker.ecovacs-deebot, node: v10.17.0 ecovacs-deebot.0 2020-02-09 20:07:45.949 info (2539) Terminated (NO_ERROR): Without reason ecovacs-deebot.0 2020-02-09 20:07:45.947 info (2539) terminating ecovacs-deebot.0 2020-02-09 20:07:45.934 info (2539) cleaned everything up... ecovacs-deebot.0 2020-02-09 20:07:45.930 error at writeOrBuffer (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/readable-stream/lib/_stream_writable.js:417:5) ecovacs-deebot.0 2020-02-09 20:07:45.930 error at doWrite (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/readable-stream/lib/_stream_writable.js:428:64) ecovacs-deebot.0 2020-02-09 20:07:45.930 error at Writable.writable._write (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/mqtt/lib/client.js:294:5) ecovacs-deebot.0 2020-02-09 20:07:45.930 error at work (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/mqtt/lib/client.js:283:12) ecovacs-deebot.0 2020-02-09 20:07:45.930 error at MqttClient._handlePacket (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/mqtt/lib/client.js:351:12) ecovacs-deebot.0 2020-02-09 20:07:45.930 error at MqttClient._handlePublish (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/mqtt/lib/client.js:1162:12) ecovacs-deebot.0 2020-02-09 20:07:45.930 error at MqttClient.emit (events.js:198:13) ecovacs-deebot.0 2020-02-09 20:07:45.930 error at MqttClient.EcovacsMQTT.client.on (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/ecovacs-deebot/library/ecovacsMQTT.js:81:18) ecovacs-deebot.0 2020-02-09 20:07:45.930 error at EcovacsMQTT._handle_message (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/ecovacs-deebot/library/ecovacsMQTT.js:308:60) ecovacs-deebot.0 2020-02-09 20:07:45.930 error at JSON.stringify () ecovacs-deebot.0 2020-02-09 20:07:45.930 error (2539) TypeError: Converting circular structure to JSON ecovacs-deebot.0 2020-02-09 20:07:45.927 error (2539) uncaught exception: Converting circular structure to JSON ecovacs-deebot.0 2020-02-09 20:07:19.224 info (2539) Dobby successfully connected ecovacs-deebot.0 2020-02-09 20:07:17.936 info (2539) Successfully connected to Ecovacs server ecovacs-deebot.0 2020-02-09 20:07:16.249 info (2539) reconnecting (2) ... ecovacs-deebot.0 2020-02-09 20:07:10.975 info (2539) reconnecting (1) ... ecovacs-deebot.0 2020-02-09 20:07:05.459 info (2539) starting. Version 0.3.4 in /opt/iobroker/node_modules/iobroker.ecovacs-deebot, node: v10.17.0 ecovacs-deebot.0 2020-02-09 20:06:32.951 info (30837) Terminated (NO_ERROR): Without reason ecovacs-deebot.0 2020-02-09 20:06:32.950 info (30837) terminating ecovacs-deebot.0 2020-02-09 20:06:32.942 info (30837) cleaned everything up... ecovacs-deebot.0 2020-02-09 20:06:32.940 error at writeOrBuffer (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/readable-stream/lib/_stream_writable.js:417:5) ecovacs-deebot.0 2020-02-09 20:06:32.940 error at doWrite (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/readable-stream/lib/_stream_writable.js:428:64) ecovacs-deebot.0 2020-02-09 20:06:32.940 error at Writable.writable._write (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/mqtt/lib/client.js:294:5) ecovacs-deebot.0 2020-02-09 20:06:32.940 error at work (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/mqtt/lib/client.js:283:12) ecovacs-deebot.0 2020-02-09 20:06:32.940 error at MqttClient._handlePacket (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/mqtt/lib/client.js:351:12) ecovacs-deebot.0 2020-02-09 20:06:32.940 error at MqttClient._handlePublish (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/mqtt/lib/client.js:1162:12) ecovacs-deebot.0 2020-02-09 20:06:32.940 error at MqttClient.emit (events.js:198:13) ecovacs-deebot.0 2020-02-09 20:06:32.940 error at MqttClient.EcovacsMQTT.client.on (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/ecovacs-deebot/library/ecovacsMQTT.js:81:18) ecovacs-deebot.0 2020-02-09 20:06:32.940 error at EcovacsMQTT._handle_message (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/ecovacs-deebot/library/ecovacsMQTT.js:308:60) ecovacs-deebot.0 2020-02-09 20:06:32.940 error at JSON.stringify () ecovacs-deebot.0 2020-02-09 20:06:32.940 error (30837) TypeError: Converting circular structure to JSON ecovacs-deebot.0 2020-02-09 20:06:32.939 error (30837) uncaught exception: Converting circular structure to JSON ecovacs-deebot.0 2020-02-09 20:05:42.489 info (30837) Dobby successfully connected ecovacs-deebot.0 2020-02-09 20:05:40.863 info (30837) Successfully connected to Ecovacs server ecovacs-deebot.0 2020-02-09 20:05:39.394 info (30837) reconnecting (7) ... ecovacs-deebot.0 2020-02-09 20:05:34.165 info (30837) reconnecting (6) ... ecovacs-deebot.0 2020-02-09 20:05:28.771 info (30837) reconnecting (5) ... ecovacs-deebot.0 2020-02-09 20:05:23.501 info (30837) reconnecting (4) ... ecovacs-deebot.0 2020-02-09 20:05:18.434 info (30837) reconnecting (3) ... ecovacs-deebot.0 2020-02-09 20:05:13.264 info (30837) reconnecting (2) ... ecovacs-deebot.0 2020-02-09 20:05:08.000 info (30837) reconnecting (1) ... ecovacs-deebot.0 2020-02-09 20:05:02.536 info (30837) starting. Version 0.3.4 in /opt/iobroker/node_modules/iobroker.ecovacs-deebot, node: v10.17.0 ecovacs-deebot.0 2020-02-09 20:04:29.926 info (26775) Terminated (NO_ERROR): Without reason ecovacs-deebot.0 2020-02-09 20:04:29.925 info (26775) terminating ecovacs-deebot.0 2020-02-09 20:04:29.916 info (26775) cleaned everything up... ecovacs-deebot.0 2020-02-09 20:04:29.914 error at writeOrBuffer (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/readable-stream/lib/_stream_writable.js:417:5) ecovacs-deebot.0 2020-02-09 20:04:29.914 error at doWrite (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/readable-stream/lib/_stream_writable.js:428:64) ecovacs-deebot.0 2020-02-09 20:04:29.914 error at Writable.writable._write (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/mqtt/lib/client.js:294:5) ecovacs-deebot.0 2020-02-09 20:04:29.914 error at work (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/mqtt/lib/client.js:283:12) ecovacs-deebot.0 2020-02-09 20:04:29.914 error at MqttClient._handlePacket (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/mqtt/lib/client.js:351:12) ecovacs-deebot.0 2020-02-09 20:04:29.914 error at MqttClient._handlePublish (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/mqtt/lib/client.js:1162:12) ecovacs-deebot.0 2020-02-09 20:04:29.914 error at MqttClient.emit (events.js:198:13) ecovacs-deebot.0 2020-02-09 20:04:29.914 error at MqttClient.EcovacsMQTT.client.on (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/ecovacs-deebot/library/ecovacsMQTT.js:81:18) ecovacs-deebot.0 2020-02-09 20:04:29.914 error at EcovacsMQTT._handle_message (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/ecovacs-deebot/library/ecovacsMQTT.js:308:60) ecovacs-deebot.0 2020-02-09 20:04:29.914 error at JSON.stringify () ecovacs-deebot.0 2020-02-09 20:04:29.914 error (26775) TypeError: Converting circular structure to JSON ecovacs-deebot.0 2020-02-09 20:04:29.912 error (26775) uncaught exception: Converting circular structure to JSON ecovacs-deebot.0 2020-02-09 20:03:05.161 info (26775) Dobby successfully connected ecovacs-deebot.0 2020-02-09 20:03:03.730 info (26775) Successfully connected to Ecovacs server ecovacs-deebot.0 2020-02-09 20:03:01.874 info (26775) starting. Version 0.3.4 in /opt/iobroker/node_modules/iobroker.ecovacs-deebot, node: v10.17.0 ecovacs-deebot.0 2020-02-09 20:02:28.921 info (24732) Terminated (NO_ERROR): Without reason ecovacs-deebot.0 2020-02-09 20:02:28.920 info (24732) terminating ecovacs-deebot.0 2020-02-09 20:02:28.911 info (24732) cleaned everything up... ecovacs-deebot.0 2020-02-09 20:02:28.910 error at writeOrBuffer (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/readable-stream/lib/_stream_writable.js:417:5) ecovacs-deebot.0 2020-02-09 20:02:28.910 error at doWrite (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/readable-stream/lib/_stream_writable.js:428:64) ecovacs-deebot.0 2020-02-09 20:02:28.910 error at Writable.writable._write (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/mqtt/lib/client.js:294:5) ecovacs-deebot.0 2020-02-09 20:02:28.910 error at work (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/mqtt/lib/client.js:283:12) ecovacs-deebot.0 2020-02-09 20:02:28.910 error at MqttClient._handlePacket (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/mqtt/lib/client.js:351:12) ecovacs-deebot.0 2020-02-09 20:02:28.910 error at MqttClient._handlePublish (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/mqtt/lib/client.js:1162:12) ecovacs-deebot.0 2020-02-09 20:02:28.910 error at MqttClient.emit (events.js:198:13) ecovacs-deebot.0 2020-02-09 20:02:28.910 error at MqttClient.EcovacsMQTT.client.on (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/ecovacs-deebot/library/ecovacsMQTT.js:81:18) ecovacs-deebot.0 2020-02-09 20:02:28.910 error at EcovacsMQTT._handle_message (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/ecovacs-deebot/library/ecovacsMQTT.js:308:60) ecovacs-deebot.0 2020-02-09 20:02:28.910 error at JSON.stringify () ecovacs-deebot.0 2020-02-09 20:02:28.910 error (24732) TypeError: Converting circular structure to JSON ecovacs-deebot.0 2020-02-09 20:02:28.909 error (24732) uncaught exception: Converting circular structure to JSON ecovacs-deebot.0 2020-02-09 20:02:24.637 info (24732) Dobby successfully connected ecovacs-deebot.0 2020-02-09 20:02:22.814 info (24732) Successfully connected to Ecovacs server ecovacs-deebot.0 2020-02-09 20:02:21.059 info (24732) reconnecting (3) ... ecovacs-deebot.0 2020-02-09 20:02:15.787 info (24732) reconnecting (2) ... ecovacs-deebot.0 2020-02-09 20:02:10.495 info (24732) reconnecting (1) ... ecovacs-deebot.0 2020-02-09 20:02:05.054 info (24732) starting. Version 0.3.4 in /opt/iobroker/node_modules/iobroker.ecovacs-deebot, node: v10.17.0 ecovacs-deebot.0 2020-02-09 20:01:32.919 info (22076) Terminated (NO_ERROR): Without reason ecovacs-deebot.0 2020-02-09 20:01:32.918 info (22076) terminating ecovacs-deebot.0 2020-02-09 20:01:32.910 info (22076) cleaned everything up...

AudidriverA4 commented 4 years ago

So besser ?

mrbungle64 commented 4 years ago

So besser ?

Ja :) Danke ich schaue mir das gleich an

gigasi commented 4 years ago

So bin leider erst so spät da.... was muss ich jetzt alles neu laden um zu testen?

mrbungle64 commented 4 years ago

Hi @gigasi

So bin leider erst so spät da.... was muss ich jetzt alles neu laden um zu testen?

Ja :)

Du kannst entweder die Library weiter testen oder auch den ioBroker Adapter von Github. Habe gerade alles aktuallisiert :)

mrbungle64 commented 4 years ago

So besser ?

@AudidriverA4 Der Fehler aus deinem Log sollte in der aktuellen Version behoben sein :)

gigasi commented 4 years ago
ecovacs-deebot.0 2020-02-09 22:30:00.784 info (9948) DEEBOT950 successfully connected
ecovacs-deebot.0 2020-02-09 22:29:58.994 info (9948) Successfully connected to Ecovacs server
ecovacs-deebot.0 2020-02-09 22:29:57.037 info (9948) starting. Version 0.3.4 in /opt/iobroker/node_modules/iobroker.ecovacs-deebot, node: v10.19.0
host.raspberrypi 2020-02-09 22:29:54.517 info instance system.adapter.ecovacs-deebot.0 started with pid 9948
tankerkoenig.0 2020-02-09 22:29:44.074 info (828) Reading data from tankerkoenig ...
host.raspberrypi 2020-02-09 22:29:24.489 info Restart adapter system.adapter.ecovacs-deebot.0 because enabled
host.raspberrypi 2020-02-09 22:29:24.488 info instance system.adapter.ecovacs-deebot.0 terminated with code 0 (NO_ERROR)
host.raspberrypi 2020-02-09 22:29:24.487 error Caught by controller[8]: at Writable.write (/opt/iobroker/node_modules/readable-stream/lib/_stream_writable.js:334:11)
host.raspberrypi 2020-02-09 22:29:24.486 error Caught by controller[8]: at writeOrBuffer (/opt/iobroker/node_modules/readable-stream/lib/_stream_writable.js:417:5)
host.raspberrypi 2020-02-09 22:29:24.485 error Caught by controller[8]: at doWrite (/opt/iobroker/node_modules/readable-stream/lib/_stream_writable.js:428:64)
host.raspberrypi 2020-02-09 22:29:24.485 error Caught by controller[8]: at Writable.writable._write (/opt/iobroker/node_modules/mqtt/lib/client.js:294:5)
host.raspberrypi 2020-02-09 22:29:24.484 error Caught by controller[8]: at work (/opt/iobroker/node_modules/mqtt/lib/client.js:283:12)
host.raspberrypi 2020-02-09 22:29:24.483 error Caught by controller[8]: at MqttClient._handlePacket (/opt/iobroker/node_modules/mqtt/lib/client.js:351:12)
host.raspberrypi 2020-02-09 22:29:24.482 error Caught by controller[8]: at MqttClient._handlePublish (/opt/iobroker/node_modules/mqtt/lib/client.js:1162:12)
host.raspberrypi 2020-02-09 22:29:24.482 error Caught by controller[8]: at MqttClient.emit (events.js:198:13)
host.raspberrypi 2020-02-09 22:29:24.481 error Caught by controller[8]: at MqttClient.EcovacsMQTT.client.on (/opt/iobroker/node_modules/ecovacs-deebot/library/ecovacsMQTT.js:82:18)
host.raspberrypi 2020-02-09 22:29:24.480 error Caught by controller[8]: at EcovacsMQTT._handle_ctl_mqtt (/opt/iobroker/node_modules/ecovacs-deebot/library/ecovacsMQTT.js:259:34)
host.raspberrypi 2020-02-09 22:29:24.479 error Caught by controller[8]: TypeError: Cannot read property 'key' of undefined
host.raspberrypi 2020-02-09 22:29:24.478 error Caught by controller[7]: @#[line:0,col:undefined]
host.raspberrypi 2020-02-09 22:29:24.478 error Caught by controller[7]: [xmldom error] invalid doc source
host.raspberrypi 2020-02-09 22:29:24.477 error Caught by controller[6]: [EcovacsMQTT] failure code: 500
host.raspberrypi 2020-02-09 22:29:24.476 error Caught by controller[5]: [EcovacsMQTT] failure code: 500
host.raspberrypi 2020-02-09 22:29:24.475 error Caught by controller[4]: [EcovacsMQTT] failure code: 500
host.raspberrypi 2020-02-09 22:29:24.474 error Caught by controller[3]: [EcovacsMQTT] failure code: 500
host.raspberrypi 2020-02-09 22:29:24.473 error Caught by controller[2]: [EcovacsMQTT] failure code: 500
host.raspberrypi 2020-02-09 22:29:24.472 error Caught by controller[1]: [EcovacsMQTT] failure code: 500
host.raspberrypi 2020-02-09 22:29:24.470 error Caught by controller[1]: [EcovacsMQTT] failure code: 500
ecovacs-deebot.0 2020-02-09 22:29:23.884 info (7045) Terminated (NO_ERROR): Without reason
ecovacs-deebot.0 2020-02-09 22:29:23.881 info (7045) terminating
ecovacs-deebot.0 2020-02-09 22:29:23.866 info (7045) cleaned everything up...
ecovacs-deebot.0 2020-02-09 22:29:23.861 error at Writable.write (/opt/iobroker/node_modules/readable-stream/lib/_stream_writable.js:334:11)
ecovacs-deebot.0 2020-02-09 22:29:23.861 error at writeOrBuffer (/opt/iobroker/node_modules/readable-stream/lib/_stream_writable.js:417:5)
ecovacs-deebot.0 2020-02-09 22:29:23.861 error at doWrite (/opt/iobroker/node_modules/readable-stream/lib/_stream_writable.js:428:64)
ecovacs-deebot.0 2020-02-09 22:29:23.861 error at Writable.writable._write (/opt/iobroker/node_modules/mqtt/lib/client.js:294:5)
ecovacs-deebot.0 2020-02-09 22:29:23.861 error at work (/opt/iobroker/node_modules/mqtt/lib/client.js:283:12)
ecovacs-deebot.0 2020-02-09 22:29:23.861 error at MqttClient._handlePacket (/opt/iobroker/node_modules/mqtt/lib/client.js:351:12)
ecovacs-deebot.0 2020-02-09 22:29:23.861 error at MqttClient._handlePublish (/opt/iobroker/node_modules/mqtt/lib/client.js:1162:12)
ecovacs-deebot.0 2020-02-09 22:29:23.861 error at MqttClient.emit (events.js:198:13)
ecovacs-deebot.0 2020-02-09 22:29:23.861 error at MqttClient.EcovacsMQTT.client.on (/opt/iobroker/node_modules/ecovacs-deebot/library/ecovacsMQTT.js:82:18)
ecovacs-deebot.0 2020-02-09 22:29:23.861 error at EcovacsMQTT._handle_ctl_mqtt (/opt/iobroker/node_modules/ecovacs-deebot/library/ecovacsMQTT.js:259:34)
ecovacs-deebot.0 2020-02-09 22:29:23.861 error (7045) TypeError: Cannot read property 'key' of undefined
ecovacs-deebot.0 2020-02-09 22:29:23.858 error (7045) uncaught exception: Cannot read property 'key' of undefined
ecovacs-deebot.0 2020-02-09 22:27:30.355 info (7045) DEEBOT950 successfully connected
ecovacs-deebot.0 2020-02-09 22:27:28.101 info (7045) Successfully connected to Ecovacs server
ecovacs-deebot.0 2020-02-09 22:27:25.369 info (7045) starting. Version 0.3.4 in /opt/iobroker/node_modules/iobroker.ecovacs-deebot, node: v10.19.0
host.raspberrypi 2020-02-09 22:27:22.769 info instance system.adapter.ecovacs-deebot.0 started with pid 7045
host.raspberrypi 2020-02-09 22:27:22.736 info "system.adapter.ecovacs-deebot.0" enabled
mrbungle64 commented 4 years ago

... host.raspberrypi 2020-02-09 22:29:24.480 error Caught by controller[8]: at EcovacsMQTT._handle_ctl_mqtt (/opt/iobroker/node_modules/ecovacs-deebot/library/ecovacsMQTT.js:259:34) host.raspberrypi 2020-02-09 22:29:24.479 error Caught by controller[8]: TypeError: Cannot read property 'key' of undefined host.raspberrypi 2020-02-09 22:29:24.478 error Caught by controller[7]: @#[line:0,col:undefined] ...

@gigasi, danke, aber das ist nicht die aktuelle Version, oder? Die Methode EcovacsMQTT._handle_ctl_mqtt gibt es nicht mehr und die Fehler sollten auch inzwischen behoben sein :)

Danke für das Log von der Library davor - das hilft mir auf jeden weiter

gigasi commented 4 years ago

Moment ich lösche noch mal alles

mrbungle64 commented 4 years ago

Moment ich lösche noch mal alles

ok, aber bitte über Github installieren - nicht über die "Latest Repo"

gigasi commented 4 years ago

ja so, oder nicht?

git clone https://github.com/mrbungle64/ecovacs-deebot.js.git cd ecovacs-deebot.js npm install cd example

mrbungle64 commented 4 years ago

ja so, oder nicht?

git clone https://github.com/mrbungle64/ecovacs-deebot.js.git cd ecovacs-deebot.js npm install cd example

Ja das stimmt für die Library

Nur in ioBroker war das noch eine ältere Version - wahrscheinlich die aus der Latest Repo. So kannst du die aktuelle installieren: "Adapter" => "Adapter aus beliebiger Quelle installieren oder aktualisieren" https://github.com/mrbungle64/ioBroker.ecovacs-deebot.git

Nicht wundern nach der Installation: Es wird immer noch Version 0.3.4 angezeigt

gigasi commented 4 years ago
ecovacs-deebot.0 2020-02-09 22:50:40.183 info (1157) DEEBOT950 successfully connected
ecovacs-deebot.0 2020-02-09 22:50:38.277 info (1157) Successfully connected to Ecovacs server
ecovacs-deebot.0 2020-02-09 22:50:36.416 info (1157) reconnecting (3) ...
ecovacs-deebot.0 2020-02-09 22:50:31.012 info (1157) reconnecting (2) ...
ecovacs-deebot.0 2020-02-09 22:50:25.571 info (1157) reconnecting (1) ...
ecovacs-deebot.0 2020-02-09 22:50:19.940 info (1157) starting. Version 0.3.4 in /opt/iobroker/node_modules/iobroker.ecovacs-deebot, node: v10.19.0
host.raspberrypi 2020-02-09 22:50:16.945 info instance system.adapter.ecovacs-deebot.0 started with pid 1157
host.raspberrypi 2020-02-09 22:50:16.907 info "system.adapter.ecovacs-deebot.0" enabled
host.raspberrypi 2020-02-09 22:50:14.157 info instance system.adapter.ecovacs-deebot.0 terminated with code 156 (156)
host.raspberrypi 2020-02-09 22:50:14.157 error Caught by controller[3]: [EcovacsAPI] Failure code 0002
host.raspberrypi 2020-02-09 22:50:14.157 error Caught by controller[2]: [EcovacsAPI] Failure code 0002
host.raspberrypi 2020-02-09 22:50:14.156 error Caught by controller[1]: [EcovacsAPI] Failure code 0002
host.raspberrypi 2020-02-09 22:50:14.155 error Caught by controller[0]: [EcovacsAPI] Failure code 0002
ecovacs-deebot.0 2020-02-09 22:50:13.607 info (572) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
ecovacs-deebot.0 2020-02-09 22:50:13.606 info (572) terminating
ecovacs-deebot.0 2020-02-09 22:50:13.604 info (572) cleaned everything up...
ecovacs-deebot.0 2020-02-09 22:50:13.601 info (572) Got terminate signal TERMINATE_YOURSELF
host.raspberrypi 2020-02-09 22:50:13.599 info stopInstance system.adapter.ecovacs-deebot.0 send kill signal
host.raspberrypi 2020-02-09 22:50:13.594 info stopInstance system.adapter.ecovacs-deebot.0 (force=false, process=true)
host.raspberrypi 2020-02-09 22:50:13.592 info "system.adapter.ecovacs-deebot.0" disabled
ecovacs-deebot.0 2020-02-09 22:50:13.395 info (572) reconnecting (3) ...
ecovacs-deebot.0 2020-02-09 22:50:07.980 info (572) reconnecting (2) ...
ecovacs-deebot.0 2020-02-09 22:50:02.621 info (572) reconnecting (1) ...
ecovacs-deebot.0 2020-02-09 22:49:56.949 info (572) starting. Version 0.3.4 in /opt/iobroker/node_modules/iobroker.ecovacs-deebot, node: v10.19.0
host.raspberrypi 2020-02-09 22:49:53.502 info instance system.adapter.ecovacs-deebot.0 started with pid 572
host.raspberrypi 2020-02-09 22:49:51.787 info Update repository "latest" under "http://download.iobroker.net/sources-dist-latest.json"
host.raspberrypi 2020-02-09 22:49:51.534 info iobroker exit 0
host.raspberrypi 2020-02-09 22:49:51.098 info instance system.adapter.ecovacs-deebot.0 terminated with code 156 (156)
ecovacs-deebot.0 2020-02-09 22:49:50.532 info (25722) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
ecovacs-deebot.0 2020-02-09 22:49:50.530 info (25722) terminating
ecovacs-deebot.0 2020-02-09 22:49:50.529 info (25722) cleaned everything up...
ecovacs-deebot.0 2020-02-09 22:49:50.524 info (25722) Got terminate signal TERMINATE_YOURSELF
host.raspberrypi 2020-02-09 22:49:50.514 info stopInstance system.adapter.ecovacs-deebot.0 send kill signal
host.raspberrypi 2020-02-09 22:49:50.502 info stopInstance system.adapter.ecovacs-deebot.0 (force=false, process=true)
host.raspberrypi 2020-02-09 22:49:50.488 info iobroker Update "system.adapter.ecovacs-deebot.0"
mrbungle64 commented 4 years ago

@gigasi

Kannst du gerade noch mal mit git clone aktualisieren und noch mal testen?

gigasi commented 4 years ago

1

mrbungle64 commented 4 years ago

Vielen Dank @gigasi, der Fehler den ich beheben wollte ist auch soweit behoben - allerdings war meine Hoffnung, dass auch der failure code: 500 damit endlich mal Geschichte ist ...

Aber wir kommen der Sache für den Ozmo 950 schon näher :) Das ist echt nicht einfach - bei dem haben die so einiges anders implementiert als bei den anderen Geräten ...

Ich denke wir sollten aber für heute mal Schluss machen - vielen Dank für's Testen und die wertvollen Informationen :)

gigasi commented 4 years ago

Ich oder besser gesagt wir haben zu danken, das du da so dranbleibst! :)

gigasi commented 4 years ago

Nur mal zu Info playSound geht jetzt auch nicht mehr über ioBroker

AudidriverA4 commented 4 years ago
Screenshot 2020-02-10 15 06 58 Screenshot 2020-02-10 15 06 49

Hab gerade mal frisch aktualisiert und alle Buttons gehen: Start, Pause, Stop, Aufladen und Sound.

Bei mir ist es ein Deebot 900.

Instanz auch stabil auf Grün geblieben bei Button drücken.

Hier noch die Log:

ecovacs-deebot.0 2020-02-10 14:01:09.300 info (6137) run: charge ecovacs-deebot.0 2020-02-10 14:01:03.936 info (6137) run: stop ecovacs-deebot.0 2020-02-10 14:00:59.621 info (6137) run: clean ecovacs-deebot.0 2020-02-10 14:00:54.589 info (6137) run: stop ecovacs-deebot.0 2020-02-10 14:00:50.083 info (6137) run: playSound ecovacs-deebot.0 2020-02-10 14:00:45.811 info (6137) run: pause ecovacs-deebot.0 2020-02-10 14:00:24.411 info (6137) run: clean ecovacs-deebot.0 2020-02-10 13:59:35.285 info (6137) Dobby successfully connected ecovacs-deebot.0 2020-02-10 13:59:30.893 info (6137) Successfully connected to Ecovacs server ecovacs-deebot.0 2020-02-10 13:59:29.293 info (6137) reconnecting (13) ... ecovacs-deebot.0 2020-02-10 13:59:24.044 info (6137) reconnecting (12) ... ecovacs-deebot.0 2020-02-10 13:59:18.799 info (6137) reconnecting (11) ... ecovacs-deebot.0 2020-02-10 13:59:13.495 info (6137) reconnecting (10) ... ecovacs-deebot.0 2020-02-10 13:59:08.246 info (6137) reconnecting (9) ... ecovacs-deebot.0 2020-02-10 13:59:03.123 info (6137) reconnecting (8) ... ecovacs-deebot.0 2020-02-10 13:58:57.852 info (6137) reconnecting (7) ... ecovacs-deebot.0 2020-02-10 13:58:52.789 info (6137) reconnecting (6) ... ecovacs-deebot.0 2020-02-10 13:58:47.724 info (6137) reconnecting (5) ... ecovacs-deebot.0 2020-02-10 13:58:42.581 info (6137) reconnecting (4) ... ecovacs-deebot.0 2020-02-10 13:58:37.481 info (6137) reconnecting (3) ... ecovacs-deebot.0 2020-02-10 13:58:32.331 info (6137) reconnecting (2) ... ecovacs-deebot.0 2020-02-10 13:58:27.015 info (6137) reconnecting (1) ... ecovacs-deebot.0 2020-02-10 13:58:21.141 info (6137) starting. Version 0.3.4 in /opt/iobroker/node_modules/iobroker.ecovacs-deebot, node: v10.17.0 ecovacs-deebot.0 2020-02-10 13:58:16.536 info (5675) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason ecovacs-deebot.0 2020-02-10 13:58:16.535 info (5675) terminating ecovacs-deebot.0 2020-02-10 13:58:16.534 info (5675) cleaned everything up... ecovacs-deebot.0 2020-02-10 13:58:16.532 info (5675) Got terminate signal TERMINATE_YOURSELF ecovacs-deebot.0 2020-02-10 13:58:11.598 info (5675) starting. Version 0.3.4 in /opt/iobroker/node_modules/iobroker.ecovacs-deebot, node: v10.17.0 ecovacs-deebot.0 2020-02-10 13:58:05.041 info (7180) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason ecovacs-deebot.0 2020-02-10 13:58:05.040 info (7180) terminating ecovacs-deebot.0 2020-02-10 13:58:05.039 info (7180) cleaned everything up... ecovacs-deebot.0 2020-02-10 13:58:05.034 info (7180) Got terminate signal TERMINATE_YOURSELF

Ihr seit ja der Hit wie das bei euch vorwärts geht Vielen Dank für euren Einsatz :-)

gigasi commented 4 years ago

Kleine Info: wenn ich app2.js starte, und den Sauger(950) über die Handy-App saugen lasse kommen Positions-Daten [EcovacsMQTT] as_dict: {"header":{"pri":1,"tzm":480,"ts":"1581358721793","ver":" 0.0.1","fwVer":"1.7.6","hwVer":"0.1.1"},"body":{"data":{"deebotPos":{"x":1094,"y ":-65,"a":-143,"invalid":0}}}}

Ist der Sauger fertig, kommt auch wieder failure code: 500

boriswerner commented 4 years ago

@gigasi du solltest dein Passwort ändern und den Beitrag oben ändern...

mrbungle64 commented 4 years ago

@gigasi du solltest dein Passwort ändern und den Beitrag oben ändern... @gigasi Wollte ich auch gerade schreiben

mrbungle64 commented 4 years ago

@gigasi

Ich habe deinen Beitrag mal gelöscht ;)

gigasi commented 4 years ago

@mrbungle64 danke pw habe ich geändert

mrbungle64 commented 4 years ago

Kleine Info: wenn ich app2.js starte, und den Sauger(950) über die Handy-App saugen lasse kommen Positions-Daten [EcovacsMQTT] as_dict: {"header":{"pri":1,"tzm":480,"ts":"1581358721793","ver":" 0.0.1","fwVer":"1.7.6","hwVer":"0.1.1"},"body":{"data":{"deebotPos":{"x":1094,"y ":-65,"a":-143,"invalid":0}}}}

Ist der Sauger fertig, kommt auch wieder failure code: 500

Danke für die Infos :)

Bzgl playSound: geht das reproduzierbar nicht mehr?

gigasi commented 4 years ago

nein geht gar nicht mehr

mrbungle64 commented 4 years ago

@gigasi

Info: Das Log hatte ich mir vor dem Löschen rauskopiert. Wolltest Du mir im Code was zeigen? Hattest Du da was angepasst?

gigasi commented 4 years ago

ja, vacbot.connect_and_wait_until_ready(); vacbot.run('Clean'); vacbot.run('GetLifeSpan', 'main_brush'); vacbot.run('GetLifeSpan', 'side_brush'); vacbot.run('GetLifeSpan', 'filter'); let interval = setInterval(() => { vacbot.run('GetCleanState'); vacbot.run('GetChargeState'); vacbot.run('GetBatteryState'); }, 15000);

Das brauch nicht sein