(2017-03-25, 18:52)deboyd Wrote: @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!

(2017-03-27, 00:42)digiltd Wrote: How are you both deploying?

(2017-03-27, 00:42)digiltd Wrote: 10 minutes to upload is a little slow, and that might be causing this time issue. To see if it is can you try opening up the requirements file and removing all the text in it (making sure you have kept a backup somewhere). Then try the deploy. This will not give you a working skill, the stuff in the requirements needs to be there for the skill to work. But it will lighten the upload package to see if that is the cause of the problem. If it is then we can see if there is an alternative way to deploy for you.

(2017-03-20, 13:29)Malachor Wrote: Hi All,

I'm following the guide here https://www.howtogeek.com/249336/how-to-control-your-kodi-media-center-with-an-amazon-echo/ but have hit a roadblock. I'm up to the bit where I have to publish the code to AWS but, after running lambda-deploy.exe deploy (from within the kodi-alexa-master folder in an elevated command prompt) I get the following error:

C:\Python27\Scripts\lambda-deploy.exe deploy
2017-03-20 11:18:15:INFO:botocore.vendored.requests.packages.urllib3.connectionpool: Starting new HTTP connection (1): 169.254.169.254
Traceback (most recent call last):
File "c:\python27\lib\runpy.py", line 174, in _run_module_as_main
"__main__", fname, loader, pkg_name)
File "c:\python27\lib\runpy.py", line 72, in _run_code
exec code in run_globals
File "C:\Python27\Scripts\lambda-deploy.exe\__main__.py", line 9, in <module>
File "c:\python27\lib\site-packages\lambda_deploy\lambda_deploy.py", line 360, in main
name=options.name
File "c:\python27\lib\site-packages\lambda_deploy\lambda_deploy.py", line 75, in __init__
self.client = boto3.client('lambda')
File "c:\python27\lib\site-packages\boto3\__init__.py", line 83, in client
return _get_default_session().client(*args, **kwargs)
File "c:\python27\lib\site-packages\boto3\session.py", line 263, in client
aws_session_token=aws_session_token, config=config)
File "c:\python27\lib\site-packages\botocore\session.py", line 836, in create_client
client_config=config, api_version=api_version)
File "c:\python27\lib\site-packages\botocore\client.py", line 70, in create_client
verify, credentials, scoped_config, client_config, endpoint_bridge)
File "c:\python27\lib\site-packages\botocore\client.py", line 224, in _get_client_args
verify, credentials, scoped_config, client_config, endpoint_bridge)
File "c:\python27\lib\site-packages\botocore\args.py", line 45, in get_client_args
endpoint_url, is_secure, scoped_config)
File "c:\python27\lib\site-packages\botocore\args.py", line 103, in compute_client_args
service_name, region_name, endpoint_url, is_secure)
File "c:\python27\lib\site-packages\botocore\client.py", line 297, in resolve
service_name, region_name)
File "c:\python27\lib\site-packages\botocore\regions.py", line 122, in construct_endpoint
partition, service_name, region_name)
File "c:\python27\lib\site-packages\botocore\regions.py", line 135, in _endpoint_for_partition
raise NoRegionError()
botocore.exceptions.NoRegionError: You must specify a region.

What am I missing here?

I can confirm my AWS default location is us-east-1 (North Virginia). I've set up all my environment variables/users/roles etc.

One thing I cannot find clarity on (because the instructions are not clear/detailed enough) is the use of the env.lambda file. Do I leave it with this naming convention, or rename it to lambda.env? I cannot rename it to just .env because windows won't let me; but nowhere does it tell you which is which and how to do it properly.

If anyone could please clarify what I have to do next it would be very much appreciated.

Regards

Mal.

(2017-03-27, 00:42)digiltd Wrote: How are you both deploying?

10 minutes to upload is a little slow, and that might be causing this time issue. To see if it is can you try opening up the requirements file and removing all the text in it (making sure you have kept a backup somewhere). Then try the deploy. This will not give you a working skill, the stuff in the requirements needs to be there for the skill to work. But it will lighten the upload package to see if that is the cause of the problem. If it is then we can see if there is an alternative way to deploy for you.

(2017-03-27, 08:48)wellsecond Wrote:

(2017-03-27, 00:42)digiltd Wrote: How are you both deploying?

10 minutes to upload is a little slow, and that might be causing this time issue. To see if it is can you try opening up the requirements file and removing all the text in it (making sure you have kept a backup somewhere). Then try the deploy. This will not give you a working skill, the stuff in the requirements needs to be there for the skill to work. But it will lighten the upload package to see if that is the cause of the problem. If it is then we can see if there is an alternative way to deploy for you.

Hey! It seems a problem with pycountry. If I remove pycountry from requirements.txt the deployment is made in about 30 seconds.

(2017-03-27, 10:05)kiwistream Wrote:

(2017-03-27, 08:48)wellsecond Wrote:

(2017-03-27, 00:42)digiltd Wrote: How are you both deploying?

10 minutes to upload is a little slow, and that might be causing this time issue. To see if it is can you try opening up the requirements file and removing all the text in it (making sure you have kept a backup somewhere). Then try the deploy. This will not give you a working skill, the stuff in the requirements needs to be there for the skill to work. But it will lighten the upload package to see if that is the cause of the problem. If it is then we can see if there is an alternative way to deploy for you.

Hey! It seems a problem with pycountry. If I remove pycountry from requirements.txt the deployment is made in about 30 seconds.

But does it work

(2017-03-27, 20:09)mcl22 Wrote: pvr-function: I found a pull request on git. But before I try it myself (as said, I'm really new to this) I'd like to know if one can expect an implementation soon?

(2017-03-27, 20:09)mcl22 Wrote: music-genre: This is really important to me. I found a request somewhere in this thread. But it seems that it wasn't ever implemented. I'd love to say something like "Alexa, ask kodi to play some rock". How about that?

(2017-03-27, 20:09)mcl22 Wrote: language-specific:
Well, I'm from Germany. So I'd really love Alexa to speak german "Umlaute" (äöü). I found a post from popy who stated he had done some changes concerning "Umlaute". But I just don't know where to start. It sounds silly when alexa sais "playing die Arzte" instead of "die Ärzte"

(2017-03-27, 20:09)mcl22 Wrote: Next thing, and I don't know if it's really language specific, but currently it's the most annoying for me: alexa doesn't get the right matches for music artists with "special" names.
For example, there's a band called STS. Alexa understands "S.T.S." and can't find the right artist. In the tags and of course in the kodi db it's "STS".
Second example: 2Pac - also in Germany you say it in english. But alexa either matches some other artist or doesn't respond to it anyway. Same thing for a german band with an english name "H-Blockx".
ASP and SOil are other examples and, pretty funny, the german punk band WIZO. It's spoken like "wieso" and the alexa app states that it understood "w.i.z.o.". That's really wired because I would understand it if she understood "wieso". But she did it right with the "z" and without the "e" but she added the dots between the letters (just like for STS). Does this have to do with the fuzzy matching?

(2017-03-27, 20:09)mcl22 Wrote: One thing I have to add: if I just ask alexa, not kodi, to play 2pac or sts (on prime music) she instantly recognizes the right artist and starts playing.

(2017-03-27, 20:09)mcl22 Wrote: Custom slots:
I used your generator to populate the custom slots and except in some cases, like mentioned above, it works pretty well. But what I've learned is that if I just use like 500 movie titles (like mentioned somewhere here) alexa does not really match that often if I ask for a movie not mentioned in the slot.
I used "Terminator" as an example. As long as the movie was in the list, she found it. When I excluded this movie she found "Anatomie" (a film that was still in the list).

(2017-03-27, 20:09)mcl22 Wrote: Last thing I wonder is how long should it take alexa for the action? I read about a guy somewhere here who stated that it took about 15 - 20 seconds. That's my experience, too. But I think I also read something about only a few seconds. So, just wondering what's normal and what one can do to improve the reaction time.

(2017-03-27, 18:45)jingai Wrote: pycountry's been replaced with a lighter alternative which should solve this problem for you guys.