[jingai]

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.

Follow the official official README please.
 

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

Covenant is a banned addon (wiki).  You are not permitted to discuss it on these forums.  Further, this skill will not work with it beyond opening the addon.

[Karellen]

@lestat1977uk

With 328 posts, would have expected you to know better. But jingai is correct. Covenant is a banned add-on here.

You are obviously using banned add-ons, which makes you ineligible for support here.

To receive assistance here, these banned items must be removed. If a clean log is not submitted within 3 days, then the relevant post(s) will be removed after this time.

[Klouse]

Hi,

can somebody please help my with my https nginx reverse proxy?

The best working location i could write was: 

Code:


location /jsonrpc {
        proxy_pass         http://kodi;
        proxy_http_version 1.1;
        proxy_set_header   Upgrade $http_upgrade;
        proxy_set_header   Connection "upgrade";
                
          auth_basic "Restricted Access";
        auth_basic_user_file /etc/nginx/.secure/.kodi.htpasswd;
        access_log /var/log/nginx/kodi.access.log;
        error_log /var/log/nginx/kodi_https.error.log;    
  }


but i'd love to have it under /kodi/jsonrpc, 
maybe somebody already did it?

Thank you!

regards,

Klaus

[lestat1977uk]

@lestat1977uk

With 328 posts, would have expected you to know better. But jingai is correct. Covenant is a banned add-on here.

You are obviously using banned add-ons, which makes you ineligible for support here.

To receive assistance here, these banned items must be removed. If a clean log is not submitted within 3 days, then the relevant post(s) will be removed after this time.
 

Hi, sorry i only referenced Covenant as example, i was not asking for any kind of support for that add-on (i do know better), in hindsight i should have made it clear that no utternaces work and i should of used a different example.  .... you are right though,  how do i submit a clean log... or do i just removed my post?

For the record i went back over the guide and have now got the skill working,   my fault for both building the skill and posting on the forum at 4am

Thanks

[Karellen]

Good that you got it working If you need to create a debug log (wiki) just click the link in My Signature below.

Just be wary of the forum rules. Its not about asking for help with the banned item, it is we won't assist if they are installed. A big difference that many members get tripped up on.

[lestat1977uk]

Good that you got it working If you need to create a debug log (wiki) just click the link in My Signature below.

Just be wary of the forum rules. Its not about asking for help with the banned item, it is we won't assist if they are installed. A big difference that many members get tripped up on.

 ok thanks for the clarification of the rules

keep up the good work!

[damascas]

Hi - just got an Echo Dot and my first thought was whether I could use it to control Kodi.  Very happy to have found this!

I have had this setup and working hosted on AWS but am testing out my skills trying to host internally.  I have apache2 on Ubuntu and the WSGI appears to be installed (going to the local url gives Method Not Allowed).  I have to admit that WSGI is a new one for me so I don't have any other way of confirming it's working properly, although I do have a test wsgi app up and running (a basic Hello World sort of thing).

I have all the port forwarding setup - I can get the Method Not Allowed in a browser outside of my local network by connecting to https://my.domain/alexa-wsgi.

When it comes to the Skill setup, under the configuration I did have https://my.domain/alexa-wsgi.  This gave me a 301 Permanently Moved when tested and I could see that the WSGI wasn't being called.  Changing the configuration to https://my.domain/alexa-wsgi/ changed the error to a 500 Internal Server Error.  

This is the error from the apache error log:
 https://pastebin.com/QHqzttJx
Can anyone help?

EDIT - Changed the log to a pastebin.  Sorry about that.

[Karellen]

@damascas

Please do not post logs in the forum. Use a public pastebin type site.

Can you remove the log from your post and upload to https://pastebin.com/ or https://paste.ubuntu.com/

[digiltd]

Hi,

can somebody please help my with my https nginx reverse proxy?

The best working location i could write was: 

Code:


location /jsonrpc {
        proxy_pass         http://kodi;
        proxy_http_version 1.1;
        proxy_set_header   Upgrade $http_upgrade;
        proxy_set_header   Connection "upgrade";
                
          auth_basic "Restricted Access";
        auth_basic_user_file /etc/nginx/.secure/.kodi.htpasswd;
        access_log /var/log/nginx/kodi.access.log;
        error_log /var/log/nginx/kodi_https.error.log;    
  }


but i'd love to have it under /kodi/jsonrpc, 
maybe somebody already did it?

Thank you!

regards,

Klaus

Here is what I use:

javascript:


 # Kodi MacMini

 location /kodi_mac_mini_NYCdtQ6KsFGAmWung3aqR7SHZUhxryEkbciV8P9BpPmSqtRKG83DiWYMy2vHn4wuEbCrgUNd/ {

     deny all;

     allow 192.168.1.0/24;



     # here I include a list of Amazon IPs (optional) 

     # include /etc/nginx/conf.d/blockips.conf;



     # when setting up "allow all", when happy it works, you can start to lock it down to certain IPs 

     # allow all;



     # the local IP and port of the Kodi install I want to forward to:

     proxy_pass http://192.168.1.123:8282/;

     

     proxy_set_header Host $host;

     proxy_set_header X-Real-IP $remote_addr;

     proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

 }

 

I use a random string for the location. You can add multiple locations to forward to different boxes.

Make sure you set the subpath in kodi.config 

javascript:
subpath  = kodi_mac_mini_NYCdtQ6KsFGAmWung3aqR7SHZUhxryEkbciV8P9BpPmSqtRKG83DiWYMy2vHn4wuEbCrgUNd

Good luck

[damascas]

Never mind - I was being stupid!  I'd missed a whole file in the setup - templates.en.yaml.  Funnily enough, put that in the right place, give apache a restart and it's all working!

Thanks very much for this, I love it!

[Klouse]

Hello,

digiltd, thank you very much, it works like a charm, i tried a lot of things, but just not a slash at the end of the location and the server path. -.-

Regards,

Klaus

[bigwillch]

This is amazing work! Thank you so much for the incredibly detailed instructions. It's working really well for me, I feel like I'm living in the future!

In terms of the supported commands, is there anything like "ask kodi to show me information about... (movie, show, episode etc.)" in order to bring up the info screen with plot, cast etc?

Also it would be great if it were possible to issue cec commands as well (i.e. "ask kodi to turn on tv", which would send the on signal through cec and set the source to kodi) - edit: just seen this, will patch my own version of it’s not something you’re keen to implement https://github.com/m0ngr31/kodi-alexa/pull/240

Edit: Sorry one more suggestion - it would be good if we could use the resume (as in resume in progress episodes/ films) command as well as just play ("resume latest episode of...")

[jingai]

In terms of the supported commands, is there anything like "ask kodi to show me information about... (movie, show, episode etc.)" in order to bring up the info screen with plot, cast etc?

Add this as an Issue on GitHub and we'll look into it.

Also it would be great if it were possible to issue cec commands as well (i.e. "ask kodi to turn on tv", which would send the on signal through cec and set the source to kodi) - edit: just seen this, will patch my own version of it’s not something you’re keen to implement https://github.com/m0ngr31/kodi-alexa/pull/240

It's just that it's a "can of worms" kind of feature. We already removed streaming music support from the main Kodi-Alexa skill for the same reason. Similarly, PVR support is expected to be its own skill as well.

The primary problem is that we're simply running low on language variations that are both concise and natural-feeling. Breaking these things up into multiple skills makes more sense, because the added context allows us to share similar phrasing without colliding with existing intents.
 

Edit: Sorry one more suggestion - it would be good if we could use the resume (as in resume in progress episodes/ films) command as well as just play ("resume latest episode of...")

Feel free to add this as an Issue on GitHub as well. I believe I played with it at some point in the past and had some troubles (phrasing just not distinct enough), but it's possible that's changed at this point. Alexa's modeling changes frequently.

[bigwillch]

Thanks for the response. Will make those github issues as suggested. Cheers!

[jingai]

"ask kodi to show me information about... (movie, show, episode etc.)" will be a bit harder to implement, if it's possible.  The biggest problem that I can see after looking into it briefly is that we need to determine what kind of media the item you requested is first.  There isn't just one "info dialog" -- it's separate for each type of media.  So it will have to search your whole library for what you wanted (if you omit the media type in your request), and then we would need to pass that library item ID to the correct info dialog, which I'm not yet sure is entirely possible.

But, I have just pushed up these:

Code:

open info
open info dialog
open info window
open information
open information dialog
open information window
show info
show info dialog
show info window
show information
show information dialog
show information window

which will present the info dialog for the currently selected item.

Still, feel free to request the feature.  I just don't know when I will personally have the time to look into it.. my real job is kicking my butt