Alexa can't discover devices

gabriel-lando commented 3 years ago

I was using the latest version (v3.2) for a while (since February 8th, 2021) and it has been working very well so far (also, the devices continue to work with Alexa).

Today, I decided to add a new light and Alexa couldn't detect this device.

I tried using my custom code and it didn't work (it did last month). So, I tried with the example fauxmoESP_basic from the library and I had the same result: Alexa cound't find any new device.

So, I tried with the version 2.4.4 (an implementation of the Wemo Switch that I already used on the past) and it worked using the basic example: Alexa could find a "switch one" smart switch device.

So, I tried with the version 3.1.1 (from de same repository, latest before the migration for GitHub) and I had the same issue.

Apparently, Alexa can't discover devices using the Philips Hue implementation.

Also, I tried using the latest commit on master and the result was the same :(

My Echo devices:

1x Echo Dot 2nd Gen
1x Echo Dot 3rd Gen

I tried with both Echo devices and they can't find this device.

Also, I tried removing one of my working devices from the Alexa app and tried to discover this device again and Alexa couldn't detect it.

My upload configuration: Board: Wemos D1 R1 Upload Speed: 921600 CPU Frequency: 80 MHz Flash Size: 4MB (FS:2MB OTA:~1019KB) Debug port: Disabled Debug Level: None lwIP Variant: v1.4 Higher Bandwidth VTables: Flash Exceptions: Legacy (new can return nullptr) Erase Flash: Only Sketch SSL Support: All SSL ciphers (most compatible)

OBS: Also, on the basic example, I tried to remove all devices and keep only the "yellow lamp" (as I saw in other issue #149 ) and the result was the same :/

Edit: ESP8266 Core version: 2.7.4

cleiton2193 commented 3 years ago

Ou os arquivos editaso pelo B1 gmans

rezendeneto commented 3 years ago

@cleiton2193 yes, I'm using the latest version of the library. I'm actually quite new with Alexa - should that work by using the Amazon Alexa app for android only? I mean, I don't actually have any Amazon Echo or Dot device.

cleiton2193 commented 3 years ago

Ah tá. Não funciona. Vc precisa de ter algum dispositivo Alexa. O dispositivo da Alexa que encontra os dispositivo adicionados pela biblioteca ,depois disso vc pode usar o app da Amazon para dar comando TB. Mais precisa de ter algum dispositivo sim.

pvint commented 3 years ago

@cleiton2193 yes, I'm using the latest version of the library. I'm actually quite new with Alexa - should that work by using the Amazon Alexa app for android only? I mean, I don't actually have any Amazon Echo or Dot device.

It should work, yes. Make sure you are on the same 2.4GHz WiFi on the Android and the ESP.

cleiton2193 commented 3 years ago

Boa tarde Pvint. Funciona sem algum dispositivo da Amazon? Apenas com o aplicativo Amazon? Uso essa biblioteca a mais de 8 meses. E nunca consegui fazer funcionar sem algum dispositivo da Amazon conectado na rede.

pvint commented 3 years ago

I'm actually not 100% certain that it will work without a real Amazon device, but I thought I remembered others saying it worked for them. It's hard for me to test because I have a bunch of them!

rezendeneto commented 3 years ago

@pvint yes, both my phone and the ESP are on the same 2.4GHz WiFi. I've also enabled the verbosity for debugging, as I'm using a small Node.JS program that sends some SSDP requests and I can see a lot going on in the serial monitor. Still I can't have the Amazon Alexa app find the ESP on the network...

rezendeneto commented 3 years ago

I'm actually not 100% certain that it will work without a real Amazon device, but I thought I remembered others saying it worked for them. It's hard for me to test because I have a bunch of them!

Maybe it's time for me to get a real amazon device then... what would you recommend me?

cleiton2193 commented 3 years ago

Tanto o echo dot 3° e 4° geração eu testei E está funcionando muito bem.

rezendeneto commented 3 years ago

@cleiton2193 ok, obrigado

pvint commented 3 years ago

@rezendeneto I'd say whatever your budget tells you to get is fine. ;)

cleiton2193 commented 3 years ago

Boa tarde. Alguém sabe me dizer se essa biblioteca funciona com o Google home mini TB?

larryl79 commented 2 years ago

I've tried first time in mylife, fauxmo (latest lib on Arduino ide) and ESPalexa examples and none of them worked for me. I've got alexa app, echo dot gen2 & gen3, and echo show 5. Board: ESP32-dev V1 (dual core, 240mhz, wifi +BT BLE) all device on same 2.4Ghz wifi.

I've tried just handle the builtin_led.

all try ended up with "I couldn't find any new devices ..."

refused access to: http://192.168.25.56:1901/api/lights

I can access to the description.xml on both lib by browser. `

1 0 http://192.168.25.37:80/ urn:schemas-upnp-org:device:Basic:1 Philips hue (192.168.25.37:80) Royal Philips Electronics http://www.philips.com Philips hue Personal Wireless Lighting Philips hue bridge 2012 929000226503 http://www.meethue.com 94b97efb34f0 uuid:2f402f80-da50-11e1-9b23-94b97efb34f0 index.html

`

rezendeneto commented 2 years ago

I've tried first time in mylife, fauxmo (latest lib on Arduino ide) and ESPalexa examples and none of them worked for me. I've got alexa app, echo dot gen2 & gen3, and echo show 5. Board: ESP32-dev V1 (dual core, 240mhz, wifi +BT BLE) all device on same 2.4Ghz wifi.

I've tried just handle the builtin_led.

all try ended up with "I couldn't find any new devices ..."

refused access to: http://192.168.25.56:1901/api/lights

I can access to the description.xml on both lib by browser. <root xmlns="urn:schemas-upnp-org:device-1-0"> <specVersion> <major>1</major> <minor>0</minor> </specVersion> <URLBase>http://192.168.25.37:80/</URLBase> <device> <deviceType>urn:schemas-upnp-org:device:Basic:1</deviceType> <friendlyName>Philips hue (192.168.25.37:80)</friendlyName> <manufacturer>Royal Philips Electronics</manufacturer> <manufacturerURL>http://www.philips.com</manufacturerURL> <modelDescription>Philips hue Personal Wireless Lighting</modelDescription> <modelName>Philips hue bridge 2012</modelName> <modelNumber>929000226503</modelNumber> <modelURL>http://www.meethue.com</modelURL> <serialNumber>94b97efb34f0</serialNumber> <UDN>uuid:2f402f80-da50-11e1-9b23-94b97efb34f0</UDN> <presentationURL>index.html</presentationURL> </device> </root>

here it only works with gen4

larryl79 commented 2 years ago

I've tried first time in mylife, fauxmo (latest lib on Arduino ide) and ESPalexa examples and none of them worked for me. I've got alexa app, echo dot gen2 & gen3, and echo show 5. Board: ESP32-dev V1 (dual core, 240mhz, wifi +BT BLE) all device on same 2.4Ghz wifi. I've tried just handle the builtin_led. all try ended up with "I couldn't find any new devices ..." refused access to: http://192.168.25.56:1901/api/lights I can access to the description.xml on both lib by browser. <root xmlns="urn:schemas-upnp-org:device-1-0"> <specVersion> <major>1</major> <minor>0</minor> </specVersion> <URLBase>http://192.168.25.37:80/</URLBase> <device> <deviceType>urn:schemas-upnp-org:device:Basic:1</deviceType> <friendlyName>Philips hue (192.168.25.37:80)</friendlyName> <manufacturer>Royal Philips Electronics</manufacturer> <manufacturerURL>http://www.philips.com</manufacturerURL> <modelDescription>Philips hue Personal Wireless Lighting</modelDescription> <modelName>Philips hue bridge 2012</modelName> <modelNumber>929000226503</modelNumber> <modelURL>http://www.meethue.com</modelURL> <serialNumber>94b97efb34f0</serialNumber> <UDN>uuid:2f402f80-da50-11e1-9b23-94b97efb34f0</UDN> <presentationURL>index.html</presentationURL> </device> </root>

here it only works with gen4

then I don't know what I doing wrong... any ideas by the details or need more detail? if yes what are you need?

cleiton2193 commented 2 years ago

Bom dia Larry. Já tive esse problema que vc está enfrentando, e só resolvi trocando o roteador. Se tiver um outro roteador aí, faz um teste .

larryl79 commented 2 years ago

Bom dia Larry. Já tive esse problema que vc está enfrentando, e só resolvi trocando o roteador. Se tiver um outro roteador aí, faz um teste .

I'm on a 48 port Cisco gigabit router switch with cisco AP-s, all echos, phone, ESP in same VLAN. Anyway I'll find something soho router in the basement, and I'll give a go for it. Thanks for the idea, I'll get back with the results.

cleiton2193 commented 2 years ago

Os dispositivos Alexa, funciona em rede 5G, mais sabemos que as nossas placas, não funciona com redes 5G, então conecte a Alexa em rede 2.4G. Espero que de certo meu amigo.

cleiton2193 commented 2 years ago

Lembrando, só funciona na última versão da biblioteca, nas anteriores, não encontra mais dispositivos.

larryl79 commented 2 years ago

so far now:

I've created separate 2.4 wifi on the Cisco access point, with a separate VLAN.
connected echo gen2, and phone to the new 2.4 wifi.
unplugged rest of alexa devices
flashed ESP32 and ESP6266 with fauxmoESP_Basic
tried search both (32/8266) with phone, and with echo gen2 (phone wifi off)
latest Asyncwebserver and asynctcp downloaded from me-no-dev github (today) (lib dependencies of example ino)
fauxmoESP lib version: 3.4
using Arduino IDE

same result, no new device found.

I still will go into the basement search for a soho wifi router, and will try with that as well...

p.s. espalexa lib same results on this wifi with both dev (32/8266)

ddweber456 commented 2 years ago

I have found if I have many Alexa Dots, Echos, Shows all on the same network, I need to unplug most if not all but 1 Alexa Dot or Echo and do the discover devices. After the discovery, the devices can be plugged back in.

larryl79 commented 2 years ago

Sorry guys, looks like my cisco devices was misconfigured. I've tried a soho router, and immediately worked, so I went back to the cisco and it's configuration... now looks fine for discovering.

I'm not sure yet it's just the cisco config was bad or adding mDNS to the scketch needed as well in the setup()

if (!MDNS.begin("esp32")) { Serial.println("Error setting up MDNS responder!"); while(1) { delay(1000); } } Serial.println("mDNS responder started"); MDNS.addService("http", "tcp", 80);

Sorry again, I never thought this. Thanks

cleiton2193 commented 2 years ago

Que bom que conseguiu meu amigo. Igual eu tinha te falado. Já aconteceu comigo e eu resolvi trocando o roteador. Abraço.

fabiopdm commented 2 years ago

Fala @cleiton2193 !

Tudo bem!? Bom ver BR`s por aqui. Sobre a biblioteca, realmente só é possível localizar os dispositivos se você tiver algum hub como o Echo Dot? Não há possibilidades de encontrar os mesmo via App da Alexa por exemplo no iOS?

Estou com problemas para encontrar os mesmos via App e não tenho o hub por aqui. Estou até pensando em comprar um, mas não agora.

Se souber de algo, já ajuda.

Abraços a todos!

brenocbn commented 2 years ago

Olá. E sobre a Alexa só encontrar os dispositivos a partir de um Echo, foi confirmado? Estou tentando somente pelo aplicativo do android e ela não encontra de jeito nenhum.

cleiton2193 commented 2 years ago

Boa tarde. Sim, precisa de ter algum dispositivo físico da Alexa para comunicação.

Obter o Outlook para Androidhttps://aka.ms/AAb9ysg

From: brenocbn @.> Sent: Wednesday, February 16, 2022 2:35:39 PM To: vintlabs/fauxmoESP @.> Cc: cleiton2193 @.>; Mention @.> Subject: Re: [vintlabs/fauxmoESP] Alexa can't discover devices (#166)

Olá. E sobre a Alexa só encontrar os dispositivos a partir de um Echo, foi confirmado? Estou tentando somente pelo aplicativo do android e ela não encontra de jeito nenhum.

— Reply to this email directly, view it on GitHubhttps://github.com/vintlabs/fauxmoESP/issues/166#issuecomment-1041917079, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKKH3FW74PYRUGP7HR7NOX3U3PN6XANCNFSM4ZELWH4A. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you were mentioned.Message ID: @.***>

brenocbn commented 2 years ago

Eu tenho uma FireStick TV Lite, mas não consigo encontrar com ela também... Talvez ela não seja como os Echos

cleiton2193 commented 2 years ago

Realmente não serve.

Obter o Outlook para Androidhttps://aka.ms/AAb9ysg

From: brenocbn @.> Sent: Wednesday, February 16, 2022 2:57:46 PM To: vintlabs/fauxmoESP @.> Cc: cleiton2193 @.>; Mention @.> Subject: Re: [vintlabs/fauxmoESP] Alexa can't discover devices (#166)

Eu tenho uma FireStick TV Lite, mas não consigo encontrar com ela também... Talvez ela não seja como os Echos

— Reply to this email directly, view it on GitHubhttps://github.com/vintlabs/fauxmoESP/issues/166#issuecomment-1041939257, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKKH3FTBHHLIRKGZC3DB66LU3PQRVANCNFSM4ZELWH4A. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you were mentioned.Message ID: @.***>

DDTORRES055 commented 2 years ago

fauxmo 3.3 with basic example is working fine (5 new devices detected), newest espalexa-libary 2.7.0 is also working fine! (Wemos D1 mini, Echo plus V 2, 1.4 high bandwith,)

I search always new devices with the alexa app, scenes ->search for new scenes.

sometimes a further remove/deleted "old" device (with another unique-id) is not really deleted in the alexa database. You can't see it in the alexa-app, but on the website "https://alexa.amazon.xxx" (on smart-home page) , which must be removed there. If it has the name of the device you will find again, it will block the discovery

be sure you when you exchange the library-version and you compile the code, that .o and .d-files of the library and sketch are really build new(i had this problem a year ago, i think reason was that new fauxmoESP.cpp was older than fauxmoESP.cpp.o/.d, buildung new did not change the .o/.d files

This worked for me

Worked with NodeMCU V3 and V1 following the table:

Platform	Gen1	Gen2	Gen3
ESP8266 Core 2.3.X	OK	OK?	OK (1)
ESP8266 Core 2.4.0	OK (2)	OK? (2)	OK (1, 2)
ESP8266 Core 2.4.1	OK (2)	OK? (2)	OK (1, 2)
ESP8266 Core 2.4.2	OK (2)	OK? (2)	OK (1, 2)
ESP32	OK	OK?	OK (1)

(1) When using gen3 devices TCP port must be 80 always. (2) Arduino Core for ESP8266 requires LwIP set to "v1.4 Higher Bandwidth".

First, I tried for the NodeMCU V3 (Gen3), and set the TCP port to 80, this to my surprise (I had almost no hope left xd), it worked. Then I wanted to try with the NodeMCU V1 (Gen1), taking the table as a reference, I removed the line that specified the TCP port in 80 (fauxmo.setPort(80);), and it did not work (I tried several times), so just to experiment I put the fauxmo.setPort(80); back in the code, and still to more surprise, it worked.

vintlabs / fauxmoESP

Alexa can't discover devices #166