ECONNREFUSED to j7+ after upgrade to 1.4.0

[dgilev]

homebridge-roomba2 pluging stopped working right after upgrade from 1.3.1 to 1.4.0. Getting the following error:

[12/12/2022, 3:57:55 PM] [xxxxxx] DEBUG: Will refresh Roomba's status again automatically in 15m
[12/12/2022, 4:12:55 PM] [xxxxxx] DEBUG: Automatically refreshing Roomba's status
[12/12/2022, 4:12:55 PM] [xxxxxx] DEBUG: Connecting to Roomba (0 others waiting)...
[12/12/2022, 4:12:55 PM] [xxxxxx] DEBUG: Connection close received
[12/12/2022, 4:12:56 PM] [xxxxxx] DEBUG: Old connection received error: connect ECONNREFUSED 192.168.1.166:8883
[12/12/2022, 4:13:55 PM] [xxxxxx] DEBUG: Timed out after 60000ms trying to connect to Roomba
[12/12/2022, 4:13:55 PM] [xxxxxx] Failed to refresh Roomba's state: Connect timed out

IP/port are correct and pingable/accessible from homebridge instance:

% telnet 192.168.1.166 8883
Trying 192.168.1.166...
Connected to irobot-xxxxxx.localdomain.
Escape character is '^]'.

Tried to reboot both homebridge and robot itself to no success. I remember that I had to change ciphers used by dorita980 module in the past version but it looks like it's already accounted for in 1.4.0 with addition of TLS_AES_256_GCM_SHA384:

ciphers: process.env.ROBOT_CIPHERS || 'AES128-SHA256,TLS_AES_256_GCM_SHA384'

Any ideas on how to troubleshoot it further? Thanks!

Versions

• Homebridge: 1.6.0
• Node: v16.13.1
• Plugin: homebridge-roomba2 v1.4.0

[karlvr]

@dgilev this is curious. Perhaps try removing AES128-SHA256 from that ciphers string to see if that makes a difference?
Sometimes having another connection open to the Roomba, such as an app etc can cause further connections to be rejected, so make sure there isn't anything else connected?

[IngmarStein]

+1. I'm getting the same error since 1.4.0 for a 980 which is pingable and reachable on port 8883, but I get connection timeouts:

[12/19/2022, 10:21:15 PM] [Robbie] Timed out after 60000ms trying to connect to Roomba
[12/19/2022, 10:21:15 PM] [Robbie] Failed to refresh Roomba's state: Connect timed out
[12/19/2022, 10:21:15 PM] [Robbie] Will refresh Roomba's status again automatically in 15m

[dgilev]

@karlvr Removing of AES128-SHA256 did the trick! But I swear I tried it before and it didn't work. 😁 Thanks for the suggestion though!

To anyone who is facing the same issue with J7 (not sure if other models are affected) on homebridge-roomba2 v1.4.0 and/or new dorita980 module: remove AES128-SHA256 from the ciphers list in homebridge-roomba2/node_modules/dorita980/lib/v2/local.js leaving only TLS_AES_256_GCM_SHA384.

[karlvr]

@dgilev wow, OK, good news but that's a bit of a bummer. I thought it was neat that we could specify multiple ciphers. Could you please try putting the two ciphers in the opposite order and see if you can connect?

[raghavsethi]

Can confirm this fixes connection issues with j7. Thanks @dgilev!

[Firemanjoe]

I'm getting the same error on my i1+ that I just purchased today and for some reason I am unable to edit the js file. It's asking for the password ad when I enter my hombridge password, it says that it's not accepted.

Thoughts?

Further clarification, I've been able to add the unit to the homebridge and I've been able to edit the json file; however, when I remove the AES128-SHA256, I loose contact for my 691; however, it also doesn't enable the i1+. It continues to timeout.

If I remove TLS_AES_256_GCM_SHA384, I'm not any further either.

[karlvr]

Please try installing version 1.5.0-beta.0... I have overhauled the connection logic so we attempt multiple ciphers now. Hopefully I've correctly detected the connection failure in all cases...

To install the beta click on the wrench on the plugin on the Plugins screen, and choose Install Alternate Version.

If you have Debug logging enabled you should see a log entry like:

[4/24/2023, 6:57:21 AM] [Roomba] DEBUG: Connection received error: Client network socket disconnected before secure TLS connection was established
[4/24/2023, 6:57:21 AM] [Roomba] Retrying connection to Roomba with cipher TLS_AES_256_GCM_SHA384

If it doesn't work, I need to see the error messages, such as the "Failed to refresh Roomba's state..." message. Please turn on Debug logging so there are more detailed logs to examine, and also please include the version of Node you are using to run Homebridge.

[Firemanjoe]

This is what I am getting now vs the previous timeout errors that I was getting. Joel Gallant www.joelgallant.ca photography.joelgallant.ca

…

On Apr 23, 2023 at 4:07:37 PM, Karl von Randow ***@***.***> wrote: Please try installing version 1.5.0-beta.0... I have overhauled the connection logic so we attempt multiple ciphers now. Hopefully I've correctly detected the connection failure in all cases... To install the beta click on the wrench on the plugin on the Plugins screen, and choose Install Alternate Version. If you have Debug logging enabled you should see a log entry like: [4/24/2023, 6:57:21 AM] [Roomba] DEBUG: Connection received error: Client network socket disconnected before secure TLS connection was established [4/24/2023, 6:57:21 AM] [Roomba] Retrying connection to Roomba with cipher TLS_AES_256_GCM_SHA384 If it doesn't work, I need to see the error messages, such as the "Failed to refresh Roomba's state..." message. Please turn on Debug logging so there are more detailed logs to examine, and also please include the version of Node you are using to run Homebridge. — Reply to this email directly, view it on GitHub <#129 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AELGWZCPIXBQQ5BRJIWSXEDXCV4XTANCNFSM6AAAAAAS4SSAWE> . You are receiving this because you commented.Message ID: ***@***.***>

[karlvr]

@Firemanjoe it looks like the email reply list what you were trying to send.

[Firemanjoe]

Yes sorry, looks like gmail stripped it out. Here you go!