search

Aircoookie / Espalexa

Alexa voice control for ESP8266/ESP32 (including brightness and color!)
MIT License
545 stars 137 forks source link

wemos d1 mini is not discovered #120

Open djoe78 opened 4 years ago

djoe78 commented 4 years ago

Hi, for a year i have been using many wemos d1 mini without problems with this library for home automation lights and i have never had problems. For a few weeks, however, I have been having trouble controlling wemos via the echo dot gen.3 or from the app (device is not responding). I have eliminated the devices I can no longer find them, unless I restart the router but still have control problems. Before these problems when I was going to the ip of a wemos it showed me correct the devices I had defined. Now show me the following message: "Not Found (espalexa-internal)". I use the esp8266 core version 2.4.2 and i not use the async server mode. I try a new wemos d1 mini with last update of this library and async server mode, but I still can't discover it, so i enable debug mode:

15:50:27.649 -> IP address: 192.168.178.51 15:50:27.751 -> Constructing device 1 15:50:27.751 -> Adding device 1 15:50:27.751 -> Espalexa Begin... 15:50:27.751 -> MAXDEVICES 10 15:50:27.751 -> Done 15:50:31.159 -> Got UDP! 15:50:31.159 -> M-SEARCH HTTP/1.1 15:50:31.159 -> HOST: 239.255.255.250:1900 15:50:31.159 -> MAN: "ssdp:discover" 15:50:31.159 -> MX: 5 15:50:31.159 -> ST: urn:schemas-upnp-org:device:avm-aha:1 15:50:31.194 -> 15:50:31.194 -> 15:50:36.143 -> Got UDP! 15:50:36.143 -> M-SEARCH HTTP/1.1 15:50:36.143 -> HOST: 239.255.255.250:1900 15:50:36.177 -> MAN: "ssdp:discover" 15:50:36.177 -> MX: 5 15:50:36.177 -> ST: urn:schemas-upnp-org:device:avm-aha:1 15:50:36.177 -> 15:50:36.177 -> 15:50:41.232 -> Got UDP! 15:50:41.232 -> M-SEARCH HTTP/1.1 15:50:41.232 -> HOST: 239.255.255.250:1900 15:50:41.232 -> MAN: "ssdp:discover" 15:50:41.232 -> MX: 5 15:50:41.232 -> ST: urn:schemas-upnp-org:device:avm-aha:1 15:50:41.232 -> 15:50:41.232 -> 15:50:46.232 -> Got UDP! 15:50:46.232 -> M-SEARCH HTTP/1.1 15:50:46.232 -> HOST: 239.255.255.250:1900 15:50:46.232 -> MAN: "ssdp:discover" 15:50:46.232 -> MX: 5 15:50:46.232 -> ST: urn:schemas-upnp-org:device:avm-aha:1 15:50:46.232 -> 15:50:46.232 -> 15:50:51.241 -> Got UDP! 15:50:51.241 -> M-SEARCH * HTTP/1.1 15:50:51.241 -> HOST: 239.255.255.250:1900 15:50:51.241 -> MAN: "ssdp:discover" 15:50:51.241 -> MX: 5 15:50:51.241 -> ST: urn:schemas-upnp-org:device:avm-aha:1 15:50:51.274 -> 15:50:51.274 -> 15:50:57.934 -> Got UDP! 15:50:57.934 -> Got UDP! 15:50:57.934 -> Got UDP! 15:50:57.934 -> Got UDP! 15:50:59.871 -> Got UDP! 15:50:59.905 -> Got UDP! 15:50:59.905 -> Got UDP!

There is a solution? thank you very much. Sorry for my english

jlgoasis commented 4 years ago

I have same problem, from few days ago it doesn't work

AST-esp-rasp commented 4 years ago

Have the same issue. 14:18:29.366 -> Got UDP! 14:18:29.366 -> M-SEARCH HTTP/1.1 14:18:29.366 -> HOST: 239.255.255.250:1900 14:18:29.366 -> MAN: "ssdp:discover" 14:18:29.366 -> MX: 1 14:18:29.366 -> ST: urn:dial-multiscreen-org:service:dial:1 14:18:29.401 -> USER-AGENT: Google Chrome/83.0.4103.106 Windows 14:18:29.401 -> 14:18:29.401 -> 14:18:30.609 -> Got UDP! 14:18:30.609 -> M-SEARCH HTTP/1.1 14:18:30.609 -> HOST: 239.255.255.250:1900 14:18:30.609 -> MAN: "ssdp:discover" 14:18:30.609 -> MX: 1 14:18:30.609 -> ST: urn:dial-multiscreen-org:service:dial:1 14:18:30.609 -> USER-AGENT: Google Chrome/83.0.4103.106 Windows 14:18:30.609 -> 14:18:30.609 ->

Device with newly compiled code is not discovered the old devices compiled in January still work.