-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exceptions when running the Bot. #3
Comments
I'm using the ecovacs-deebot.js library and the model 920 isn't on the list of tested/supported devices. The error log looks like a mqtt xml parse problem but i cant really debug the problem. |
I updated the plugin to the newest version (0.4.3) of the ecovacs-deebot lib. |
thx for the fast support, i will give it a try. |
Ok, very good. Is the instruction from mrbungle64 something you can do? |
Didn't follow this but after installing this update the plugin doesn't work anymore. Going back to the previous release. |
Ok, any debug/log info? I could try testing it, if you would change the password back to the test one? |
canvas@2.6.1 install /home/pi/pimatic-app/node_modules/canvas
node-pre-gyp WARN Using request for node-pre-gyp https download npm ERR! code ELIFECYCLE Something wrong with installing canvas. Going back to an older version doesn't work anymore, same error. |
How did you go back to older version and did you delete and reinstall already? |
@djmvt |
Hi, if you use ecovacs-deebot in a different environment (like Pimatic) where is canvas used for? |
Hi @bertreb |
canvas kept annoying me when trying to reinstall for some reason, also with the instructions from @mrbungle64. Weird thing is: pimatic-deebot have been running absolutely fine since the first tests a few weeks ago, so this was unexpected. But after deleting both canvas and deebot again and rebooted the Pi it looks like everything got installed again as it was supposed to be installed. deebot is running again. @bertreb tried to go back to an older version with npm install pimatic-deebot@0.0.24 |
@mrbungle64 Thanks for explaining. It seems that this issue is solved. |
In the meantime we also updated both Readme files on GitHub |
I become the same error by installing the new pimatic debot plugin version, and I not use iobroker or other debot tools. I have this only in pimatic |
Hi @heiko1988 have you already read and followed the mentioned instructions? |
@heiko1988 and you could try the steps in the last post of @djmvt. |
Oh, sorry have this not read, after Instal canvas. The plugin work fine aging withe the ozmo debot 950 Thanks :) |
the deebot 920 is now supported by fixing this issue: think the libary needs an update? |
@bertreb I recommend that you also include these installation instructions with your project: |
@mrbungle64 thanks. I will add the instructions and update the pimatic plugin |
Works like a charm! thx! |
I Have a Deebot 920 and after installation the Plugin and adding the bot. My pimatic instance is constantly restarting.
error [pimatic]: An uncaught exception occurred: TypeError: Cannot read property 'attributes' of null
at EcovacsMQTT._message_to_dict (/home/pi/pimatic-app/node_modules/pimatic-deebot/node_modules/ecovacs-deebot/library/ecovacsMQTT.js:292:18)
at EcovacsMQTT._handle_message (/home/pi/pimatic-app/node_modules/pimatic-deebot/node_modules/ecovacs-deebot/library/ecovacsMQTT.js:266:28)
at MqttClient.EcovacsMQTT.client.on (/home/pi/pimatic-app/node_modules/pimatic-deebot/node_modules/ecovacs-deebot/library/ecovacsMQTT.js:79:18)
at MqttClient.emit (events.js:198:13)
at MqttClient._handlePublish (/home/pi/pimatic-app/node_modules/pimatic-deebot/node_modules/ecovacs-deebot/node_modules/mqtt/lib/client.js:1162:12)
at MqttClient._handlePacket (/home/pi/pimatic-app/node_modules/pimatic-deebot/node_modules/ecovacs-deebot/node_modules/mqtt/lib/client.js:351:12)
at work (/home/pi/pimatic-app/node_modules/pimatic-deebot/node_modules/ecovacs-deebot/node_modules/mqtt/lib/client.js:283:12)
at Writable.writable._write (/home/pi/pimatic-app/node_modules/pimatic-deebot/node_modules/ecovacs-deebot/node_modules/mqtt/lib/client.js:294:5)
at doWrite (/home/pi/pimatic-app/node_modules/pimatic-deebot/node_modules/ecovacs-deebot/node_modules/mqtt/node_modules/readable-stream/lib/_stream_writable.js:428:64)
at writeOrBuffer (/home/pi/pimatic-app/node_modules/pimatic-deebot/node_modules/ecovacs-deebot/node_modules/mqtt/node_modules/readable-stream/lib/_stream_writable.js:417:5)
at Writable.write (/home/pi/pimatic-app/node_modules/pimatic-deebot/node_modules/ecovacs-deebot/node_modules/mqtt/node_modules/readable-stream/lib/_stream_writable.js:334:11)
at TLSSocket.ondata (_stream_readable.js:709:20)
at TLSSocket.emit (events.js:198:13)
at TLSSocket.emit (/home/pi/pimatic-app/node_modules/pimatic/startup.coffee:64:24)
at addChunk (_stream_readable.js:288:12)
at readableAddChunk (_stream_readable.js:269:11)
at TLSSocket.Readable.push (_stream_readable.js:224:10)
at TLSWrap.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)
This is most probably a bug in pimatic or in a module, please report it!
The text was updated successfully, but these errors were encountered: