mirror of
https://github.com/tzapu/WiFiManager.git
synced 2026-04-27 09:05:56 +03:00
[GH-ISSUE #229] After Config Portal Timeout ESP always act as Access Point #187
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#187
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 @mocheffendi on GitHub (Sep 29, 2016).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/229
Dear Tzapu,
I Use Configuration Portal timeout
wifiManager.setConfigPortalTimeout(180);
But after Timeout occurs the ESP8266 still act as Access Point
How to shutdown the Access Point after Config Portal Timeout.
Thanks
Best Regards
M. Effendi
@krzbor commented on GitHub (Oct 9, 2016):
I have a similar problem. When timeout ESP properly restarts, it is running my program, but the AP is still visible. I can connect to the AP. I can not, however, connect with the web: 192.168.4.1.
@kentaylor commented on GitHub (Oct 10, 2016):
That is occurring when the esp8266 starts up in dual mode. You can set it to station mode in your code or there is another version of WiFiManager that Selectively Operates In Dual Mode.
@krzbor commented on GitHub (Oct 12, 2016):
Is it enough to add WiFi.mode (WIFI_STA); before ESP.reset ();?
@kentaylor commented on GitHub (Oct 12, 2016):
Better to do it at start up like this for the reasons given there.
@krzbor commented on GitHub (Oct 14, 2016):
Thank you very much