(2016-11-01, 19:55)jingai Wrote: Well, I think if you really want to diagnose the problem, executing the command remotely is the next step.

The two commands I gave you to try via curl are the exact commands the PlayMovie Intent sends in this case.

The only other thing I can think is even a little feasible is that maybe Comcast is throttling bandwidth on certain ports. If you're using port 80 or 8080, they may be throttling it to prevent you from running a web server at home. It's a long shot, but maybe try changing the port to something else.

If you're not afraid of going into the code a little, in alexa_play_movie() in wsgi.ini (around line 973 if your copy is current) you can add some additional print statements around things to see how long they're taking to execute. Particularly, I'd check around kodi.GetMovies(), kodi.matchHeard(), and kodi.PlayMovie(). I think kodi.matchHeard() is the only thing left here that could be the problem, but it'd be odd for this to take 10 seconds.

(2016-11-01, 19:55)jingai Wrote: Well, I think if you really want to diagnose the problem, executing the command remotely is the next step.

The two commands I gave you to try via curl are the exact commands the PlayMovie Intent sends in this case.

The only other thing I can think is even a little feasible is that maybe Comcast is throttling bandwidth on certain ports. If you're using port 80 or 8080, they may be throttling it to prevent you from running a web server at home. It's a long shot, but maybe try changing the port to something else.

If you're not afraid of going into the code a little, in alexa_play_movie() in wsgi.ini (around line 973 if your copy is current) you can add some additional print statements around things to see how long they're taking to execute. Particularly, I'd check around kodi.GetMovies(), kodi.matchHeard(), and kodi.PlayMovie(). I think kodi.matchHeard() is the only thing left here that could be the problem, but it'd be odd for this to take 10 seconds.

(2016-11-01, 20:31)newoski Wrote:

(2016-11-01, 19:55)jingai Wrote: Well, I think if you really want to diagnose the problem, executing the command remotely is the next step.

The two commands I gave you to try via curl are the exact commands the PlayMovie Intent sends in this case.

The only other thing I can think is even a little feasible is that maybe Comcast is throttling bandwidth on certain ports. If you're using port 80 or 8080, they may be throttling it to prevent you from running a web server at home. It's a long shot, but maybe try changing the port to something else.

If you're not afraid of going into the code a little, in alexa_play_movie() in wsgi.ini (around line 973 if your copy is current) you can add some additional print statements around things to see how long they're taking to execute. Particularly, I'd check around kodi.GetMovies(), kodi.matchHeard(), and kodi.PlayMovie(). I think kodi.matchHeard() is the only thing left here that could be the problem, but it'd be odd for this to take 10 seconds.

Crap. Since I didn't create the AWS, I enlisted help there, I can't easily change the port.

With that said, would a better workaround to this entire problem to create a VM on my Unraid server and host the app locally on my network?

What would the best Unraid VM container type be for this kind of thing?

(2016-11-01, 20:38)jingai Wrote:

(2016-11-01, 20:31)newoski Wrote:

(2016-11-01, 19:55)jingai Wrote: Well, I think if you really want to diagnose the problem, executing the command remotely is the next step.

The two commands I gave you to try via curl are the exact commands the PlayMovie Intent sends in this case.

The only other thing I can think is even a little feasible is that maybe Comcast is throttling bandwidth on certain ports. If you're using port 80 or 8080, they may be throttling it to prevent you from running a web server at home. It's a long shot, but maybe try changing the port to something else.

If you're not afraid of going into the code a little, in alexa_play_movie() in wsgi.ini (around line 973 if your copy is current) you can add some additional print statements around things to see how long they're taking to execute. Particularly, I'd check around kodi.GetMovies(), kodi.matchHeard(), and kodi.PlayMovie(). I think kodi.matchHeard() is the only thing left here that could be the problem, but it'd be odd for this to take 10 seconds.

Crap. Since I didn't create the AWS, I enlisted help there, I can't easily change the port.

With that said, would a better workaround to this entire problem to create a VM on my Unraid server and host the app locally on my network?

What would the best Unraid VM container type be for this kind of thing?

Well, probably not easier to host it yourself.. and I can't really help you with Unraid as I'm not at all familiar with it. There is a Docker file present in the package though, so that may be one way to go.

For me, personally, to help you further you'll either need to acquaint yourself with the AWS Lamba deployment process (the README for the skill does a decent job of getting you there) so we can change things to debug the problem, and/or run the curl command I gave you remotely.

(2016-11-01, 20:44)jingai Wrote: I mean from outside your LAN, pointing the command at your DDNS. If you can use your mobile data, for instance, that would work. Or take a machine to a coffee shop/friends house.. or SSH into a machine off-site.. etc.

(2016-11-01, 22:25)jingai Wrote: Then we need to isolate which call is causing the delay, but that will require you have the ability to deploy new code.

(2016-11-01, 23:00)jingai Wrote: Since it sounds like you're running an older version of the skill, the first thing you might try is simply updating to the latest.