For devices with a screen such as the show and the fire tablet(with show mode). Should be able to activate blue shade or adjust the brightness amount(similar to being able to adjust volume levels) for areas where you might have a screened device in a darkened room and don’t want it at max brightness. I use a fire tablet as my bedside alexa device and have to manually adjust the screen brightness at bedtime so it’s not blinding in the dark.

It would be great to understand the total number of people who currently have the skill enabled. Right now we are only given the number of people who enabled the skill each week but there is no information on the number of people who have disabled the skill.

A routine that invokes showing a Web page on a visual device screen would be useful for lots of different applications.
Smart home integration for ip cameras is my intended use of this feature.
As most ip cameras are difficult or impossible to show on echo show type devices. This new feature would enable the screen to show the Web site containing the camera stream from a trigger via node red or other mqtt and smart home devices. Without any voice commands needed to be issued to the device directly.

On you Firestick remote, Say, "Alexa" then tell the Firestick Alexa, "Screen note", an on screen dialog box appears on the TV. then whatever you say into the Firestick remote appears in the dialog box. This would be an easy way to communicate with a deaf or hard of hearing person. With some time settable limits, 10 seconds, 45 minutes, or until dissmissed. It would also be a way to leave notes for others. I don't know if there is a way to make it display on OTA TV programing but that seems important.

                                                         Qmavam

I have multiple Alexa's one is attached to hi fi simply called Alexa. The other is on my work bench called Computer. Would be nice to still be able to say 'Alexa' play xyz while at my workbench and have the device named Computer relay the command to the one attached to the hi fi without needing any other workaround commands like 'everywhere'

Couple of things that could make it easier from a user perspective if you don't mind the feedback

You can only see 10 utterances per page, would be great to be able to see 50 / 100 per page

Would be good to filter on the columns, e.g. filter, all the expected intents with "xyz"

Would be good to duplicate an notation set to then use again with edits

Would be good to be able to download an annotation set as a CSV, so you can edit and then upload again

A generic Notification proactive schema can look like below

Event Name - AMAZON.CustomAlert.Available

message example - vehicle <content.name> <customalert.message> at <customalert.time>
example

event: {

name: AMAZON.CustomAlert.Available,

payload: {

  customAlert: {

    time: 2028-11-20T21:00:00Z,

    message: String

  }

  content: {name: vehicle name}}

I would like an ability to pause reminders.
If I set up a weekly, or even daily reminder, perhaps I will go on vacation or will need to stop hearing that reminder for awhile. I have to delete the reminder, then remake it later. It would nice to be able to say "alexa, pause this reminder until May 4th" or at least have the option to set that up in the Alexa app.

we are working on connected car skill. we want to send custom notifications to user for example when there is harsh driving, geofence breach etc. the format of the notification might be

<any string > at <datetime>

where any string - mandatory (size of string should not be greater then suitable for alexa)

for example
<car1 entered geofence> at <21-8-2020 12:00 PM>
<harsh driving detected by car1> at <21-8-2020 12:00 PM>

Our service has multiple frontends. For this example, let's assume we have an Alexa Skill and Web interface.

CASE 1: User subscribes via Web and uses the Web. OK
CASE 2: User subscribes via skill and uses the skill. OK
CASE 3: User subscribes via the Web and users the skill. OK (The skill can check the payment API of the web application for sub status.)

FAIL CASE: User subscribes via Alexa skill and uses the web app. There is no way for the web application to verify the Alexa skill subscription status.

Please add this.

Currently, extending the the session timeout duration is not a supported feature of Alexa Skills Kit.

Yet, I hope that a skill is closed only when I give certain command, so that I don't need to activate it again. (I only activate one skill at a time)

I want the direction of voice heard by echo pass to my robot (through ZigBee, or Internet), so that the robot could make its move to that direction.
This feature is CRITICAL for home robot control. In case the robot has a map of the room, and could navigate by itself, also the position of Echo in room is known, once a command is made, the robot could move to that direction by itself.
Why such important feature is not supported yet?

It would be useful for Proactive Events to automatically notify new notifications (with audio or badge in the display series: echo spot / show) without having to ask Alexa: are there new notifications ?.

I'd would love it if it is possible to add again custom notifications for services like the popular skill "Notifyme". I Want to create a skill like "Notifyme" for germany but it isnt possible with the new proactive schemas. So i would love it if it is possible to add a schema for complete custom messages. I would also have the idea that you can identify skills that use this feature if this should be the problem.

If I create a multi-value slot using AMAZON.NUMBER, I don't get a conjunction of separate values. E.g. if my utterance includes "1, 2, and 3" instead of getting the conjoined value "1 2 3", I get the number 123. Multi-value slots should work if the slot type is AMAZON.NUMBER.

I'd like to set a dynamic entity with specific answers, and then prompt for the slot with that type. This isn't possible because of this error:"No other directives are allowed to be specified with a Dialog directive. The following Directives were returned: [Dialog.UpdateDynamicEntities]"

The use case is refining the customer's choice where lots of the choices have similar values. The dynamic entity is being used to distinguish between them.

My grandfather uses alexa for menial requests such as the date and time, weather forecasts, reading the bible etc... However he often makes requests like such: "Alexa kindly <operation>" which she unfortunately doesn't comprehend. Is it possible to add some degree of adverb functionality/recognition in?

It seems garage door opener are only supported on Locale en-US.
When trying to certify our skill we get the following message from the certifcation team:
One of the language variants of your Smart Home skill includes
functionality that is not yet available for Alexa in that language. Please remove any unsupported functionality from the skill before resubmitting.

Unsupported Functionality: Garage Doors
Language(s) Impacted: Spanish (Spain)