Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AP appears despite of entering client mode. #911

Closed
3 tasks
YogKar opened this issue Jul 11, 2019 · 8 comments
Closed
3 tasks

AP appears despite of entering client mode. #911

YogKar opened this issue Jul 11, 2019 · 8 comments

Comments

@YogKar
Copy link

YogKar commented Jul 11, 2019

Basic Infos

Hardware

WiFimanager Branch/Release:

  • travis

Esp8266/Esp32:

  • ESP8266

**Hardware:

  • ESP12 E/F/S (nodemcu, wemos, feather)

Description

Using https://github.com/tzapu/WiFiManager/tree/travis

I need non blocking AP, and so i am using "https://github.com/tzapu/WiFiManager/tree/travis"
I was testing the basic Autoconnect .
When I configure , save New AP in portal, and restart ESP8266 module, The device gets configured in client mode and connects to the configured AP. But along with that it also Shows AP which is typically ESPxxx (starting with ESP). which ideally should have not been appearing.
to check further I tried to connect it. but could not get the config portal page. and this happens in blocking as well in non blocking mode.

what must be happening? How should this be resolved?

#457
The above issue looks similar . Is it resolved ?

Update:
https://github.com/tzapu/WiFiManager/tree/0.14
That problem is not with 0.14

Settings in IDE

Module: NodeMcu

Additional libraries:

Sketch

#include <Arduino.h>

void setup() {

}

void loop() {

}

Debug Messages

messages here
@tablatronix
Copy link
Collaborator

WiFi.mode(WiFi_STA); // set mode explicitly
Esp does that by default

@YogKar
Copy link
Author

YogKar commented Jul 12, 2019

It worked.
Thanks for working on nonblocking and sharing it. It's a huge effort saver.

@tablatronix
Copy link
Collaborator

I assume you meant you are using
https://github.com/tzapu/WiFiManager/tree/development

not travis. ?

@YogKar
Copy link
Author

YogKar commented Jul 13, 2019

"https://github.com/tzapu/WiFiManager/tree/development" shows that the "build failing" for both ESP8266 and ESP32. So i thought it's somewhere incomplete or broken.

But after your reply I tested it. Its working flawless.

@tablatronix
Copy link
Collaborator

the script needs to be fixed, it broke when something changed in esp toolchain, I have not had time to look at it

@YogKar
Copy link
Author

YogKar commented Jul 13, 2019

I have to add few things so that other visitors here get some help and if I have done wrong you can correct me. This is based on my experience.

  1. polling process() every 10ms gave me best results while using non-blocking mode..
  2. I stopped polling when the device is configured in station mode (client).
    Makes sense?

@tablatronix
Copy link
Collaborator

Yes you will have to process the web server constantly or it will not handle requests fast enough, and probably turn debugging off and serial prints.

You can process when ever you want the library will return if the webserver is not running, you can also run the webserver in sta mode without the ap or without the captive portal

@YogKar
Copy link
Author

YogKar commented Jul 16, 2019

Sure.

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

No branches or pull requests

2 participants