(2016-12-12, 22:25)jingai Wrote:

(2016-12-12, 22:12)jouster Wrote: You say you host it yourself. Do you find this easier? What do you use or recommend for this.

I have access to a raspberry pi or a NAS that can run host a server for the requirements if needed. I just need pointing in the right direction.

It's up to what you find difficult, I guess, but it's just a web server (Apache + mod_wsgi in my case). I prefer to host it locally for a number of reasons.. the biggest being that I already had the web server in place for other things, so I didn't see the need to employ another service in the middle. It's faster, I don't have to place any trust in a 3rd party, etc.

The downsides are obvious too, though: if you don't know what you're doing, it's potentially a bigger security risk than just making Kodi accessible to the outside world. You'll be maintaining it yourself, dealing with certificates yourself, etc etc.

So.. it's up to you to decide.

(2016-12-12, 22:12)jouster Wrote: I will look at my logs but I fear the results I'll see will just lead to more questions.

Not likely, actually. Either it's getting the requests or it's not. If the logs are empty, the problem is the skill set up on the dev console. If the logs aren't empty but are presenting some error, posting the error here should be enough for us to help you figure out what to do.

You can look at the screenshots in @jonjon's post above if it helps.

(2016-12-12, 22:12)jouster Wrote:

(2016-12-12, 22:07)jingai Wrote:

(2016-12-12, 21:59)jouster Wrote: You say you don't personally use AWS. I am. Now wondering what you personally use.

I host it myself, but don't misunderstand: I wasn't saying AWS is a 'bad' way to host it. Was just indicating my level of experience with it.

(2016-12-12, 21:59)jouster Wrote: The links you've sent me are the exact procedure I have followed which is why I am tearing my hair out.

I have followed them to the letter and I'm still getting the endpoint issue when attempting to test in AWS.

Not trying to be rude or anything, but obviously you missed something It's difficult to say where you went wrong though.

You should start by checking the Lambda logs to see if the skill is even seeing any of the requests.

(2016-12-12, 21:59)jouster Wrote: You mentioned in earlier post about pointing to my endpoint. Via a browser to see what response I get. This is where I was a little confused for now and was hoping this would at least either point to the expected result meaning I could look else where for my issue or see if there is something wrong early on.

I don't know if there's a URL you can point a browser at to test Lambda functions. I'm sorry I mislead you there.

You don't need to apologise and none of you replies are coming across as rude

The internet and chat rooms in general are so hard to communicate via at time as so much is lost in text.

You say you host it yourself. Do you find this easier? What do you use or recommend for this.

I have access to a raspberry pi or a NAS that can run host a server for the requirements if needed. I just need pointing in the right direction.

I will look at my logs but I fear the results I'll see will just lead to more questions.

I guess I may need some assistance from someone tuning this using the AWS process themselves

At the end of the day I'd rather run it locally hosted as it will (IMHO) be the better way to host it. This is how I have my KODI running in general (on a 100TB server) so I always appreciate how local data is more beneficial in some instances.


Sent from my iPhone (typie typie)

(2016-12-13, 13:03)jouster Wrote: Application ID verification failed: ValueError
Traceback (most recent call last):
File "/var/task/wsgi.py", line 1813, in lambda_handler
verify_application_id(appid)
File "/var/task/wsgi.py", line 1799, in verify_application_id
raise ValueError("Application ID verification failed")
ValueError: Application ID verification failed

(2016-12-13, 16:26)jouster Wrote: and removed SKILL_APPID from the end of this line so this is now how the line looks in my ENV file

(2016-12-13, 16:26)jouster Wrote: 14:22:26 /var/task/fuzzywuzzy/fuzz.py:35: UserWarning: Using slow pure-python SequenceMatcher. Install python-Levenshtein to remove this warning
14:22:26 warnings.warn('Using slow pure-python SequenceMatcher. Install python-Levenshtein to remove this warning')

(2016-12-13, 16:26)jouster Wrote: 'result': KeyError
Traceback (most recent call last):
File "/var/task/wsgi.py", line 1821, in lambda_handler
return on_intent(event['request'], event['session'])
File "/var/task/wsgi.py", line 1788, in on_intent
return one_intent[1](intent_slots)
File "/var/task/wsgi.py", line 1257, in alexa_watch_random_movie
movies_array = kodi.GetUnwatchedMovies()
File "/var/task/kodi.py", line 804, in GetUnwatchedMovies
for d in data['result']['movies']:
KeyError: 'result'

(2016-12-13, 17:49)jouster Wrote: Yes I've pulled that right from the file.

I'll reinstate the skill section now and also remove that strangely unwanted section too.

(2016-12-13, 17:49)jouster Wrote: Access wise I'm a little confused still as I can access the remote screen via a machine from outside the house and on any machine from within.

(2016-12-13, 17:53)jingai Wrote:

(2016-12-13, 17:49)jouster Wrote: Yes I've pulled that right from the file.

I'll reinstate the skill section now and also remove that strangely unwanted section too.

Heed the text in this section please:

Code:

You do not need to change the options that already have values.

You shouldn't be touching LAMBDA_ENV_VARS at all.

(2016-12-13, 17:49)jouster Wrote: Access wise I'm a little confused still as I can access the remote screen via a machine from outside the house and on any machine from within.

You being able to access it and the skill being able to access it are two entirely different things. You've got something wrong in your .env file. The error I pointed out above would prevent it from talking to Kodi, for instance.