Include considered utterances generated as as a part of the fallback intent. For my skill, I noticed the utterance profiler often has the correct interpretation. Perhaps the back-end with its additional context, can proper interpret the intent.

Current localization documentation states the following:

"Note that list events and skill events that are sent to your service do not include the locale property."
https://developer.amazon.com/de/docs/custom-skills/develop-skills-in-multiple-languages.html

Request / idea:

Please add locale support to Skillevents and Listevents as well so that event based skill can be translated based on that information. Currently developers can only use a fallback language - e.g. english.

According to Alexa dev forum there is no workaround in place as well.

I would need the "locale" property in the "request" for the corresponding event type. E.g. "AlexaHouseholdListEvent.ItemsCreated".

When using Alexa hosted skill there's no ability to define the
"outDir": "dist" instead a hardcoded index.js is always used. While this isn't a blocker it's not a great experience.

It would be nice to define a build command when the deploy happens for example in package.json under scripts like the following

npm run compile

which would then compile the TypeScript source code in the src directory and output it to the dist directory.

Capability to Set timer and Get timer on Non cooking appliances should be added.

Like to set timer on Laundry appliances or dish appliances and get time remaining on those appliances.

Could you please include in the JSON response an indicator of which environment the request are coming from? I.e. "Live" or "Development". This would make CloudWatch filtering easy.

Thanks!

Alexa users have the ability to store location addresses using the Alexa App, example work, school, groceries, etc. It would be great if we could get this information from within the skill itself, with user permissions of course. This would work just like retrieving the device address. We can build skills that get direction or transit information for user's favorite locations.

Can we have a command line version of the Test console? Right now, ask-cli only works with custom skills and not smart home skills.

This would make it possible to do some common parameter checking before the request gets passed on to the real handler and return a response if there is a problem that negates the need for more processing.

Kindly provide support for an additional parameter support in account linking process. I have a scenario in which I need to know the user region. For eg if a user has signed up in service at (.com) region then all the intents inside will use the endpoints with .com and if the user has account in .eu region then all the intent action endpoints go as .eu. So there should be an option to specify the region and to store that under user while making each request to the intent.

We have a number of use cases where the objective is to enable the user to speak to a live person:

• Call a restaurant to order a meal
• Call the right doctor's office
• Call the "Call Center" for a particular pharmaceutical

As the capability to use VOIP through Alexa already exists, providing it to developers through the SDK would enable us to greatly improve user experience and fulfill our use cases through voice UI alone.

Would like to see all possible options for the ASK CLI Config. especially for those with restricted values. e.g. possible categories, locales, various options in apis['interfaces'], etc. in skills.json

I want an API to get the Alexa Speech Recognition text result. For example,

user says "Alexa, what is the weather today?"
device microphone records the sound and processes it as binary audio, then send to Alexa cloud service
due to the accent, distance, background noise or something else, Alexa may get any of the following result as transcription text from the input binary audio stream:
"Alexa, what the weather today?"
"Alexa, what is the wee today?"
"Alexa, what is the bad weather today?
I hope this API could get the actual Alexa recognition/transcription result in text and return.

since the last update photos within skills are finally also shown in android display. these correspond to the bodytemplate 3 for echo devices with displays. it would be nice if you could also set the bodytemplate for skills that also appear on smartphones displays. if you try to include the bodytemplates in the code the skill crashes in the alexa app.

to get it to the point. the function "card.renderer()" is automatically set to bodytemplate3. The developer should have the possibility to decide in which template format the photos should appear on the app with the function card.renderer().

Similarly to the AcceptGrant Directive. https://developer.amazon.com/docs/device-apis/alexa-authorization.html#acceptgrant

Would be nice to receive an event (DeleteGrant?) whenever the user tap on the disable skill button.

In this way we can clean/free resources on our side too.
Currently the only way to detect that a user had disabled the skill is with the error response from the alexa event gateway.

There are few error types available when replying to an alexa event: https://developer.amazon.com/docs/device-apis/alexa-errorresponse.html#error-type-values

Seems that the error type does not influence the response of alexa to the user..
See: https://forums.developer.amazon.com/questions/176777/smart-home-skill-error-response.html

Please document how alexa will react to each error.

The Echo Look doesn't currently have any support in the Node SDK. I would like to develop an app that takes advantage of the video and picture capability of this device.