I have exactly the same issue
Jeez… ST please just reinstate the old skill that literally no-one had any issues with. Many thanks. 
8 Likes
This x100. WTF.
5 Likes
I’m pretty sure that the old skill was written in Groovy and the new one is not. I don’t think it’s coming back.
I just sync everything to st and then sync only ST to Alexa, no duplicates no problems.
1 Like
Well, for a start, I take it that you don’t have hue lighting then… The Alexa skill captures all of the bespoke scenes you have setup for all rooms and zones. Smartthings does not…
3 Likes
I do. However I use st to make scenes.
1 Like
Different things work for different people. But many native integrations offer features that are not available through the SmartThings integration, So many people do prefer to use the manufacturer’s offering.
In addition, it provides a backup for when the smartthings cloud is down.
Choice is good, I do feel this is a choice that should be left up to the customer. 
5 Likes
^This! Man oh Man I would be totally screwed if all of my devices became discoverable in the Alexa App. It would be an absolutely nightmare with naming. Multiple Alexa Routines that have the same name as Switches in SmartThings…For those without a ton of devices, yeah, I see how it wouldn’t be much of an issue but for me…I just can’t imagine the mess.
Yeessh!
6 Likes
Hi @Lars,
Do you have any update on this. It has been many days and this issue remains unresolved. I see many people on Facebook are also facing the same issue. Please help us get this resolved.
Thanks!
Simulated Alexa switches (virtual device by bjpierron) have stopped working? Everything was working fine until last week. I have been using these virtual switches for months without any problem. These virtual switches are being used as triggers in Alexa routines. State changes fine in app, but routines do not trigger. However, I can trigger those routines manually from Alexa app. It’s just those switches are unable to trigger Alexa routines from smartthings app. I have unlinked and re-linked smartthings skill in Alexa app multiple times, but to no avail. Thanks in advance.
2 Likes
Hi , we are still working on this. I do not believe it is connected to which DTH people are using though, either all events from all devices work or none at all. Does anyone have a contrary experience?
2 Likes
Ok well if echo speaks is dead please make it so that echo devices show in smartthings as speakers and please enable voice announcements for them.
7 Likes
Exactly. Seems to me it would be a super easy fix for ST too, but they seem entirely obstinant on restoring this extremely basic functionality the old skill had.
2 Likes
I’ve just toyed with Alexa out of curiosity. I set up a routine that is triggered when a virtual contact sensor opens.
If I use a genuine momentary type action in a device handler, where an open event is followed immediately by a close event, the Alexa routine does not trigger.
If I add a delay between the open and close - say as little as one second - the Alexa routine will trigger OK.
Not sure if that is what you had in mind.
1 Like
That will happen on September 8, however, when everyone remaining on the classic skill is cut over to the new one.
https://support.smartthings.com/hc/en-us/articles/360046899371#voice
1 Like
Hopefully before then a miracle happens and they pull their heads out.
4 Likes
I’m currently building Alexa out of my ST system. I only have six devices allocated to Alexa, but I have two hubs and several other locations tied into my setup, and the thought of disabling some 90-odd devices in the Alexa app fills me with dread, especially as some of these devices are security related. I have a Household account on Amazon so basically anyone in my two households can re-enable anything and make changes, and my home security is compromised. Nice one Samsung… Again the community asks ‘why fix what ain’t broken?’.
2 Likes
I actually just did had to go into Alexa and manually disable every redundant device one by one, which came out to roughly fifty three of them. It is just as hellish and annoying as can be imagined and just as bad, in the Alexa app you can’t even hide them so they’re visible when selecting what goes into a room.
3 Likes
I do not say this lightly because I generally love updates and changes but I literally hate everything in the new app. The updated app is harder to navigate, much less functional, utterly counter-intuitive to find anything with such poor organization, and also manages to add nothing except now my TV appears on it.
Also, the thing with being unable to pick and choose what to integrate with Alexa is insane. And I can’t find IFTTT (It still show in Classic), which worries me, because if IFTTT also goes all or nothing, I can’t use it with SmartThings at all. The old ID with the device list doesn’t show all devices and their network/zigbee/zwave id’s and some aren’t editable; is there a new one somewhere that I can’t find that shows all devices, logs, and IDs? The new development portal was somewhat lacking.
I love SmartThings as my central integration hub and coding for it, but it honestly may be easier to balkanize my home automation again with Alexa to temporarily centralize it–which will suck–while I repurpose my Pi for home automation and start from scratch with it; the things I use SmartThings for don’t seem to be there anymore.
4 Likes
As of now I have removed Alexa from my ST. The idea of having everything exposed in the Alexa app just proved too much. I am getting some workarounds for the few devices I did have, so it’s not catastrophic, just extremely irritating that Samsung have taken such a unilateral decision, as they seem to be doing on this whole migration thing. Currently assessing Home Assistant on a RPi, but that requires a $5 per month subscription to get Alexa to work, so that’s probably out too…
4 Likes