Skip to content
This repository has been archived by the owner on Sep 6, 2023. It is now read-only.

Connecting to AP that is "out-of-range" #231

Open
PikWay opened this issue Nov 29, 2017 · 5 comments
Open

Connecting to AP that is "out-of-range" #231

PikWay opened this issue Nov 29, 2017 · 5 comments

Comments

@PikWay
Copy link

PikWay commented Nov 29, 2017

Hi
When I'm trying to connect to AP that is currently out-of-range ESP starts to spin trying to connect (with error: No AP found). Only way to stop it is reboot (until you don't have this in boot.py).
I've made workaround in my code, but can someone check is this expected behavior? Maybe n-attempts and then throw some exception?

@nickzoic
Copy link
Collaborator

nickzoic commented Nov 29, 2017 via email

@PikWay
Copy link
Author

PikWay commented Nov 29, 2017

Code is just like yours:
import time,network
def connectWLAN():
sta=network.WLAN(network.STA_IF)
sta.connect('foo','bar')
while not sta.isconnected():
time.sleep(1)
print(sta.ifconfig())

and after executing connectWLAN() it starts to write to serial console:
I (118715) wifi: STA_DISCONNECTED, reason:201
no AP found
I (121545) wifi: STA_DISCONNECTED, reason:201
no AP found
I (124375) wifi: STA_DISCONNECTED, reason:201
no AP found
I (127205) wifi: STA_DISCONNECTED, reason:201
no AP found

Keyboart interrupt doesnt affect this, because it's trying to connect somewhere in background, meanwhile you cannot issue any commands in console (and sometimes ampy also doesn't work). I think it's related to #165 - I'll check that.

@PikWay
Copy link
Author

PikWay commented Nov 29, 2017

Checked dpgeorge fix, but seems like except to logger it prints "no AP found"

sta.connect('foo','bar')
no AP found
no AP found
no AP found
no AP found

no AP found

no AP found
no AP found
no AP found
no AP found

no AP found
no AP found
no AP found
no AP found
no AP found
no AP found
no AP found
no AP found

@robert-hh
Copy link
Contributor

Don't know if that helps, but you can stop those connect attempts and the related messages with disconnect(), e.g. after your timeout, and try maybe later.

@PikWay
Copy link
Author

PikWay commented Nov 29, 2017

I've already made workaround. First scan, then check is essid I want to connect in list and if yes - connect.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants