Probably futile but I’d try:
If that falls, call SmartThings support
My Samsung Motion Sensor still does not work with Alexa. I can add the routine by going to the device in Alexa and tap add routine. Alexa detects motion, but it will not run my routine that I have always used to announce that there is motion.
See above. It’s a known problem, smartthings engineering is working on it, no timeline has been announced for solution, There’s nothing that we can do as customers, and until the fix is announced here or in one of the official announcements you can expect performance to continue to be frustratingly erratic. 
And you can expect jd to make that same reply several more times lol
I just hate to see somebody who’s already frustrated spend hours more working on something that they can’t fix. 
We as a community can’t remove the frustration in this case, but at least we can help someone avoid adding to it.
I got this mail from Amazon saying that Samsung Smartthings has a new skill and I have to link with that skill.
But when I find the skill “Smartthings” (and also reaching with the link in the email), I see that my ST account is already linked with that skill.
So I am already using it.
What now ?
Maybe nothing.
I’ve gotten similar emails even after I went thru the process of removing the old skill and installing the new one. I don’t think receiving the email is any indication you’re on the old version of the skill.
How long ago did you add the Alexa SmartThings skill, do you remember?
In my Alexa app, the skill info looks like this:
I have removed Alexa completely from SmartThings and I still got the email. Go figure…
Made the jump to the new skill. Wasn’t as painful as some others experiences. Most of my routines are built around scenes so thankfully didn’t have to mess around too much.
Thanks for the info. I was hoping that I missed a post on a fix. I feel this is probably my only issue right now.
How defragmented can their new coding be if they can get their own toys to work again? Is it a security issue with Zigbee and Alexa ST skill?
Anyone know if there is a webpage/URL, created by a ST Alexa Skill developers, listing change logs and/or listing currently known bugs with ST Alexa skill, so we (or I) do not keep asking the same questions?
We know they are working on it.
I’m sorry, not to vent, but the fact that Alexa integration and this skill is still not working properly, after multiple weeks, is just completely unacceptable. I’ve understood all the other issues with the migration, need to only run platform/app for stability, updating orphaned DTH’s, what happened with Echo speaks. All of those things, while extremely frustrating, have reasonable and understandable explanations. But this Alexa integration, this has no justification to drag on for this long, and it needs to be fixed, NOW. The skill ratings continue to decline, we’re up to a 77% one star rating now. I highly encourage anyone using this skill to leave an appropriate rating on Amazon. I’d be happy to update mine once it is working properly.
Dear SmartThings,
Something I learned from years in business. Err on the side of communication. Give us updates even if it doesn’t say anything new.
I gave up trying to make ST work reliably and just have it operating a few zigbee devices. I went with Wink and everything worked great. I didn’t even mind that they started charging, then everything stopped working for a few days and I got reminded to expect a clueless smart home and hours scouring for forum guessworkarounds.
Disable new Alexa skill, wait an hour, re-enable. Delete duplicates. Wait an hour. Alexa still doesn’t work.
Here is a communication that you should understand: Buy a Hubitat, wait an hour, then throw your ST hub in the trash.
New user that just started the journey with SmartThings. I am struggling with SmartThings reporting to Alexa and initiating a command. The scenario is:
I installed the sensor, configured, built the routine in Alexa. However, when the door is open, it can take anywhere from 90 seconds to 15 minutes to trigger the response in Alexa. I have tried both “say” and “announcement” in Alexa using only an Echo Dot.
I read there is a work around with a Smart App but unfortunately I only have the new/current SmartThings app. The workaround calls for the Classic app. I tried a virtual switch but had same result. Is this a configuration issue. Alexa issue? Or a user issue?
Can someone please help me. If there is a solution and/or fix, please let me know and point me in the right direction. From what I have seen so far, I like this platform. But if there are major gaps with Alexa voice and SmartThings, I need to look elsewhere.
This is a known issue with no fix right now.
SmartThings really needs to post this on the status page as degraded performance @Lars @JasonM
@Chris_Nowland , take a look at the voice monkey skill I posted about here Alexa Voicemonkey Skill
It’s a little clunky to setup, but may get you through this interim (hopefully VERY interim) problem. It will work with the new app, but you have to install Webcore, which is an advanced home automation program discussed here https://wiki.webcore.co/ Webcore does work in the new app as well.
Thanks @mwav3. That may be digging a little deeper than my technical abilities. However, will take a look in to it and see if I can get it working.
That’s a great idea. That will force visibility on an issue that is impacting many.
It worked great up until April of this year when a new version of the smartthings/Alexa skill was introduced. Now it’s broken.
See above:
The solution you forgot was to move on to a new platform. Smartthings is simply not working anymore. There were a number of years which saw smartthings as an excellent solution. On top of the other nonsense they’ve been up to at Samsung, a new, forced, Alexa integration which has now cluttered everyone’s Alexa ecosystem with a bunch of junk no one wants there is the cherry on top of the insult Samsung has been slapping users with.
As you expected, this didn’t work, but I kept fiddling and discovered a procedure to get devices/scenes into the Alexa app:
The first time I got it to work, I had renamed the hub location as step 0, and named it back as step 2.5. I’m not having to do that now, so I don’t know if that was necessary to prime it the first time to work now. I suspect not.
