2016-11-14, 17:44
@jonjon (and anyone else that wants to), could you test this branch for the environment variables defaults issue (None appearing in URL)?
(2016-11-14, 17:44)jingai Wrote: @jonjon (and anyone else that wants to), could you test this branch for the environment variables defaults issue (None appearing in URL)?
(2016-11-14, 19:00)jacobh Wrote: I can confirm this works.
You might want to add a comment in about the AWS Lambda python interpreters strange behavior.
(2016-11-14, 16:50)jingai Wrote: @Dominique, is the endpoint actually accessible?
# The Kodi webserver only supports HTTP.
#
# You can change KODI_SCHEME to https to tell the skill to use https (from AWS to your local network)
# It is assumed that you know what https is and that you have already set this up with your own certificates
# KODI_SCHEME = https
KODI_ADDRESS = supersecret.evenmoresecret.com
KODI_PORT = 34242
KODI_USERNAME = supersecretusername
KODI_PASSWORD = supersecretandsuperlongpassword
# If using a reverse proxy you might need to add an extra bit to the url before "jsonrpc"
#
# KODI_SCHEME://KODI_ADDRESS:KODI_PORT/KODI_SUBPATH/jsonrpc
#
# Set this with KODI_SUBPATH (no slashes)
# KODI_SUBPATH = supersecretsubpath
SKILL_APPID = amzn1.ask.skill.123123123123123212123312312321
LAMBDA_ENV_VARS = KODI_SCHEME,KODI_ADDRESS,KODI_PORT,KODI_SUBPATH,KODI_USERNAME,KODI_PASSWORD,SKILL_APPID
AWS_DEFAULT_REGION = eu-west-1
LAMBDA_TIMEOUT = 60
LAMBDA_MEMORY_SIZE = 128
LAMBDA_HANDLER = wsgi.lambda_handler
AWS_ACCESS_KEY_ID = ABDHSDGDHSKDHSALHFDSHFDJSHFJDLKS
AWS_SECRET_ACCESS_KEY = ASDASDASDASDASDASDASDASDASDASDASD
LAMBDA_ROLE = arn:aws:iam::123123123123:role/lambda_kodi_basic_execution
Sending request to http://supersecret.evenmoresecret.com:34242/jsonrpc
(2016-11-15, 02:37)Dominique Wrote:(2016-11-14, 16:50)jingai Wrote: @Dominique, is the endpoint actually accessible?
Thanks for your response. How exactly would I check that?
(2016-11-16, 03:40)Dominique Wrote:(2016-11-15, 15:06)jingai Wrote: Hit it with a web browser -- you should get HTTP 500 (No Content) in response. The page will be empty, but if you get the right response, it's at least accessible.
Yes it was a HTTP 500 error. So what now?
(2016-11-16, 03:45)jingai Wrote: I'm really sorry.. I meant 502. 500 is Internal Server Error.
If 500 is actually what you got, then something is wrong with the server that isn't related to the skill.
(2016-11-15, 20:35)jingai Wrote: My turn to ask a question
I've found that after some period of time, Alexa will start intercepting the basic commands (e.g., play, pause, stop, skip, etc) herself rather than passing them to the skill.
If I change the invocation of the skill, this will usually fix it for a short time, but eventually she will start intercepting them again.
I am suspecting this may have something to do with the reason Amazon requires a two-word invocation for skills. I've been keeping mine to one word (alternating between cody and kodi). Or maybe something to do with the new(ish) audio player interface they have..
Has anyone managed to get this working 100% reliably?