@Lars @sk108 I have the same issue. The state of SmartThings sensors (real and simulated) accurately reflects in Alexa, but does not trigger the corresponding routine. I migrated my account to the new skill yesterday and made sure that there are no duplicate ST devices.
1 Like
@Lars, this is one of my fears along with losing the ability to control what devices ST and Alexa share. I’m being forced into a solution that I don’t believe has been well thought through, and along with all the irons in the fire ST has going on right now, I’m not confident the next few months for ST and customers will be a pleasant experience.
6 Likes
I’ll use stronger language @johnconstantelo
@Lars @blake.arnold, the inability of the new Alexa skill or the new Google skill to filter out devices to their respective voice assistant is ABSOLUTELY UNACCEPTABLE… This is from what I’ve seen here, on FB and Reddit your #1 issue with users facing Voice assistant skill migration, it is universally reviled and should be a MUST FIX and warrant an emergency hotfix.
There is no harm in allowing a user selection and control of what they expose to a third party and the decision to disallow that selection is causing end users undue difficulty and confusion during an already difficult migration.
18 Likes
I attempted to link the new skill last night and none of my devices were discovered in the Alexa app. I linked SmartThings 3 different times with nothing. I also attempted to discover the hub itself with no results. Am I missing something or is there another workaround to use? Thanks.
Well said. I had children in the room, so I toned it down a bit… 
4 Likes
Hey, its still kid friendly. 
. Family show y’know…
3 Likes
Does the new integration allow you to control which ST devices you want to expose to Alexa and which you want to hide?
I completed the integration and found Alexa added 50 devices that I do not want exposed to Alexa, if not because voice management for these isn’t useful and it makes managing Alexa a pain. There are security concerns as well.
All devices are exposed to Alexa or Google Home using the new integrations. Please read the above thread and you’ll quickly see most users are not happy about this new ‘feature’.
7 Likes
I’m sure most, if not all of you already know this but Hubitat Alexa virtual switches work to trigger routines.
Because we really don’t know if/when triggering routines will come back for many of us, I ordered a Hubitat, got it in 2 days (shipped from USA to Canada). Took me about 2hrs to get familiar with it and get it to trigger an Alexa routine (I knew nothing about Hubitat).
I do like the SmartThings UI better so Hubitat isn’t replacing SmartThings for now. So far it’s only going to be used as a go between to activate Alexa routines.
It’s not an ideal situation, especially with people that have tones of devices. But at least you might be able to get your home automation running again with a bit of work.
Plus if/when SmartThings triggering Alexa routines gets fixed and I jump back over to having it do routines I’ll have a back up if/when it breaks again 
1 Like
Can I reinstall the classic Alexa SmartApp, at least until this is forced on everyone?
Nope. They burned the bridge. Its a one way transition.
1 Like
Please PM me your account and I will take a look.
I can officially confirm - the new Alexa app sucks rocks.
I had no choice but to update since it’s being forced. First I need to deal with a handful of scenes that didn’t get discovered, probably because I had locks in them; then I can go disable a couple hundred devices Alexa has no reason to know about. What a gigantic cluster f-bomb…
7 Likes
Would it be a good idea to disable the old skill And remove all of the ST devices from the Alexa app before enabling the new skill?,Just a preemptively avoid getting duplicate devices?
Yes, and - we shouldn’t have to…
1 Like
That’s exactly what I did, and I have no duplicate devices. Take good notes on what Alexa groups you have because those get wiped when the devices get deleted. I’m rebuilding those now.
Also take note on your existing Scenes. Some of mine did not get discovered with the new skill. Like I mentioned above, probably due to my locks or other security devices. I’m in process of creating virtual switches to turn on/off that will be used in Automations to trigger a Scene. I’m using the Virtual Device Creator smartapp to create the device, get Alexa to discover it, then drop it into a Room, and then build the automation. So far this workaround works, but a heck of a stupid way of duplicating a much more elegant process with the old skill.
3 Likes
I “upgraded” to the new Alexa skill (and the new Google integration) after the announcement yesterday.
I was prepared for the inability to select which devices were exposed, and while it sucks, it’s at least manageable. I did prepare by removing the old skill first to minimize duplicate devices. Still took a long time to disable each of the devices I didn’t want connected, one by one.
What I was not prepared for, and what is a much larger issue for me, is that my virtual ST devices no longer trigger Alexa routines. I can see I’m not alone in this, and that ST engineering is looking into it. Forcing users to “upgrade” to a new skill with drastically less practical functionality is a pretty crappy move IMO.
4 Likes
Now that it has been announced that the old skill “Smartthings Classic” will disappear, someone from the ST team could please indicate which is the correct official procedure (step by step) to migrate to the new skill, and thus avoid users who still They have the old skill all the inconveniences with repeated devices and failures in the routines that several of us have had.
1 Like
I just deleted all of my devices and disconnected my old Alexa skill started from scratch and enabled the new skill and everything went just fine. Thank you.
3 Likes
First post here
1 Like