homebridge-roomba2: ECONNREFUSED to j7+ after upgrade to 1.4.0

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

About this issue

Commits related to this issue

Most upvoted comments

So apparently a reboot of the robot through the app is not the same thing as the reboot that you have linked. I’ll give that a try tomorrow as I’m calling it a night for now.

It looks like I need to set it up as a new bot again - which is fine, but I’ll do that in the morning! Thanks for the help & I’ll update tomorrow.

@karlvr - Thanks Karl - no issues with the multiple tags/posts. I’m more than happy to help out and see how it can get working. I’m installing the latest one now and I’ll advise in a moment.

Installed and I’m still getting the same “Identifier rejected” error. Going to reboot the homebridge as well and see if that can somehow make a difference.