homebridge-plugins / homebridge-roomba2

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

J7 Not connecting #106

Closed DanLysk closed 2 years ago

DanLysk commented 2 years ago

I have been able to get my Serial, BLID, and password nor problem. Hoobs still says it can't connect. This is a J7 Roomba. I will share screenshots. CapturFiles_2 CapturFiles_1 CapturFiles

karlvr commented 2 years ago

@DanLysk please try the latest version (v1.3.0 has just been released)

DanLysk commented 2 years ago

Hey! Thanks for the heads up on 1.3.1... I got the plug-in updated in HOOBS... Here is what I get now. CapturFiles

Drewbacca2 commented 2 years ago

I just updated to 1.3.1 and am having the same problem with my J7. My 980 runs perfectly though. I'd been using the beta version for the last couple months flawlessly. Unfortunately, something seems to be broken, because I can't go back to the beta. I even tried restoring my Hoobs system to a back-up, and the J7 won't connect at all anymore. I've made sure the cipher is changed over in local.js too.

mpreissner commented 2 years ago

You need to update the local.js file to use TLS_AES_256_GCM_SHA384 for the ROBOT_CIPHERS variable for it to work on a J7. This was the fix found in https://github.com/karlvr/homebridge-roomba2/issues/81, though it seems that updating to the latest version of the plugin resets the variable to the old cipher. I'm running the homebridge official image, and my local.js file is at /usr/local/lib/node_modules/homebridge-roomba2/node_modules/dorita980/lib/v2/local.js

Mine's working flawlessly after fixing that.

Drewbacca2 commented 2 years ago

I’ve done that and got it working. I run a HOOBS system, so the local.js file was in a different place and took me awhile to find. The problem is that I also run a 980, which didn’t work with the new cipher. So, I had to install two bridges, one with the new one, and one with the old one. It seems to be working now, but for some reason, the Roombas tend to have trouble docking more than without the plugin. I figured it was because of frequent connections with my device by the plugin, so I reduced the devices down to just the start trigger and disabled the rest. It worked better but still will occasionally fail to dock or run out of batteries. Any thoughts on this?

On Mar 24, 2022, at 8:10 AM, mpreissner @.***> wrote:

You need to update the local.js file to use TLS_AES_256_GCM_SHA384 for the ROBOT_CIPHERS variable for it to work on a J7. This was the fix found in #81 https://github.com/karlvr/homebridge-roomba2/issues/81, though it seems that updating to the latest version of the plugin resets the variable to the old cipher. I'm running the homebridge official image, and my local.js file is at /usr/local/lib/node_modules/homebridge-roomba2/node_modules/dorita980/lib/v2/local.js

Mine's working flawlessly after fixing that.

— Reply to this email directly, view it on GitHub https://github.com/karlvr/homebridge-roomba2/issues/106#issuecomment-1077611287, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXP34QNLV457TEIE4NDQ75TVBRSV3ANCNFSM5QSEJWMQ. You are receiving this because you commented.

mpreissner commented 2 years ago

No clue. I've had no issues with my J7 ever since I got it working.

You shouldn't have to run separate bridges for the two Roomba types. You could run the Dorita980 plugin and the roomba2 plugin on the same bridge, as the Roomba2 uses a localized copy of the 980 modules within its folder structure - should just have to modify the local.js in that one to get the j7 working. Although, running separate bridges is a good idea anyway...if any issues crop up with one of them, it could affect the other if they're on the same bridge, so probably not worth changing the config since you've got it running already.

Drewbacca2 commented 2 years ago

Really, we’re having more trouble with the 980 than the J7. It’s gotten stuck 5 out of the last 8 days. However, a couple of those times were due to things getting in the way, so I’m not ready to blame the Roomba2 plugin. It had been working fine for months before the latest update. I don’t have the Dorita980 plugin and have just used the one that’s built into yours. Thank you for your responses. I had struggled for months with the homebridge-irobot app, but I could never get both the J7 and the 980 working at the same time. Yours has seemed to fix that.

On Mar 24, 2022, at 10:48 AM, mpreissner @.***> wrote:

No clue. I've had no issues with my J7 ever since I got it working.

You shouldn't have to run separate bridges for the two Roomba types. You could run the Dorita980 plugin and the roomba2 plugin on the same bridge, as the Roomba2 uses a localized copy of the 980 modules within its folder structure - should just have to modify the local.js in that one to get the j7 working. Although, running separate bridges is a good idea anyway...if any issues crop up with one of them, it could affect the other if they're on the same bridge, so probably not worth changing the config since you've got it running already.

— Reply to this email directly, view it on GitHub https://github.com/karlvr/homebridge-roomba2/issues/106#issuecomment-1077775231, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXP34QJKKSCOUOXLENJANX3VBSFERANCNFSM5QSEJWMQ. You are receiving this because you commented.

longman391 commented 2 years ago

I’ve done that and got it working. I run a HOOBS system, so the local.js file was in a different place and took me awhile to find. The problem is that I also run a 980, which didn’t work with the new cipher. So, I had to install two bridges, one with the new one, and one with the old one. It seems to be working now, but for some reason, the Roombas tend to have trouble docking more than without the plugin. I figured it was because of frequent connections with my device by the plugin, so I reduced the devices down to just the start trigger and disabled the rest. It worked better but still will occasionally fail to dock or run out of batteries. Any thoughts on this?

Can you share where this file was located on HOOBS? I'm coming up empty and traversing the hierarchy by hand isn't easy with all of the instanced plugins.

longman391 commented 2 years ago

Nevermind, found it: /var/lib/hoobs/roomba2bridge

DanLysk commented 2 years ago

I updated my Cypher… .Still no worky for my J7

Daniel Lysk 501-804-7542 | @. @.> www.CentralArkansasVegan.org http://www.centralarkansasvegan.org/ -------- @ @ @ @ _~@ ----- \<,_ _\<, \<,_ _\<, `\<,_ ---- ()/ () ()/ () ()/ () ()/ () ()/ ()



> On Mar 24, 2022, at 11:51 AM, Drewbacca2 ***@***.***> wrote:
> 
> 
> Really, we’re having more trouble with the 980 than the J7. It’s gotten stuck 5 out of the last 8 days. However, a couple of those times were due to things getting in the way, so I’m not ready to blame the Roomba2 plugin. It had been working fine for months before the latest update. I don’t have the Dorita980 plugin and have just used the one that’s built into yours. Thank you for your responses. I had struggled for months with the homebridge-irobot app, but I could never get both the J7 and the 980 working at the same time. Yours has seemed to fix that.
> 
> > On Mar 24, 2022, at 10:48 AM, mpreissner ***@***.***> wrote:
> > 
> > 
> > No clue. I've had no issues with my J7 ever since I got it working.
> > 
> > You shouldn't have to run separate bridges for the two Roomba types. You could run the Dorita980 plugin and the roomba2 plugin on the same bridge, as the Roomba2 uses a localized copy of the 980 modules within its folder structure - should just have to modify the local.js in that one to get the j7 working. Although, running separate bridges is a good idea anyway...if any issues crop up with one of them, it could affect the other if they're on the same bridge, so probably not worth changing the config since you've got it running already.
> > 
> > —
> > Reply to this email directly, view it on GitHub <https://github.com/karlvr/homebridge-roomba2/issues/106#issuecomment-1077775231>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXP34QJKKSCOUOXLENJANX3VBSFERANCNFSM5QSEJWMQ>.
> > You are receiving this because you commented.
> > 
> 
> —
> Reply to this email directly, view it on GitHub <https://github.com/karlvr/homebridge-roomba2/issues/106#issuecomment-1077831984>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AX3GDPFZHBDBUBRDYMI54PDVBSMRZANCNFSM5QSEJWMQ>.
> You are receiving this because you were assigned.
> 
karlvr commented 2 years ago

@DanLysk this may also be related to an issue with Node 18. Can you confirm which version of node your Homebridge is running on? On the Homebridge UI status page it's listed in the System Information panel.

DanLysk commented 2 years ago

Looks like I am on Node 16.18.1. I got Roomba working with a full Hoobs reload. Thank you for the follow up.

Daniel Lysk 501-804-7542 | @.** www.CentralArkansasVegan.org -------- @ @ @ @ _~@ ----- \<,_ _\<, \<,_ _\<, `\<,_ ---- ()/ () ()/ () ()/ () ()/ () ()/ (*)



> On Nov 18, 2022, at 10:21 PM, Karl von Randow ***@***.***> wrote:
> 
> 
> @DanLysk <https://github.com/DanLysk> this may also be related to an issue with Node 18. Can you confirm which version of node your Homebridge is running on? On the Homebridge UI status page it's listed in the System Information panel.
> 
> —
> Reply to this email directly, view it on GitHub <https://github.com/karlvr/homebridge-roomba2/issues/106#issuecomment-1320792903>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AX3GDPDOPOHCFBGMFC3AQW3WJBITBANCNFSM5QSEJWMQ>.
> You are receiving this because you were mentioned.
> 
karlvr commented 2 years ago

I hope this is resolved once and for all with version 1.3.2-beta.1. Please try it out and re-open this issue if there are still connection problems with J7s.