homebridge-plugins / homebridge-roomba2

Homebridge plugin to connect iRobot Roomba devices with Homebridge/HomeKit.
MIT License
143 stars 17 forks source link

Issue w/ getrobotpwd call #83

Closed nam777 closed 1 year ago

nam777 commented 2 years ago

homebridge@retropie:/usr/lib/node_modules/homebridge-roomba2 $ sudo npm run getrobotpwd 10.0.X.XX

homebridge-roomba2@1.2.2 getrobotpwd /usr/lib/node_modules/homebridge-roomba2 cd node_modules/dorita980 && npm install && node ./bin/getpassword.js "10.0.X.XX"

npm WARN ajv-keywords@2.1.1 requires a peer of ajv@^5.0.0 but none is installed. You must install peer dependencies yourself. npm WARN eslint-plugin-react@6.8.0 requires a peer of eslint@^2.0.0 || ^3.0.0 but none is installed. You must install peer dependencies yourself.

audited 357 packages in 4.856s

5 packages are looking for funding run npm fund for details

found 9 vulnerabilities (1 low, 5 moderate, 2 high, 1 critical) run npm audit fix to fix them, or npm audit for details Make sure your robot is on the Home Base and powered on (green lights on). Then press and hold the HOME button (or DOCK+SPOT on some models) on your robot until it plays a series of tones (about 2 seconds). Release the button and your robot will flash WIFI light. Then press any key here... events.js:377 throw er; // Unhandled 'error' event ^

Error: connect EHOSTUNREACH 10.0.X.XX:XXXX at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1159:16) Emitted 'error' event on TLSSocket instance at: at emitErrorNT (internal/streams/destroy.js:106:8) at emitErrorCloseNT (internal/streams/destroy.js:74:3) at processTicksAndRejections (internal/process/task_queues.js:82:21) { errno: -113, code: 'EHOSTUNREACH', syscall: 'connect', address: '10.0.X.XX', port: XXXX } npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! homebridge-roomba2@1.2.2 getrobotpwd: cd node_modules/dorita980 && npm install && node ./bin/getpassword.js "10.0.X.XX" npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the homebridge-roomba2@1.2.2 getrobotpwd script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2021-10-25T19_16_01_220Z-debug.log

myzinsky commented 2 years ago

you have to sniff the password currently with a man in the middle attack:

https://github.com/koalazak/dorita980/issues/142

nam777 commented 2 years ago

Thanks. Used Charles Proxy and it worked like a charm.

myzinsky commented 2 years ago

Have you managed to geht the bot running then? For me it does not yet work with Roomba2

nam777 commented 2 years ago

It is up and running.