Unable to get BLID and password on j7

[mpreissner]

Following all instructions, get the following when using the getrobotpwd:

events.js:352
throw er; // Unhandled 'error' event
^

Error: Client network socket disconnected before secure TLS connection was established
at connResetException (internal/errors.js:628:14)
at TLSSocket.onConnectEnd (_tls_wrap.js:1561:19)
at TLSSocket.emit (events.js:387:35)
at endReadableNT (internal/streams/readable.js:1317:12)
at processTicksAndRejections (internal/process/task_queues.js:82:21)
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) {
code: 'ECONNRESET',
path: undefined,
host: '10.100.10.17',
port: 8883,
localAddress: undefined
}
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.100.10.17"
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-14T16_10_01_846Z-debug.log

I tried using the workaround described in #8, but that didn't work either. I've confirmed that none of my mobile devices are logged into the iRobot app, disabled the roomba2 plugin in hombridge, rebooted the roomba, still can't get it to work.

Using the workaround with the produces the following:

root@homebridge:~/Roomba980-Python/roomba# python3 getpassword.py
2021-10-14 09:21:14 INFO [Roomba.Password] Using Password version 2.0a
2021-10-14 09:21:14 INFO [Roomba.Password] reading/writing info from config file ./config.ini
2021-10-14 09:21:14 INFO [Roomba.Password] waiting on port: 5678 for data
2021-10-14 09:21:14 INFO [Roomba.Password] Robot at IP: 10.100.10.17 Data: {
"ver": "4",
"hostname": "iRobot-1151264EEC834223B9F20FED66463386",
"robotname": "Roomba",
"robotid": "1151264EEC834223B9F20FED66463386",
"ip": "10.100.10.17",
"mac": "50:14:79:B1:E4:55",
"sw": "sapphire+1.0.17+Firmware-Production+52",
"sku": "j755020",
"nc": 0,
"proto": "mqtt",
"cap": {
"binFullDetect": 2,
"dockComm": 1,
"edge": 0,
"maps": 3,
"pmaps": 5,
"tLine": 2,
"area": 1,
"eco": 1,
"multiPass": 2,
"pose": 1,
"team": 1,
"pp": 0,
"lang": 2,
"5ghz": 1,
"prov": 3,
"sched": 1,
"svcConf": 1,
"ota": 2,
"log": 2,
"langOta": 0,
"expectingUserConf": 1
},
"cloudConnState": 10
}
2021-10-14 09:21:25 INFO [Roomba.Password] 0 robot(s) already defined in file./config.ini, found 1 robot(s) on network
2021-10-14 09:21:25 INFO [Roomba.Password] To add/update Your robot details,make sure your robot (Roomba) at IP 10.100.10.17 is on the Home Base and powered on (green lights on). Then press and hold the HOME button on your robot until it plays a series of tones (about 2 seconds). Release the button and your robot will flash WIFI light.
Press to continue...
s to skip configuring this robot:
2021-10-14 09:21:31 INFO [Roomba.Password] Roomba (Roomba) IP address is: 10.100.10.17
2021-10-14 09:21:31 DEBUG [Roomba.Password] Connection Successful
2021-10-14 09:21:31 DEBUG [Roomba.Password] Waiting for data
2021-10-14 09:21:41 ERROR [Roomba.Password] Connection Timeout Error (for 10.100.10.17): The read operation timed out
2021-10-14 09:21:41 ERROR [Roomba.Password] Unable to get password from roomba
2021-10-14 09:21:41 ERROR [Roomba.Password] Error getting password for robot Roomba at ip10.100.10.17, received 7 bytes. Follow the instructions and try again.

[the1maximus]

@mpreissner I was having the same issue with an i4 I just purchased, but finally after playing with it for a few hours I finally got it.

1. Reboot the Roomba through the app.
2. Go to Account Setting in the iRobot app and Log out of all devices.
3. Open terminal in Homebridge, Follow the Command Line steps to switch to the proper directory
4. In the roomba2 dir run command "npm fund"
5. Run the get password command
6. At The prompt to press the button, Don't press any button on the Roomba, instead just press a button to continue.
7. At this point all of the info will generate, except you will get an error for the password.
8. Repeat the get password command
9. At the prompt to press a button, press and hold ONLY the HOME button for a few seconds and hit a button on the keyboard.

If done correctly you should get a prompt from the Roomba that it was setup successfully, and the terminal window will have all of the info and the password.

[mpreissner]

Unfortunately, that didn't do the trick. First, as I understand it, npm fund only lists packages where the developers are seeking funding to support their work. This has nothing to do with dependency installation. In any case, npm fund gives me this:

`root@homebridge:/usr/local/lib/node_modules/homebridge-roomba2# npm fund
homebridge-roomba2@1.2.2
├─┬ https://github.com/sponsors/isaacs
│ └── glob@7.2.0
├─┬ https://github.com/sponsors/epoberezkin
│ └── ajv@6.12.6
├─┬ https://github.com/sponsors/ljharb
│ └── is-object@1.0.2
├─┬ https://github.com/sponsors/feross
│ └── run-parallel@1.2.0, queue-microtask@1.2.3
├─┬ https://www.patreon.com/feross
│ └── run-parallel@1.2.0, queue-microtask@1.2.3
└─┬ https://feross.org/support
└── run-parallel@1.2.0, queue-microtask@1.2.3

╭───────────────────────────────────────────────────────────────╮
│ │
│ New major version of npm available! 6.14.13 → 8.1.0 │
│ Changelog: https://github.com/npm/cli/releases/tag/v8.1.0 │
│ Run npm install -g npm to update! │
│ │
╰───────────────────────────────────────────────────────────────╯

`
and both times I run the getrobotpwd command, I get this (same output the first with no button press and second with button press):

`root@homebridge:/usr/local/lib/node_modules/homebridge-roomba2# npm run getrobotpwd 10.100.10.17

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

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 5.728s

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:352
throw er; // Unhandled 'error' event
^

Error: Client network socket disconnected before secure TLS connection was established
at connResetException (internal/errors.js:628:14)
at TLSSocket.onConnectEnd (_tls_wrap.js:1561:19)
at TLSSocket.emit (events.js:387:35)
at endReadableNT (internal/streams/readable.js:1317:12)
at processTicksAndRejections (internal/process/task_queues.js:82:21)
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) {
code: 'ECONNRESET',
path: undefined,
host: '10.100.10.17',
port: 8883,
localAddress: undefined
}
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.100.10.17"
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-15T12_25_59_941Z-debug.log`

So I guess the problem here is really that certain dependencies are unmet, specifically ajv@^5.0.0 and esline@^2.0.0 ro @^3.0.0. I would consider this to be a flaw in the programming of the getrobotpwd command or a flaw in the plugin itself.
If these packages are required for the the password command to function, they should be installed as dependencies of the plugin, or as part of the runtime when executing the command. Also, for informational purposes, the new j7 robot only has one button. Based on the instructions of holding the home button until some tones are played, I expect that the j7 button operates the same as the home button on other models, as it does play tones when held for a few seconds, but it's important to note distinctions like this when supporting different models.

I'm going to try and resolve this dependency issue and will hopefully get it working today.

[the1maximus]

@mpreissner I’m sorry to hear you still didn’t have any success. As for the steps I followed, I was trying anything, that I came across. When I did the npm fund and then the getrobotpwd commands after one another I was able to generate all of the info except the password. I kept following that same structure, until I came across the idea of just holding the home button instead of home and spot, and sure enough that did the trick. I don’t know if it was a matter of timing, or just pure luck, but It’s working 100% now.

I will say though that my Log files kept throwing errors for the contact sensor features, so I just removed them. Thankfully the iRobot notifications are fairly quick.

[mpreissner]

So I tried installing the dependencies (ajv and eslint), but I still kept getting unmet dependency errors. Pasting my log from the latest run (I uninstalled/reinstalled the roomba2 plugin). This one is without a button press...

0 info it worked if it ends with ok 1 verbose cli [ 1 verbose cli '/usr/local/bin/node', 1 verbose cli '/usr/local/bin/npm', 1 verbose cli 'run', 1 verbose cli 'getrobotpwd', 1 verbose cli '10.100.10.17' 1 verbose cli ] 2 info using npm@6.14.13 3 info using node@v14.17.3 4 verbose run-script [ 'pregetrobotpwd', 'getrobotpwd', 'postgetrobotpwd' ] 5 info lifecycle homebridge-roomba2@1.2.2~pregetrobotpwd: homebridge-roomba2@1.2.2 6 info lifecycle homebridge-roomba2@1.2.2~getrobotpwd: homebridge-roomba2@1.2.2 7 verbose lifecycle homebridge-roomba2@1.2.2~getrobotpwd: unsafe-perm in lifecycle true 8 verbose lifecycle homebridge-roomba2@1.2.2~getrobotpwd: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/usr/local/lib/node_modules/homebridge-roomba2/node_modules/.bin:/usr/local/lib/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 9 verbose lifecycle homebridge-roomba2@1.2.2~getrobotpwd: CWD: /usr/local/lib/node_modules/homebridge-roomba2 10 silly lifecycle homebridge-roomba2@1.2.2~getrobotpwd: Args: [ 10 silly lifecycle '-c', 10 silly lifecycle 'cd node_modules/dorita980 && npm install && node ./bin/getpassword.js "10.100.10.17"' 10 silly lifecycle ] 11 silly lifecycle homebridge-roomba2@1.2.2~getrobotpwd: Returned: code: 1 signal: null 12 info lifecycle homebridge-roomba2@1.2.2~getrobotpwd: Failed to exec getrobotpwd script 13 verbose stack Error: homebridge-roomba2@1.2.2 getrobotpwd:cd node_modules/dorita980 && npm install && node ./bin/getpassword.js "10.100.10.17"13 verbose stack Exit status 1 13 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16) 13 verbose stack at EventEmitter.emit (events.js:375:28) 13 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14) 13 verbose stack at ChildProcess.emit (events.js:375:28) 13 verbose stack at maybeClose (internal/child_process.js:1055:16) 13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5) 14 verbose pkgid homebridge-roomba2@1.2.2 15 verbose cwd /usr/local/lib/node_modules/homebridge-roomba2 16 verbose Linux 5.10.63-v7l+ 17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "getrobotpwd" "10.100.10.17" 18 verbose node v14.17.3 19 verbose npm v6.14.13 20 error code ELIFECYCLE 21 error errno 1 22 error homebridge-roomba2@1.2.2 getrobotpwd:cd node_modules/dorita980 && npm install && node ./bin/getpassword.js "10.100.10.17"22 error Exit status 1 23 error Failed at the homebridge-roomba2@1.2.2 getrobotpwd script. 23 error This is probably not a problem with npm. There is likely additional logging output above. 24 verbose exit [ 1, true ]

And this one is with a button press...

0 info it worked if it ends with ok 1 verbose cli [ 1 verbose cli '/usr/local/bin/node', 1 verbose cli '/usr/local/bin/npm', 1 verbose cli 'run', 1 verbose cli 'getrobotpwd', 1 verbose cli '10.100.10.17' 1 verbose cli ] 2 info using npm@6.14.13 3 info using node@v14.17.3 4 verbose run-script [ 'pregetrobotpwd', 'getrobotpwd', 'postgetrobotpwd' ] 5 info lifecycle homebridge-roomba2@1.2.2~pregetrobotpwd: homebridge-roomba2@1.2.2 6 info lifecycle homebridge-roomba2@1.2.2~getrobotpwd: homebridge-roomba2@1.2.2 7 verbose lifecycle homebridge-roomba2@1.2.2~getrobotpwd: unsafe-perm in lifecycle true 8 verbose lifecycle homebridge-roomba2@1.2.2~getrobotpwd: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/usr/local/lib/node_modules/homebridge-roomba2/node_modules/.bin:/usr/local/lib/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 9 verbose lifecycle homebridge-roomba2@1.2.2~getrobotpwd: CWD: /usr/local/lib/node_modules/homebridge-roomba2 10 silly lifecycle homebridge-roomba2@1.2.2~getrobotpwd: Args: [ 10 silly lifecycle '-c', 10 silly lifecycle 'cd node_modules/dorita980 && npm install && node ./bin/getpassword.js "10.100.10.17"' 10 silly lifecycle ] 11 silly lifecycle homebridge-roomba2@1.2.2~getrobotpwd: Returned: code: 1 signal: null 12 info lifecycle homebridge-roomba2@1.2.2~getrobotpwd: Failed to exec getrobotpwd script 13 verbose stack Error: homebridge-roomba2@1.2.2 getrobotpwd:cd node_modules/dorita980 && npm install && node ./bin/getpassword.js "10.100.10.17"13 verbose stack Exit status 1 13 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16) 13 verbose stack at EventEmitter.emit (events.js:375:28) 13 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14) 13 verbose stack at ChildProcess.emit (events.js:375:28) 13 verbose stack at maybeClose (internal/child_process.js:1055:16) 13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5) 14 verbose pkgid homebridge-roomba2@1.2.2 15 verbose cwd /usr/local/lib/node_modules/homebridge-roomba2 16 verbose Linux 5.10.63-v7l+ 17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "getrobotpwd" "10.100.10.17" 18 verbose node v14.17.3 19 verbose npm v6.14.13 20 error code ELIFECYCLE 21 error errno 1 22 error homebridge-roomba2@1.2.2 getrobotpwd:cd node_modules/dorita980 && npm install && node ./bin/getpassword.js "10.100.10.17"22 error Exit status 1 23 error Failed at the homebridge-roomba2@1.2.2 getrobotpwd script. 23 error This is probably not a problem with npm. There is likely additional logging output above. 24 verbose exit [ 1, true ]

[rcoletti116]

Device compatibility is based on the underlying library dorita980. It seems the J7 has some issues, but you might check out this issue over there as some users have returned their password by inspecting the app traffic.

[mpreissner]

Thanks. Yeah, I managed to get the BLID (which appears to be identical to the RobotID) and the password using Charles Proxy. Unfortunately, when putting the values into the plugin config in Homebridge, the various Roomba "Devices" are added, but constantly timeout on response...effectively, I can't do anything with them. If the ongoing function of the roomba2 plugin relies on dorita980 (not just the BLID/password discovery), then this won't get fixed until dorita980 is fixed.

[mpreissner]

Update: There's some progress on the Dorita980 side. Using the dorita code and passing it the environment variable ROBOT_CIPHERS=TLS_AES_256_GCM_SHA384 for ROBOT_CIPHERS or editing the getpassword.js file to use that value results in successful BLID retrieval, but still no password.

Regardless, I've noticed that although I see "No Response" from the roomba devices created by the plugin in Homekit, my homebridge itself does seem to update. Unfortunately, it takes a really long time, and causes all of my homebridge-linked accessories to take a while to update. I keep seeing this in my homebridge logs (and yes, roomba2 is running on a child bridge - I don't have any plugins running on the main bridge):

[20/10/2021, 09:38:58] [homebridge-roomba2] This plugin slows down Homebridge. The read handler for the characteristic 'On' was slow to respond! See https://git.io/JtMGR for more info.
[20/10/2021, 09:38:58] [homebridge-roomba2] This plugin slows down Homebridge. The read handler for the characteristic 'Status Low Battery' was slow to respond! See https://git.io/JtMGR for more info.
[20/10/2021, 09:38:58] [homebridge-roomba2] This plugin slows down Homebridge. The read handler for the characteristic 'Battery Level' was slow to respond! See https://git.io/JtMGR for more info.
[20/10/2021, 09:38:58] [homebridge-roomba2] This plugin slows down Homebridge. The read handler for the characteristic 'Charging State' was slow to respond! See https://git.io/JtMGR for more info.
[20/10/2021, 09:38:58] [homebridge-roomba2] This plugin slows down Homebridge. The read handler for the characteristic 'Filter Change Indication' was slow to respond! See https://git.io/JtMGR for more info.
[20/10/2021, 09:38:58] [homebridge-roomba2] This plugin slows down Homebridge. The read handler for the characteristic 'Contact Sensor State' was slow to respond! See https://git.io/JtMGR for more info.
[20/10/2021, 09:38:58] [homebridge-roomba2] This plugin slows down Homebridge. The read handler for the characteristic 'Contact Sensor State' was slow to respond! See https://git.io/JtMGR for more info.
[20/10/2021, 09:38:58] [homebridge-roomba2] This plugin slows down Homebridge. The read handler for the characteristic 'Contact Sensor State' was slow to respond! See https://git.io/JtMGR for more info.

[karlvr]

@mpreissner could you please try installing the beta of the plugin? In Homebridge UI, go to the Plugins tab, click the spanner / wrench on the homebridge-roomba2 plugin, then click Install Previous Version. I'm interested in whether it at least resolves the "plugin slows down Homebridge" issue, if not actually resolving your issue.

Your issue does seem like something that Dorita980 will need to resolve, and once it does, we'll need to upgrade the dependency for this plugin.

[mpreissner]

Updated to the beta. Log output below:

[20/10/2021, 18:43:57] [Roomba] Restarting Process...
Initializing HAP-NodeJS v0.9.6...
[20/10/2021, 18:43:58] [Roomba] Launched child bridge with PID 31589
[20/10/2021, 18:43:59] Registering accessory 'homebridge-roomba2.Roomba2'
[20/10/2021, 18:43:59] [Roomba] Loaded homebridge-roomba2 v1.3.0-beta.7 child bridge successfully
[20/10/2021, 18:43:59] Loaded 0 cached accessories from cachedAccessories.0E7F387A4456.
[20/10/2021, 18:43:59] [Roomba] Refreshing Roomba's status (repeating in 60m)
[20/10/2021, 18:43:59] [Roomba] DEBUG: Connecting to Roomba (0 others waiting)...
Preparing Advertiser for 'Roomba 8CC4' using ciao backend!
Starting to advertise 'Roomba 8CC4' using ciao backend!
[20/10/2021, 18:43:59] Homebridge v1.3.5 (Roomba) is running on port 56152.
[20/10/2021, 18:43:59] [Roomba] DEBUG: Connection close received
[20/10/2021, 18:44:01] [Roomba] DEBUG: Connection close received from old connection
[20/10/2021, 18:44:01] [Roomba] Running status: Returning no value due to timeout
[20/10/2021, 18:44:01] [Roomba] Low Battery status: Returning no value due to timeout
[20/10/2021, 18:44:01] [Roomba] Battery level: Returning no value due to timeout
[20/10/2021, 18:44:01] [Roomba] Charging status: Returning no value due to timeout
[20/10/2021, 18:44:01] [Roomba] Bin status: Returning no value due to timeout
[20/10/2021, 18:44:01] [Roomba] Dock status: Returning no value due to timeout
[20/10/2021, 18:44:01] [Roomba] Running status: Returning no value due to timeout
[20/10/2021, 18:44:01] [Roomba] Bin status: Returning no value due to timeout
[20/10/2021, 18:44:02] [Roomba] DEBUG: Connection close received from old connection
[20/10/2021, 18:44:03] [Roomba] DEBUG: Connection close received from old connection
[20/10/2021, 18:44:04] [Roomba] DEBUG: Connection close received from old connection
[20/10/2021, 18:44:05] [Roomba] DEBUG: Connection close received from old connection
[20/10/2021, 18:44:07] [Roomba] DEBUG: Connection close received from old connection
[20/10/2021, 18:44:10] [Roomba] DEBUG: Connection close received from old connection
[20/10/2021, 18:44:12] [Roomba] DEBUG: Connection close received from old connection
[20/10/2021, 18:44:16] [Roomba] DEBUG: Connection close received from old connection
[20/10/2021, 18:44:17] [Roomba] DEBUG: Connection close received from old connection
[20/10/2021, 18:44:19] [Roomba] DEBUG: Connection close received from old connection
[20/10/2021, 18:44:21] [Roomba] DEBUG: Connection close received from old connection
[20/10/2021, 18:44:25] [Roomba] DEBUG: Connection close received from old connection
[20/10/2021, 18:44:27] [Roomba] DEBUG: Connection close received from old connection
[20/10/2021, 18:44:29] [Roomba] DEBUG: Connection close received from old connection
[20/10/2021, 18:44:30] [Roomba] DEBUG: Watching Roomba's status (repeating in 30s, idle timeout in 570s)
[20/10/2021, 18:44:30] [Roomba] DEBUG: Connecting to Roomba (0 others waiting)...
[20/10/2021, 18:44:31] [Roomba] DEBUG: Connection close received from old connection
[20/10/2021, 18:44:34] [Roomba] DEBUG: Connection close received
[20/10/2021, 18:44:36] [Roomba] DEBUG: Connection close received from old connection
[20/10/2021, 18:44:38] [Roomba] DEBUG: Connection close received from old connection
[20/10/2021, 18:44:42] [Roomba] DEBUG: Connection close received from old connection
[20/10/2021, 18:44:43] [Roomba] DEBUG: Connection close received from old connection
[20/10/2021, 18:44:45] [Roomba] DEBUG: Connection close received from old connection
[20/10/2021, 18:44:48] [Roomba] DEBUG: Connection close received from old connection
[20/10/2021, 18:44:52] [Roomba] DEBUG: Connection close received from old connection
[20/10/2021, 18:44:53] [Roomba] DEBUG: Connection close received from old connection
[20/10/2021, 18:44:55] [Roomba] DEBUG: Connection close received from old connection
[20/10/2021, 18:44:57] [Roomba] DEBUG: Connection close received from old connection
[20/10/2021, 18:44:59] [Roomba] Timed out after 60001ms trying to connect to Roomba
[20/10/2021, 18:44:59] [Roomba] Failed to connect to Roomba to refresh state: Connect timed out

It still appears fine from the Homebridge Accessories page (no "No Response" errors there), but from the Homekit app, still seeing no response. I am no longer seeing the "plugin slows down Homebridge" message, so that appears to be fixed.

[wonghc1]

@mpreissner I was having the same issue with an i4 I just purchased, but finally after playing with it for a few hours I finally got it.

1. Reboot the Roomba through the app.
2. Go to Account Setting in the iRobot app and Log out of all devices.
3. Open terminal in Homebridge, Follow the Command Line steps to switch to the proper directory
4. In the roomba2 dir run command "npm fund"
5. Run the get password command
6. At The prompt to press the button, Don't press any button on the Roomba, instead just press a button to continue.
7. At this point all of the info will generate, except you will get an error for the password.
8. Repeat the get password command
9. At the prompt to press a button, press and hold ONLY the HOME button for a few seconds and hit a button on the keyboard.

If done correctly you should get a prompt from the Roomba that it was setup successfully, and the terminal window will have all of the info and the password.

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 1.467s

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...
Robot Data:
undefined

[myzinsky]

I can confirm that sniffing the password works with this THOR app. You have to accept a cert and profile and then with a MitM attack you can fish out the password.

However, the robot is not responding:

[23/10/2021, 17:39:36] [homebridge-roomba2] This plugin slows down Homebridge. The read handler for the characteristic 'On' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.

I can also confirm that installing the BETA will help to remove this warning.

Nevertheless no response from the robot so far...

[mpreissner]

@karlvr if it would help, I’d be willing to give you access to my homebridge server to debug and work directly with the j7. All I’d need is your public IP address and an SSH key and I can punch a hole in my firewall for you. Let me know. Thanks!

[myzinsky]

Okay, once you have sniffed the password with a man in the middle attach, the solution is to replace all AES128-SHA256 with TLS_AES_256_GCM_SHA3 in

/usr/lib/node_modules/homebridge-roomba2/node_modules/dorita980/

Then the robot can be used with home bridge

[mpreissner]

Okay, once you have sniffed the password with a man in the middle attach, the solution is to replace all AES128-SHA256 with TLS_AES_256_GCM_SHA3 in

/usr/lib/node_modules/homebridge-roomba2/node_modules/dorita980/

Then the robot can be used with home bridge

So, I just did this, and I'm still not getting a response in Homekit. I am getting different errors, however.

[26/10/2021, 07:27:08] [Roomba] Running status: Returning no value due to timeout
[26/10/2021, 07:27:08] [Roomba] Bin status: Returning no value due to timeout
[26/10/2021, 07:27:08] [Roomba] Running status: Returning no value due to timeout
[26/10/2021, 07:27:08] [Roomba] Dock status: Returning no value due to timeout
[26/10/2021, 07:27:08] [Roomba] Low Battery status: Returning no value due to timeout
[26/10/2021, 07:27:13] [Roomba] DEBUG: Watching Roomba's status (repeating in 30s, idle timeout in 594s)
[26/10/2021, 07:27:17] [Roomba] Running status: Returning no value due to timeout
[26/10/2021, 07:27:17] [Roomba] Running status: Returning no value due to timeout
[26/10/2021, 07:27:17] [Roomba] Bin status: Returning no value due to timeout
[26/10/2021, 07:27:17] [Roomba] Dock status: Returning no value due to timeout
[26/10/2021, 07:27:17] [Roomba] Low Battery status: Returning no value due to timeout
[26/10/2021, 07:27:43] [Roomba] DEBUG: Watching Roomba's status (repeating in 30s, idle timeout in 573s)
(node:14745) UnhandledPromiseRejectionWarning: Error: error:1426E0B9:SSL routines:ciphersuite_cb:no cipher match
at Object.createSecureContext (_tls_common.js:216:13)
at Object.connect (_tls_wrap.js:1597:48)
at Object.buildBuilder (/usr/local/lib/node_modules/homebridge-roomba2/node_modules/mqtt/lib/connect/tls.js:13:20)
at MqttClient.wrapper [as streamBuilder] (/usr/local/lib/node_modules/homebridge-roomba2/node_modules/mqtt/lib/connect/index.js:140:36)
at MqttClient._setupStream (/usr/local/lib/node_modules/homebridge-roomba2/node_modules/mqtt/lib/client.js:277:22)
at new MqttClient (/usr/local/lib/node_modules/homebridge-roomba2/node_modules/mqtt/lib/client.js:258:8)
at Object.connect (/usr/local/lib/node_modules/homebridge-roomba2/node_modules/mqtt/lib/connect/index.js:143:10)
at localV2 (/usr/local/lib/node_modules/homebridge-roomba2/node_modules/dorita980/lib/v2/local.js:30:23)
at new local (/usr/local/lib/node_modules/homebridge-roomba2/node_modules/dorita980/index.js:17:10)
at getRoomba (/usr/local/lib/node_modules/homebridge-roomba2/dist/accessory.js:253:28)
at RoombaAccessory.connect (/usr/local/lib/node_modules/homebridge-roomba2/dist/accessory.js:300:24)
at RoombaAccessory.refreshState (/usr/local/lib/node_modules/homebridge-roomba2/dist/accessory.js:209:14)
at Timeout.checkStatus [as _onTimeout] (/usr/local/lib/node_modules/homebridge-roomba2/dist/accessory.js:606:18)
at listOnTimeout (internal/timers.js:557:17)
at processTimers (internal/timers.js:500:7)
(node:14745) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 4)
[26/10/2021, 07:28:13] [Roomba] DEBUG: Watching Roomba's status (repeating in 30s, idle timeout in 543s)
(node:14745) UnhandledPromiseRejectionWarning: Error: error:1426E0B9:SSL routines:ciphersuite_cb:no cipher match
at Object.createSecureContext (_tls_common.js:216:13)
at Object.connect (_tls_wrap.js:1597:48)
at Object.buildBuilder (/usr/local/lib/node_modules/homebridge-roomba2/node_modules/mqtt/lib/connect/tls.js:13:20)
at MqttClient.wrapper [as streamBuilder] (/usr/local/lib/node_modules/homebridge-roomba2/node_modules/mqtt/lib/connect/index.js:140:36)
at MqttClient._setupStream (/usr/local/lib/node_modules/homebridge-roomba2/node_modules/mqtt/lib/client.js:277:22)
at new MqttClient (/usr/local/lib/node_modules/homebridge-roomba2/node_modules/mqtt/lib/client.js:258:8)
at Object.connect (/usr/local/lib/node_modules/homebridge-roomba2/node_modules/mqtt/lib/connect/index.js:143:10)
at localV2 (/usr/local/lib/node_modules/homebridge-roomba2/node_modules/dorita980/lib/v2/local.js:30:23)
at new local (/usr/local/lib/node_modules/homebridge-roomba2/node_modules/dorita980/index.js:17:10)
at getRoomba (/usr/local/lib/node_modules/homebridge-roomba2/dist/accessory.js:253:28)
at RoombaAccessory.connect (/usr/local/lib/node_modules/homebridge-roomba2/dist/accessory.js:300:24)
at RoombaAccessory.refreshState (/usr/local/lib/node_modules/homebridge-roomba2/dist/accessory.js:209:14)
at Timeout.checkStatus [as _onTimeout] (/usr/local/lib/node_modules/homebridge-roomba2/dist/accessory.js:606:18)
at listOnTimeout (internal/timers.js:557:17)
at processTimers (internal/timers.js:500:7)

This is after hardcoding the new robot ciphers in the getpassword.js and local.js files in the dorita980 stuff (only two occurrences I found).

[adammodlin]

I'm trying this on my J7+ with the latest HomeBridge Roomba2 plugin and seeing this response:

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: Client network socket disconnected before secure TLS connection was established
    at connResetException (internal/errors.js:628:14)
    at TLSSocket.onConnectEnd (_tls_wrap.js:1561:19)
    at TLSSocket.emit (events.js:412:35)
    at endReadableNT (internal/streams/readable.js:1317:12)
    at processTicksAndRejections (internal/process/task_queues.js:82:21)
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) {
  code: 'ECONNRESET',
  path: undefined,
  host: '192.168.1.9',
  port: 8883,
  localAddress: undefined
}