-
Notifications
You must be signed in to change notification settings - Fork 97
Is it possible to use AsyncWebServer.h instead of WebServer.h? #29
Comments
Hi @cancodr Thanks for using the library. I'll definitely have a look at the possibility of supporting or make a new ESPAsync_WiFiManager lib to support ESPAsyncWebServer. Currently, as the ESP_WiFiManager usage is short, and necessary only when Config Portal is required, I suggest you can try the following workaround (I personally haven't tried and seen the real issues and if it's working)
Please post the results or arising issues to save us time, preferably with code we can verify / duplicate. Regards, |
Hi @cancodr Already successful to port this ESP_WiFiManager to use ESPAsyncWebServer instead of ESP8266WebServer/WebServer. Will publish the new library as ESPAsync_WiFiManager within several days. Regards, |
That's great! Thank you! |
Release v1.0.11 is ready Your enhancement request leading to this completely new library is noted in contributions-and-thanks ;-) Why do we need this Async ESPAsync_WiFiManager library
Releases 1.0.11
|
I personally wouldn't suggest using the Asyncwebserver library for a project. It runs incredibly unstable and contains a few bugs that often cause the ESP-32 to crash. The WiFi Manager library is very useful, but there are quicker ways to enable a dynamic change between station and access point mode. I personally use LitteFS to access the file storage of my ESP-32, create a json document that I call config, and have a web portal where you can insert the username and password an send it via Post to the ESP. To avoid useless crashes with the Asyncwebserver library, I'd suggest using the Mongoose webserver instead. |
I'm developing an ESP32 project which uses AsyncWebServer.h (https://github.com/me-no-dev/ESPAsyncWebServer). I realize that this library uses WebServer.h, however the two libraries seem to conflict with each other. Moreover, I think it will be more efficient to just use one.
Any hints on how to port this for use with AsyncWebServer, or at least how to get around the conflict issue in the short term?
The text was updated successfully, but these errors were encountered: