[GH-ISSUE #485] NodeMCU is not connecting to Wifi after reset #408

New issue

Open

opened 2026-02-28 01:25:09 +03:00 by kerem · 5 comments

kerem commented

2026-02-28 01:25:09 +03:00

Owner

Originally created by @netwein on GitHub (Jan 17, 2018).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/485

Hi,

I'm using WifiManager on my NodeMCU. After uploading the code to the NodeMCU using Arduino IDE the app works great and I'm having an Access Point which I'm configuring to use my home wifi and the NodeMCU connects to the wifi and sends the data great. Unfortunately, when disconnecting the NodeMCU from the power and then reconnecting it back the NodeMCU is not connecting to my wifi or starting the temporary AP. I've expected that it will remember the SSID and password for my wifi and connect directly to it.
Is it a bug? How can I debug this?

Thanks.

Originally created by @netwein on GitHub (Jan 17, 2018). Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/485 Hi, I'm using WifiManager on my NodeMCU. After uploading the code to the NodeMCU using Arduino IDE the app works great and I'm having an Access Point which I'm configuring to use my home wifi and the NodeMCU connects to the wifi and sends the data great. Unfortunately, when disconnecting the NodeMCU from the power and then reconnecting it back the NodeMCU is not connecting to my wifi or starting the temporary AP. I've expected that it will remember the SSID and password for my wifi and connect directly to it. Is it a bug? How can I debug this? Thanks.

kerem added the

Question

DEV Help Wanted

labels

2026-02-28 01:25:09 +03:00

kerem commented

2026-02-28 01:25:10 +03:00

Author

Owner

@tablatronix commented on GitHub (Jan 17, 2018):

setDebugOutput(boolean debug);
also try bumping the connect timeout, are you using the examples ?

@tablatronix commented on GitHub (Jan 17, 2018): setDebugOutput(boolean debug); also try bumping the connect timeout, are you using the examples ?

kerem commented

2026-02-28 01:25:10 +03:00

Author

Owner

@netwein commented on GitHub (Jan 17, 2018):

I've based on the example code.
The "debugOutput" is true by default.
When I'm with Serial Monitor right after upload the code I can see the the logs in the serial monitor.
If I'm just connecting the NodeMCU to computer, I don't see anything in the serial monitor and I've tried by using some python script listening to the serial and all I'm getting is "1" printed in a new line...

@netwein commented on GitHub (Jan 17, 2018): I've based on the example code. The "debugOutput" is true by default. When I'm with Serial Monitor right after upload the code I can see the the logs in the serial monitor. If I'm just connecting the NodeMCU to computer, I don't see anything in the serial monitor and I've tried by using some python script listening to the serial and all I'm getting is "1" printed in a new line...

kerem commented

2026-02-28 01:25:10 +03:00

Author

Owner

@tablatronix commented on GitHub (Jan 17, 2018):

do you have a reset button ? open serial monitor, reset module you should get a bunch of stuff

@tablatronix commented on GitHub (Jan 17, 2018): do you have a reset button ? open serial monitor, reset module you should get a bunch of stuff

kerem commented

2026-02-28 01:25:10 +03:00

Author

Owner

@netwein commented on GitHub (Jan 20, 2018):

I've tried I'm not getting nothing in the serial monitor..

@netwein commented on GitHub (Jan 20, 2018): I've tried I'm not getting nothing in the serial monitor..

kerem commented

2026-02-28 01:25:10 +03:00

Author

Owner

@tablatronix commented on GitHub (Jan 20, 2018):

What about your own serial.print commands?
Do you see those? Do you have serial.begin?

@tablatronix commented on GitHub (Jan 20, 2018): What about your own serial.print commands? Do you see those? Do you have serial.begin?