[jingai]

I broke something else in the process of fixing that.. give me a few hours and it'll be fixed. Just don't have a chance to work on it until after my kids go to bed.

[deboyd]

@digiltd

I am back again with (slightly) more skill. I have progressed through all my issues and now, have landed upon this "time" issue like many other people on this thread. If it is true that my PC time is out of sync with the destination clock, then changing my PC time to equal the destination clock should fix the problem.

My PC clock is currently in Central Time and the destination clock is US-West-2. I changed my PC clock to be Pacific Time and re-ran the command to upload .env to AWS. It took the same 10 minutes and had the exact same error. Am I using the right time zone for US-West-2? Any other thoughts?

Here is my specific error read out:


botocore.exceptions.ClientError: An error occurred (InvalidSignatureException) when calling the CreateFunction operation: Signature expired: 20170325T155703Z is now earlier than 20170325T160002Z (20170325T160502Z - 5 min.)

Thank you in advance!

I have this issue as well. Synced my time and tried to deploy on Mac and Linux machines with no progress.

Please, if you make some progress let us know and I will do the same.

I'm not sure if this is relevant, but the last file location accessed during the upload to Lambda is File "c:\python27\lib\site-packages\botocore\client.py", line 543, in _make_api_call
raise error_class(parsed_response, operation_name)

If I open this file, there is a paragraph which directly talks about time.

"This class handles taking out the relevant arguments from the endpoint
resolver and determining which values to use, taking into account any
client configuration options and scope configuration options.

This class also handles determining what, if any, region to use if no
explicit region setting is provided. For example, Amazon S3 client will
utilize "us-east-1" by default if no region can be resolved.s"

Just throwing it out there incase it helps us come closer to a solution.

Thanks!
Dan

[wellsecond]

@digiltd

I am back again with (slightly) more skill. I have progressed through all my issues and now, have landed upon this "time" issue like many other people on this thread. If it is true that my PC time is out of sync with the destination clock, then changing my PC time to equal the destination clock should fix the problem.

My PC clock is currently in Central Time and the destination clock is US-West-2. I changed my PC clock to be Pacific Time and re-ran the command to upload .env to AWS. It took the same 10 minutes and had the exact same error. Am I using the right time zone for US-West-2? Any other thoughts?

Here is my specific error read out:


botocore.exceptions.ClientError: An error occurred (InvalidSignatureException) when calling the CreateFunction operation: Signature expired: 20170325T155703Z is now earlier than 20170325T160002Z (20170325T160502Z - 5 min.)

Thank you in advance!

I have this issue as well. Synced my time and tried to deploy on Mac and Linux machines with no progress.

Please, if you make some progress let us know and I will do the same.

I'm not sure if this is relevant, but the last file location accessed during the upload to Lambda is File "c:\python27\lib\site-packages\botocore\client.py", line 543, in _make_api_call
raise error_class(parsed_response, operation_name)

If I open this file, there is a paragraph which directly talks about time.

"This class handles taking out the relevant arguments from the endpoint
resolver and determining which values to use, taking into account any
client configuration options and scope configuration options.

This class also handles determining what, if any, region to use if no
explicit region setting is provided. For example, Amazon S3 client will
utilize "us-east-1" by default if no region can be resolved.s"

Just throwing it out there incase it helps us come closer to a solution.

Thanks!
Dan

The issue was not time related. It was a problem with the large size of a package named pycountry. It was replaced by a lighter alternative and deployment is already working for me.

It should be working for you as well. Give a try.

[deboyd]

[/quote]

The issue was not time related. It was a problem with the large size of a package named pycountry. It was replaced for a lighter alternative and deployment is already working for me.

It should also be working for you as well. Give a try.
[/quote]

Where can I find this lighter alternative? Cheers!
Dan

[deboyd]

The issue was not time related. It was a problem with the large size of a package named pycountry. It was replaced for a lighter alternative and deployment is already working for me.

It should also be working for you as well. Give a try.
[/quote]

Where can I find this lighter alternative? Cheers!
Dan
[/quote]

Never mind mate! Used my common sense and re-ran the deploy. It works! Thank you!

[jingai]

The pycountry alternative is fixed on the master and flask-ask branches now. Hopefully.

[wellsecond]

I broke something else in the process of fixing that.. give me a few hours and it'll be fixed. Just don't have a chance to work on it until after my kids go to bed.

It's fully working for me now. Thank you!

[jingai]

We could use a German translator for the responses if anyone is willing.

[kiwistream]

Finally have it working, big thank you to the devs for putting together the guide & apps.

Does anyone have any tips for getting Alexa to play any episode from any season, I can only get Alexa to play the latest episode of TV shows. Movies for example I found if you say "Alexa ask Kodi to play MOVIE" then movie name works really well.

Thanks

[jingai]

@kiwistream, "Alexa, ask Kodi to play season X episode Y of <show>"

[wellsecond]

@kiwistream, "Alexa, ask Kodi to play season X episode Y of <show>"

And how to execute an specific Addon?

EDIT: Oh, I am sorry, I just realized that alexa.utterances has a list of commands.

[sveni_lee]

@jingai,
thanks for your work on this project.

yesterday I started to chang the wsgi.py for German languages but know I see I would be better to do this within the templates.de.yaml.

I start also to include all changes from the freemans13 fork for PVR. But if you say that version 2.5 will come soon and will include this I could spend my time with translation.

[mcl22]

Thank You for the fast answer.

I'm really looking forward for the pvr function. But concerning your answer for my sts, 2pac, etc. problem I wonder what is going to happen with the pvr feature. The coolest thing would be to ask kodi just for the channel name. But most channels (in Germany) do have names that, i guess, would cause the same problems. Examples: RTL, Sat1, Pro7, ARD, ZDF, n-tv, n24, ...
It's not possible to do some kind of linking, is it? I mean a possibility to tell the skill something like "if you get a s.t.s. then try sts" or "R.T.L. is RTL" or "Sat eins ist Sat1".

For the music genre I'm gonna follow your advise and use playlists for the moment.

I'have already tried version 2.5 and the problem with the Umlaute is still there. If I ask kodi to play "Die Ärzte" the response is "Spiele die Arzte", also in 2.5. Better and really funny example is: "play music from Abstürzende Brieftauben" - response "spiele Absturz Ende Brieftauben"

Concerning the custom slots: I don't have a problem with including everything on the first run. But if alexa only gets the right match if the asked movie, artist whatever is part of the list, I'm gonna run into problems every time I add a new movie or artist.
Not that that happens every day. But updating the slots every time I add something new wouldn't be that comfortable.

Last question: is there some kind of tutorial for running the skill on my own webserver? I do already run a webserver on a raspberry. So the ressource is there.

[sveni_lee]

@mcl

could you tell me were did you load version 2.5.
I would like to test it and may be see what I can do on the German translation...

[mcl22]

well, i hope i got it right that this is version 2.5:
https://github.com/m0ngr31/kodi-alexa/tree/flask-ask