Failure to communicate (what we have here...)
Posted: Fri May 25, 2018 9:36 am
I've been running in to a problem setting up an ESP8266 as a web server. It seems that after a ?period of time? or ?X number of http requests? the chip hangs / becomes non-responsive. I've sort of created a work around by "count++" for every http and "if (count > number) ESP.restart". Which is a bit heavy handed.
Google says I'm not alone, refs to memory leak etc. There is the command "server.begin" and I was hopping to find "server.stop/restart/quit/" - no luck. So I'm wondering if there is any other way to communicate with a 8266. SSH? Telnet? Ftp? Just not http.
Another question: code: respond to a http request and some kind of "flush" after it?
Thanks
Google says I'm not alone, refs to memory leak etc. There is the command "server.begin" and I was hopping to find "server.stop/restart/quit/" - no luck. So I'm wondering if there is any other way to communicate with a 8266. SSH? Telnet? Ftp? Just not http.
Another question: code: respond to a http request and some kind of "flush" after it?
Thanks