I Just purchased a Samsung robot vacuum. I have a V2. It was interesting to get it to connect to the Smart Home app. Getting it to connect to smartthings has been trying. About 20% of the time it will actually find the vacuum, only once it has seen the acknowledgement of paring to the vacuum. But the device is not saved in smartthings. The wifi connection is solid to the vacuum.
Yeah thanks JD, Those steps do not actually work, they seem a little confusing, but it it very structured. The issue is they donāt actually work as intended, I can see the hub trying to communicate with the vacuum and i can see responses periodically. I know the Vacuum is communicating because it works perfectly in Smart home. I can send someone logs.
Iām sure thatās very frustrating. This forum is a community forum and while there are SmartThings employees who read all the messages eventually, itās not used for individual support cases.
So at this point the best thing would be to open a support ticket.
We just pushed a fix out to the platform. Can you try again, and if youāre seeing continued issues, please contact support so we can dig in to see if something is going on.
Hey Aaron, No change on the connection. still the same problem, it doesnāt het past step 2, the vacuum says allowed on its display after holding the charge button for 3 seconds. but smartthings doesnāt see the acknowledgment.
I was seeing this issue last week. During the pairing process Iād get as far as needing to press the charge button for 3 seconds but nothing would happen. I tried to pair this thing on both iOS and Android, probably 25 times with no luck.
I then submitted an official ticket and tried to pair again with live logging open so I could add to the support case. What do you know it paired.
I unfortunately donāt have a reason why. But can confirm this was an issue for me.
I am having this problem right now. I bought a new phone and had to reinstall the Smart Home software. I have tried to add the device and have gone through several attempts with no success. I can see the device when I scan for it but it does not get past the authentication. If I try again by adding the AP it still hangs at the authentication piece. Any help would be appreciated.
Did anyone every find a solution to this issue? Iām having the the same problem where the Powerbot shows āallowedā during Device Authentication but the Smart Home app will not proceed any further and allow me to add the device.
Truthfully, I found that I hardly āplayā with the Vacuum anymore. I have it set to run, through SH, at a specific time of the day and from there, let it do its thing.
I can tell you that the vacuum does work in ST even though the SH integration is jacked up. I can control it with Alexa, CoRE or just from the Things page in the Mobile App. In CoRE, I went all crazy setting up Pistons and what not but to be honest with myselfā¦I have no idea why?
@rontalley - I can do the same. I see the same thing as you. It is sloppy by both Samsung and ST that the DH they built doesnāt work. If they published the information required to make it work, Iām sure the community would create a better DH.
Having the issue with Robot Vacuum where it works in Smart Home but integration is broken in Smart Things on IOS. Very disappointing, I left a bad review in the app store and this was their reply.
āHi, Ellen with SmartThings support here. Iām so sorry for the bad experience and that you didnāt have a good time working with our support team as well. Iāll look into this case specifically to make sure that our teams get your feedback. Youāre correct that this is a known issue occurring on iOS devices, and Iām really sorry itās affected your home set up this way. This isnāt at all the experience we want for you and Iām so sorry weāve given the impression that support for iOS is even possibly prioritized below other clients. We prioritize fixes based on how much the issue impedes your usage of SmartThings, so this issue is very high priority for us to solve quickly. While I donāt know an exact ETA on the fix for this bug, I do know that we have our mobile teams actively working on it already. I completely realize that this affects some of our most loyal customers and Iāll make sure we have a note made so we can reach out to you as soon as our teams have tested and deployed a fix.ā
This issue has been going on a year now, so I have zero confidence they are serious about actually resolving it. If I could I would take everything back and totally ditch Samsung. The vacuum is great by itself donāt get me wrong, but all I want to do is program my vacuum to run automatically when I leave the house.
@Robot - Unfortunately I donāt believe this is ever going to be fixed. Just about 11 months ago (YES 11 MONTHS) @Aaron told me through PM that he was working on this issue. However, nothing came of it. This all started when ST had their major yearly meltdown.
Will @Aaron or anyone else at ST ever respond to this issue? I suspect not.
The vacuum is connected to ST, that is the funny part. Iāve asked that they open source the DH and I would fix it for them, no response on that either.
Yeah same exact issue. ST is connected to the Robot Vacuum, you can turn it on and off but the dashboard controls / integration with Smart Home is broken. On the Right Now screen it shows the message saying attempting to connect. If you thumb swipe that screen up you can actually see the controls.
Also cannot get the vacuum to come on when ST set to Goodbye/Away.
Never could get the connect app to work but I have been very successful at setting room for the vac to start (or not to start) at specific times or rules designated in CoRE. Havenāt move these rules to webCoRE.
I originally bought the Samsung PowerBot in January 2016 and was able to integrate with SmartThings hub just fine. Things worked until March 2016 when the vacuuum had a wheel issueā¦ so I bought another one in about June. From then until now, still no ability to integrate with SmartThings, although it does integrate with the clunky Samsung home app. So Iām thinking this never gets addressed, and Samsung stuff just isnāt going to work with Samsung stuff in this caseā¦ which youād think would be pretty embarrassing, but clearly no one cares.