mirror of
https://github.com/tzapu/WiFiManager.git
synced 2026-04-27 00:55:52 +03:00
[GH-ISSUE #1153] [QUESTION] ControlManager Existing after connecting to network from captive portal #989
Labels
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
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/WiFiManager#989
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Karmakstylez on GitHub (Nov 29, 2020).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/1153
Hello,
Is there a way to keep the ControlManager accessible instead of wiping the settings and start over again so you can change the WiFi or reset the info via de captive portal?
Please let me know.
~Karmakstylez
@andrezanna commented on GitHub (Dec 20, 2020):
Hello, i'm interested in this too.
Thanks
@FlMerz commented on GitHub (Dec 20, 2020):
Hi I think that's not possible with the current version. The problem is that the controller must change from ap mode to sta mode to check your inserted WiFi credentials. During the start of the sta mode the ap mode will be disabled which will close the config portal...
Maybe you can increase the speed of changing back to ap mode if you don't restart the esp completely.
@tablatronix commented on GitHub (Dec 20, 2020):
Yes in the dev and alpha version, you can ondemand and non blocking start the webserver on sta mode also
@tablatronix commented on GitHub (Dec 20, 2020):
#500