[adenicol]

 

Try hitting https://192.168.0.19/kodi-alexa

You've mapped that there with the WSGIScriptAlias command  

 When I go to https://192.168.0.19/kodi-alexa I get "Method Not Allowed   The method is not allowed for the requested URL."

[adenicol]

 

Try hitting https://192.168.0.19/kodi-alexa

You've mapped that there with the WSGIScriptAlias command   

 When I go to https://192.168.0.19/kodi-alexa I get "Method Not Allowed   The method is not allowed for the requested URL." 

I have gotten it working.. it's words when I invoke it from Amazon but if I hit the URL locally I was getting the error.

[MPH80]

Try hitting https://192.168.0.19/kodi-alexa

You've mapped that there with the WSGIScriptAlias command   

 When I go to https://192.168.0.19/kodi-alexa I get "Method Not Allowed   The method is not allowed for the requested URL."  

I have gotten it working.. it's words when I invoke it from Amazon but if I hit the URL locally I was getting the error. 

Yeah - method not allowed is a good sign. That's means the WSGI app is loading and trying to perform a 'GET' on the URL. Amazon performs a POST to the URL - hence method not allowed.

[csbiberle]

@Coolzero

This part of the error shows the problem

Code:

botocore.exceptions.ClientError: An error occurred (ValidationException) when ca
lling the CreateFunction operation: 1 validation error detected: Value 'arn:aws:
iam::123123123123:user/Kodi' at 'role' failed to satisfy constraint: Member must
satisfy regular expression pattern: arn:aws:iam::\d{12}:role/?[a-zA-Z_0-9+=,.@\
-_/]+

For LAMBDA_ROLE you have put the details for a "user" when it should be a "role".

Go through this section again https://github.com/m0ngr31/kodi-alexa#aws-variables and make sure what you are pasting in looks something like:

Code:

arn:aws:iam::123123123123:role/role_name_you_used

Good luck 

I am also having this problem but I am very certain that my ARN variable relates to a role:

arn:aws:iam::[lots of numbers]:role/lambda-kodi

I have followed the tutorial given out here https://www.youtube.com/watch?v=_KSlz_lT1k4

Where should I go next?

[digiltd]

@Coolzero

This part of the error shows the problem

Code:

botocore.exceptions.ClientError: An error occurred (ValidationException) when ca
lling the CreateFunction operation: 1 validation error detected: Value 'arn:aws:
iam::123123123123:user/Kodi' at 'role' failed to satisfy constraint: Member must
satisfy regular expression pattern: arn:aws:iam::\d{12}:role/?[a-zA-Z_0-9+=,.@\
-_/]+

For LAMBDA_ROLE you have put the details for a "user" when it should be a "role".

Go through this section again https://github.com/m0ngr31/kodi-alexa#aws-variables and make sure what you are pasting in looks something like:

Code:

arn:aws:iam::123123123123:role/role_name_you_used

Good luck  

I am also having this problem but I am very certain that my ARN variable relates to a role:

arn:aws:iam::[lots of numbers]:role/lambda-kodi

I have followed the tutorial given out here https://www.youtube.com/watch?v=_KSlz_lT1k4

Where should I go next? 

Yeah, you are following a really old tutorial for a really old version.

The video description also mentions this "Since creating this tutorial the code has changed. If you want to follow this video you will need to use this older version of the code"

Best to start again (go into AWS and delete your lambda functions as well) and follow the readme on the official repo https://github.com/m0ngr31/kodi-alexa

[sahara]

Hi digiltd,

https://github.com/m0ngr31/kodi-alexa/is...-container

moved as per your request.
I noticed I have the same issue with South Park. If I say Alexa, tell Kodi to play Southpark season 4 episode 7 I receive the same error. If episode is playing and ask alexa, ask Kodi what is playing, response is correct.

Thanks

[digiltd]

Hi digiltd,

https://github.com/m0ngr31/kodi-alexa/is...-container

moved as per your request.
I noticed I have the same issue with South Park. If I say Alexa, tell Kodi to play Southpark season 4 episode 7 I receive the same error. If episode is playing and ask alexa, ask Kodi what is playing, response is correct.

Thanks

Sorry for the delay, I initially thought it was to do with either your slot values or the way The Flash gets loaded into Kodi (with a "(2014)" in the title) to differentiate it from the original 90s version of the show. 

But after having a play I expect that is not the problem, does "play a random episode of the flash" work? also try with South Park (two words, not one ) and the other ones you are having problems with. I don't know how you pronounce "Gantz" but if it is like "ants" with a G on the front then "gantz" should be fine, putting it as G . A. N. T. Z would mean it is spelt out letter by letter like F . B . I

Then if she plays the right show you know that it Alexa is hearing you correctly.

Then try "play season 4 episode 7 of South Park" rather than "play South Park season 4 episode 7"

That should work. 

I have submitted a pull request to the Skill with utterances that will allow for both ways

[sahara]

Hi, just managed to test it out.
Everything works now, a bit different than I imagined, but it is perfect like this. What I mean. If I tell "Alexa, tell Kodi to play Supernatural" I receive the same error again. If I tell to play next episode of Supernatural it is working. Or The Flash, etc.
As for Gantz I had to add G. A. N. T. Z. to the slot. She understands on Guns so it won't work.

[digiltd]

Hi, just managed to test it out.
Everything works now, a bit different than I imagined, but it is perfect like this. What I mean. If I tell "Alexa, tell Kodi to play Supernatural" I receive the same error again. If I tell to play next episode of Supernatural it is working. Or The Flash, etc.
As for Gantz I had to add G. A. N. T. Z. to the slot. She understands on Guns so it won't work.

 When you say "Alexa, tell Kodi to play Supernatural" that might be because she hears "super natural" (check your logs or the app to see what she is sending).

Also you are using the generic "play" command, which is always going to make things trickier for her. She doesn't know if "supernatural" it is a show, a movie, a video playlist, an audio playlist, a band, an album, a song etc. But when you say "play the next episode of the supernatural" she then knows it is a tv show because she heard to word "episode".

You might find saying "play the tv show supernatural" works better.

[jingai]

Hi, just managed to test it out.
Everything works now, a bit different than I imagined, but it is perfect like this. What I mean. If I tell "Alexa, tell Kodi to play Supernatural" I receive the same error again. If I tell to play next episode of Supernatural it is working. Or The Flash, etc.
As for Gantz I had to add G. A. N. T. Z. to the slot. She understands on Guns so it won't work.

 Yes, "play/watch the next episode of ..." is the correct incantation.  If you want to watch the next episode of a show you just watched, you can say "continue last show."  You can ask for a specific episode as well with, "Alexa, ask Kodi to play season X episode Y of show."

As for G. A. N. T. Z., you will probably need to spell it out.

[jingai]

 When you say "Alexa, tell Kodi to play Supernatural" that might be because she hears "super natural" (check your logs or the app to see what she is sending).

 The problem is that that is a short phrase, with more than half of it being a slot she has to figure out.  Alexa matches on a confidence threshold, and if no utterance meets the minimum threshold, she will fall through to the last intent in the model.  According to Amazon, this is by design, even though it's shitty design.

In the model, it just happens that the fall-through intent is the one to play recently added songs.  If I had to guess, sahara doesn't have any songs in his/her library, which is why it's producing an error instead.

[digiltd]

 When you say "Alexa, tell Kodi to play Supernatural" that might be because she hears "super natural" (check your logs or the app to see what she is sending).

 The problem is that that is a short phrase, with more than half of it being a slot she has to figure out.  Alexa matches on a confidence threshold, and if no utterance meets the minimum threshold, she will fall through to the last intent in the model.  According to Amazon, this is by design, even though it's shitty design.

In the model, it just happens that the fall-through intent is the one to play recently added songs.  If I had to guess, sahara doesn't have any songs in his/her library, which is why it's producing an error instead. 

Not sure if correcting me or adding to the explanation... but isn't that what I said? (albeit in a different way)

Also you are using the generic "play" command, which is always going to make things trickier for her. She doesn't know if "supernatural" it is a show, a movie, a video playlist, an audio playlist, a band, an album, a song etc. But when you say "play the next episode of the supernatural" she then knows it is a tv show because she heard to word "episode".

[jingai]

I was expanding on the explanation; specifically, explaining why it fell through to a seemingly-unrelated handler.  Amazon seems to think that what they've done is right, although they didn't always do this.  At some point in the past, it would return an error saying that she couldn't understand what you wanted.  Now it falls through to the last intent in the model on a no-match.

For anyone wondering why she responds by playing recently added songs when you didn't ask for it, that's why.

[sahara]

Correct, I do not have any music in Kodi. Thanks for clearing that up for me. Now that I know how it should work, all good

[lestat1977uk]

https://www.howtogeek.com/249336/how-to-...azon-echo/

Hi All,

i followed this guide above to set this up, the best of my knowledge i have followed this thoroughly and everything looked successful.

However when i ask Alexa  to do anything,  E.g.  Ask kodi to run covenant or any of the other utterances programmed.......

the blow happens:

Alexa says there was a problem with the requested skills response and the following error is displayed in the app 

 Skill responded with HTTP 500 status code


Can anyone please help me troubleshoot this issue?