alexa

I'm trying to create a Amazon Alexa Skills Kit to do some kind of automation which would be required to take speech input comprised of strings and numbers ( a-test12fish ). When I've used custom slots in Alexa Skills Kit, it is not letting me key in strings with numbers. When I try to key in ask alexa, dangerZone find a-test12fish , I'm getting the following error: Error: Invalid text input. Text should begin with alphabets and should only contain alphabets, whitespaces, periods or apostrophes How can I overcome this error? Here's a solution. You probably don't want to complete this in the

https://www.alexa.com/topsites/countries/CN 为啥 cnblogs 这么多年，一直不更新改版啥的？ 来源： https://www.cnblogs.com/jenasy/p/11647453.html

I have 3 slots ( account , dollar_value , recipient_first ) within my intent schema for an Alexa skill and I want to save whatever slots are provided by the speaker in the session Attributes. I am using the following methods to set session attributes: def create_dollar_value_attribute(dollar_value): return {"dollar_value": dollar_value} def create_account_attribute(account): return {"account": account} def create_recipient_first_attribute(recipient_first): return {"recipient_first": recipient_first} However, as you may guess, if I want to save more than one slot as data in sessionAttributes ,

I am building Alexa Skill for Google calendar. The client side code works as expected on local machine because I can authenticate the local machine using the link. But, when I deploy the code on AWS Lambda there is no way that I can authenticate as I cannot input code via AWS console. I am getting trouble in setting up authentication of Google Calendar API when deployed on AWS lambda. This documentation doesn't help much to me Google Implementing Server Side Authentication You should create a service account. Those are designed especially for server-to-server communication. Documentation can

During account linking process, Alexa user is redirected and presented with a form to enter his credentials (ID and/or password). Based on what's provided, the user is then being validated by the authentication flow, upon which success an accessToken is embedded in Alexa request and the user is redirected to the OAuth resource. Is there a way to pass the ID of the user obtained in the above interaction as part of the Alexa request (JSON session\user\userId ), instead of (or in addition to) it being a userId that gets generated during user's enabling their skill on a device? Or can the userId

Having issues making a REST call to an API between a node.js Lambda function and Alexa. I'm using the request library to make the calls with an account linked skill. I've only set one sample utterance for the intent, and the simulator see this fine. Also, the cloudwatch logs show a 200 response code from the api endpoint and any of the returned data from the API from console.logs to CW. 'use strict'; var http = require('http'); var request = require('request'); var Alexa = require('alexa-sdk'); var APP_ID = "amzn1.ask.skill.XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXX"; exports.handler = function(event,

i am running a nginx on my Debian 8.5 64bit which is used as reverse proxy for my node applications. Each request walks through my reverse proxy before getting routed to the special apps. Therefor i am using this config: upstream socket_nodes { server 127.0.0.1:3000; server myUrl.com:3000; server MY.ROOTSERVER.IP.ADDRESS:3000; } server { listen 80 default_server; listen [::]:80 default_server; server_name myUrl.com; return 301 https://$server_name$request_uri; } server { # SSL configuration # listen 443 ssl default_server; listen [::]:443 ssl default_server; include snippets/ssl-my-website.com