What’s the "technical" issue here with not being able to select the devices you want to show up in the Alexa App? It seems very intentional…but ST hasn’t given us a reason why. I DO NOT WANT ALL OF MY DEVICES DISCOVERABLE IN THE ALEXA APP!!!
Here’s one reason why:
I have over 30 Echo Devices including Echos in the Day Room and Garage that can easily be spoken to through windows.
It’s a stretch but someone could walk up and say, Alexa turn off Stay or Away Panel and the alarm is disabled. 
@Lars Any updates on when ST sensors will be able to trigger Alexa routines again? ST users have invested substantial amount of money and time building out their home automation using ST sensors and Alexa routines…all of which became bricked in an instant with the new Alexa skill.
I’ll add my seemingly 100th voice to this. The Alexa integration is completely butchered without virtual switch routines and selecting devices on import.
Smartthings, if you are listening, this has to be a top priority. It’s absolutely ridiculous to expect us to expose ALL of our devices to Alexa.
Example: My Inovelli Fan/Light switch has 1 parent device (### Fan Light) and 5 child devices (### Fan Light Fan/### Fan Light Light/### Fan Light Default Local Level/### Fan Light Fan LED/### Fan Light Light LED). I know @jody.albritton has one of these as well from his community posts over there.
So when I say “A, set ### Fan Light Fan to 100%” she is like WTF do you want me to do? She literally never figured it out.
So now I have renamed the devices inside Alexa to make them a bit easier to control (and disabled the ones I don’t need), but that device alone took me ~20 mins to properly set. I have 5 of these and about 20 other inovelli devices with children galore (because of course a switch can’t have a color? Inovelli innovating around limitations of ST).
This doesn’t even speak to the security issues of voice control over security-sensitive items, which is catastrophic to a smarthome security environment.
We need transparency here. PLEASE.
Do you know what’s the “standard” voice command to set the Guard to “Home”?
I’m not currently home so I cannot test it…
“Alexa, I’m home”
yeah, I’ve configured Virtual Motion Sensor that changes to “active” whenever one of my Presence Sensor changes to active (god bless webcore).When the virtual motion sensor changes to “inactive” Alexa Guard changes to Away.
What I cannot understand why the opposite Alexa Routine won’t fire up: when Virtual Motion Sensor changes to active, one Echo should say the phrase “Alexa I’m home” and the other Echo should listen.
It’s such a nightmare with these so called updates…
I echo this (no pun intended).
I don’t like exposing everything to Amazon. Like my locks. Sure I have them disabled in the Alexa app, but that’s one more possible point someone could exploit to get into my home.
In my case, Alexa has no reason to access locks, sensors, alarms, etc. I just don’t like that. And you cannot just delete the device from Amazon because it will be re-discovered automatically.
Without input from ST staff,we can only speculate. I used to speculate this was a technical issue with their OAuth scope process. BUT, that doesn’t seem to be true based on their dev docs for Oauth
An
*used for theentity-idspecifies that the permission may be applied to all entities that the token type has access to, or may be replaced with a specific ID.
So it appears it is very much possible to provide x:devices:* permissions for specific device IDs to Alexa.
https://smartthings.developer.samsung.com/docs/auth-and-permissions.html
So this is either an intentional decision or OAuth by device ID wasn’t live when the new integration was built.
Mines the same too
Its all or nothing for me, all in last week, sensors, contacts and simulated contacts, its came back a few times, this morning had a few random messages come though that were triggered from the night before, then its all stopped again now, all was working great before that.
Cheers Dave
I could never get one Alexa device to respond to another saying “Alexa I’m Home”.
Here here!
For example, without the DTH, there is effectively zero support for the GE Motion-Dimmer. I have different modes for different times of the day and location mode. Losing the ability to have those automations for the motion-dimmer would probably be a deal breaker for me.
Introducing a new platform should not cause regressions in functionality. That’s the first rule of software development and delivery. If it is going to take time to deliver it in the new platform, so be it. But in the interim, run the two in parallel until there is feature parity (or at least 99%).
How can we help you figure out what is broken in the integration? Are there diagnostics, logging, etc we can provide you? Do you have an instrumented version of the skill that can provide you more detailed information that we can deploy to zero in on the issue?
So this morning I saw the notice in the new app about SmartThings discontinuing Echo Speaks. At first, I was surprised and a little bummed. But after reading a bit on the forums I can certainly understand their reasoning.
Well without reading much more into it, I went ahead and updated my SmartThings skill in the Alexa app. Then several of my key automations stopped working. But fear not! After spending way too long reading and typing (this original comment was a plea for help), I managed to get it straightened out. So I wanted to share!
Everything appeared fine in ST. The app would show a device “On”/“Open”, and then “Off”/“Closed” when I toggle it from any source. But I was seeing the same device in the Alexa app only as a switch (although it was responding to toggle). Even though it would give me the ability to assign it to a new routine as a trigger device (i.e. Alexa saw it as a sensor), it would not activate any routine activation on toggle. The Alexa app did, however, remove the “old” trigger devices and warn me I needed to assign a trigger to enable this routine.
So I disabled both the new ST skill and the Classic ST skill in my Alexa account. I then re-enabled the Classic ST skill, discovered devices, reassigned the “new” devices to routines as triggers. And most importantly had to switch the toggle at the top of the routine page in the Alexa app (yeah, the one labeled “Disabled” 
) back to “Enabled”. Good as new! Or at least as good as yesterday…
Here is the DTH I have been using. And actually now that I look at it closely, the one I have installed on the IDE is an old version (it still has health checks and other unnecessary features). And I’m wondering now if that could be the source of the compatibility issues with the new ST ecosystem/Alexa skill. I’ll look into it soon and report back. Although I’m a little apprehensive to mess with anything now!
Right now the older ST skill is scheduled to disappear on September 8. 
so only the new skill will be available after that time.
Yes, definitely keep us posted. Earlier today I created a new Simulated Alexa Switch using the same DTH you linked to (I have done this many, many, many times and continue to every so many days to see if it has been fixed, lol)… my newly created routine with the newly created virtual switch worked 2 times and then it didn’t work anymore after that. My experience has been that sometimes they don’t work, sometimes they do work, and sometimes they work but the action is delayed. (I know this because I use them for announcements and sometimes the announcements will go off hours later.)
Personally, I do not think it has anything to do with the DTH… I think it has something to do Alexa being pissed off at Samsung too. 
Hi.
I just uninstalled the old classic smartthings skill and I installed the new one.
After finishing discovery I notice that not all my devices are be discovered by Alexa.
Some motion sensors are not showing up on available devices. I installed/uninstalled the skill twice.
I think you’re right. And actually I just pulled this post up again to check on replies and to reply to myself: so far all those Alexa routine triggers appear to still be working but every device, scene, and automation appears to now be non-responsive inside the ST app. It’s not giving me any errors though. Definitely some growing pains since I didn’t he migration
What DTHes do the missing devices have ?Regular motion sensors should not be an issue.
