• 1
  • 2
  • 3(current)
  • 4
  • 5
  • 176
Release Kanzi: Amazon Alexa skill for Kodi
#31
Just wanted to reply back and thank m0ngr31 for his upgrade of the code and spending his time helping with getting it all setup. So thanks again!

I have it working for movies and my TV section now running on my ESXi server at home.
It's pretty legit to be able to ask it to watch specific shows.
Hope everyone else has fun with it too.

- Echellon
Reply
#32
HI thanks for all your work on this. I have been trying on and off to get this to work hoping there would be a post that i could use to test things.. Recently as I ran "rhc tail -o "-n 20" -a kodi" I got the following errors.

DL is deprecated, please use Fiddle
RSA 1024 bit CA certificates are loaded due to old openssl compatibility
[Wed Jan 20 21:11:38 2016] [error] [client xxx.xx.xxx.129] response = one_intent[1](intent_slots)
[Wed Jan 20 21:11:38 2016] [error] [client xxx.xx.xxx.129] File "/var/lib/openshift/xxxxxxxxxx/app-root/runtime/repo/wsgi.py", line 338, in alexa_pick_random_movie
[Wed Jan 20 21:11:38 2016] [error] [client xxx.xx.xxx.129] movies = movies_response['result']['movies']
[Wed Jan 20 21:11:38 2016] [error] [client xxx.xx.xxx.129] KeyError: 'result' xx.xx.xxx.xx - - [20/Jan/2016:21:10:35 -0500] "POST / HTTP/1.1" 500 624 "-" "Apa
che-HttpClient/UNAVAILABLE (Java/1.8.0_66)"

Any advice you could give would be appreciated.
Reply
#33
(2016-01-20, 01:48)edwsn2005 Wrote: I set it to 0 and still no luck. I'm new to all of this. The setup for Heroku seems a little more complicated than OpenShift.

Might have to re-deploy after you remove the worker. You can try OpenShift too, but there have just been little issues with it where it won't talk to Kodi properly for some unknown reason.

(2016-01-20, 22:23)Echellon Wrote: Just wanted to reply back and thank m0ngr31 for his upgrade of the code and spending his time helping with getting it all setup. So thanks again!

I have it working for movies and my TV section now running on my ESXi server at home.
It's pretty legit to be able to ask it to watch specific shows.
Hope everyone else has fun with it too.

- Echellon

Glad you were able to get it working!

(2016-01-21, 04:52)lakram Wrote: HI thanks for all your work on this. I have been trying on and off to get this to work hoping there would be a post that i could use to test things.. Recently as I ran "rhc tail -o "-n 20" -a kodi" I got the following errors.

DL is deprecated, please use Fiddle
RSA 1024 bit CA certificates are loaded due to old openssl compatibility
[Wed Jan 20 21:11:38 2016] [error] [client xxx.xx.xxx.129] response = one_intent[1](intent_slots)
[Wed Jan 20 21:11:38 2016] [error] [client xxx.xx.xxx.129] File "/var/lib/openshift/xxxxxxxxxx/app-root/runtime/repo/wsgi.py", line 338, in alexa_pick_random_movie
[Wed Jan 20 21:11:38 2016] [error] [client xxx.xx.xxx.129] movies = movies_response['result']['movies']
[Wed Jan 20 21:11:38 2016] [error] [client xxx.xx.xxx.129] KeyError: 'result' xx.xx.xxx.xx - - [20/Jan/2016:21:10:35 -0500] "POST / HTTP/1.1" 500 624 "-" "Apa
che-HttpClient/UNAVAILABLE (Java/1.8.0_66)"

Any advice you could give would be appreciated.
Try rebuilding your library or switch to Heroku
Reply
#34
(2016-01-21, 05:04)m0ngr31 Wrote: [quote='edwsn2005' pid='2220145' dateline='1453247295']
I set it to 0 and still no luck. I'm new to all of this. The setup for Heroku seems a little more complicated than OpenShift.

Might have to re-deploy after you remove the worker. You can try OpenShift too, but there have just been little issues with it where it won't talk to Kodi properly for some unknown reason.

How can I send you a direct message on here? I tried to send you one through your profile but it stated that I didnt have authorization to send you one.
Reply
#35
I think you have to have a certain number of posts to PM me. You can send me an email: joeipson (at) gmail (dot) com
Reply
#36
Thanks I have tried the switch to Heroku but alas the same error...Ask Kodi provides a response but I get a remote could not be called/timeout for any other command.. So because I am so new to all this could you explain what you mean by "rebuilding your library" and I will try that

Thanks for all your help!
Reply
#37
(2016-01-22, 06:26)lakram Wrote: Thanks I have tried the switch to Heroku but alas the same error...Ask Kodi provides a response but I get a remote could not be called/timeout for any other command.. So because I am so new to all this could you explain what you mean by "rebuilding your library" and I will try that

Thanks for all your help!
From what other users have told me, they deleted their sources, added them from scratch, and then did a library update. See if that helps at all.
Reply
#38
(2016-01-22, 21:35)m0ngr31 Wrote:
(2016-01-22, 06:26)lakram Wrote: Thanks I have tried the switch to Heroku but alas the same error...Ask Kodi provides a response but I get a remote could not be called/timeout for any other command.. So because I am so new to all this could you explain what you mean by "rebuilding your library" and I will try that

Thanks for all your help!
From what other users have told me, they deleted their sources, added them from scratch, and then did a library update. See if that helps at all.

Thanks for the advice. I gave this a try but again the program just can't seem to communicate with Kodi. I have tried everything, ports are open, fresh install of everything, recreated app and skill, both on RHC and heroku, setup a new library in Kodi and still I get echo to tell me available commands (which means the app is working) but still can't seem to communicate with kodi. If anyone has had any luck I would appreciate any advice. I will continue to give this a go and if I find a solution I will be sure to post it.
Reply
#39
Can you PM me the details on your Kodi server so I can try talking to it manually? That'll help me debug what is going on.
Reply
#40
Has anyone done this on a private server? I'm struggling with configuring the WSGI elements on Apache to trigger the API on Kodi.
Reply
#41
(2016-02-01, 05:14)astro14 Wrote: Has anyone done this on a private server? I'm struggling with configuring the WSGI elements on Apache to trigger the API on Kodi.

Echellon got it running on his own server if you want to ask him.
Reply
#42
I was able to get this working through my home server. If anyone is looking to modify the readme for implementation on their own server, here are the basic requirements.

Add mod_wsgi to apache with apt, generate a self signed cert with this guide.

In the wsgi.py script, you'll need to comment out (or remove) lines 4-9, as they are specific to Openshift deployments.

In your default-ssl.conf file for your SSL apache configuration you need to add a line for WSGIScriptAlias, something like:
Code:
WSGIScriptAlias /kodi-alexa /var/www/html/kodi-alexa/wsgi.py

In Alexa Skill Set, Add your IP and service name as the HTTPS URL: https://XXXX.ddns.net/kodi-alexa
On the SSL Certificate page, copy and paste the contents of your apache.crt file generated from the guide above.

Finally, if you haven't already, you'll have to open your apache server to the Internet with port forwarding.

All in all it works pretty well. If I ask for playing a random movie or episode, occasionally I'll get Alexa telling me that the "Requested Skill took too long to respond," but it will work. Probably a timeout that I need to find and change.

HTH, available to answer questions if I can.
Reply
#43
Glad you got it going!

If you have huge libraries of things to parse out, it can take a while and then the Echo will think it times out. Mine does it when my hard drive has to spin up from sleeping.
Reply
#44
I had a quick question. Thanks for all your hard work. I am able to use all the utterances you provided in your documentation perfectly fine, so I know I have everything setup correctly as far as being able to talk to Kodi. I decided to add some of the old utterances from the project you forked from, for example: WhatNewShows what shows are ready. However if I ask "Alexa ask kodi what shows are ready" I get this error back "There was an error calling the remote endpoint, which returned HTTP 500 : Internal Server Error".

This is what shows up in my logs:

Code:
2016-02-10T06:28:21.399728+00:00 app[web.1]: [2016-02-10 06:28:21 +0000] [9] [ERROR] Error handling request /
2016-02-10T06:28:21.399733+00:00 app[web.1]: Traceback (most recent call last):
2016-02-10T06:28:21.399734+00:00 app[web.1]:   File "/app/.heroku/python/lib/python2.7/site-packages/gunicorn/workers/sync.py", line 130, in handle
2016-02-10T06:28:21.399735+00:00 app[web.1]:     self.handle_request(listener, req, client, addr)
2016-02-10T06:28:21.399736+00:00 app[web.1]:   File "/app/.heroku/python/lib/python2.7/site-packages/gunicorn/workers/sync.py", line 171, in handle_request
2016-02-10T06:28:21.399736+00:00 app[web.1]:     respiter = self.wsgi(environ, resp.start_response)
2016-02-10T06:28:21.399737+00:00 app[web.1]:   File "/app/wsgi.py", line 767, in application
2016-02-10T06:28:21.399738+00:00 app[web.1]:     output = h[1](environ, start_response)
2016-02-10T06:28:21.399738+00:00 app[web.1]:   File "/app/wsgi.py", line 737, in do_alexa
2016-02-10T06:28:21.399739+00:00 app[web.1]:     response = one_intent[1](intent_slots)
2016-02-10T06:28:21.399740+00:00 app[web.1]:   File "/app/wsgi.py", line 613, in alexa_what_new_episodes
2016-02-10T06:28:21.399740+00:00 app[web.1]:     new_episodes = kodi.GetUnwatchedEpisodes()
Am I missing a reason why the previous utterances wouldn't work now?
Reply
#45
No, they should work still. I haven't removed any of the code. I'll play around with it a little and see what happens.
Reply
  • 1
  • 2
  • 3(current)
  • 4
  • 5
  • 176

Logout Mark Read Team Forum Stats Members Help
Kanzi: Amazon Alexa skill for Kodi15