I have created a simple flash briefing skill that reads from a rss feed. However it is pronouncing the name of the company wrong. I have reviewed the SSML page on the amazon developer site, but i do not see a way to get to the js that runs the skill. Is there any way to edit the js behind the skill if I am using the default API? Is there another solution short of writing a standalone skill?
It's not possible to do that yet. SSML is allowed in the Feed content only.
However you can up-vote the idea, you are not the first one who faces this issue.
Related
I have set up an Echo Dot device for my account. My intent is to call an Alexa skill on this device externally.
I have seen a lot of tutorials, but I could only see that these skills were started by voice.
Is there any way to trigger an Alexa skill by using an API, and not using voice at all? If not, what would be the market available alternatives for such a workflow?
It's not possible yet to trigger Alexa directly without Alexa wasn't asked. You could use notifications. Alexa will have a yellow ring and user has to ask for messages.
See https://developer.amazon.com/en-US/docs/alexa/smapi/proactive-events-api.html for details.
I've found a way of achieving this.
By using IFTTT, there is a skill called IFTTTriger that you can install in your Alexa device, and later on, install the https://mkzense.com/iftttrigger . In that way, I was able to create an IFTTT applet that could trigger Alexa using a virtual device.
That is the only way available as of now. Worked perfectly well.
I already finish the chatbot, but I have no idea of how to upload it to my website, please, help :)
I tried to look for some code to send to the IT developers, but cannot find it :( And the IT guys are too busy, so I'ld like to get the answer by myself so I can send it to them if I'm not able to apply it. Thank you. (Btw: I'm not an IT person... :( )
Where to start?
The dialog / conversation part of your Watson Assistant part chatbot is available as a REST API.
There are several deployment options available. For the more popular choices the Assistant tooling provides integrations. So if you want to access your chatbot through slack, or facebook messenger or on a word press site then look at the documentation as to how - https://cloud.ibm.com/docs/services/assistant?topic=assistant-deploy-integration-add
If you are developing your own application or web-page, then your developers will need to design the User Interface and handle the quirks of your dialog. eg. Decide how to display images, options etc., all from the API, which is essentially only message in, response out - https://cloud.ibm.com/apidocs/assistant-v2#send-user-input-to-assistant. There are samples available for them to base from - eg. https://github.com/watson-developer-cloud/assistant-intermediate
If your website is using Wordpress, there is a very easy way to deploy the chatbot to it using a wordpress plug in - https://wordpress.org/plugins/conversation-watson/
I have been checking around on this topic, but have not seen a concrete solution on how to get it working. I am building a Custom Skill for Alexa, which currently supports speech. Now I would like to extend the skill with video streaming to a TV.
The only thing the Custom Skill seems to support for this is streaming to Echo Show with the VideoApp directives?
I have seen answers that say it is possible, just return a list of devices, but these devices and their appliance id's seem to be hardcoded, I would need to get an actual list of devices linked to the users account.
So the question is: is it actually possible to incorporate Video Skill functionality (and device discovery) in a custom skill, or would it need to be a separate skill?
Since the SmartTV is not an Alexa-enabled device, streaming to it will be a separate API from the Alexa APIs.
An Alexa skill is similar to a web API, where the front end, user interface, is Alexa.
Imagine if you were building a website that had a couple of buttons on it and a text box. Users would enter some info in the text box and press one of the buttons to start streaming on the TV. The code behind the website would have to communicate with the smart TV somehow to stream the content.
The same way, your skill code would have to figure out a way to communicate with the Smart TV.
This is not something that Alexa would support directly, so it become necessary to identify the API for your SmartTV and a way to communicate to it from the internet which won’t be trivial.
More of a question than a problem but I'm wondering if anyone has attempted or seen the use of a CMS for an Alexa Skill. I'm imagining a simple FAQ based Alexa skill. The JSON for the intent would have to be generated elsewhere or at least supplied elsewhere. The idea is that through the CMS you could supply the intent and also the response. I know this is very lose but I'm kind of feeling out if anyone has done anything with this.
Have you seen this project?
https://www.hackster.io/tom-harrigan280/alexawp-20a282
Github repo is here:
https://github.com/tomharrigan/AlexaWP
I believe it close to what you are looking for. It uses Wordpress as the source of content for responses to Alexa requests.
It's my first few hours today to use Alexa so please bear with me for now.
I followed a tutorial that I found and was able to configure Alexa skills upto the Lamdba function. I was able to use the Test section inside Lamdba service and it worked really well. It can pull data from the external api. I was able to click the Listen button too.
However, I can't figure out how I will deploy this so that I can call the utterances using my real physical Alexa device. Not sure what to do next. And is it possible that I'll be the only one to use it?
You don't have to publish it to use it on your physical alexa device. As long as the alexa device is configured with the same Amazon account that you use to configure your skill then you can use the skill 'live' on your device.
In the configuration, I believe you must have progressed to the 'test' tab, but you don't need to fill in the publishing info to test the skill both virtually and on the device.