0 votes
in ESP8266 WiFi Color Kit by (130 points)
Hi,

originally I had compilation problems with the most recent ESP driver and most recent libraries but these were solved when moving ' #include <ESP8266mDNS.h> ' up in the list of libraries to load. However, now the next problem appears: it takes about 5-10 min for the Wemos D1 Mini Pro 16 Mb to connect to the wifi. Then, when it then finally connects, there seems to be a problem to call the redirect website ( http://esp8266.local ) on my computer, although it is stated that the HTTP server started. I get a "cannot connect to server message" back.

What are possible reasons? When I run the Wifi scanner, it looks like the Wemos D1 Mini Pro has problems to find my network and so perhaps it doesn't react fast enough as server? Or can my firewall stand in the way? Your help to problem solve is much appreciated. I get following output on the console:

"

WiFi connected
IP address:
192.168.0.220
mDNS responder started
Loading config
Failed to open config file
No refresh token found. Requesting through browser
Open browser at http://esp8266.local
WiFi connected!
HTTP server started
"
by (13.9k points)
Re: WiFi connection
Lots of different potential causes. Try a different access point, move the device closer to the original AP, run the WiFi scanner application. See e.g. https://stackoverflow.com/questions/44139082/esp8266-takes-long-time-to-connect for details.

Re: failed mDNS resolution
I could reproduce this behavior. The Arduino-core folks changed their mDNS lib since when we published our original code. I already fixed this in my development environment. However, there's something else amiss with the Spotify API interaction. I'll push an update as soon as that is fixed as well.
ago by (13.9k points)
I fixed the mDNS issue some two weeks ago. However, we're still struggling with the memory consumption of the SSL connection to Spotify with the current Arduino core. Both the display/graphics buffer and the SSL stack need rather large chunks of heap memory. I haven't found a way yet to juggle the scarce heap in a way that satisfies both.

If you are interesting in following along or helping out I keep my changes public in a separate branch (`fix/bssl-memory`): https://github.com/ThingPulse/esp8266-spotify-remote/tree/fix/bssl-memory

Please log in or register to answer this question.

Welcome to ThingPulse Q&A, where you can ask questions and receive answers from other members of the community.

https://thingpulse.com

...