Ditto…
Well, after removing the old SmartThings Classic skill and all my SmartThings devices from Alexa, then enabling the new SmartThings Alexa skill and discovering my devices, so far everything I’ve used Alexa for before still works. Voice command to Turn on and off any lights. Even voice commands to change the OTA channels on my Samsung HDTV device which worked before still works. I use Alexa since the built-in Bixby on my HDTV can’t do it. It’s a good thing that everything I used Alexa for before still works because I cannot find the the old SmartThings Classic Alexa skill anymore, and Amazon’s Alexa’s website for the old SmartThings Classic skill shows me that it’s no longer available for me. But maybe it’s because I have the new SmartThings skill enabled now.
As I mentioned above, my big problem with Alexa was when I changed the name of a device in SmartThings, that device would break in Alexa. That’s why I didn’t care to setup too much stuff in Alexa, like routines. But with the new SmartThings skill, that’s now FIXED! Because I changed a device’s name in SmartThings and it immediately changed the devices name in Alexa too so it now seems to flow though.
Also, to test out a routine trigger, I created an Alexa routine to say ‘motion detected’ on my Alexa speaker and to also turn on a SmartThings virtual switch when motion is detected from one of my motion sensors and it works fine.
That’s what worries me a lot. I shouldn’t have to delete and start over, but then again that seems to be ST’s way of doing things (support’s 1st request and no backup for your hub when it dies). We have so much set up in Alexa that this would be a decent amount of work.
I’m running both Alexa skills right now and pretty happy, but had quite a few duplicates. The only thing not working with the new skill is my Inovelli NZW37 double plug. I can control both plugs together, but not separately. Same applies to the Classic app compared to the new version. It’s my last device preventing me from deleting the old app and the old skill.
Glad to hear this is working for new installs of the skill. Hopefully they can fix it for those of us that migrate.
My Alexa switches no longer work in my Alexa routines
I can also confirm as of 4/20/2020 the new SmartThings Alexa Skill has not been corrected. Using the old skill I was able to use a simulated contact sensor (that I used WebCore to open/close based on certain rules) to control my BigAssFan Hiaku Lights (As these are not natively supported by SmartThings). When a contact opened or closed it would trigger the Alexa routine it was associated with. This is no longer the case.
Alexa allows me to continue to use the sensor as a trigger, and Alexa also see’s the correct state of the sensor. The issue lies with the sensor not actively triggering the Alexa routine. This is a pita as I’ve used this trick to automate multiple devices that Alexa supports but SmartThings does not.
I hope this is corrected swiftly.
SmartThings and swiftly are two words that can’t coexist together
This release was targeted at new users. We will make an announcement when migration of existing accounts is ready for the general public. Until then please know and accept the risks of trying this out.
Yup, thanks Jody. I’m stay put until ya’ll say go.
Is there anyway to revert back?
Hi all, I wanted to address some of your questions and comments:
*We are aware of the issues with events not triggering for motion sensors etc and are currently testing a fix. I’ll let you know when fix is out so we can confirm that everything is working as expected.
*If you decide to switch to the new skill, you should not have to forget all devices in Alexa app before relinking.
*“Hopefully, the new Alexa skill will live sync devices better than the old skill does”
New skill reports any changes in SmartThings app to Alexa immediately. However, sometimes the Alexa app lags a bit in updating the state visually.
*Blinds are supported and can be set using 0-100%, there is currently no support in Alexa APIs to use more natural language like “open the shades”. If device only support open/close then 0% is closed and anything else will be fully open.
Thanks for the info @Lars. Any idea if the new skill will support the SmartThings Cam with Echo Show devices?
Thanks for the response Lars.
My setup:
1 Hub V2
1 Location set
54 various devices, zwave and zigbee.
Smartthings Classic App on Android using Samsung Account
Multiple Alexa devices around the house (dots, echos, shows)
I don’t run any devices or routines specific to Alexa. Everything is through ST
Problem:
I noticed a few days ago that Alexa wasn’t discovering some changes I made to scenes and routines. In addition, the Alexa app seemed to show a few duplicate items. I decided to break the connection between Alexa and ST. Clear everything out of Alexa and resync everything fresh.
- I disabled the ST Classic skill in Alexa
- The Alexa Smart App disappeared from ST Classic App
- I removed all ST devices from Alexa App
Trying to start over, the ST Classic skill is gone as mentioned above. I only get the new skill I enable it and get the green “linked” label, but nothing shows up in ST Classic App. So now, I can’t even link the account correctly.
I’ve tried everything. Clearing cache from the apps. Force stopped apps. Enable and disable linking in various combinations. Everything is working correcting with ST and everything looks good in the ST Classic app as well as on the website. But for the life of me, I can’t get Alexa and ST to link. Thoughts?
Try the new app. You may have to grant permission there.
I have been contacted by three friends whose Alexa/smartthings integrations have stopped working. Only one is using virtual switches. They don’t use this forum. I was too tired to look into the details so I’m not sure exactly what’s going on.
Shouldn’t there be something on the status page about this?
Alexa doesn’t show in the new app either!
It’s not under settings > connected services? OR try + > voice assistants from the main page.
A shambles, a total shambles again