Aircoookie/Espalexa

Device is not discovered

Opened this issue · 6 comments

I used the example sketch "EspalexaColor" and added "#define ESPALEXA_DEBUG" before "#include <Espalexa.h>" to see debug output.
It seems that espalexa didn't recognize the discovery of my echo because while my echo is searching for devices espalexa didn't output anything...

I used the WeMos D1 R2 with esp8266 toolchain v3.0.2 and Espalexa v2.7.0.
My board settings: http://epvpimg.com/RAudfab

Try this:
#194

Thanks for your replay but unfortunately, this did not bring any improvement.
I dont't think that this is any kind of crash because in serial monitor i can't see anything which points on that.
Espalexa is not writing any debug output while my echo is discovering new devices...

I'm getting this output in Debug mode using an ESP32

Constructing device 1
Adding device 1
Constructing device 2
Adding device 2
Adding device 3
Espalexa Begin...
MAXDEVICES 10
Done
[MAIN] Free heap: 72256 bytes
Got UDP!
M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
ST: ssdp:all
MAN: "ssdp:discover"
MX: 3

Responding search req...
Got UDP!
M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
ST: upnp:rootdevice
MAN: "ssdp:discover"
MX: 3

Responding search req...
Got UDP!
M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
ST: ssdp:all
MAN: "ssdp:discover"
MX: 3

Responding search req...
Got UDP!
M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
ST: upnp:rootdevice
MAN: "ssdp:discover"
MX: 3

Responding search req...
Got UDP!
M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
ST: ssdp:all
MAN: "ssdp:discover"
MX: 3

Responding search req...
Got UDP!
M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
ST: upnp:rootdevice
MAN: "ssdp:discover"
MX: 3

Responding search req...

Responding to description.xml ...

Send setup.xml

10http://192.168.0.15:80/urn:schemas-upnp-org:device:Basic:1Espalexa (192.168.0.15:80)Royal Philips Electronicshttp://www.philips.comPhilips hue Personal Wireless LightingPhilips hue bridge 2012929000226503http://www.meethue.com94b97ec4a784uuid:2f402f80-da50-11e1-9b23-94b97ec4a784index.html

Not-Found HTTP call:
URI: /api
Body: {"devicetype": "Echo"}
AlexaApiCall
ok
devType
Not-Found HTTP call:
URI: /api/2WLEDHardQrI3WHYTHoMcXHgEspsM8ZZRpSKtBQr/lights
Body:
AlexaApiCall
ok
l0
lAll
Not-Found HTTP call:
URI: /api
Body: {"devicetype": "Echo"}
AlexaApiCall
ok
devType
Not-Found HTTP call:
URI: /api/2WLEDHardQrI3WHYTHoMcXHgEspsM8ZZRpSKtBQr/lights
Body:
AlexaApiCall
ok
l0
lAll
Not-Found HTTP call:
URI: /api/2WLEDHardQrI3WHYTHoMcXHgEspsM8ZZRpSKtBQr/lights/1649656320
Body:
AlexaApiCall
ok
l1649656320
1649656320
Not-Found HTTP call:
URI: /api/2WLEDHardQrI3WHYTHoMcXHgEspsM8ZZRpSKtBQr/lights/1649656321
Body:
AlexaApiCall
ok
l1649656321
1649656321
Not-Found HTTP call:
URI: /api/2WLEDHardQrI3WHYTHoMcXHgEspsM8ZZRpSKtBQr/lights/1649656322
Body:
AlexaApiCall
ok
l1649656322
1649656322
[MAIN] Free heap: 69524 bytes
Not-Found HTTP call:
URI: /api/2WLEDHardQrI3WHYTHoMcXHgEspsM8ZZRpSKtBQr/lights/1649656320
Body:
AlexaApiCall
ok
l1649656320
1649656320
Not-Found HTTP call:
URI: /api/2WLEDHardQrI3WHYTHoMcXHgEspsM8ZZRpSKtBQr/lights/1649656321
Body:
AlexaApiCall
ok
l1649656321
1649656321
Not-Found HTTP call:
URI: /api/2WLEDHardQrI3WHYTHoMcXHgEspsM8ZZRpSKtBQr/lights/1649656322
Body:
AlexaApiCall
ok
l1649656322
1649656322
[MAIN] Free heap: 68884 bytes
[MAIN] Free heap: 68884 bytes
[MAIN] Free heap: 68884 bytes

Alexa isnt finding anything

I am also facing same issue.
did you find the fix?

Same issue for me. I am using ESPALEXA_ASYNC and library version 2.7.0

UPDATE: I found the device following the instructions from
#41 (comment)