Roomba Intergration - Unable to connect to Roomba

[poelleke]

The problem

I am trying to add the Roomba integration. I had to find the password myself for this. but when I enter this I get the message that it cannot connect.

What version of Home Assistant Core has the issue?

core-2023.6.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

iRobot Roomba and Braava

Link to integration documentation on our website

https://www.home-assistant.io/integrations/roomba/

Diagnostics information

2023-06-11 09:06:24.799 INFO (roombapy) [roombapy.remote_client] Connecting to 192.168.1.16, attempt 1 of 3
2023-06-11 09:06:25.585 INFO (Thread-1763 (_thread_main)) [roombapy.roomba] Connecting to Roomba 192.168.1.16
2023-06-11 09:06:25.585 ERROR (Thread-1763 (_thread_main)) [roombapy.roomba] Roomba 192.168.1.16 connection error, code Bad username or password
2023-06-11 09:06:25.586 WARNING (Thread-1763 (_thread_main)) [roombapy.roomba] Unexpectedly disconnected from Roomba 192.168.1.16, code Not authorised
2023-06-11 09:06:26.070 INFO (roombapy) [roombapy.remote_client] Connecting to 192.168.1.16, attempt 1 of 3
2023-06-11 09:06:27.368 INFO (Thread-1764 (_thread_main)) [roombapy.roomba] Connecting to Roomba 192.168.1.16
2023-06-11 09:06:27.368 ERROR (Thread-1764 (_thread_main)) [roombapy.roomba] Roomba 192.168.1.16 connection error, code Bad username or password
2023-06-11 09:06:27.369 WARNING (Thread-1764 (_thread_main)) [roombapy.roomba] Unexpectedly disconnected from Roomba 192.168.1.16, code Not authorised
2023-06-11 09:06:27.908 INFO (roombapy) [roombapy.remote_client] Connecting to 192.168.1.16, attempt 1 of 3
2023-06-11 09:06:29.173 INFO (Thread-1765 (_thread_main)) [roombapy.roomba] Connecting to Roomba 192.168.1.16
2023-06-11 09:06:29.173 ERROR (Thread-1765 (_thread_main)) [roombapy.roomba] Roomba 192.168.1.16 connection error, code Bad username or password
2023-06-11 09:06:29.174 WARNING (Thread-1765 (_thread_main)) [roombapy.roomba] Unexpectedly disconnected from Roomba 192.168.1.16, code Not authorised
2023-06-11 09:06:29.662 INFO (roombapy) [roombapy.remote_client] Connecting to 192.168.1.16, attempt 1 of 3
2023-06-11 09:06:31.581 INFO (roombapy) [roombapy.remote_client] Connecting to 192.168.1.16, attempt 1 of 3
2023-06-11 09:06:31.738 ERROR (roombapy) [roombapy.remote_client] Can't connect to 192.168.1.16, error: [Errno 111] Connection refused
2023-06-11 09:06:31.738 INFO (roombapy) [roombapy.remote_client] Connecting to 192.168.1.16, attempt 2 of 3
2023-06-11 09:06:31.741 ERROR (roombapy) [roombapy.remote_client] Can't connect to 192.168.1.16, error: [Errno 111] Connection refused
2023-06-11 09:06:31.741 INFO (roombapy) [roombapy.remote_client] Connecting to 192.168.1.16, attempt 3 of 3
2023-06-11 09:06:31.750 ERROR (roombapy) [roombapy.remote_client] Can't connect to 192.168.1.16, error: [Errno 111] Connection refused
2023-06-11 09:06:31.750 ERROR (roombapy) [roombapy.remote_client] Unable to connect to 192.168.1.16
2023-06-11 09:06:31.751 WARNING (roombapy) [roombapy.roomba] Unexpectedly disconnected from Roomba 192.168.1.16, code Unable to connect to Roomba at 192.168.1.16

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant]

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)}}

[TheAlphaLaw]

@poelleke I had to move to Homekit integrations. Seems in this case they're better maintained.

[poelleke]

@poelleke I had to move to Homekit integrations. Seems in this case they're better maintained.

I don't use homekit. I don't have any apple products either.

[TheAlphaLaw]

@poelleke I had to move to Homekit integrations. Seems in this case they're better maintained.

I don't use homekit. I don't have any apple products either.

@poelleke I had to move to Homekit integrations. Seems in this case they're better maintained.

I don't use homekit. I don't have any apple products either.

I don't own any Apple products, but there are many things that integrate into Homekit via Homebridge and then into Home Assistant that don't have native support. https://homebridge.io/

[Hellmanx]

The project is dead. The devs seemed to have gone silent.

[joostlek]

What type of Roomba do you have?

[Hellmanx]

What type of Roomba do you have?

I Have an i3+. Worked before.

I personally have deleted the roombaa configuration and tried adding it again. It seems that the integration cannot send the cloud password to what ever it needs to send it to. Keeps failing.

[poelleke]

What type of Roomba do you have?

i have a Roomba Combo J7+

[joostlek]

How come you had to get your password manually? I remember I only had to press 2 buttons on the Roomba and it worked.

To verify some stuff, do you have any funky networking setup? Are you able to ping the Roomba from your HA setup?

[Hellmanx]

How come you had to get your password manually? I remember I only had to press 2 buttons on the Roomba and it worked.

To verify some stuff, do you have any funky networking setup? Are you able to ping the Roomba from your HA setup?

Never worked for me. HA can automatically detect the roombaa. HA just won't get the password automatically. I can get the password manually, but HA will say "Failed to connect" when I put in the password

[joostlek]

What firmware version are you running?

[Hellmanx]

What firmware version are you running?

Looks like 2.4.7

[joostlek]

In pschmitt/roombapy#97 I can see that there are multiple people having issues with the J7+. They have a workaround with capturing the password via their phone.

[poelleke]

In pschmitt/roombapy#97 I can see that there are multiple people having issues with the J7+. They have a workaround with capturing the password via their phone.

The roomba is on frimware 22.52.6
And i have already get the password from a workaround. But the problem is when i try to connect the intergration with the roomba it gives me a time out on the connection

[joostlek]

It seems that the J7+ communicates different than previous versions (I mean they went from firmware 2.4.x to 22.x.x). The roombapy lib is made from a fork, and that fork is inspired by another repo, and I found an issue in that repo for the J7+ (koalazak/dorita980#157), and they seem to link back to the HA forums (https://community.home-assistant.io/t/roomba-j7-integration-help/339705). Maybe this will help?

[Jshanks]

Just popping in to say i'm seeing this still with an S9+ on 2023.8.3. Discovery finds it and suggests adding it, that fails. Pulling the BLID and Password work via Dorita980's methods, but still get an error message stating that it can't connect in HA.

[jschonenberg]

I have the same issues with a Roomba i3+.
Integration used to work perfectly, but recently it disconnected and I can't seem to get it working again.

While setting up the integration it finds the Roomba perfectly fine, but then cannot retrieve the password automatically. I can retrieve the password manually using dorita980, but after entering it the integration states that it can't connect to the Roomba.

[seanmccabe]

Getting the same issue with the J7+, documentation says it should work, but it does not.
Retrieve the password using Dorita980 (the HA implementation also doesn't work, its just blank). However, entering the retrieved password says fails to connect

[Traxtar928]

Same issue with my i3+... Mine connects and integrates by just pressing the home button (not the spot button). After connection, HA communicates just fine and controls the Roomba.

The next day, the integration fails and cannot reconnect. Entities are all unavailable. I have no idea why this keeps happening.

[halfskye]

Experiencing the same issue with a Roomba s9+ on Product Software 22.29.6

Noticed today that the integration couldn't connect (not sure for how long) so I tried to reconnect but was unable. Then tried to remove the integration and then re-add it. It had previously detected the password automatically when I had originally setup the integration last year if I remember correctly, I needed to now run the dorita980 method to retrieve the password. When trying to connect using the manually retrieved password, I get a "Failed to connect" error.

[Traxtar928]

Are you pressing the home AND spot button, or just the home button? If pressing both, try just the home button and see if it pulls the password. That worked for me, but did not resolve the integration failing after a day.

[lambros414]

I'm having a similar issue with an i4 replacement. I was able to connect an i4 to HA with no problem. That roomba worked fine for about a month, then had charging issues. I got a replacement from iRobot. The new one isn't connecting. Funny thing is I can still connect my original one very easily. It actually is auto discovered. The new one, nope. I have to manually get the password information and input it during the connection process. When I do, I get "Connection failed". I have rebooted, factory reset and more several times.

I am working the issue with iRobot as well, but obviously they don't have to support third party products.

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.

[lambros414]

[Traxtar928],

thank you for your advice. I was FINALLY able to reconnect my roomba. just didn't press the home and spot buttons. I went to enter the password, I did, and even before I was going to hit the clean button, it connected. Seems like when the home and spot button are pushed, it won't communicate with the roomba (despite the instructions on the integration being different).

Thank you! all of my automations are working again!, at least for now.

[BIRDIE13]

Are you pressing the home AND spot button, or just the home button? If pressing both, try just the home button and see if it pulls the password. That worked for me, but did not resolve the integration failing after a day.

Can confirm that this worked with my i3 as well. Been struggling for a week trying to add the integration on a new HA instance. Thanks!

[seanmccabe]

I got this working for my j7+.

Instructions says hold the button for 20 seconds. DON'T. Press it once and it will work.

Holding causes the unit to reset.

The instructions for this should be updated.
In the case of the j7 it has only one button.

[aarnaegg]

I got this working for my j7+.

Instructions says hold the button for 20 seconds. DON'T. Press it once and it will work.

Holding causes the unit to reset.

The instructions for this should be updated.
In the case of the j7 it has only one button.

I'm trying this and it's not working… When I press the button once, it starts vacuuming. I get [Errno 111] Connection refused too. I got a J9+ (I assume would work the same as the J7) but I suppose it's not possible to add it?

[seanmccabe]

I got this working for my j7+.

Instructions says hold the button for 20 seconds. DON'T. Press it once and it will work.

Holding causes the unit to reset.

The instructions for this should be updated.
In the case of the j7 it has only one button.

I'm trying this and it's not working… When I press the button once, it starts vacuuming. I get [Errno 111] Connection refused too. I got a J9+ (I assume would work the same as the J7) but I suppose it's not possible to add it?

I'm not sure, I had heard the security was updated for that model, but could be wrong.

Are you pressing the button whilst it's on the dock and HA is looking for it.

[aarnaegg]

Are you pressing the button whilst it's on the dock and HA is looking for it.

I am. It plays the tone/beep, but I always get failed to connect after entering my password.

[seanmccabe]

Are you pressing the button whilst it's on the dock and HA is looking for it.

I am. It plays the tone/beep, but I always get failed to connect after entering my password.

Your password as in Roomba password, or the retrieved one?

[TimothyLeeAdams]

The problem is that there's only 1 button on this model and and when pressed, it starts a clean job. When held for 2-5 seconds while on the dock, it triggers the dock to evac. Neither triggers the connection when trying to setup with the integration.

[ffzeus22]

The problem is that there's only 1 button on this model and and when pressed, it starts a clean job. When held for 2-5 seconds while on the dock, it triggers the dock to evac. Neither triggers the connection when trying to setup with the integration.

As said above, there is only one button on the j7 and j9. A single short press begins cleaning, a long press, when docked, starts the clean base emptying, and a long press off of the base reboots the bot. There appears to be some error in how Home Assistant communicates with these bots.

[seanmccabe]

The problem is that there's only 1 button on this model and and when pressed, it starts a clean job. When held for 2-5 seconds while on the dock, it triggers the dock to evac. Neither triggers the connection when trying to setup with the integration.

As said above, there is only one button on the j7 and j9. A single short press begins cleaning, a long press, when docked, starts the clean base emptying, and a long press off of the base reboots the bot. There appears to be some error in how Home Assistant communicates with these bots.

I've got a J7+.
Leave it on the dock and when HA says to hold the buttons, just press the button once and it will pair.

I've done it a couple of times successfully.

HA can't get the password itself, but once you have it, the pairing works.

[aarnaegg]

The problem is that there's only 1 button on this model and and when pressed, it starts a clean job. When held for 2-5 seconds while on the dock, it triggers the dock to evac. Neither triggers the connection when trying to setup with the integration.

As said above, there is only one button on the j7 and j9. A single short press begins cleaning, a long press, when docked, starts the clean base emptying, and a long press off of the base reboots the bot. There appears to be some error in how Home Assistant communicates with these bots.

I've got a J7+. Leave it on the dock and when HA says to hold the buttons, just press the button once and it will pair.

I've done it a couple of times successfully.

HA can't get the password itself, but once you have it, the pairing works.

So the J7+ does work. You just have to retrieve the robot password yourself. The J9/J9+ does not work at all, even with the password. Seems everyone is missing that part. J7 does work J9 does not.

[TimothyLeeAdams]

The problem is that there's only 1 button on this model and and when pressed, it starts a clean job. When held for 2-5 seconds while on the dock, it triggers the dock to evac. Neither triggers the connection when trying to setup with the integration.

As said above, there is only one button on the j7 and j9. A single short press begins cleaning, a long press, when docked, starts the clean base emptying, and a long press off of the base reboots the bot. There appears to be some error in how Home Assistant communicates with these bots.

I've got a J7+. Leave it on the dock and when HA says to hold the buttons, just press the button once and it will pair.
I've done it a couple of times successfully.
HA can't get the password itself, but once you have it, the pairing works.

So the J7+ does work. You just have to retrieve the robot password yourself. The J9/J9+ does not work at all, even with the password. Seems everyone is missing that part. J7 does work J9 does not.

Interesting... I have a J9+, but have no luck with that approach. I'm just curious, when you do the pairing process and press the button on your J7+, does it start a clean job or does it do nothing other t

[aarnaegg]

Interesting... I have a J9+, but have no luck with that approach. I'm just curious, when you do the pairing process and press the button on your J7+, does it start a clean job or does it do nothing other than pair?

I have both the J7+ and J9+. I try the very exact same steps with the J7+ on the J9+, it does not work at all. As someone said above, the connections to the J9 is different than all the other roombas. So I think until the developers (@pschmitt @cyr-ius @shenxn) update this integration it won't work?

[seanmccabe]

The problem is that there's only 1 button on this model and and when pressed, it starts a clean job. When held for 2-5 seconds while on the dock, it triggers the dock to evac. Neither triggers the connection when trying to setup with the integration.

As said above, there is only one button on the j7 and j9. A single short press begins cleaning, a long press, when docked, starts the clean base emptying, and a long press off of the base reboots the bot. There appears to be some error in how Home Assistant communicates with these bots.

I've got a J7+. Leave it on the dock and when HA says to hold the buttons, just press the button once and it will pair.
I've done it a couple of times successfully.
HA can't get the password itself, but once you have it, the pairing works.

So the J7+ does work. You just have to retrieve the robot password yourself. The J9/J9+ does not work at all, even with the password. Seems everyone is missing that part. J7 does work J9 does not.

Interesting... I have a J9+, but have no luck with that approach. I'm just curious, when you do the pairing process and press the button on your J7+, does it start a clean job or does it do nothing other t

It just pairs, doesnt start a cleaning job or anything else.

[tuupos]

Have a j9+ as well. No luck here either.... My 960 connects without problems. Hope someone can get it to work .

[tuupos]

Can we work around this by automate it via home assistant --> IFTTT --> ROOMBA and get the j9 to work?

[MikeBookham]

J7+ A press of the button causes a beep but no HA connection.
The only way was to manually retrieve both the BLID (username) and the password, refer to the instructions in the Roomba 980 or dority 980 repository.

I followed the dority 980 option 3 Docker method, if you get an error stating that the username/password is incorrect then I suggest changing your password to 20 characters or less (Upper/Lower/Numbers - no special characters).
I have done this twice now due to an HA update wiping the Roomba key.

[jdwhite]

Are you pressing the home AND spot button, or just the home button? If pressing both, try just the home button and see if it pulls the password. That worked for me, but did not resolve the integration failing after a day.

Can confirm that this worked with my i3 as well. Been struggling for a week trying to add the integration on a new HA instance. Thanks!

Roomba i8: confirm pressing home only for 2-3 seconds works; home and spot together did not. HA was able to grab pull the password no problem.

[klavergne]

I have a Roomba i7, and I have not had issues until recently. It was appearing in HA as normal, and still is. But when I press the "clean" button in the HA dashboard, it does nothing. I turned on debug logs in the iRobot integration and reloaded it, and I got a lot of errors in the logs. Below is what I got:

2024-01-15 09:08:00.107 DEBUG (SyncWorker_2) [roombapy.remote_client] Setting TLS certificate
2024-01-15 09:08:00.108 DEBUG (SyncWorker_2) [roombapy.roomba] CONTINUOUS connection
2024-01-15 09:08:00.112 DEBUG (MainThread) [homeassistant.components.roomba] Initialize connection to vacuum
2024-01-15 09:08:00.115 INFO (SyncWorker_11) [roombapy.remote_client] Connecting to {IP address}, attempt 1 of 3
2024-01-15 09:08:00.209 ERROR (SyncWorker_11) [roombapy.remote_client] Can't connect to {IP address}, error: [Errno 111] Connection refused
2024-01-15 09:08:00.209 INFO (SyncWorker_11) [roombapy.remote_client] Connecting to {IP address}, attempt 2 of 3
2024-01-15 09:08:00.214 ERROR (SyncWorker_11) [roombapy.remote_client] Can't connect to {IP address}, error: [Errno 111] Connection refused
2024-01-15 09:08:00.215 INFO (SyncWorker_11) [roombapy.remote_client] Connecting to {IP address}, attempt 3 of 3
2024-01-15 09:08:00.221 ERROR (SyncWorker_11) [roombapy.remote_client] Can't connect to {IP address}, error: [Errno 111] Connection refused
2024-01-15 09:08:00.221 ERROR (SyncWorker_11) [roombapy.remote_client] Unable to connect to {IP address}
2024-01-15 09:08:00.223 DEBUG (MainThread) [homeassistant.components.roomba] Error to connect to vacuum: Unable to connect to Roomba at {IP address}

That just keeps repeating in the logs, because it tried to reload the integration repeatedly.

I have been trying to get a list of all the "room ids" (I don't remember what they are actually called) for the rooms in my house, so that I can use HA to start vacuuming individual rooms. I had been able to use dorita980 to do that until a couple of days/months ago. (I had not tried for a while until last week.) Now I can't get it to connect. I get the same "connection refused" error directly from dorita980. (I'm not sure what the relationship is between this HA integration and that project, if there is one, but I thought I would mention it, since the results are the same. I have also submitted an issue to that project.)

Roomba i7
Software Version: 22.52.10

[kotasd]

Is this issue even being worked? It appears to be known problem for quite some time with lots of potential workarounds that seem to not work in the end. Same issues with J5.

[Orhideous]

Is this issue even being worked?

@kotasd Yes, right now (no joke).

[kotasd]

Is this issue even being worked?

@kotasd Yes, right now (no joke).

Great, I was about to just write off my Roomba being HA controlled.

[aBlindReefer]

I’m not able to connect a j7+ either (Latest haos). I’ve tried the Roomba980 repository instructions as well. Not complaining and I appreciate the time and effort that goes into these things but just for comparison (just for reference as they were able to get through whatever changes happened with this model) the Homeseer plugin asks for your iRobot account user name and password at startup (not blid and password). This would be a nice addition as opposed to having to use ssh/terminal, python, and additional GitHub repositories to enter this information.

[ObJuanK]

I was able to connect to and issue commands to my J7+ using dority 980 this repo to get the BLID and password.
From my computer I created a myapp.js file as the repo suggests and I was able to issue it a command to clean and dock etc...
Using the same password in HA I get a "Failed to connect" error identical to this

Not really helpful I dont think, but some log entries from HA during the attempt

2024-03-22 19:45:51.977 ERROR (roombapy) [roombapy.remote_client] Can't connect to 10.55.100.17
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/roombapy/remote_client.py", line 80, in connect
    self._open_mqtt_connection()
  File "/usr/local/lib/python3.12/site-packages/roombapy/remote_client.py", line 108, in _open_mqtt_connection
    self.mqtt_client.reconnect()
  File "/usr/local/lib/python3.12/site-packages/paho/mqtt/client.py", line 1044, in reconnect
    sock = self._create_socket_connection()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/paho/mqtt/client.py", line 3685, in _create_socket_connection
    return socket.create_connection(addr, timeout=self._connect_timeout, source_address=source)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/socket.py", line 852, in create_connection
    raise exceptions[0]
  File "/usr/local/lib/python3.12/socket.py", line 837, in create_connection
    sock.connect(sa)
ConnectionRefusedError: [Errno 111] Connection refused

[quadcom]

Just posted this in another thread, similar situation.

#112544 (comment)

[RonaldvE]

I figured out my problem. I was not allowing UDP traffic on my firewall. After I corrected that issue, I was able to get it to connect.

This solved it for me as well! Forwarding for Port 443 was set as TCP only and after allowing Both (TCP and UDP) my Roomba 980 connected instantly!

[quadcom]

I figured out my problem. I was not allowing UDP traffic on my firewall. After I corrected that issue, I was able to get it to connect.

This solved it for me as well! Forwarding for Port 443 was set as TCP only and after allowing Both (TCP and UDP) my Roomba 980 connected instantly!

I'm confused, what are you forwarding 443 to? The vac? Your HA server? Why would opening your FW to HTTPS traffic allow internal network traffic to get this working. This makes no sense.

[aarnaegg]

I'll give this a try today. For months I have still not been able to connect my J9+ to HA. HA can see it, but can never connect.

[tuupos]

Solution found for J7/J9

#112544 (comment)

[issue-triage-workflows]

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.

[ffzeus22]

Still unable to connect with j9+. Is this proect dead?

[DigiMaxIO]

For those still struggling with this, I found (at least in my case) that the reason was that I had another service still connected to roomba. In my particular case I had mine connected to homebridge. But anything else similar to that will likely cause the same problem.

[mempoule]

FYI, I spent like... hours figuring it out, here's the solution. Dirty, but works.

tldr: install on pi with official OS, and export core.device_registry, and core.config_entries

1. Install on HAOS (my main install is on Docker, because I want to save power =/= adding another pi, and I already have a proxmox running 24/7)
2. Make sure you are on the same vlan / subnet.
   This could seem stupid, but I don't want to have a HA directly on the IoT VLAN, and it seems it was the "main" problem.
3. Go back to Integration, and add the Roomba, which won't wait for timeout to give you the error, and will ask you to give IP, and press home 2 sec.
   Tadaaaa, it is integrated.

Now extract the two files core.device_registry, and core.config_entries from your pi, and locate the lines mentionning Roomba (you should find IP address matching your input, etc.
Add those lines on the corresponding files on your docker instance, reboot, and it's done :)