(2016-11-18, 17:18)jingai Wrote: (2016-11-18, 12:06)shukerr Wrote: Now, I have another little annoyance that I'd appreciate some guidance on. I'm a UK user, but not sure that's related.
If I haven't specifically listed a Movie, TV Show or Music in the Custom Slots Values then it simply will not find it.
For TV shows I either get the dull chime from the echo or a comment along the lines of "I can't find the answer you're looking for..."
For music it is trying to play it through Amazon Music & saying "I can't find an album by XYZ n your collection."
In the case of music the artist name is repeated back correctly so Alexa has definitely understood correctly.
Everything I've entered into the custom slot values works perfectly.
I don't mind populating the custom slot values, but my impression was that it should still have a reasonable chance of working regardless.
You definitely don't have to enter them into the slots, except for the DoSearch intent "Alexa, tell Kodi to search for ...". I'll be fixing that soon, but for other commands they use fuzzy matching that should get you the right answer most of the time.
List off some specific commands you're trying to issue. It's possible we simply haven't thought of those phrases.
And what do your server logs say when it doesn't match?
(2016-11-18, 12:06)shukerr Wrote: Lastly, this app to populate the values mentioned earlier in the forum is now offline. https://sleepy-wave-26412.herokuapp.com/
@m0ngr31 hosts that, so I can't say why it's not online.
@
jingai
So, I've been doing some more testing in the UK & I think I know what's going on with these custom slot values.
I checked the utterances file to ensure I was only using correct phrases. e.g. "Alexa, ask media centre to listen to music by Dolly Parton"
Still only entities specifically within the custom slot values will work.
I checked the Heroku logs and nothing was being passed to Heroku when the custom slot value did not exist.
I've changed over to AWS Lamda and it's the same. The requests are only passed to Lamda when the specific artist/album etc is present in the custom slot value.
No card is created, but I can see in the history that the request was heard perfectly.
My Alexa account also includes Amazon Music, Spotify & TuneIn Radio. Amazon Music is set as the default service for both music and stations
It's looking fairly likely that Alexa is ignoring the invocation name and passing the request to the default service.
From one of your earlier posts I've just changed the invocation name from "media centre" to "raspberry pi" and am getting some results for media not contained in the custom slot values.
There's a fair few still being routed to the Amazon Music service, but changing the invocation name has definitely made a big difference.
I don't know if it's possible to present a skill as a "music service" as it could then be set as the default.
It's pretty annoying for Alexa to ignore the invocation name and then feed the request to it's own app.