Alexa integration does not find devices?

Configuration
1

I have set up the Amazon Alexa Smart Home skill according to the guide and faced no issues. I was able to create the Alexa Skill, AWS Lambda function, set up service endpoint and linked accounts.

When testing the Lambda function, it outputs everything that I want to (only scripts): https://pastebin.com/AccEn6Am

However, after setting all that up I should be able to find those scripts from the Alexa app’s discovery function. However, Alexa does not find any new devices (or scenes, lights or switches). I have tried both the Android app and the web-based app.

Does anybody have suggestions on what I could do to find the devices? The paid cloud is not an option for me.

1 Like
2

what server did you use?

3

I got it working by migrating to U.S. servers. I’m based in EU, so I thought that I was supposed to use the EU server.

4

Yeah, for some reason the most robust server is NA Virginia

5

Thanks, worked for me in 2021 as well. I am based in EU, Stockholm, but that didn’t work.
Instead:

  • Set devices to US address
  • Select English
  • Chose Virginia AWS region for lambda function.
  • During skill creation choose https://pitangui.amazon.com/

After that devices were successfully discovered.

1 Like
6

Changing the region worked for me.

7

I’m using the manual way to connect to Alexa, ie not Nabu Casa (and Google Home too). Alexa used to pick up new devices or scripts but this year it just refuses to discover anything new. Google Home app still does discover new stuff.
Any ideas? Pulling my hair out!

9

I had the same issue, had to go to the alexa mobile app, go to my skills and under the DEV section, disable the skill and enable (login again). After that, it all works. Hope this helps someone else.

10

Same issue here, but I found a different solution. Turns out my settings in Settings → Voice Assistants wasn’t set to expose new entities. And since that was turned off and I had the device enabled for a couple days, it wasn’t considered a new entity anymore so enabling that option didn’t help immediately. I had to go in and manually expose the entity. Hope that helps someone!

11

Sorry to revive an old thread - hoping your all still here but how (and what) do you change the region? I an in Australia, can get discovery happening in Lambda test, the only way to link my alexa account was to choose japan as the redirect URL yet my AWS console shows N. Virginia

12

Apologies as well for reviving this. I’m having the same issue. Account links correctly, but no devices are being discovered.
I’m in (the lost land of) New Zealand, and Alexa Dev console wouldn’t recognise the ARN with the default AWS server (Sydney), so I switched it to Oregon.
I’m unsure about all the other places where I need to change regions as well

I currently have:

  • AWS: Oregon (us-west2)
  • Alexa Developer Console: ARN from above (us-west2 url). Language set as English US (originally English AU, but I changed it)

User [Ilja_Leiko] said “Set devices to US address” and “Select English”, but not sure which devices he means.
Do I need to change anything else in my Amazon account, Alexa App or AWS account?

In the Alexa App there are several places where I can change locations. Do I need to change anything there?

  • Settings->Your locations->Add locations (my NZ address)
  • Settings->Device setting->Echo Dot (and also ‘Alexa on this phone’)->Settings->Device location (my NZ address)

I tried changing device location for Echo dot and disabling and reenabling the skill, but it didn’t work either.

Thanks for anything that can help or point in the right direction.