Espalexa
Espalexa copied to clipboard
Aircoookie
Alexa cannot discover
Still Discovery issues, been working with this for a total of about 20 hours and still cannot get any devices to be discovered. Below is debug data, I can see the M-SEARCH coming in but ESPAlexa never sends anything back. Why does it see the M-SEARCH messages and ignore them, of course thats assuming when the DEBUG is turned that I would aslo see something going out back to the Alexa after the M-Search. Below is what I see in the serial monitor.
20:06:19.645 -> Connecting to WiFi 20:06:19.645 -> Connecting.......... 20:06:23.119 -> Connected to ZORRO-24 20:06:23.119 -> IP address: 192.168.0.29 20:06:23.224 -> Constructing device 1 20:06:23.224 -> Adding device 1 20:06:23.224 -> Espalexa Begin... 20:06:23.224 -> MAXDEVICES 10 20:06:23.224 -> Done 20:06:36.604 -> HTTP Req espalexa ... 20:06:36.604 -> 20:06:48.153 -> Got UDP! 20:06:48.153 -> M-SEARCH * HTTP/1.1 20:06:48.153 -> HOST: 239.255.255.250:1900 20:06:48.153 -> MAN: "ssdp:discover" 20:06:48.188 -> MX: 2 20:06:48.188 -> ST: urn:schemas-upnp-org:device:MediaRenderer:1 20:06:48.188 -> 20:06:48.188 -> 20:06:49.514 -> Got UDP! 20:06:49.514 -> M-SEARCH * HTTP/1.1 20:06:49.514 -> HOST: 239.255.255.250:1900 20:06:49.514 -> MAN: "ssdp:discover" 20:06:49.514 -> MX: 2 20:06:49.514 -> ST: urn:schemas-upnp-org:device:MediaServer:1 20:06:49.514 -> 20:06:49.514 ->
Power off and on your echo device. I have found these several times and this works.
On Mon, Apr 29, 2019, 09:09 nickm324 [email protected] wrote:
Still Discovery issues, been working with this for a total of about 20 hours and still cannot get any devices to be discovered. Below is debug data, I can see the M-SEARCH coming in but ESPAlexa never sends anything back. Why does it see the M-SEARCH messages and ignore them, of course thats assuming when the DEBUG is turned that I would aslo see something going out back to the Alexa after the M-Search. Below is what I see in the serial monitor.
20:06:19.645 -> Connecting to WiFi 20:06:19.645 -> Connecting.......... 20:06:23.119 -> Connected to ZORRO-24 20:06:23.119 -> IP address: 192.168.0.29 20:06:23.224 -> Constructing device 1 20:06:23.224 -> Adding device 1 20:06:23.224 -> Espalexa Begin... 20:06:23.224 -> MAXDEVICES 10 20:06:23.224 -> Done 20:06:36.604 -> HTTP Req espalexa ... 20:06:36.604 -> 20:06:48.153 -> Got UDP! 20:06:48.153 -> M-SEARCH * HTTP/1.1 20:06:48.153 -> HOST: 239.255.255.250:1900 20:06:48.153 -> MAN: "ssdp:discover" 20:06:48.188 -> MX: 2 20:06:48.188 -> ST: urn:schemas-upnp-org:device:MediaRenderer:1 20:06:48.188 -> 20:06:48.188 -> 20:06:49.514 -> Got UDP! 20:06:49.514 -> M-SEARCH * HTTP/1.1 20:06:49.514 -> HOST: 239.255.255.250:1900 20:06:49.514 -> MAN: "ssdp:discover" 20:06:49.514 -> MX: 2 20:06:49.514 -> ST: urn:schemas-upnp-org:device:MediaServer:1 20:06:49.514 -> 20:06:49.514 ->
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Aircoookie/Espalexa/issues/64, or mute the thread https://github.com/notifications/unsubscribe-auth/AD4UFC4JWSUOMQAW2GTV33DPSZDGJANCNFSM4HI7ZEVQ .
Have done that with my Echo and it made no difference. Although I have 1 Echo and 3 dots does that mean I need to Power them all off or just the Echo?
Power reset the one you use to discovery.
I do not know if all echo will search or not. If so, you may try all.
On Mon, Apr 29, 2019, 20:33 nickm324 [email protected] wrote:
Power off and on your echo device. I have found these several times and this works. … <#m_-8835594054427220059_> On Mon, Apr 29, 2019, 09:09 nickm324 @.***> wrote: Still Discovery issues, been working with this for a total of about 20 hours and still cannot get any devices to be discovered. Below is debug data, I can see the M-SEARCH coming in but ESPAlexa never sends anything back. Why does it see the M-SEARCH messages and ignore them, of course thats assuming when the DEBUG is turned that I would aslo see something going out back to the Alexa after the M-Search. Below is what I see in the serial monitor. 20:06:19.645 -> Connecting to WiFi 20:06:19.645 -> Connecting.......... 20:06:23.119 -> Connected to ZORRO-24 20:06:23.119 -> IP address: 192.168.0.29 20:06:23.224 -> Constructing device 1 20:06:23.224 -> Adding device 1 20:06:23.224 -> Espalexa Begin... 20:06:23.224 -> MAXDEVICES 10 20:06:23.224 -> Done 20:06:36.604 -> HTTP Req espalexa ... 20:06:36.604 -> 20:06:48.153 -> Got UDP! 20:06:48.153 -> M-SEARCH * HTTP/1.1 20:06:48.153 -> HOST: 239.255.255.250:1900 20:06:48.153 -> MAN: "ssdp:discover" 20:06:48.188 -> MX: 2 20:06:48.188 -> ST: urn:schemas-upnp-org:device:MediaRenderer:1 20:06:48.188 -> 20:06:48.188 -> 20:06:49.514 -> Got UDP! 20:06:49.514 -> M-SEARCH * HTTP/1.1 20:06:49.514 -> HOST: 239.255.255.250:1900 20:06:49.514 -> MAN: "ssdp:discover" 20:06:49.514 -> MX: 2 20:06:49.514 -> ST: urn:schemas-upnp-org:device:MediaServer:1 20:06:49.514 -> 20:06:49.514 -> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#64 https://github.com/Aircoookie/Espalexa/issues/64>, or mute the thread https://github.com/notifications/unsubscribe-auth/AD4UFC4JWSUOMQAW2GTV33DPSZDGJANCNFSM4HI7ZEVQ .
Have done that with my Echo and it made no difference. Although I have 1 Echo and 3 dots does that mean I need to Power them all off or just the Echo?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Aircoookie/Espalexa/issues/64#issuecomment-487561294, or mute the thread https://github.com/notifications/unsubscribe-auth/AD4UFCZW2PBZVZG2YN2IDFLPS3TJDANCNFSM4HI7ZEVQ .
that still doesnt explain why when running Debug on the ESP its is receiving the M-Search requests but the ESP is ignoring them and not sending anything back.
Actually maybe neither of those devices in the log I provided above are an Alexa and just something else on my network.
Which ESP are you using, ESP-8266 or ESP-32? I can have a test to see if it is blocked again.
@Aircoookie It is true that using NodeMCU (ESP-8266) is very hard to get discovered with later version. I get 3 success out of out of 10 discoveries. I need to retry and retry in order to get discovered once.
And for ESP-32, I did find similar things. It works but sometimes it won't get discovered.
PS: ESPALEXA_DEBUG message is still "Espalexa 2.4.2 debug mode". And there are other warnings in library. Please fit them too. Thanks!
@Aircoookie Do you find similar discovery issue? The discovery success rate for the current version is very low.
I did a factory reset on my router and am able to discover devices now. Not sure what that had to do with it but it seems to have made a difference.
It may not be caused by the router. From my tests with the same router, I need to try many times in order to get one success.
You can try discovery, then removed those light devices, and do discovery again. Repeat this test and see the success rate.
Last time I find it almost 100% success. And now around 20% with current version.
@eos1d3 that rate sounds bad. I'll let you know once I had time to run a few discovery tests.
I am having the same issue, except in the debug, GOT UDP! shows up in lists of 10 or more
