[GH-ISSUE #1410] Can I use it with ESPAsyncWebServer? #1207

Open
opened 2026-02-28 01:29:02 +03:00 by kerem · 15 comments
Owner

Originally created by @baloyou on GitHub (May 4, 2022).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/1410

i like this library, simple and stable.

but i need to used it with ESPAsyncWebServer.

how to do it?

Originally created by @baloyou on GitHub (May 4, 2022). Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/1410 i like this library, simple and stable. but i need to used it with ESPAsyncWebServer. how to do it?
Author
Owner

@MaralS commented on GitHub (May 7, 2022):

Hello,

I had to give up because of the conflicts between with the two library.
I'm still working on it to find a solution to use both but it's frustrating.

<!-- gh-comment-id:1120142117 --> @MaralS commented on GitHub (May 7, 2022): Hello, I had to give up because of the conflicts between with the two library. I'm still working on it to find a solution to use both but it's frustrating.
Author
Owner

@tablatronix commented on GitHub (May 7, 2022):

There is an async branch that is being worked on atm, eventually I hope to combine it into main lib but the functionality is totally different

<!-- gh-comment-id:1120233062 --> @tablatronix commented on GitHub (May 7, 2022): There is an async branch that is being worked on atm, eventually I hope to combine it into main lib but the functionality is totally different
Author
Owner

@Darkest commented on GitHub (May 7, 2022):

What do you mean by saying "totally different functionality"?

<!-- gh-comment-id:1120276087 --> @Darkest commented on GitHub (May 7, 2022): What do you mean by saying "totally different functionality"?
Author
Owner

@tablatronix commented on GitHub (May 8, 2022):

its async, so all callback methods need access to the server res obj.
also there seems to be some ota differences that need to be handled differently

<!-- gh-comment-id:1120340237 --> @tablatronix commented on GitHub (May 8, 2022): its async, so all callback methods need access to the server res obj. also there seems to be some ota differences that need to be handled differently
Author
Owner

@MaralS commented on GitHub (May 13, 2022):

its async, so all callback methods need access to the server res obj. also there seems to be some ota differences that need to be handled differently

It's good to know !

<!-- gh-comment-id:1125950199 --> @MaralS commented on GitHub (May 13, 2022): > its async, so all callback methods need access to the server res obj. also there seems to be some ota differences that need to be handled differently It's good to know !
Author
Owner

@tablatronix commented on GitHub (May 13, 2022):

I will work on this in a week or so, async branch might be behind master, i am gonna redo it from scratch in a bit as I am restructuring stuff to see if we can just change all wm methods to use a arg templates for hooking into different servers

<!-- gh-comment-id:1126131559 --> @tablatronix commented on GitHub (May 13, 2022): I will work on this in a week or so, async branch might be behind master, i am gonna redo it from scratch in a bit as I am restructuring stuff to see if we can just change all wm methods to use a arg templates for hooking into different servers
Author
Owner

@mdjavedakhtar commented on GitHub (Jul 19, 2022):

have you found any solution.
i am also tryig to do the same but no luck

<!-- gh-comment-id:1188704087 --> @mdjavedakhtar commented on GitHub (Jul 19, 2022): have you found any solution. i am also tryig to do the same but no luck
Author
Owner

@baloyou commented on GitHub (Jul 24, 2022):

have you found any solution.
i am also tryig to do the same but no luck

i don't have a solution either

<!-- gh-comment-id:1193231125 --> @baloyou commented on GitHub (Jul 24, 2022): > have you found any solution. > i am also tryig to do the same but no luck i don't have a solution either
Author
Owner

@Pratched commented on GitHub (Mar 15, 2023):

Hello, I tried this branch mentioned here with my ESP8266 as I am in need of an AsyncWebServer...

Originally I started of with the master branch of WifiManager and adding the credentials worked quite well.
However later on (after I saved and didnt delete the credentials) I switched to the Async capable branch, which was working alright so long. That is to say, until I did reset the WiFi credentials and suddenly could no longer enter the credentials.
When I switched back to using the master branch, everything works very well again. See below for more detail...is there anything I could do, to use WiFi-Manager WITH Async as of now with its essential capabilities?

When using the Async-Branch without saved credentials, you would connect to the AP and hit "Update Wifi". But If you do so the following serial output is printed:

...
*wm:[1] AP IP address: 192.168.4.1
*wm:[1] Starting Web Portal 
*wm:[2] HTTP server started 
*wm:[2] Config Portal Running, blocking, waiting for clients... 
*wm:[2] <- HTTP Root 
*wm:[2] <- Request redirected to captive portal 
*wm:[2] <- HTTP Root 
*wm:[2] <- HTTP Root 
*wm:[2] <- Request redirected to captive portal 
*wm:[2] <- HTTP Root 
*wm:[2] <- Request redirected to captive portal 
*wm:[2] <- HTTP Wifi 
*wm:[2] WiFi Scan SYNC started 

--------------- CUT HERE FOR EXCEPTION DECODER ---------------

Soft WDT reset

>>>stack>>>

ctx: sys
sp: 3fffeae0 end: 3fffffb0 offset: 01a0
3fffec80:  00000000 3ffef5c0 3ffef258 3ffeffe0  
...

which is ended by restarting the ESP (and print out in serial monitor like this:

...
3fffffa0:  00000000 3f007472 00000000 3ffef73c  
<<<stack<<<

--------------- CUT HERE FOR EXCEPTION DECODER ---------------

 ets Jan  8 2013,rst cause:2, boot mode:(3,6)

load 0x4010f000, len 3424, room 16 
tail 0
chksum 0x2e
load 0x3fff20b8, len 40, room 8 
tail 0
chksum 0x2b
csum 0x2b
v0005b520
~ld

*wm:[1] AutoConnect 
*wm:[1] No Credentials are Saved, skipping connect 
*wm:[2] Starting Config Portal 
...

EDIT: I am using the LoLin v3 version.

PS: For a temporary solution I am using this AsyncWifiManager, as I find It way easier to get started as e.g. this one.

<!-- gh-comment-id:1470014296 --> @Pratched commented on GitHub (Mar 15, 2023): Hello, I tried this branch mentioned here with my ESP8266 as I am in need of an AsyncWebServer... Originally I started of with the master branch of WifiManager and adding the credentials worked quite well. However later on (after I saved and didnt delete the credentials) I switched to the Async capable branch, which was working alright so long. That is to say, until I did reset the WiFi credentials and suddenly could no longer enter the credentials. When I switched back to using the master branch, everything works very well again. See below for more detail...is there anything I could do, to use WiFi-Manager WITH Async as of now with its essential capabilities? When using the Async-Branch without saved credentials, you would connect to the AP and hit "Update Wifi". But If you do so the following serial output is printed: ``` ... *wm:[1] AP IP address: 192.168.4.1 *wm:[1] Starting Web Portal *wm:[2] HTTP server started *wm:[2] Config Portal Running, blocking, waiting for clients... *wm:[2] <- HTTP Root *wm:[2] <- Request redirected to captive portal *wm:[2] <- HTTP Root *wm:[2] <- HTTP Root *wm:[2] <- Request redirected to captive portal *wm:[2] <- HTTP Root *wm:[2] <- Request redirected to captive portal *wm:[2] <- HTTP Wifi *wm:[2] WiFi Scan SYNC started --------------- CUT HERE FOR EXCEPTION DECODER --------------- Soft WDT reset >>>stack>>> ctx: sys sp: 3fffeae0 end: 3fffffb0 offset: 01a0 3fffec80: 00000000 3ffef5c0 3ffef258 3ffeffe0 ... ``` which is ended by restarting the ESP (and print out in serial monitor like this: ``` ... 3fffffa0: 00000000 3f007472 00000000 3ffef73c <<<stack<<< --------------- CUT HERE FOR EXCEPTION DECODER --------------- ets Jan 8 2013,rst cause:2, boot mode:(3,6) load 0x4010f000, len 3424, room 16 tail 0 chksum 0x2e load 0x3fff20b8, len 40, room 8 tail 0 chksum 0x2b csum 0x2b v0005b520 ~ld *wm:[1] AutoConnect *wm:[1] No Credentials are Saved, skipping connect *wm:[2] Starting Config Portal ... ``` EDIT: I am using the LoLin v3 version. PS: For a temporary solution I am using [this](https://github.com/alanswx/ESPAsyncWiFiManager) AsyncWifiManager, as I find It way easier to get started as e.g. [this one](https://github.com/khoih-prog/ESPAsync_WiFiManager).
Author
Owner

@tablatronix commented on GitHub (Mar 15, 2023):

I will take a look, I need to update that branch anyway

<!-- gh-comment-id:1470940838 --> @tablatronix commented on GitHub (Mar 15, 2023): I will take a look, I need to update that branch anyway
Author
Owner

@Pratched commented on GitHub (Mar 15, 2023):

FYI: on other occasions I had similar issues with code snippets that would block the ESP for too much time; like delay(5000) even...

<!-- gh-comment-id:1470946859 --> @Pratched commented on GitHub (Mar 15, 2023): FYI: on other occasions I had similar issues with code snippets that would block the ESP for too much time; like `delay(5000)` even...
Author
Owner

@Giermann commented on GitHub (Dec 10, 2024):

Is there any progress?
It seems most of the repositories are not being updated, at least they have not been updated during the last 2 years.
I am simply looking for a small implementation of non-blocking WiFiManager, OTA and a common Web interface, no matter if connected to an existing WiFi or acting as an AP - while the ESP itself is doing other, more important tasks without the need of a network connection.
And I was told, that ESPAsyncWebServer should be preferred over the blocking WebServer.

Do I have to implement everything on my own or is there a library available that I did not find yet?

<!-- gh-comment-id:2532415097 --> @Giermann commented on GitHub (Dec 10, 2024): Is there any progress? It seems most of the repositories are not being updated, at least they have not been updated during the last 2 years. I am simply looking for a small implementation of non-blocking WiFiManager, OTA and a common Web interface, no matter if connected to an existing WiFi or acting as an AP - while the ESP itself is doing other, more important tasks without the need of a network connection. And I was told, that ESPAsyncWebServer should be preferred over the blocking WebServer. Do I have to implement everything on my own or is there a library available that I did not find yet?
Author
Owner

@StefanoTesla commented on GitHub (Jun 25, 2025):

Is there any progress? It seems most of the repositories are not being updated, at least they have not been updated during the last 2 years. I am simply looking for a small implementation of non-blocking WiFiManager, OTA and a common Web interface, no matter if connected to an existing WiFi or acting as an AP - while the ESP itself is doing other, more important tasks without the need of a network connection. And I was told, that ESPAsyncWebServer should be preferred over the blocking WebServer.

Do I have to implement everything on my own or is there a library available that I did not find yet?

Did you found a solution??

<!-- gh-comment-id:3004358759 --> @StefanoTesla commented on GitHub (Jun 25, 2025): > Is there any progress? It seems most of the repositories are not being updated, at least they have not been updated during the last 2 years. I am simply looking for a small implementation of non-blocking WiFiManager, OTA and a common Web interface, no matter if connected to an existing WiFi or acting as an AP - while the ESP itself is doing other, more important tasks without the need of a network connection. And I was told, that ESPAsyncWebServer should be preferred over the blocking WebServer. > > Do I have to implement everything on my own or is there a library available that I did not find yet? Did you found a solution??
Author
Owner

@Giermann commented on GitHub (Jun 25, 2025):

No, not yet.

<!-- gh-comment-id:3004399089 --> @Giermann commented on GitHub (Jun 25, 2025): No, not yet.
Author
Owner

@tablatronix commented on GitHub (Jun 26, 2025):

There is a branch

<!-- gh-comment-id:3006950584 --> @tablatronix commented on GitHub (Jun 26, 2025): There is a branch
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/WiFiManager#1207
No description provided.