You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While testing how wifiMulti handles choice of AP I took the NodeMCU close to my secondary access point. The SSID of this AP was in the list added by addAP, but the passphrase had changed since uploading the sketch to the NodeMCU. Naturally, no connexion occurred (other devices were able to connect to the AP by using the correct passphrase).
However, I think it's unfortunate that wifiMulti.run refuses to quit trying to connect to this AP, despite the availability of other, working APs on it's list (by moving back closer to my primary AP, it connected fine). Maybe I didn't wait long enough (over 2 minutes) ?
This may be a design feature but I can't immediately figure why this might be desirable behaviour.
Secondary observation: highest strength, unprotected APs seem to be ignored if they aren't explicitly added by addAP. This too seems unfortunate.
EDIT: I can understand that an "open" AP could cause problems if it requires a further http dialogue to establish connectivity, but then it becomes the same case as an AP with a bad passphrase (or MAC filtering).
Basic Infos
Hardware
Hardware: NodeMCU 1.0 Amica ESP-12E
Core Version: 2.2.0
IDE Arduino: 1.6.8
Description
While testing how
wifiMulti
handles choice of AP I took the NodeMCU close to my secondary access point. The SSID of this AP was in the list added byaddAP
, but the passphrase had changed since uploading the sketch to the NodeMCU. Naturally, no connexion occurred (other devices were able to connect to the AP by using the correct passphrase).However, I think it's unfortunate that
wifiMulti.run
refuses to quit trying to connect to this AP, despite the availability of other, working APs on it's list (by moving back closer to my primary AP, it connected fine). Maybe I didn't wait long enough (over 2 minutes) ?This may be a design feature but I can't immediately figure why this might be desirable behaviour.
Secondary observation: highest strength, unprotected APs seem to be ignored if they aren't explicitly added by
addAP
. This too seems unfortunate.EDIT: I can understand that an "open" AP could cause problems if it requires a further http dialogue to establish connectivity, but then it becomes the same case as an AP with a bad passphrase (or MAC filtering).
Settings in IDE
Module: NodeMCU 1.0 (ESP-12E Module)
Flash Size: 4M (3M SPIFFS)
CPU Frequency: 80Mhz
Flash Mode: n/a
Flash Frequency: 40Mhz
Upload Using: SERIAL
Reset Method: n/a
Sketch
Debug Messages
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: