mirror of
https://github.com/tzapu/WiFiManager.git
synced 2026-04-27 09:05:56 +03:00
[GH-ISSUE #833] Access Point remains visible after a successful autoConnect() #697
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#697
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 @sglvladi on GitHub (Feb 22, 2019).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/833
Basic Infos
Hardware
WiFimanager Branch/Release:
Esp8266/Esp32:
Hardware: ESP-12e, esp01, esp25
ESP Core Version: 2.4.0, staging
Description
From time to time, I can observe that, once a given ESP8266 has successfully connected to a network, the WM Access Point is still visible (and connectable), but the WebServer is not running (trying to access 192.168.4.1 doesn't return the WM web page). Just as a note, the desireable functionality would be to enter STA mode, i.e. no AP should be visible, which I think should be what happens when a simple autoConnect() call is made.
What is very interesting is that the issue doesn't seem to happen with all ESPs and it is also not dependent on the ESP Core Version. I have tried loading the same sketches/projects to identical devices, and some will exhibit the issues, while others will not. However, if a device does exhibit the problem, it will keep exhibiting it forever, irrespective of what version of the Arduino core is running.
Settings in IDE
Module: NodeMcu, Wemos D1
Additional libraries:
Sketch
The sketch I am using is pretty massive and contains a few custom defined libraries, however none of them perform any operations on the Wifi. Essentially, on every loop the sketch will check to see if the device is still connected to an AP, and if not it will make a call to the WiFiManager.autoConnect() method.
Thus, here's a summary of the sketch:
I am not sure exactly why I have the
WiFi.disconnect();in there, but I can vaguely remember that it was added at some point "just" to be sure that we have disconnected from the network, before attempting any reconnections/etc.. I doubt that this would be causing any issues, but seeing as this is the only command that operates on the Wifi, other that WM itself, I thought I would make a not of it.Debug Messages
There is no (easily) identifiable debugging relating to this issue (for now)..
Thanks much in advance.
@tablatronix commented on GitHub (Feb 22, 2019):
just set the mode to sta in your code, something has remembered softap default flash