mirror of
https://github.com/tzapu/WiFiManager.git
synced 2026-04-27 17:15:53 +03:00
[GH-ISSUE #869] Portal Configuration does not save SSID and Password if another saved router is in the range. #734
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#734
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 @Enry95 on GitHub (Apr 19, 2019).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/869
Basic Infos
Hardware
WiFimanager Branch/Release:
Esp8266/Esp32:
Hardware: ESP-12e, esp01, esp25
ESP Core Version: 2.4.0, staging
Description
Hi, thank you for your amazing library, it do saved me in this project and I love it.
But there is a quite annoying problem in the configuration and here's why:
SSID and Password does not set from the portal if there is another router saved and working.
If I have the ESP8266 connected to Router A and I want to connect it to Router B but Router A is still in the range, it completely ignores the new SSID and Password and keep the previous one.
The only way to go around this problem is to call a wifiManager.resetSettings(); and open the portal again.
I have the latest version of ESP core, but this happens with any version.
I think that if I say a WiFi module to set another Router, it should point to that router, doesn't matter if it's connected to another router in the range or not.
Thank you so much for your attention
Settings in IDE
Module: Generic ESP8266 Module
Serial Output
*WM: Sent config page
*WM: Request redirected to captive portal
*WM: Request redirected to captive portal
*WM: Request redirected to captive portal
*WM: WiFi save
*WM: Sent wifi save page
*WM: Connecting to new AP
*WM: Connecting as wifi client...
*WM: Already connected. Bailing out.
OK
*WM: freeing allocated params!
@tablatronix commented on GitHub (Apr 19, 2019):
use hotfixes or development branch