[ST Edge] vEdge Creator: a virtual device generator for end users

[Paul_Oliver (PCO)]

I am having the same problem with intermittent deliver of Alexa messages using the Alexa Switch in ST. The problem is definitely on the Amazon side.

We had similar problem 2-1/2 years ago using the old Groovy Virtual Alexa Switches became unreliable. So some of us switched over to using Voice Monkey to trigger Alexa routines. ST triggered an WebCore piston, the piston made and http call to Voice Monkey and Voice Monkey triggered and Alexa Routine.

The problem today is that WebCore is gone. I suppose SharpTools Premium or @TAustin Web Requestor (requires a constantly running server) could be used instead of WebCore to make the http calls.

Voice Monkey uses a virtual Door Bell to trigger the Alexa routines and it worked reliability. After several months Amazon fixed the problem and there was no reason to use Voice Monkey.

The Tasker “Auto Voice” plug-in also uses virtual Door Bells to trigger Alexa Routine.

@TAustin is any chance you could add a Virtual Door Bell with integral Switch to your virtual device creator. If this works it would be an easy solution.

New SmartThings Alexa skill (2020)

Thank you @Terri_Baker for pointing out the Voice Monkey Skill I may have found a better solution for all this virtual contact sensor nonsense using that skill to trigger voice announcements, or technically any routine in Alexa you want, from Webcore. Plus, you can use your variables in Webcore as part of the announcement with this. This was something I was going to miss the most in Echo Speaks. Also, with the webcore webrequest, you can bypass IFTTT and send the request straight from Webcore to the Voice Monkey skill Instructions to setup the skill are here voicemonkey.io . Once setup, create a routine in the device you want to speak that opens the Voice Monkey Skill like this: [Screenshot_2020-09-04-10-04-00] Then, in webcore, setup whatever trigger you want, and as action do “m…