linuxserver.io Posted May 1, 2019 Share Posted May 1, 2019 Application Name: Kanzi Application Site: https://lexigr.am Docker Hub: https://hub.docker.com/r/linuxserver/kanzi/ Github: https://github.com/linuxserver/docker-kanzi This release is a little bit special as the application author is actually an Unraid user, so you all have @m0ngr31 to thank for this awesome Alexa skill to enable voice control with Kodi. Please post any questions/issues relating to this docker you have in this thread. If you are not using Unraid (and you should be!) then please do not post here, instead head to linuxserver.io to see how to get support. 1 Quote Link to comment
Squid Posted May 1, 2019 Share Posted May 1, 2019 You are the kings!!! I've been waiting for someone to build a skill of kodi! [emoji8][emoji8]Sent via telekinesis Quote Link to comment
CHBMB Posted May 2, 2019 Share Posted May 2, 2019 On 5/1/2019 at 11:03 PM, Squid said: You are the kings!!! I've been waiting for someone to build a skill of kodi! Sent via telekinesis Quoting that so you can't delete it at a later date when I annoy you...... BTW, this one is from me 😘 @m0ngr31 implemented some upstream changes to accomodate a smooth docker experience it has to be said. 1 Quote Link to comment
Squid Posted May 4, 2019 Share Posted May 4, 2019 Couple of questions I'm assuming that this is supposed to be a reverse proxy URL to this container? First stumbling block. I've created an Alexa Developer Account, and can get the Authorization Code, but it's not taking it. Do I need an AWS developer account instead? The directions on GitHub aren't clear, and contradict itself at times (just weary of handing over a CC# if I don't need to) root@55358642ec01:/config# lexigram login --no-browser true ? Please type in your new profile name: Squid -------------------- Initialize CLI -------------------- ? There is no AWS credential setup yet, do you want to continue the initialization? (Default: False) Yes Warning: Profile: "Squid" will not be able to deploy lambda functions since no AWS credentials are set up. Paste the following url to your browser: https://www.amazon.com/ap/oa?redirect_uri=https%3A%2F%2Fs3._blahblahblahAsIveNoIdeaWhatIsPersonallyIdentifiableOrNot ? Please enter your Authorization Code: xxxxxxxxxxxxx Access token failed. Error: getaddrinfo EAI_AGAIN api.amazon.com:443 Quote Link to comment
CHBMB Posted May 4, 2019 Share Posted May 4, 2019 7 hours ago, Squid said: Couple of questions I'm assuming that this is supposed to be a reverse proxy URL to this container? Yep As for the second bit, I just created a developer account at the URL in the readme. No CC details required. Just try leaving the profile at default. The instructions here are a little more comprehensive. https://lexigr.am/docs/docker.html Quote Link to comment
strike Posted May 19, 2019 Share Posted May 19, 2019 Thanks for this! Need some help tho. I've gone through the setup in the readme but how do I add the skill to alexa? On the app page it says: "Just login with your normal Amazon account and it'll walk you through a few steps you have to take." What steps exactly? Do I need to create a new skill? After the setup, there are no skills in my developer account and there is no kanzi skill in alexa. Quote Link to comment
strike Posted May 20, 2019 Share Posted May 20, 2019 On 5/19/2019 at 5:34 AM, strike said: Thanks for this! Need some help tho. I've gone through the setup in the readme but how do I add the skill to alexa? On the app page it says: "Just login with your normal Amazon account and it'll walk you through a few steps you have to take." What steps exactly? Do I need to create a new skill? After the setup, there are no skills in my developer account and there is no kanzi skill in alexa. Anyone? Quote Link to comment
Weavus Posted May 16, 2020 Share Posted May 16, 2020 Anyone able to run this behind nginx and actually get the Alexa skill to communicate with it? I’m getting SSL errors as it seems AWS does not like letsencrypt certs and even uploading the full pem as a self cert certificate still prevents the skill from successfully being able to connect. Quote Link to comment
Pariah0x29a Posted November 26, 2020 Share Posted November 26, 2020 (edited) On 5/15/2020 at 7:02 PM, Weavus said: Anyone able to run this behind nginx and actually get the Alexa skill to communicate with it? I’m getting SSL errors as it seems AWS does not like letsencrypt certs and even uploading the full pem as a self cert certificate still prevents the skill from successfully being able to connect. I'm also having SSL issues with it. This is the error I'm having: SSL Handshake failed Request Identifier: amzn1.echo-api.request.a1ee4681-a033-4fe8-9b5e-03a0c95cb636 The SSL handshake to endpoint Resource [https://kanzi.mydomain.duckdns.org/], Type [HTTP], Region [DEFAULT] failed. Please check that your java keystore is correctly configured. I am using this with SWAG and all of my other subdomains work just fine, HTTPS and all. Just this one is giving issues. Also when I first deploy the skill it always says it failed and then immediatly after says it was successfull... is this normal? I've deleted everything and started fresh and it still happens.. This is in the log when I deploy for the first time: [19:57:03] Deploy skill [failed] [19:57:03] → Error deploying. Please try again [?25h[?25h Kanzi 10.29.2020-7cec59f successfully deployed with invocation name kanzi at https://kanzi.mydomain.duckdns.org/ Edited November 26, 2020 by Pariah0x29a Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.