[GH-ISSUE #850] WiFiManager and painlessMesh together #717

New issue

Open

opened 2026-02-28 01:26:44 +03:00 by kerem · 20 comments

kerem commented 2026-02-28 01:26:44 +03:00

Owner

Copy link

Originally created by @kbssa on GitHub (Mar 15, 2019).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/850

Anyone here have tried to combine WiFiManager and painlessMesh or at least know that is it feasable to use both in the same code.

My application really needs the WiFiManager captive portal like, but I have no idea on how to implement it with the painlessMesh.

If anyone coulp point me to the right direction, I would appreciate a lot.

Originally created by @kbssa on GitHub (Mar 15, 2019). Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/850 Anyone here have tried to combine WiFiManager and painlessMesh or at least know that is it feasable to use both in the same code. My application really needs the WiFiManager captive portal like, but I have no idea on how to implement it with the painlessMesh. If anyone coulp point me to the right direction, I would appreciate a lot.

kerem added the

Documentation

Good First Issue

Example

labels 2026-02-28 01:26:44 +03:00

kerem commented 2026-02-28 01:26:44 +03:00

Author

Owner

Copy link

@pranjal-joshi commented on GitHub (May 30, 2020):

I also have similar requirements.
My logic is to attempt a direct connection with wifi station firstly. If wifi is unable to connect then switch to mesh mode.
It would be great to hear about updates about this from you!

<!-- gh-comment-id:636348196 --> @pranjal-joshi commented on GitHub (May 30, 2020): I also have similar requirements. My logic is to attempt a direct connection with wifi station firstly. If wifi is unable to connect then switch to mesh mode. It would be great to hear about updates about this from you!

kerem commented 2026-02-28 01:26:44 +03:00

Author

Owner

Copy link

@pranjal-joshi commented on GitHub (Jun 2, 2020):

@kbssa Have you succeeded in using both of them together? I found that WiFiManager is very buggy to use. So i used ESPAsyncWebServer lib to create my own web server and with the help of ArduinoJson, I am writing my config on the SPIFFS of ESP8266!
Hope this helps! :)

<!-- gh-comment-id:637665490 --> @pranjal-joshi commented on GitHub (Jun 2, 2020): @kbssa Have you succeeded in using both of them together? I found that WiFiManager is very buggy to use. So i used **ESPAsyncWebServer** lib to create my own web server and with the help of **ArduinoJson**, I am writing my config on the SPIFFS of ESP8266! Hope this helps! :)

kerem commented 2026-02-28 01:26:44 +03:00

Author

Owner

Copy link

@tablatronix commented on GitHub (Jun 2, 2020):

What is painless mesh ?

<!-- gh-comment-id:637682990 --> @tablatronix commented on GitHub (Jun 2, 2020): What is painless mesh ?

kerem commented 2026-02-28 01:26:44 +03:00

Author

Owner

Copy link

@pranjal-joshi commented on GitHub (Jun 2, 2020):

What is painless mesh ?

@tablatronix
painlessMesh is a library that creates a mesh network of ESPs so that they can communicate with each other without router.
Link to the painlessMesh library

<!-- gh-comment-id:637685918 --> @pranjal-joshi commented on GitHub (Jun 2, 2020): > What is painless mesh ? > > @tablatronix painlessMesh is a library that creates a mesh network of ESPs so that they can communicate with each other without router. [Link to the painlessMesh library](https://github.com/gmag11/painlessMesh)

kerem commented 2026-02-28 01:26:44 +03:00

Author

Owner

Copy link

@tablatronix commented on GitHub (Jun 2, 2020):

So why would you use this with wm if its not networking based?
Or even how would you ?

<!-- gh-comment-id:637723497 --> @tablatronix commented on GitHub (Jun 2, 2020): So why would you use this with wm if its not networking based? Or even how would you ?

kerem commented 2026-02-28 01:26:44 +03:00

Author

Owner

Copy link

@pranjal-joshi commented on GitHub (Jun 3, 2020):

So why would you use this with wm if its not networking based?
Or even how would you ?

Certainly it can be used along with external WiFi networks as well. As ESP provides MODE_AP_STA, My design is considers connecting to a WiFi network to access MQTT broker directly. But if WiFi is weak or unavailable due to range issues, I will enter into mesh mode so that I can send MQTT packets over the mesh to a node which is also connected to internet, thus effectively considering that node as a bridge node of the mesh network.

<!-- gh-comment-id:637905198 --> @pranjal-joshi commented on GitHub (Jun 3, 2020): > So why would you use this with wm if its not networking based? > Or even how would you ? Certainly it can be used along with external WiFi networks as well. As ESP provides `MODE_AP_STA`, My design is considers connecting to a WiFi network to access MQTT broker directly. But if WiFi is weak or unavailable due to range issues, I will enter into mesh mode so that I can send MQTT packets over the mesh to a node which is also connected to internet, thus effectively considering that node as a bridge node of the mesh network.

kerem commented 2026-02-28 01:26:44 +03:00

Author

Owner

Copy link

@tablatronix commented on GitHub (Jun 3, 2020):

I still do not get it, its 2 seperate things, what would prevent them from working togather?
Its the same as using 2 libraries.

<!-- gh-comment-id:638216435 --> @tablatronix commented on GitHub (Jun 3, 2020): I still do not get it, its 2 seperate things, what would prevent them from working togather? Its the same as using 2 libraries.

kerem commented 2026-02-28 01:26:44 +03:00

Author

Owner

Copy link

@pranjal-joshi commented on GitHub (Jun 3, 2020):

I still do not get it, its 2 separate things, what would prevent them from working together?
Its the same as using 2 libraries.

I never said that these 2 libs are not compatible with each other. I think @kbssa was asking for a logical approach to implement this, maybe like a pseudo-code!
Bdw, @tablatronix Please fix the ESP requires hard reset issue. This made me switch from WM to another library.

<!-- gh-comment-id:638219110 --> @pranjal-joshi commented on GitHub (Jun 3, 2020): > I still do not get it, its 2 separate things, what would prevent them from working together? > Its the same as using 2 libraries. I never said that these 2 libs are not compatible with each other. I think @kbssa was asking for a logical approach to implement this, maybe like a pseudo-code! Bdw, @tablatronix Please fix the **ESP requires hard reset** issue. This made me switch from WM to another library.

kerem commented 2026-02-28 01:26:44 +03:00

Author

Owner

Copy link

@tablatronix commented on GitHub (Jun 3, 2020):

What do you mean ESP requires hard reset? There is no issue for that..

<!-- gh-comment-id:638219854 --> @tablatronix commented on GitHub (Jun 3, 2020): What do you mean ESP requires hard reset? There is no issue for that..

kerem commented 2026-02-28 01:26:44 +03:00

Author

Owner

Copy link

@tablatronix commented on GitHub (Jun 3, 2020):

I will see about creating an example for combinging with painlessmesh and espmesh or espnow

• example candidate

<!-- gh-comment-id:638220325 --> @tablatronix commented on GitHub (Jun 3, 2020): I will see about creating an example for combinging with painlessmesh and espmesh or espnow - [ ] example candidate

kerem commented 2026-02-28 01:26:44 +03:00

Author

Owner

Copy link

@pranjal-joshi commented on GitHub (Jun 3, 2020):

What do you mean ESP requires hard reset? There is no issue for that..

While using WM v2.0.2, I faced the issue that after receiving the config, the ESP still stays in blocking mode (even though it successfully saves the config in the memory). However, with a hard reset/power-cycle, the ESP successfully retrieves config from memory and proceeds as expected.

<!-- gh-comment-id:638232554 --> @pranjal-joshi commented on GitHub (Jun 3, 2020): > What do you mean ESP requires hard reset? There is no issue for that.. While using WM v2.0.2, I faced the issue that after receiving the config, the ESP still stays in blocking mode (even though it successfully saves the config in the memory). However, with a hard reset/power-cycle, the ESP successfully retrieves config from memory and proceeds as expected.

kerem commented 2026-02-28 01:26:44 +03:00

Author

Owner

Copy link

@pranjal-joshi commented on GitHub (Jun 3, 2020):

I will see about creating an example for combinging with painlessmesh and espmesh or espnow

• example candidate

@tablatronix - This might be a good point to take a look before writing an example.
https://github.com/gmag11/painlessMesh/blob/master/examples/mqttBridge/mqttBridge.ino

<!-- gh-comment-id:638233446 --> @pranjal-joshi commented on GitHub (Jun 3, 2020): > I will see about creating an example for combinging with painlessmesh and espmesh or espnow > > * [ ] example candidate @tablatronix - This might be a good point to take a look before writing an example. [https://github.com/gmag11/painlessMesh/blob/master/examples/mqttBridge/mqttBridge.ino](https://github.com/gmag11/painlessMesh/blob/master/examples/mqttBridge/mqttBridge.ino)

kerem commented 2026-02-28 01:26:44 +03:00

Author

Owner

Copy link

@tablatronix commented on GitHub (Jun 3, 2020):

are you saving parameters and not wifi? you have to set shoudBreak true or else it doesnt stop the cp, or switch to using the setup menu and not wifi for custom params.

Its not a bug but kind of a throwback to v.0 that I have not figured out a good way to fix without breaking old code. ( since you are NOW allowed to skip saving wifi everytime )

<!-- gh-comment-id:638256172 --> @tablatronix commented on GitHub (Jun 3, 2020): are you saving parameters and not wifi? you have to set shoudBreak true or else it doesnt stop the cp, or switch to using the setup menu and not wifi for custom params. Its not a bug but kind of a throwback to v.0 that I have not figured out a good way to fix without breaking old code. ( since you are NOW allowed to skip saving wifi everytime )

kerem commented 2026-02-28 01:26:44 +03:00

Author

Owner

Copy link

@pranjal-joshi commented on GitHub (Jun 3, 2020):

@tablatronix Good to know about this. In my sketch, I was trying to save both WiFi config (SSID+PASS) along with 4-5 custom params which are to be stored on SPIFFS.
If you didn't have mentioned about shouldBreak in the docs, please consider it so.

<!-- gh-comment-id:638263678 --> @pranjal-joshi commented on GitHub (Jun 3, 2020): @tablatronix Good to know about this. In my sketch, I was trying to save both WiFi config (SSID+PASS) along with 4-5 custom params which are to be stored on SPIFFS. If you didn't have mentioned about `shouldBreak` in the docs, please consider it so.

kerem commented 2026-02-28 01:26:44 +03:00

Author

Owner

Copy link

@tablatronix commented on GitHub (Jun 3, 2020):

Ill try to find a better fix for this this week and add better callbacks for param saves.

I thought it was added to the readme but I am not seeing it ...
hmm

<!-- gh-comment-id:638281054 --> @tablatronix commented on GitHub (Jun 3, 2020): Ill try to find a better fix for this this week and add better callbacks for param saves. I thought it was added to the readme but I am not seeing it ... hmm

kerem commented 2026-02-28 01:26:44 +03:00

Author

Owner

Copy link

@tablatronix commented on GitHub (Jun 3, 2020):

doh it was added to hotfixes ill adjust that...

Save settings
This gets called when custom parameters have been set AND a connection has been established. Use it to set a flag, so when all the configuration finishes, you can save the extra parameters somewhere.

IF YOU NEED TO SAVE PARAMETERS EVEN ON WIFI FAIL OR EMPTY, you must set setBreakAfterConfig to true, or else saveConfigCallback will not be called.

//if this is set, it will exit after config, even if connection is unsuccessful.
    void          setBreakAfterConfig(boolean shouldBreak);

<!-- gh-comment-id:638281999 --> @tablatronix commented on GitHub (Jun 3, 2020): doh it was added to hotfixes ill adjust that... ``` Save settings This gets called when custom parameters have been set AND a connection has been established. Use it to set a flag, so when all the configuration finishes, you can save the extra parameters somewhere. IF YOU NEED TO SAVE PARAMETERS EVEN ON WIFI FAIL OR EMPTY, you must set setBreakAfterConfig to true, or else saveConfigCallback will not be called. //if this is set, it will exit after config, even if connection is unsuccessful. void setBreakAfterConfig(boolean shouldBreak); ```

kerem commented 2026-02-28 01:26:44 +03:00

Author

Owner

Copy link

@tablatronix commented on GitHub (Jun 3, 2020):

You should test out

  // wm.setParamsPage(true); // move params to seperate page, not wifi, do not combine with setmenu!, use setSaveParamsCallback

<!-- gh-comment-id:638283786 --> @tablatronix commented on GitHub (Jun 3, 2020): You should test out ```C++ // wm.setParamsPage(true); // move params to seperate page, not wifi, do not combine with setmenu!, use setSaveParamsCallback ```

kerem commented 2026-02-28 01:26:44 +03:00

Author

Owner

Copy link

@kubitz commented on GitHub (Sep 6, 2021):

I will see about creating an example for combinging with painlessmesh and espmesh or espnow

• example candidate

@tablatronix - This might be a good point to take a look before writing an example.
https://github.com/gmag11/painlessMesh/blob/master/examples/mqttBridge/mqttBridge.ino

@pranjal-joshi did you end up implementing this in one of your projects?

<!-- gh-comment-id:913820433 --> @kubitz commented on GitHub (Sep 6, 2021): > > I will see about creating an example for combinging with painlessmesh and espmesh or espnow > > > > * [ ] example candidate > > @tablatronix - This might be a good point to take a look before writing an example. > https://github.com/gmag11/painlessMesh/blob/master/examples/mqttBridge/mqttBridge.ino @pranjal-joshi did you end up implementing this in one of your projects?

kerem commented 2026-02-28 01:26:44 +03:00

Author

Owner

Copy link

@markg85 commented on GitHub (Mar 20, 2022):

I'm curious about this too.
Contrary to what was said in this post earlier, I do think mesh an wifimanager should be complementary if you have a root node that lives on your normal network too. Kind of a gateway node into your mesh network.

In that case, the root node has normal plain wifi and needs to be configured as such. Hence the need for something like WifiManager.

An example with mesh + WifiManager would be an awesome starting point!

<!-- gh-comment-id:1073340495 --> @markg85 commented on GitHub (Mar 20, 2022): I'm curious about this too. Contrary to what was said in this post earlier, I do think mesh an wifimanager should be complementary **if** you have a root node that lives on your normal network too. Kind of a gateway node into your mesh network. In that case, the root node has normal plain wifi and needs to be configured as such. Hence the need for something like WifiManager. An example with mesh + WifiManager would be an awesome starting point!

kerem commented 2026-02-28 01:26:44 +03:00

Author

Owner

Copy link

@hemangjoshi37a commented on GitHub (Jun 7, 2022):

I am curious if anyone already has this implemented in their project: painlessmesh and wifimanager coming together.
Please let me know because I am trying this to do this from very long time.
Hemang Joshi

<!-- gh-comment-id:1148485890 --> @hemangjoshi37a commented on GitHub (Jun 7, 2022): I am curious if anyone already has this implemented in their project: _**painlessmesh** and **wifimanager** coming together._ Please let me know because I am trying this to do this from very long time. [Hemang Joshi](https://hjlabs.in/)

kerem referenced this issue 2026-02-28 02:12:35 +03:00

[PR #718] [MERGED] Implements #717: Added getParameters and getParametersCount methods. #1668

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

master

revert-1849-master

feature_fastconnect

feature_auth

feature_slimable

PEAP

feature_statichtmlparams

feature_asyncwebserver

feature_pagestringsref

parameter-smart-ptr

gh-pages

Legacy_v1

hotfixes

autochannelselect_feature

travis

smartconfig

v2.0.17

v2.0.16-rc.2

v2.0.15-rc.1

v2.0.0-rc.1

v2.0.14-beta

v2.0.13-beta

v2.0.12-beta

v2.0.11-beta

v2.0.10-beta

v2.0.9-beta

v2.0.8-beta

2.0.7-beta

2.0.6-beta

2.0.5-beta

2.0.4-beta

0.16.0

2.0.3-alpha

0.15.0

0.14

0.13

0.12

0.11

0.10

0.9

0.8

0.7

0.6

0.5

v0.4

v0.3

v0.2

v0.1

Labels

Clear labels   

📶 WiFi

  

🕸️ HTTP

  

Branch

  

DEV Help Wanted

  

Discussion

  

Documentation

  

ESP32

  

Example

  

Good First Issue

  

Hotfix

  

In Progress

  

Incomplete

  

Needs Feeback

  

Priority

  

QA

  

Question

  

Task

  

Upstream/Dependancy

  

bug

  

duplicate

  

enhancement

  

invalid

  

pull-request

Mirrored from GitHub Pull Request

  

wontfix

No labels

📶 WiFi

🕸️ HTTP

Branch

DEV Help Wanted

Discussion

Documentation

ESP32

Example

Good First Issue

Hotfix

In Progress

Incomplete

Needs Feeback

Priority

QA

Question

Task

Upstream/Dependancy

bug

duplicate

enhancement

invalid

pull-request

wontfix

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

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#717

No description provided.