Possible fixes when no devices are found in Alexa App

[sybren-marechal]

I see a lot of people troubleshooting on "no devices found".

For myself, this is the same problem. I was able to connect and configure everything. (all of my devices were discovered in the logfile). But when using the APP, Alexa can't find any.

What could be the possible mistakes I made? I have checked everything double, and multiple issues with the same problem. But sadly, wasn't able to figure out the problem.

[jd2121]

I am having the same issue. I had deleted all devices in my Alexa account to start fresh and now nothing is discovered. I have even started with a fresh install of Home Assistant and set up haaska fresh as well and nothing is discovered anymore. The connection succeeds and shows devices, but they arent discovered in the Alexa app or website. I also unlinked and relinked the haaska skill in the app... but no change.

I am wondering if there is something in the back end of Alexa that remembers deleted devices, so it won't let them be discovered again.

[Karshilistic]

I am facing the same issue. New installation, test works okay, but discovery does not find any devices. I don't even know where to begin debugging.

I have another older installation that I will check for differences.

[Karshilistic]

Same as #166

[jd2121]

I am facing the same issue. New installation, test works okay, but discovery does not find any devices. I don't even know where to begin debugging.

I have another older installation that I will check for differences.

I added include and exclude filters into my configuration.yaml file and it started working for me. My guess is that there is something that Alexa doesn't like and it rejects everything as a result.

`#Enable Haaska for Alexa Communication api:

alexa: smart_home: filter: include_domains: - light - switch - fan - lock - cover include_entity_globs: - sensor._door_sensor - binary_sensor.door - binary_sensor.motion* - binary_sensor.window_* exclude_entity_globs: - media_player.* - switch._yard - remote. exclude_entities: - switch.everywhere_do_not_disturb_switch - switch.bedroom_do_not_disturb_switch - switch.monthly_dynamic_schedule - switch.sprinklers_rain_delay - switch.sprinklers_in_standby_mode `

[Karshilistic]

Well, I tried adding filters, as well as defining the endpoint, Client ID and Client secret (from the permissions tab in the skill), and it still didn't work. Since the Lambda function test comes back with the correct response, I am led to believe that there is something wrong in the connection between the Alexa Skill and the Lambda function. I will attempt to re-setup the skill (or the whole process if need be) and edit my post with results. If @mike-grant, or anyone else who had this issue can weigh in about this with other solutions that would be wonderful.

Edit 1:

I added a Lambda function in EU(Ireland) in case it's a region issue, and linked it to the same skill. I will redo the whole process next. This is very weird, but using the Test function in the Alexa Developer Console, inputting "discover devices" in the text input on the left pane, Alexa actually responds that it actually discovered my devices. However, from inside the app on my phone as a user, it still can't discover any devices.

Edit 2:

I am not sure if it was the EU(Ireland) addition or something else, but it is now working. Apparently I also had an outdated version of the app and it wasn't working correctly. I suggest to anyone trying this to

1. Check that your app is fully updated
2. Test the skill from the test tab in Alexa Developer Console
3. Add different regions, update their endpoints in the Alexa skill
4. In configuration.yaml, add filters and define the endpoint, Client ID and Client secret (from the permissions tab in the skill).

I am still not sure what exactly made it work. I will monitor the invocations on the lambda function to identify which region it's using.

[hagak]

I appear to have starting having this same issue recently. I have had this skill working with my HA config for over a year now and just recently it will no longer discover new devices. Note it has not issues controlling devices it already knows about it just can not find new devices. As above my Lamdba function test works and sees my new switchs in the result so the Lamdba to Home Assistant connection appears to be working. It is the Alexa Skill to Lamdba that I think is broken.

[hagak]

Well after 2 days of not detecting my new devices even when i manually request it to look for them it finally detected them on its own.

[ybizeul]

Anybody has a solution for this ? It doesn't seem the function is ever called. Like everyone, Test is working fine, but no devices are found.

Now I noticed this method is significantly different from the one "officially" documented on HA web site, but right now I can't run HA on 443, which is a requirement.

I'm no expert in Alexa skills, but in CloudWatch, I don't see any run for this function when registering the app.

[ybizeul]

I ended up moving to "official" documentation as describe on HA docs (so, not using hasska) and had the same problem.

So I moved everything to us-east and it fixed everything. I don't undernstand why, because my main language is French and I'm supposed to use Ireland. I didn't try again with hasska, but I'm assuming it would have been a fix as well.

It would be great to understand exactly what the factors actually are for a region pickup.

[ybizeul]

End of storry : it looks like there are many loops and holes involved just to change the region of an Amazon account, and changing the address itself isn't quite sufficient. For those interested, you also have to follow the link that says "Ok now you can use the xxx store, click me", then click and from here you should see an old fashion Amazon button that says "migrate my account to xxx store"

[planestoner]

After 24hrs of tomfoolery I have sorted my install. I am in the UK so naturally followed the instructions but using Europe (Ireland)eu-west-1 server. My test passed but no devices were found in Alexa Discovery. I deleted everything and started again with everything configured for US East (N. Virginia)us-east-1 - same result. I then created a seperate Lambda function for (Ireland)eu-west-1 and pointed the skill to that - same result.

I then added 'locale: en-GB' to my configuration.yaml and all devices were discovered.

I'm guessing that locale default: en-US kicked in and conflicted with the locale of my Alexa device. There is probably a way to check the locale and cross-check for conflict by my tiny brain isn't up to the task.

Fingers crossed it all doesn't fall apart tomorrow and I have to retract this.

[andybrodie]

I then added 'locale: en-GB' to my configuration.yaml and all devices were discovered.

I'm guessing that locale default: en-US kicked in and conflicted with the locale of my Alexa device. There is probably a way to check the locale and cross-check for conflict by my tiny brain isn't up to the task.

I'm set up the same way and have the same problem. UK-based with (presumably) an Echo in UK English and my lambda is in Ireland. I can successfully test the lambda and see all my devices in the response, and I can successfully link the skill to my account. I can also see that when I ask Alexa to scan for devices that the lambda is being invoked through Cloudwatch metrics, but still, no devices found

I modified my configuration.yaml, so that the section relating to this looks like this:

alexa:
  locale: en-GB
  smart_home:

Can someone confirm, please, is the addition of the locale in the right place?

EDIT - I got it wrong the configuration wrong, it SHOULD be like this:

alexa:
  smart_home:
    locale: en-GB

I.e. the locale goes under smart_home:. Once I moved it and restarted HA, everything worked!

[crazyvpa]

Can´t find the devices or the scripts in Alexa but test works can someone point-me what to check i have no clue? Thanks in advance.

[jd2121]

Can´t find the devices or the scripts in Alexa but test works can someone point-me what to check i have no clue? Thanks in advance.

I've had the same issue in the past where it would test fine, but no devices show up. I tinkered with the include and exclude filters in the home assistant configuration.yaml file. That fixed the issue one time. Another time I had to start from scratch to get it working... and yet another time I simply had to wait a day or two and the devices magically appeared... May have been an Amazon server delay (I had deleted the devices by mistake and just had to wait a bit for them to show back up).

[crazyvpa]

After, 4 from the scratch instalations and changing in beteween all the configs pointed here, i still don´t see the devices... what a noob i am...

[frankfrommelt]

Well, I know this will not help you in first place, but it worked for me following the instructions. The only tiny "mistake" I made was not excluding any domains from being exported to Alexa. So, I had a little bit of cleanup-work to do. Lesson learned: In the web interface of Alexa it is a lot faster to delete many devices. But at least this proved it worked. So, maybe not excluding any domains (and exporting everything to Alexa) might prove it works. To do so you just have to remove all off the exclusions from configuration.yaml, restart HA and have Alexa search for new devices. If devices show up now you know it was the configuration.yaml. If there are still no devices in Alexa you know that it is something else... ;-)

[crazyvpa]

i tried with filters and without...

The log in lambda but in alexa no device is found...

[crazyvpa]

i tried with filters and without...

The log in lambda but in alexa no device is found...