Right now, it seems all interaction with Echo must happen through launching of the app. Is there any possibility that Alexa itself will have a webservice endpoint to "push" interaction with the user?
Ie, if I want Echo to say something (doorbell was pressed), can I do that?
Context:
Feature where Echo can 1) say or 2) do something based on a remote trigger (other than talking to Echo).
1) say examples: read text, read email aloud, calendar reminder, etc. = dictation
2) do examples: pair to Bluetooth speaker, trigger home automation actions like lights, play playlist x, etc. = home automation and internal functions
NOTE: Only some internal functions, like play music, pair speaker should open to be triggered remotely. Start listening, order this, rename device, etc.- should be not work through remote triggers.
Use cases: 1) motion sensor detects motion - echo turn on lights, turn on Bluetooth speaker, start playing your favorite radio station. 2) echo says "you have a meeting with John in 15 minutes"
For the above scope, reading through this post, I think both users and Amazon would want this but not when there is any risk of exploitation.
Risks & avoidance:
One risk is remote trigger without users knowledge or consent. I think there is a good proven industry example on how to avoid this: apples app permission pop-ups. When an iPhone app wants access to your photos, contact, use GPS - the OS asks your permission. And you can see what permissions you have given and have the option to turn them off again. Second risk is blocking invoking of dangerous internal functions, like order things, start listening, etc. I think this can be solved in the same way. Remote triggers apps should run in a special code environment. This environment would simple block certain request (order on-line) and check user permissions for others. If dictation is requested the first time, Echo would ask "Skill X request permission to speak to you automatically though a remote trigger. Do you want to allow this? You can always change you mind later via the Alexa app or by asking me".
Hope this helps
The system is almost ready to be used in home automation. The ability to customize what Alexa will say ensures interaction with people who are not "trained" and do not know Alexa's routines.
The method used for notifications is the old answering machine approach. We need to be able to ask a user for information at specific times and on certain days. We also need to be able to have our mobile app trigger an intent based on conditional logic. It is terribly limiting and poor user experience to require me to says Alexa change the channel to NBC, when I could press a button and she asks me what channel do you want to go to. Or I go to the gym and when I arrive home she asks me how my work out was and what I did and for how long.
What is the expected Timeline for Notification API?
Usecase: notification by FHEM "dishwasher finished" / "window still open" / "oven - the food is ready" and so on
and: notify to specific device / group / all
Push speech is a no-brainer, Amazon like others have said isn't going to introduce it until Google Home does.
Another 90days comming soon passed... ;-(
For all devs getting bored waiting for Amazon to enable Push... Meanwhile started to implement Actions and Push for Google Home, might wanna join? https://www.youtube.com/watch?v=BCcL5HGoNSM
<a href="https://developer.amazon.com/blogs/alexa/post/8cc45487-d5fb-413b-b6c7-eeea4794d10c/amazon-announces-notifications-for-alexa-feature-is-coming-soon-sign-up-to-stay-tuned"> </a>
Context:
Feature where Echo can 1) say or 2) do something based on a remote trigger (other than talking to Echo).
1) say examples: read text, read email aloud, calendar reminder, etc. = dictation
2) do examples: pair to Bluetooth speaker, trigger home automation actions like lights, play playlist x, etc. = home automation and internal functions
NOTE: Only some internal functions, like play music, pair speaker should open to be triggered remotely. Start listening, order this, rename device, etc.- should be not work through remote triggers.
Use cases:
1) motion sensor detects motion - echo turn on lights, turn on Bluetooth speaker, start playing your favorite radio station.
2) echo says "you have a meeting with John in 15 minutes"
For the above scope, reading through this post, I think both users and Amazon would want this but not when there is any risk of exploitation.
Risks & avoidance:
One risk is remote trigger without users knowledge or consent. I think there is a good proven industry example on how to avoid this: apples app permission pop-ups. When an iPhone app wants access to your photos, contact, use GPS - the OS asks your permission. And you can see what permissions you have given and have the option to turn them off again.
Second risk is blocking invoking of dangerous internal functions, like order things, start listening, etc. I think this can be solved in the same way. Remote triggers apps should run in a special code environment. This environment would simple block certain request (order on-line) and check user permissions for others. If dictation is requested the first time, Echo would ask "Skill X requests permission to speak to you automatically though a remote trigger. Do you want to allow this? You can always change you mind later via the Alexa app or by asking me".
Hope this helps
This is really important, guys. PLEASE IMPLEMENT
Sill waiting for push notifications as its really an essential item for completing the home automation cycle. Amazon is still missing the option to group echo speakers as well for audio playback :( I really don't want to transition to google home but if amazon doesn't make some progress in these areas I can't see much other choice.
24 People are following this question.
