iRobot Roomba S9+ "Cloud cannot connect to [my Roomba's name]" message
I have troubleshot the crap out of this on my own and have gotten nowhere. When Firewalla Gold is not in place, the Roomba connects just fine to my existing network (Orbi Mesh); when I add FWG and turn my Orbi router into an access point, the Roomba throws the error message in the title. What's odd is I see zero traffic from the device in question. What's ALSO odd is I have an older Roomba that has zero issues. I assume that means the newer devices use a different way to communicate to the cloud services, but again, I'm seeing zero traffic from the Roomba S9+ itself.
Following iRobot's recommendations for punching a hole through the firewall does not resolve the issue: https://homesupport.irobot.com/app/answers/detail/a_id/9025 (I also created an Allow rule to allow all internal traffic)
Turning on Emergency Access does not resolve the issue.
Has anyone else successfully configured their FWG to get communication working with a Roomba S9+?
-
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+... -
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.
-
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? -
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. -
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?
-
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.
-
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)
-
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)
-
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?
-
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.
Please sign in to leave a comment.
Comments
67 comments