I have the same problem with one N4300 despite all the option correctly set and it’s useless talk to Samsung because it’s an old problem that Samsung don’t fix. If you search in internet and in this forum you will find many discussions on this problem …
Model: QN75Q6FN
Software Version: T-KTM2AKUC-1300.4, BT - S
Sub-micom Version: T-KTMOCTV-1113T-KTMOCJP-1113 ← I don’t know how to find this.
Clearly a similar but different exact model. Sorry about that.
All was well until yesterday - My Alexa routines, triggered by https://github.com/bjpierron/SmartThings-Alexa/blob/master/devicetypes/bjpierron/simulated-alexa-switch.src/simulated-alexa-switch.groovy stopped triggering.
I tried a few things - then decided to disable and re-enable the skill. I seem to have both the new and the classic skill - I did the new one and then tried the classic which predictably could not be re-enabled.
I’ve done a few of the checks here about looking for duplicates on the amazon website - deleting all ST devices and re-finding stuff all to no avail. I’ve migrated using the iOS classic app.
Is it the consensus still that the triggers, virtual or otherwise, are still broken or is there a recipe I should be following.
Regards,
Stephen
1 Like
Tagging @Lars
Hello, I have the exact same problem. Two or three days ago all my Alexa routines triggered by an Alexa Simulated Switch were working fine, but today they are not working anymore. Is there any solution?
There’s an entry on the status page today saying there’s a problem with Alexa and Google home integrations:
Some users may be experiencing issues with delays and/or failures with voice and device control using Amazon Alexa and Google Assistant. For Amazon Alexa users, this could specifically include control of locks and failures in their Alexa Routines that depend on SmartThings devices.
1 Like
Sigh
It’s not a great situation.
1 Like
Triggers are now working again for me. The issue above has been resolved it seems.
1 Like
@lars Anything?
2 Likes
I have the same issue as you. The motion NOT detected has stopped working. Triggers fine but alexa now won’t turn anything off again 
Did you find a solution?
It’s still a bit flakey, but I essentially had to add/re-add the motion sensors in Alexa and re-create the routine over and over again until it started working again.
Yeah, really wouldn’t mind an update on this too. Feels like its been a long time now…
Thanks to @johnandy for pointing out the new “custom action” option in Alexa routines. I figured I’d post about it on this thread.
Alexa now let’s you do a custom action in an Alexa routine. Basically, you can type anything you would say to Alexa and trigger an event. An example could be “set a 30 minute reminder” when a door unlocks to tell you to lock it. It can be used for anything really, and provides much more flexibility. Users have posted they can disarm Alexa guard this way, which previously was not possible. Screenshots below:
11 Likes
It even allows you to disable other Alexa Routines that are setup by simply placing "disable’ and then the Routine name.
Very handy work around for some incompatible devices and device actions.
3 Likes
Oh snap! This is pretty darn good! Have they added the ability to trigger by a ST Switch yet?
No. That was the first thing I checked. Looks like I’m adding a virtual sensor tonight…
Virtual open/close or virtual presence work great!
1 Like
And just like that I have control over my Deebot from ST! (no more cleaning schedule getting wiped out because the vacuum got stuck and ran out of battery before the next scheduled run!) And I can view Ring on my Fire TV when someone rings the doorbell! Hallelujah.
2 Likes
Not available in the UK again… Gutting as this would have immensely simplified many of my automations where I trigger a Sonos speaker to talk to Alexa to execute certain actions. Also, we still haven’t even got Alexa Guard over here…
1 Like
