Samsung Vacuum not connecting

Yes it appears they broke it again… What a fucking joke, I am done with Samsung. I switched from iphone to android just so the damn vacuum would work in Smart Things, it worked for about a month then they released an update and it broke just like it was in the iOS app version they have been promising to fix over 2 years now. I’m selling my SmartThings and getting a Wink Hub which has native support for Nest anyways. Everything about SmartThings is hacked together and unreliable.

I’m afraid to ask but…did this ever get fixed?

My R7040 is working :man_shrugging:

I have the issue described here. Smartthings classic does not connect to my r9350.

“Workaround” This will connect your powerboat robot vacuum to smart home and Smart Thing without a hub or router. I hope Samsung Tech support reads this, it may help with their bug. I’ve had the same problem that you are all having, I tried connecting my powerboat R9350 to Samsung smart home and it says ether can’t find AP and not connected. I tried it on two different routers using a Pixel 2 and a Samsung Tab A. Yes, you can turn off the mobile data and it will find the AP but it still shows disconnected. My problem also was I had a possessed powerbot and it would just start cleaning, so I needed to find a way to get into the settings. This “workaround” works and will connect your powerbot to both the smart home app and the smart thing app and will allow you to get into the settings until Samsung fixes the bug. So, trying everything I found this to work, hope it helps. Step 1, put powerbot on the charger, make sure it’s on. 2, put your phone into hotspot mode “this will be your router”. 3, you’ll need a second device with the smart home app on it, then connect to the hotspot. 4, go through the steps of adding your powerbot and you’ll be able to get into the setting on your powerbot, make floor plans, turn off schedule, do updates and everything else you would like to do. 5, Once you are done just turn off your hotspot. If you ever need to make any changes, you’ll just need to turn on the same hotspot. Sorry its just a workaround until Samsung can fix the app.

1 Like

I have the same issue! I just purchased an R9250 and it would not connect to my router. I was able to use my phone as a hotspot and use my wife’s phone to set up the robot vacuum. About 30 minutes later its status changed to disconnected and both SmartThings and smart home apps and I can no longer go into the settings of either.

Phone: Galaxy S9+ Android Oreo 8.0.0 on T-Mobile
PowerBot R9250 VR2AJ9250WW/AA
SmartThings app 1.7.21-25
Smart Home app 3.1072.19.204

So I purchased few weeks ago the Samsung powerbot R9350 and set it up to the wifi and the smarthing app all good. Today I wanted to use the app to map the house and when I click on the tile I keep getting connection failure. I disconnected the powerbot, I removed the device from the smarthing app and added it again and still get the same connection failure error. So I ran the powerbot using the remote that came with it and the tile in the smarthing app shows the status as cleaning but when I try to open the tile to control the other features I get the connection failure error.

Very weird, any ideas of what to do as that was the main reason why I got it so to map and control the vacuuming through the app

Thanks

Thanks for all the help in this thread, I wish I have read it before buying my R9350.

I have tried Patrick’s workaround with no luck, both apps refuse to connect to the vacuum, no matter what phone or network I’m connected to I always get this messages:

smartthings can’t find it, and when I try to manually add it, it says only this two models are supported:
VR10M7040W9/AX
VR20M7070WS/AX

I can’t believe all of this vacuums aren’t working anymore (mine worked for two days), there must be someone or someway to figure this out, any more suggestions will be really appreciated, thanks!

Hey everyone,

Just wanted to mention that I just acquired a Powerbot 9350 and I’m also now having this same issue. It’s worth noting that yesterday, all was working fine. The only thing I can think of that changed was that my router’s firmware updated itself today. I’m now getting the same CONNECTION FAILURE that everyone else is getting, despite seeing the status of the vacuum in SmartThings (charging/cleaning) etc.

I too haven’t been able to get this working. I’ve switched my Router to different wifi modes (Tri-Band SmartConnect on/off), I’ve reset the router, reset the vacuum, I’ve even hard reset my SmartThings hub and had a total blast setting it up along with all my devices from scratch again to no avail. I have also tried SmartThings Classic and the new SmartThings app.

If anyone here has any tips, it would be much appreciated. Thanks so much

Hi There,

I’ve had the Samsung Powerbot 9350 for a couple weeks now, and since yesterday I’ve been having the same issue described in this thread. smartthings is not able to connect to the powerbot. It displays a connection failure error message.

This is a screenshot of the error:

Here’s what I’ve noticed (might be useful if it can be reported to smartthings developers):

  • the version of the device reported at api.smartthings.com has changed from 190515 to 190620
  • the vacuum originally set up a upnp port forward on the router for tcp port 5050, it is no longer doing that after a restart of the router.
  • tcp port 5050 used to be open open on the vacuum now it is not.
  • the vacuum ip address can still be pinged
  • the vacuum is still able to connect to the smartthings cloud and report its status (i.e… when it is picked up, or when the charging station is unplugged)

Edit Day 2:
After leaving the vacuum on the charger for a day, then turning off and back on twice, the first time without waiting to turn it back on and the second time leaving it turned off for 5 minutes.
Then smartthings was able to connect to the vacuum. I hope this time it lasts and doesn’t stop connecting again.
Here’s what’s different today:

  • the UPNP port forwarding status page on the router showed two port mappings.
    • one mapped to the ip of the mobile phone (tcp port 5058)
    • one mapped to the ip of the vacuum cleaner (tcp port 5050)
    • when the smartthings app is unable to connect, like yesterday, the vacuum’s port mapping is not mapped on the router.
    • when the smartthings app is able to connect, like today, the vaccum’s port mapping is mapped on the router.

I’m guessing that, whatever network service running on port 5050 on the vacuum seems to either stop working at some point, or the vacuum doesn’t start that service unless it can create the upnp port mapping on the router.

Hopefully, a smartthings developer can read this thread…

So far I’m considering returning this robot vacuum, the software support for it is too buggy.

1 Like

Hi ihasbini,

For what it’s worth, mine, along with Orosas 9350s both randomly started working today. Really strange. Wondering what type of router you have? That being said, I don’t really think the router has anything to do with it though since I experienced the same connection issues when using a mobile phone as a data hotspot, then another phone to connect and set up the vacuum.

I used to have a Powerbot R7070 and I not once ever experienced this issue. I don’t think there is any way to check or force firmware updates on these, is there?

Hey applesandsynths,

My router is an Asus RT-AC87U running the AsusWRT merlin firmware.

No, I don’t think there’s any way to force a firmware update and it’s only by coincidence that I noticed a version number change. I stumbled on graph.api.smartthings.com earlier while I was looking for a way to change the floor plan for the vacuum which isn’t happening from the app (another software issue). On there i noticed a versionNumber attribute that changed from 190515 to 190620.

Mine is also on 190620 so maybe they pushed a firmware update to our Powerbots then that resolved the issue. Seems to coincidental for 3 of them to all start working again on the same day I’d say. Let’s hope this is water under the bridge :confused:

EDIT: When clicking on Version, I came across this which is rather odd. Every day, the version numbers alternate between the two:

2019-07-08 7:35 PM UTC - 1 day ago versionNumber 190620
2019-07-08 7:35 PM UTC - 1 day ago versionNumber 190515
2019-07-08 7:35 PM UTC - 1 day ago versionNumber 190620
2019-07-08 7:35 PM UTC - 1 day ago versionNumber 190515
2019-07-07 11:40 PM UTC - 2 days ago versionNumber 190620
2019-07-07 11:40 PM UTC - 2 days ago versionNumber 190515
2019-07-07 11:38 PM UTC - 2 days ago versionNumber 190620
2019-07-07 11:38 PM UTC - 2 days ago versionNumber 190515
2019-07-07 3:36 PM UTC - 2 days ago versionNumber 190620
2019-07-07 3:36 PM UTC - 2 days ago versionNumber 190515

EDIT 2: Seems like the vacuum no longer shows up in the Google Home app. I’ve tried pairing the vac to SmartThings again, and I’ve also tried clearing cache/storage on the Google Home app, unlinking and relinking SmartThings to Google Home/Assistant. All other SmartThings devices show up in Google Home with the exception of the PowerBot. Is this happening for you as well? I noticed that the PowerBot also doesn’t show up in the Scenes section of the SmartThings app. All other SmartThings devices do show up as a device I can add in here.

Same here the version number alternated several times last saturday/sunday:

Date Name Value Units
2019-07-07 10:10 PM UTC - 3 days ago versionNumber 190620
2019-07-07 10:10 PM UTC - 3 days ago versionNumber 190515
2019-07-07 10:10 PM UTC - 3 days ago versionNumber 190620
2019-07-07 10:10 PM UTC - 3 days ago versionNumber 190515
2019-07-07 5:52 PM UTC - 3 days ago versionNumber 190620
2019-07-07 5:52 PM UTC - 3 days ago versionNumber 190515
2019-07-07 5:52 PM UTC - 3 days ago versionNumber 190620
2019-07-07 5:52 PM UTC - 3 days ago versionNumber 190515
2019-07-07 5:24 PM UTC - 3 days ago versionNumber 190620
2019-07-07 5:24 PM UTC - 3 days ago versionNumber 190515
2019-07-07 5:24 PM UTC - 3 days ago versionNumber 190620
2019-07-07 5:24 PM UTC - 3 days ago versionNumber 190515
2019-07-07 9:32 AM UTC - 4 days ago versionNumber 190620
2019-07-07 9:32 AM UTC - 4 days ago versionNumber 190515
2019-07-07 9:32 AM UTC - 4 days ago versionNumber 190620
2019-07-07 9:32 AM UTC - 4 days ago versionNumber 190515
2019-07-07 8:07 AM UTC - 4 days ago versionNumber 190620
2019-07-07 8:07 AM UTC - 4 days ago versionNumber 190515
2019-07-07 8:07 AM UTC - 4 days ago versionNumber 190620

As for google home, I unlinked the google account from the smartthings account as the vacuum only appeared as a on/off switch in google home. Didn’t try to relink again, no need for it. Unless, I can tell it to clean a specific room thru google home.

Same, doesn’t show up in scenes.

Still unable to switch floor plans or delete unwanted ones on my side.

I restarted the vacuum with the switch underneath. I reinstalled the app. Smart Things, not Smart Home. I had previously turned off Smart Network Switch on my Samsung phone. I turned it back on. I turned the vacuum on manually, with the play/pause button on the vacuum. I turned it off via the remote. I waited a few minutes, then tried to install the vacuum via the AP thing. It worked. I do not know which of these things, or combo of things did it, but it works fine now.

I found that if I turned the vacuum off with the switch underneath, had a coffee then turned it back on (not sitting on the charger) it connected perfectly.
Hope this helps

© 2019 SmartThings, Inc. All Rights Reserved. Terms of Use | Privacy Policy

SmartThings; SmartApps®; Physical Graph; Hello, Home; and Hello, Smart Home are all trademarks of the SmartThings, Inc.