2019-10-16, 14:59
(2019-09-14, 22:59)eurekabeacon Wrote:You don't need a skill ID. (I've never used them.) The only thing the skill ID does is to limit the skill to a particular Alexa box.(2019-09-14, 13:14)RodinMe Wrote:(2019-09-14, 10:41)eurekabeacon Wrote: I've installed this skill using AWS Lambda, deploying went just fine, but when I perform any "Alexa, tell Kodi to ..." the Dot responds with:
"There was a problem with the requested skill's response"
I've also tried running in the developer console, and this is the response I get (obfuscating the tail end of any identifying ids):
https://paste.kodi.tv/raw/fopaximoli
Any help is much appreciated.
PS: here is my kodi.config if that might provide any insight:
https://paste.kodi.tv/raw/ukemiraces
I took a look at your kodi.config file. I assume that you're trying to set up kanzi, not koko (because there's no referral to a proxy.) I also see that you're not trying to use a cache. So the setup is very basic. The error says that the problem occurs in transmission. I think it could be with either the lambda function or your kodi setup. I suspect it's the latter.
I assume that you have a dns name for your outside IP? Try using your kodi box using a web browser and the dns name rather than your inside IP address or name. Also, double check the kodi settings as shown on the lexigram instructions here: https://lexigr.am/docs/getting-started.html, particularly making sure that you've included the remote control settings to "On", found at Settings -> Service -> Control -> Application -> Allow remote control.
Kodi is accessible via web browser. I’ve verified all the settings you suggested. Could this have something to do with the fact that I didn’t assign a skill ID?
Your problem is with the Lambda function. The error is only telling you that the function didn't provide a valid HTTP response. Take a look at, and maybe post, the CloudWatch log from the failed function.