Hi James
I tested the updated plugin and its working great.
Thanks again for the quick fix.
I tested the updated plugin and its working great.
Thanks again for the quick fix.
HOT TIP! Exploring the commands packaged in VC's standard configurations is a great way to learn how to build your own. You can also clone a command as a starting point: just right-click and select "Clone" (or type Alt-C).
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Show posts MenuQuote from: nime5ter on April 07, 2017, 07:37:34 AM
The most efficient starting point for trying to resolve the problem at this point is to review each of James's instructional steps again to make sure each has been properly implemented.
His instructions are here: http://voxcommando.com/forum/index.php?topic=2682.msg23144#msg23144
These included:
2. Have VC version 2.2.3.4 or later installed.
3. Create the environment variables, as described, by re-accessing the web page for the "Jarvis" function that you initially created in the AWS console.
4. Make sure the username and password used in your environment variables matches the username and password you created in VoxCommando's TCP plugin settings.
5. On the same web page in the AWS console, replace the entire Node.js lambda code that Dave originally provided with the code that James attached to his post (link above). *important* you must change one line at the beginning of James's code near line 5:edit one line in that script var Echo_App_ID = "amzn1.ask.skill...." to use your own App ID.
Make sure your App ID has quotation marks around it, as in the example provided.
6. In VoxCommando, delete the old command group from Dave's original instructions and replace it with the VC command XML in James's post.