Can't add my new/replaced irobot into home assistant

[lambros414]

The problem

I had a roomba i4 and have successfully connected it to Home assistant through the irobot integration. Have been using for over a month. that robot died and I had to get a replacement from iRobot. That Roomba is now working with the iRobot app. When I removed the old roomba, I removed the integration within HA. When I trying to reinstall, I am getting an error: "Failed to connect"

I had to manually retrieve my password using the docker approach:

docker run -it node sh -c "npm install -g dorita980 && get-roomba-password-cloud

I did get a password back....

Found 1 robot(s)! Robot "Roomba" (sku: i415020 SoftwareVer: daredevil+2.4.1p1+Firmware-Build+1537): BLID=> XXXXXXXXXXXXXXXXXXXXXXXX Password=> XXXXXXXXXXXXXXXXXXXXXX <= Yes, all this string.

When I try to add the device, it sometime finds the host, sometime does not. I have the IP address of the roomba so have attempted to put it in manually.

I get a message that it can't retrieve the password manually, so I add the password I retrieved (the whole thing, except the leading and following spaces). Every time I attempt to connect, I get an error "Failed to connect"

I have rebooted the roomba SEVERAL times. I have made sure the roomba app isn't running on my phone. I think I have done everything.

I was able to successfully add the previous roomba (before it died), so I am pretty sure I following instructions properly.

Any thoughts?

What version of Home Assistant Core has the issue?

2023.9.0

What was the last working version of Home Assistant Core?

2023.9.0

What type of installation are you running?

Home Assistant OS

Integration causing the issue

iRobot

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @pschmitt, @cyr-ius, @shenxn, mind taking a look at this issue as it has been labeled with an integration (roomba) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `roomba` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign roomba` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

roomba documentation roomba source _{^{(message by IssueLinks)}}

[lambros414]

Hi,

Thank you for forwarding my issue to hopefully the right people.

If the right people are on the thread, I would like to share a couple of things that may help, or possibly can give suggestions for a work around….

After numerous attempts to add my new roomba to HA by doing factory resets, trying manually to add, etc with no luck, I attempted, and succeeded in including my old robot back in (I still have the old robot, and it works electronically, but other parts broke). The old robot has NO problems pairing. As a matter of fact, HA even automatically found that robot and asked if I wanted to include it.

I have determined that there must be something different between the two. They are both i4 rombas. I spoke with iRobot, they confirmed that not only are they the same version, but were made only a few months apart. There is a difference though, the newer one was made at a different plant. Also, my older one seems to have a software version that the new one is not yet able to be upgraded to. (iRobot is looking into that on their side).

My question for our forum or HA people is the following…. Even though I removed the old robot, and the integration, are there residual files in HA that may have information about the old robot that allows it to pair and could be preventing my new one from pairing. I was hoping to find a way of completely cleansing my HA instance from any of the integration files, and reinstalling everything from absolute scratch to see if that is the problem.

If it isn’t, I am hoping iRobot will be able to share some information that I can share here that can hopefully explain why one robot pairs, and one does not.

Any feedback would be greatly appreciated.

Cheers,

Chuck Lambros

On Sep 8, 2023, at 6:59 PM, home-assistant[bot] @.***> wrote:

Hey there @pschmitt https://github.com/pschmitt, @cyr-ius https://github.com/cyr-ius, @shenxn https://github.com/shenxn, mind taking a look at this issue as it has been labeled with an integration (roomba) you are listed as a code owner https://github.com/home-assistant/core/blob/dev/CODEOWNERS#L1055 for? Thanks!

Code owner commands (message by CodeOwnersMention)

roomba documentation https://www.home-assistant.io/integrations/roomba roomba source https://github.com/home-assistant/core/tree/dev/homeassistant/components/roomba (message by IssueLinks)

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/99957#issuecomment-1712315986, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANVOMJ5YAXSB4QVFH7TYEHTXZOPN5ANCNFSM6AAAAAA4Q44R24. You are receiving this because you authored the thread.

[lambros414]

Sorry, leaving one more comment here. Haven't heard back from anyone yet, but I do have some more, or possibly clarifying information.

Although I thought I could add my old roomba back into HA, since it was auto discovered. When I did go through the process, it stopped the same way my new one does in that it asks for the password (which I get using the method included in the instructions, but then says "connection failed"

I am beginning to believe that possibly an HA update must have broke the integration, since I was able to install it pretty easily back at end of July, beginning of August. There have been a few core updates of HA since then.

I would be surprised if others were not having this issue as well.

Sorry if possibly my last comment may have been misleading.

I have built a number of automations for the roomba when it was integrated. I'm very sad that it is no longer connected to HA. I would be happy to assist anyone who does own (or works on the code) in any way I can.

Thanks in advance,

Chuck

[eduperez]

My Roomba 960 updated the firmware on August 3rd; since then, I cannot connect to it from HA. I have been scanning the ports using nmap, and it has none open. So, I guess it is no longer usable locally.

[herbertgoat]

I have an i981 Roomba that I can no longer connect to HA. It has worked in the past but I wouldn't like to guess when it stopped working, but is many versions of HA ago (probably 2022)

I have tried several times to connect using all the documented ideas but none work (factory reset Roomba, manual connect etc)

[mattbruman]

My old Roomba 989 must have updated and broke because about a month ago it stopped connecting to HA and I am unable to repair it to HA. I guess its time to retire the little guy and upgrade to something more HA friendly.

[Harrison-Phillips]

Was there ever any progress on this topic? I have also ran into this issue where I cannot reconnect an i7 after deleting its integration. I tried factory restarting it and re-adding the device but auto-discovery doesn't work.

[djh00t]

I am also having this issue.

[Orhideous]

Does this issue exist in 2024.2.4?

[aarnaegg]

@Orhideous I'm still getting Failed to connect on my J7+ and J9+ Roombas on 2024.2.4 / 1.6.13. I still appreciate the work being done!

[Orhideous]

@aarnaegg If you're interested in helping me diagnose the problem (and there's nothing meaningfuk in the logs), would you mind if I wrote to you in a few days? I have an idea what to do.

[aarnaegg]

@Orhideous Yeah I'll do that. Just let me know what you need.

[mattbruman]

Does this issue exist in 2024.2.4?

After I seen the roomba update I tried again. I was able to finally reconnect my 989 model to HA again. But I did have to factory reset the robot and add back to my network.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.