[SOLVED] Alexa Skills won't take my Lambda Function as an EndPoint

Configuration
1

Hello,

I want to integrate Home Assistant in my Alexa account with this following instructions.

I must admit it’s not that hard to follow, but I’m stuck at this stage where the management consol say :

Failed to save skill information
The requested content has an invalid property ‘skillmanifest’.

I’m located in France so I firstly created my lambda function in Ireland, but then I tried in N.Virginia but not with a better success.

A bit of searching point me to this → I need to insert the Alexa Skill Kit in place of the Alexa Smart Home in order to work. Same results.

I also tried haaska as per their instruction on the wiki of the repository, same issue.

Is their something broken or do the fault come from me or my account ?

Thanks !

2

Theissue was on Amazon side as they told me on the Amazon dev forum.

It’s all good now and working like a charm.

3

Same issue for me. Hopefully they can fix mine too. Awaiting moderation… Amazon Sign-In

  • String instance with value “arn:aws:lambda:us-east-2::function:myHomeAssistantFunction” at property path “$.manifest.apis.smartHome.regions.NA.endpoint.uri” does not match the regular expression: “arn:aws:lambda:us-east-1:[0-9]{12}:function:[a-zA-Z0-9-]+(/[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12})?(:[a-zA-Z0-9-]+)?”.
  • The Lambda ARN arn:aws:lambda:us-east-2::function:myHomeAssistantFunction is not valid for any of the supported regions.
4

OHHH I missed one critical step in the instructions.

IMPORTANT - Alexa Skills are only supported in certain AWS regions Your current server location will be displayed on the top right corner (for example, Ohio), make sure you select the server closest to your location / region based on your Amazon account’s country, whilst also ensuring that it is within one of the supported regions for Alexa Skills otherwise this will not work!

  • US East (N.Virginia) region for English (US) or English (CA) skills

The US East (N. Virginia) is == “arn:aws:lambda:us-east-1[…]”
The US East (Ohio) which it defaulted for me was == “arn:aws:lambda:us-east-2[…]”

So I deleted the function and trigger from Ohio and created it in N. Virginia, and everything is working now!