Posts: 2,437
Joined: Mar 2010
Reputation:
50
jingai
Skilled Skinner
Posts: 2,437
Huh? Just use the local IP address of the machine on which Kodi is running.
Posts: 403
Joined: Nov 2011
Reputation:
1
If I try that immediately after my Chromebox running LibreELEC boots, that command doesn't seem to do anything. If I give it a few minutes and then run it... it launches the movie nearly instantly.
Posts: 2,437
Joined: Mar 2010
Reputation:
50
jingai
Skilled Skinner
Posts: 2,437
Well, I'm thoroughly confused then.. the only thing left it can be is that it's just, for whatever reason, taking 10 seconds to return the list of movies to the skill.
Are you perhaps currently saturating your uplink?
Posts: 2,437
Joined: Mar 2010
Reputation:
50
jingai
Skilled Skinner
Posts: 2,437
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.