skill does not discover devices but lambda does / InsecureRequestWarning

[svente08]

Hi all,

I have two questions.

1st question:

Running HA with https I get this warning in lambda log:

... InsecureRequestWarning ....

Is that something that I can ignore?

2nd question:

I'm able to discover devices running the lambda test on AWS

{ "header": { "payloadVersion": "1", "namespace": "Control", "name": "DiscoverAppliancesRequest" }, "payload": { "accessToken": "whatever" } }

a part of lambda output:

{ "header": { "payloadVersion": "2", "namespace": "Alexa.ConnectedHome.Discovery", "name": "DiscoverAppliancesResponse", "messageId": "65b50bde-b357-4404-a75f-6e3bf1f1ef71" }, "payload": { "discoveredAppliances": [ { "modelName": "Unknown", "actions": [ "turnOn", "turnOff" ], "friendlyDescription": "Home Assistant Switch", "version": "Unknown", "additionalApplianceDetails": { "entity_id": "switch.eg_esszimmer_steckdose_links", "supported_features": 0 }, "manufacturerName": "Unknown", "friendlyName": "Steckdose links", "applianceId": "8e74c8c39cd4632aa17a4bc67bb4de2efe68dccf", "isReachable": true }, { "modelName": "Unknown", "actions": [ "turnOn", "turnOff" ], "friendlyDescription": "Home Assistant Switch", "version": "Unknown", "additionalApplianceDetails": { "entity_id": "switch.1e_kl_gaeste_decke", "supported_features": 0 },

Output haaska test:

{ "header": { "payloadVersion": "2", "namespace": "Alexa.ConnectedHome.System", "name": "HealthCheckResponse", "messageId": "4f076a1c-88fc-49f3-8828-b368223eddc6" }, "payload": { "isHealthy": true } } true

Skill is enabled in Alexa but Alexa does not discover these/any devices.

Can anyone give me a hint debugging this? I have this issue with both configs (HA on http or https)

Thanks Sven

[redstar2k1]

RE 2nd question, what country/region is your Amazon Developer account set (https://developer.amazon.com/settings/profile/detail.html) and on what region (North America/Europe) is your Lambda function set? If your developer country is any other then UK or Germany, your Lambda function needs to be setup on North America (US East Ohio).

[svente08]

You're great... I'm located in Germany my Lambda was running in Virginia now I moved to Ireland and it works.

MANY THANKS.

[blackfyre]

Well... I've got a similar problem... Everything has been set up in or moved to the eu-west-1 region and the dev account region is set to the UK. Lambda responds correctly to the deploy, test, discover commands, but Alexa still can't find any of the smart home devices. Oauth seems to work as I can add and enable the created haaska skill without obvious errors.

[cooperaj]

I'm in the same boat as you @blackfyre. No devices but everything works otherwaise :/

[absk1s3]

I just posted this on another thread! Im having the same problem as @blackfyre and @cooperaj

I have set my AWS datacenter to eu-west-1 (Ireland) and made sure my endpoint in developer.amazon.com points to the eu-west-1 and it still not working. I wonder if its a problem in the account linking with the information from login.amazon.com.

Im based in the UK, maybe it's UK specific problem?

[DrJukka]

just run into this same issue with same behaviour as as @blackfyre and @cooperaj. Using Ireland. Earlier did succeed with custom skills (colour picker example). Anybody figure what could solve the issue ?

[absk1s3]

Hello @DrJukka

I managed to get it working! I started again from scratch, in the skill setup I made sure english uk was selected as the language and the payload version as 2.

I think everything has to be exact to your region.

[jastorino]

I have the same issue where my lambda works when I test it from the aws lambda screen but the skill does not trigger the lambda to discover any devices.

I have my region set to US every where and I use the North Virginia region in the lambda.

Did everyone get this working? Is there anything else I can try to debug and troubleshoot?

Thanks

[benmprojects]

Did anyone get this to work?