[sowl]

Hi

Thanks for this amazing skill.
I am using this skill on my fire tv.It is working fine. Only issue I am facing is the UI interface.. Whenever i am asking fire tv to perform any task it show that text in UI. Is it possible to remove that as sometime it will keep showing display interface and in background already started.

How to completely remove display interface from skill.

[wortart]

Hello i have followed all the steps and all without problems.

But thw skill is not responding i don't know why.

When i try to launch the skill this is the anwer "The requested skill did not provide a valid response".
The endpoint is correct, and i ahve upload the zip, no problems all the tics.

So i am trying to find the error but the log is also saying nothing, i think.

Json Input

JSON Output

nothing

If there is someone with any idea of what is happening please let me know.

Thanks.
[/quote]

[Mysticalp]

Sorry if this has been asked before, but I couldn't find any info. I'm using the Fire Stick 4K and this skill works perfectly.
I'm just trying to make it so that when Kanzi does any operation, Kodi is opened if it was not in the foreground already. Is that possible?

[RodinMe]

Hello i have followed all the steps and all without problems.

But thw skill is not responding i don't know why.

When i try to launch the skill this is the anwer "The requested skill did not provide a valid response".
The endpoint is correct, and i ahve upload the zip, no problems all the tics.

So i am trying to find the error but the log is also saying nothing, i think.

Json Input

JSON Output

nothing

If there is someone with any idea of what is happening please let me know.

Thanks.

You haven't provided enough information to be able to help much. My only comment that could help is that your problem looks to be with your custom skill and that you don't get to the endpoint server. Have you gone into the Alexa Developer Console and checked your custom skill?  I assume you have done so.  Try the "test" function at the top.  In that function, check the "Device Log." and speak or type a command that you think should work.  ie, "Alexa, tell Kanzi to play the song Anything Goes", where the song title is something in your library.  You'll probably get the error you've already seen.  Then scroll down to the bottom of the "Test" option where it says "Device Log."  Then open the line that says "Capture Error."  Scroll to the bottom of the code and see if you see something.  You might post that Device Log line here.


I have a couple of questions: 
1.  Are you setting up Kanzi or Koko?  Kanzi is designed to control your Kodi box only.  Koko is designed to allow the transfer of (audio only, I think) to your Alexa box to play music through Alexa.
2.  What are you using as an endpoint - Heroku, AWS Lambda, or OwnCloud?
2.  If using Heroku, have you set up a user account in Heroku, and does the endpoint include a user name and password?  I'm not terribly familiar with this option, so I can't help much.
3.  The questions hereafter apply to the AWS Lambda option.  If using AWS Lambda, have you signed into and learned how to use the AWS console to troubleshoot your Lambda function, perhaps examine the cache files? and examine the Cloudwatch logs?
4.  Have you learned how to turn on logging on your Kodi box and learned how to read those logs?
5.  Have you created a role for Kodi using IAM, and enabled the reading and writing of Cloudwatch logs, and of S3 buckets if using S3 for caching?

RodinME


[/quote]

[RodinMe]

I'm having a new problem creating both Kanzi and Kodi.  I'm able to use Lexigram to create both Kanzi and Koko, but neither work.  I've spent a lot of time debugging, and suspect that the problem has to do with reading and writing to S3.  This problem only occurs when trying to use AWS Lambda as a backend.  It doesn't occur when I use the same kodi.config file but deploy to Heroku.  Also, using the Alexa Developer testing, the Alexa skill is able to find my Kodi library and interpret the utterances without difficulty.  The problem is in the calls to the Lambda backend.  I thought at first that the problem could be with IAM privileges, but I don't think so.  The same IAM user privileges which may be failing with Lambda work with Heroku and make successful writes to S3.  I'm posting the a file from the Alexa skill test log, here:  https://paste.kodi.tv/tiqocufiki.kodi.

I'd appreciate any help or thoughts.

Thanks.

Rod in ME.

[RodinMe]

I'm having a new problem creating both Kanzi and Kodi.  I'm able to use Lexigram to create both Kanzi and Koko, but neither work.  I've spent a lot of time debugging, and suspect that the problem has to do with reading and writing to S3.  This problem only occurs when trying to use AWS Lambda as a backend.  It doesn't occur when I use the same kodi.config file but deploy to Heroku.  Also, using the Alexa Developer testing, the Alexa skill is able to find my Kodi library and interpret the utterances without difficulty.  The problem is in the calls to the Lambda backend.  I thought at first that the problem could be with IAM privileges, but I don't think so.  The same IAM user privileges which may be failing with Lambda work with Heroku and make successful writes to S3.  I'm posting the a file from the Alexa skill test log, here:  https://paste.kodi.tv/tiqocufiki.kodi.

I'd appreciate any help or thoughts.

Thanks.

Rod in ME.

[RodinMe]

I'm having a new problem creating both Kanzi and Kodi.  I'm able to use Lexigram to create both Kanzi and Koko, but neither work.  I've spent a lot of time debugging, and suspect that the problem has to do with reading and writing to S3.  This problem only occurs when trying to use AWS Lambda as a backend.  It doesn't occur when I use the same kodi.config file but deploy to Heroku.  Also, using the Alexa Developer testing, the Alexa skill is able to find my Kodi library and interpret the utterances without difficulty.  The problem is in the calls to the Lambda backend.  I thought at first that the problem could be with IAM privileges, but I don't think so.  The same IAM user privileges which may be failing with Lambda work with Heroku and make successful writes to S3.  I'm posting the a file from the Alexa skill test log, here:  https://paste.kodi.tv/tiqocufiki.kodi.

I'd appreciate any help or thoughts.

Thanks.

Rod in ME.

An additional point:  I get the failure only when I include an S3 cache for the lambda function.  The function can be generated, uploaded, and tested when there's no cache but not if I specify an S3 cache and access code.  This error persists with different S3 buckets and IAM user credentials.  RodinME

[eurekabeacon]

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

[RodinMe]

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.

[eurekabeacon]

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?

[captainfearless]

Hi, all set up and deployed perfectly, but error message from my echo.

Here is the capture error log, any ideas?
https://pastebin.com/pj1rZZEj

[RodinMe]

Hi, all set up and deployed perfectly, but error message from my echo.

Here is the capture error log, any ideas?
https://pastebin.com/pj1rZZEj

Your error is in the Lambda function, not the skill.  Triple check your kodi.config file.  Are you using a cache?  Have you gone to AWS IAM and created a user other than your AWS login, and added CloudWatch capabilities?  Take a close look at the Lexigram configuration and Lambda upload instructions to make sure you've done it EXACTLY as instructed.
 
You can also create a Lambda function test by using your custom skill's testing function in the Alexa developer, typing or saying the phrase and running the test, and capturing the input JSON to create a Lambda function test scenario.

Finally, I've found it's often easier to start again from scratch.  Delete your skill and Lambda function and using Lexigram's instructions from the very beginning, including downloading and filling out a new kodi.config file, creating and uploading the new zip file, and deploying.

[RodinMe]

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? 

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.

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.

[K_O_D_I_L]

Hey, Firstly just wanted to say what  a fantastic project its just a shame despite having installed this about 20 times now i cant get it to work correctly. The problem is when i add media it wont detect the changes even after using the update command. however it still works with the the medial before the update. Also if i freshly deploy the skill it  will pretty much work flawlessley until once again i add media then the same thing happens. Ive not found a fix yet after 2 days despite numerous changes, does anybody have any ideas on this. leia 18.4.

[RodinMe]

Take a look at this website:  https://www.technadu.com/how-to-create-a...odi/12584/.  A couple of comments about it.  

1.  The location of the Kodi and default media files varies depending on the OS (platform) on which Kodi is installed.  See https://kinkeadtech.com/location-of-kodi...ta-folder/.
2.  The instructions are useful if you have no existing library.  If you have one, within the Kodi app, go to <Settings>/<Media>/<Library>/<ManageSources_Music>/<Add music>/.  Then select <Browse> to find the new music within your system.  Note that you should be able to see your entire system, and your local network if you're on a Windows, Network, or other networked system.  Using the browsing feature, find and name the new file source.  After you've added it, you should see a dropdown box "Add to library."  By selecting "Yes", you should have added the new media to your library.