mirror of
https://github.com/tzapu/WiFiManager.git
synced 2026-04-27 09:05:56 +03:00
[GH-ISSUE #100] Trying to connect to password less ap uses old settings #77
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#77
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 @solexious on GitHub (Feb 12, 2016).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/100
Hello,
I'm currently troubleshooting trying to connect to a ap, I removed it's password to fault find why it was failing to connect. I noticed that if I entered the ssid but no password into the wifimanager connection form the serial output shows it just tries to connect to my last known good wifi settings:
*WM: Sent config page
*WM: Request redirected to captive portal
*WM: Handle root
*WM: WiFi save
*WM: Sent wifi save page
*WM: Connecting to new AP
*WM: Connecting as wifi client...
*WM: Using last saved values, should be faster
*WM: Connection result:
*WM: 3
connected...yeey :)
Scanning the new network it should be connecting to now, and the old network that it was last saved to shows it is now connected to the old network.
@tzapu commented on GitHub (Feb 12, 2016):
hi, this was a bug fixed in 0.8 or 0.9, please update WiFiManager
@solexious commented on GitHub (Feb 12, 2016):
updated from 0.8 to 0.9 with the same issue still
@tzapu commented on GitHub (Feb 12, 2016):
in the latest wifimanger the condition is
if (ssid != "")so it shouldn t really matter if the password is empty or notare you still getting this in the log
after
@solexious commented on GitHub (Feb 12, 2016):
Tried it again now and its now working, odd.
Thanks though!