2016-11-03, 18:15
Two things. First, there needs to be context, since the user (like myself) might have more than one copy of the skill (for more than one instance of Kodi). So, "Alexa, ask <skill>" is how we provide that context.
Second, it appears from the video that what he's doing is keeping the session open. This is a decent idea when you're by yourself and have control over other sources of audio in the vicinity, but if you have say, family in the room chatting, this will cause misfires.
Basically, the reason we don't do this is the same reason Alexa doesn't do it for any of the built in stuff she can process: without first hearing the wake word, it's impossible to determine if what she heard was simply humans talking to other humans (or other noise), or if it was a command directed to her.
I would love for it to work as you see in the video, but ultimately, Alexa has no idea of context. This is something that would have to be addressed by Amazon to get right.
Second, it appears from the video that what he's doing is keeping the session open. This is a decent idea when you're by yourself and have control over other sources of audio in the vicinity, but if you have say, family in the room chatting, this will cause misfires.
Basically, the reason we don't do this is the same reason Alexa doesn't do it for any of the built in stuff she can process: without first hearing the wake word, it's impossible to determine if what she heard was simply humans talking to other humans (or other noise), or if it was a command directed to her.
I would love for it to work as you see in the video, but ultimately, Alexa has no idea of context. This is something that would have to be addressed by Amazon to get right.
