The new integration will not show up in SmartThings classic like the old one did because it is not a smartapp.
Can you describe “So now, I can’t even link the account correctly.”? Does the linking from Alexa app fail? If not the devices should all appear in Alexa as normal…
I’m just got off the phone with support with Smartthings and Alexa. Here’s what I’ve learned.
The Classic Skill in Alexa is gone. If you break the connection, it’s gone forever.
The Classic App and Skill haven’t been updated in over a year. They want people to switch.
They aren’t getting many calls with people having problems with the Classic App. “Most people have switched”.
I enabled the new Skill in Alexa and it does show up as a “Connected Device” in the new App.
Support said everything was showing good on their end, that it shows my Alexa is connected.
After 30 mins, Support transferred me to Alexa Support and we spent 45 mins running through the gambit of scripted trouble shooting steps.
One this that I did notice that neither Smarthings or Alexa support could answer, was this…
When I am in the Alexa app and try to manually add a device - > Hub -> Smartthings, it always told me that nothing was linked (even though I was linked with the new Skill). When I continued to add the hub manually, it always took me to the Classic Skill to install, which is no longer available. So Alexa wants to use the Classic skill for some reasons.
The 90 mins ended up with Alexa Support escalating to a technical team. Should hear back in 2-3 days.
I don’t know yet. These are very much “plug and play” mass market consumers. One of them has a high-end Samsung television, which is why they are using smartthings. The other two got it when they got a smart lock. They’ve all had smartthings for at least a year, and one case I think maybe three years. I’ll see if I can find out more. Basically they just sent me a text: “SmartThings stopped working with Alexa, do you know what’s wrong?”
Has the virtual switch bug been patched? I’m using the simulated contact Sensor from the DTH list. I have it set as a trigger got my alexa routine and it doesn’t fire the routine.
I hope they can resolve everyone’s migration issues.
Since the previous motion sensor worked to trigger an Alexa routine on a fresh clean install of the new Alexa skill, I just setup another Alexa routine to test a multi-purpose sensor to announce on my Alexa speaker that the door was opened and it worked too.
I’m glad that I wasn’t totally invested with a lot of Alexa routines and groups since I was able to just wipe everything in Alexa and start fresh since I only had three Alexa groups with various lights in them which were real easy to set back up.
Anyway, I guess I’ll need to start taking a look at other Skill’s that Alexa routines can trigger as actions and see if there’s anything I like.
Hi everyone, If you have been seeing issues with motion sensors not triggering or locks not giving an OK response, please run a new discovery in Alexa (either via Alexa app or say “Discover new devices”). No need to unlink and relink.
Let me know if that does not resolve the issue. Simulated sensors should also work as expected now.
I’m still seeing weird behavior with devices flagged as a light. This z-wave dimmer is flagged as a light in the Alexa app and shows under Lights in its room, and it along with the Wyze bulbs flagged as lights can be manually turned on and off using the switch for the whole Lights group, but verbally saying “Alexa, turn off the lights” (or on) only changes the Wyze bulbs. With the Classic skill it worked correctly verbally with the SmartThings dimmer, too.
This is the same issue one of my friends has. They have not made any changes, they are still using the old skill, and devices that used to be included as “lights“ still show as lights in the app but are not turning off when they say “echo, turn off the lights.“ And they used to.
For the “light” tagging issue, did anyone reach out to Amazon support?
Marking the device as a light in Amazon app has nothing to do with the skill implementation which would explain why you are seeing the issue both with old and new skill. I will reach out to my engineering contacts at Amazon as well about this.
Does the new skill support the ability to not share devices with Alexa? When I open the connected service I don’t see any options to remove devices from discovery.