iRobot Roomba S9+ "Cloud cannot connect to [my Roomba's name]" message

Comments

67 comments

  • Avatar
    IHaveABigNetwork

    I've worked with iRobot on this as well and still get the same message.  I've punched the same holes and tried Emergency access.  Also all on a S9+.

    0
    Comment actions Permalink
  • Avatar
    Michael Plavin

    Glad it's not just me. This is pretty frustrating, since I'd expect FWG to at least log traffic, but nope. I'll give iRobot a buzz and see if I can get anywhere with them, although I suspect they'll just point me to the documentation I posted above or ask me to factory reset my Roomba, which I've already done to no avail.

    Anyone from Firewalla run into this issue and have a good workaround? I posted about this on the Firewalla Subreddit but didn't get any good responses; one person said they thought they had it working, but it later turned out they were incorrect. We cannot be the only two people on the entire planet who have Firewalla devices and iRobot Roomba S9+...

    0
    Comment actions Permalink
  • Avatar
    Firewalla

    Reading the doc, you really do not need to add allow rules.  As for the error, need some more information

    1. are you using segmentation on your network?

    2. the emergency mode for certain traffic blocked using DNS may take a while to work.  Reason is DNS need to timeout on the roomba inside.    After turning on emergency mode, try to reboot (not sure how) roomba to reset its DNS services.

     

    0
    Comment actions Permalink
  • Avatar
    IHaveABigNetwork

    I'm not using segmentation.


    I've reset the roomba and waited days to no avail while leaving it in emergency mode.

    0
    Comment actions Permalink
  • Avatar
    Michael Plavin

    1. No segmentation here. I have tried both using and not using a device group with no changes to the result.

    2. Same as IHABN. Again, I would expect to see SOMETHING logged from the device with or without Emergency Access, but I'm not, which is bizarre.

    0
    Comment actions Permalink
  • Avatar
    Firewalla

    How about the DNS features? like DoH?   or using pi-hole?

    The reason you have not seen flows may be it can't get DNS resolved.   

    1
    Comment actions Permalink
  • Avatar
    IHaveABigNetwork

    I used DoH but turned it off rebooting both the device and the Gold.  Not using pi-hole.

    0
    Comment actions Permalink
  • Avatar
    Michael Plavin

    iRobot's 2nd level support is supposed to call me back in the next 24-48 hours with any additional information.

    0
    Comment actions Permalink
  • Avatar
    Michael Plavin

    No pi-hole, and I did use DoH, but only for certain devices, like my personal computer, work computer, etc. - not the Roomba. I assumed that, since it's something that can be enabled on a device-by-device basis, devices that don't use it would just use the default DNS.

    @IHaveABigNetwork - how long have you been dealing with this?

    0
    Comment actions Permalink
  • Avatar
    IHaveABigNetwork

    I switched from my Edgerouter 4 to my Gold about a month ago.  Problem has been since then.

    0
    Comment actions Permalink
  • Avatar
    Firewalla

    What is the DNS service is the Roomba using?  Also, if you guys talk to roomba, see if can find out what services that box talks to. 

    0
    Comment actions Permalink
  • Avatar
    Michael Plavin

    I noticed something on the wifi settings on the Roomba S9: it says "Robot is communicating with the MQTT broker" under Connectivity Status now that I don't have the FWG in the network. I had previously opened the port for MQTT (TCP 8883 and 443, per the iRobot docs), but I'm looking online and it says that port 1833 is the default MQTT port.

    The 980 says "Server OK" under Connectivity Status.

    I'm sure both use MQTT (someone posted the 980's python library to GitHub, but I'm wondering if one can be run locally and the other REQUIRES cloud access, for whatever reason...

    @IHaveABigNetwork - I don't have my FWG installed at the moment. If you do, can you try opening that port and seeing if it resolves the issue? I'm going to reconfigure the network and reinstall my FWG as well.

    0
    Comment actions Permalink
  • Avatar
    Michael Plavin

    Update: no change. In fact, I allowed ALL traffic, and still received the error message.

    0
    Comment actions Permalink
  • Avatar
    Firewalla

    @michael, I have created a ticket and we will follow up there.  We may need support access and look at the polices and see if there are anything that's blocking

    0
    Comment actions Permalink
  • Avatar
    Michael Plavin

    No worries.

    0
    Comment actions Permalink
  • Avatar
    James Willhoite

    I have the S9+ and the Brava and have no problems. I am running the FWG in Router mode, and have a primary lan and 2 VLAN going. I use TP-Link EAP 245.

    0
    Comment actions Permalink
  • Avatar
    Michael Plavin

    Hmmmm. Okay. Did you have to create any rules for the S9+? I have a 980 that works just fine.

    0
    Comment actions Permalink
  • Avatar
    James Willhoite

    Nothing at all. I had it on my main network (no VLAN tag) and I just recently moved it to a VLAN along with all my other IoT devices to separate them. I’ve had no problem.

    I used to use a Linksys router as a AP before it went out and I got the TP-Link. Had no issues with that either. Sounds to me like it is your Mesh.

    Do you have an old router you could turn into a AP to test it out?

    0
    Comment actions Permalink
  • Avatar
    IHaveABigNetwork

    My 980 works fine. The s9+ is the problem. It works fine if I use my Edgerouter or eero as router

    0
    Comment actions Permalink
  • Avatar
    Michael Plavin

    Are you using the Eero in a mesh configuration?

    0
    Comment actions Permalink
  • Avatar
    IHaveABigNetwork

    Yes I'm a long time tester for Eero. Eero only runs in a mesh configuration. It's in bridge mode with my Gold acting as the router.

    0
    Comment actions Permalink
  • Avatar
    Jack Allalouf

    I am having the same issue with an i7. Works fine on my hotspot. Won't connect to the cloud via firewalla. Opened all the ports it asks for. Nada.

    0
    Comment actions Permalink
  • Avatar
    Michael Plavin

    Jack, what's your network setup? Trying to find commonality between the folks who are having issues.

    So far, I have an Orbi mesh in AP mode, IHABN has an Eero Mesh in bridge mode (same thing as AP mode)...

    0
    Comment actions Permalink
  • Avatar
    Mark Schey

    Just wanted to chime in that I’m having the same issue with Firewalla Gold and a Roomba i7+. The Roomba appears on the Firewalla but zero data is transferred. Like everyone here, I tried opening all the recommended ports, emergency mode, and the like.

    I’m on an Orbi WiFi6 but also tried an old. Linksys RE9000 and no go. It seems specific to the Firewalla Gold, not the WiFi access point.

    0
    Comment actions Permalink
  • Avatar
    James Willhoite

    I would agree but as I stated before, I have the S9+ and the Brava M6 and have had no problem with either one. It seems like the common component is a Mesh Wifi. What software version is running on your Roomba? Could it be an issue with the Roomba and the Firmware?

     

    Roomba S9+:    3.12.6

    Clean Base:       3.3.6

    Brava M6:          3.10.8

    Firewalla:           1.971 (3570931c)

    0
    Comment actions Permalink
  • Avatar
    IHaveABigNetwork

    Mesh is not a factor, and it's important to note there is no single "mesh" technology.  Orbi's implementation does not remotely look like Eero's. 

    I can use an old Ubiquity AP with the FWG and the same behavior persists.  If I use an old Asus router, the behavior is not present and all works well.

    Roomba S9+: 3.12.6

    Cleanbase: 3.3.6

    FWG: 1.971 (3570931c)

    0
    Comment actions Permalink
  • Avatar
    James Willhoite

    It looks like we are running the same versions. I have a TP-Link EAP 245 AP, I also had a Linksys AC1700 (router that I had running as just a AP) that went out and the TP-Link replaced it. I had no problems with either one and the Firewalla Gold.

    I'm sure you tried already, but did you try "Rebooting" the Roomba?

    https://homesupport.irobot.com/app/answers/detail/a_id/9087/~/rebooting-or-resetting-your-robot

    Here are the sites / ip addresses that my Roomba uploads to

     

    And here are the Downloads the Roomba does

     

    In case you want to see if any of those are being blocked for some reason?

    0
    Comment actions Permalink
  • Avatar
    IHaveABigNetwork

    Good suggestions and yes, I've rebooted my iRobot.

    I appreciate you posting those endpoints as two were ones I had missed in my wiresharks.  I just got through testing them, but unfortunately, all of those endpoints are accessible and resolve from my Ubuntu server (obviously I can't test from the S9+ itself).

    I'm assuming you're using IPv6 as well?  I'm on spectrum (and can fail over to Verizon 4g) and both WAN's exhibit the problem.

    I know it sounds illogical, but it's like the FWG is blocking PARTIAL traffic to the iRobot, but not all.

    0
    Comment actions Permalink
  • Avatar
    James Willhoite

    I am running IPv6 on my WAN, but I am not running IPv6 on my local network or VLANS.

    0
    Comment actions Permalink
  • Avatar
    James Willhoite

    Did you try the "Diagnostics" feature in the App and select the Roomba?

     

    0
    Comment actions Permalink

Please sign in to leave a comment.