-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
No wifi in nodeMCU clone (no AP, no client) #1397
Comments
How did you erase the flash? I would recommend to do it in accordance with this howto: |
I erased it by using the official python tool, as called by https://github.com/marcelstoer/nodemcu-pyflasher/releases But erasing is not the relevant issue here. |
Can you build the code from scratch? And then build it twice? |
Yes, that did the trick. Now wifi is working again on my nodeMCU clone! This build indeed was broken. |
OK, then I will remove it from the releases list |
Last two releases are broken: ESPEasy_mega-20180517 is fine. |
@svde That's really strange, since nothing has changed there. |
Summarize of the problem/feature request
My nodeMCU clone does not have any wifi any more, using build mega-20180510
This seems the same problem as in item #1337 , so after solving it in build 20180502, the problem does now reappear.
System configuration
nodeMCU / 4Mb / build mega-20180510 (ESP82xx Core 2_4_1, NONOS SDK 2.2.1(cfd48f3), LWIP: 2.0.3)
After upgrading wifi could not connect any more.
Instead of connecting I only get lots of
WIFI : Disconnected! Reason: '(201) No AP found'
Then I flashed again, but now following a complete erase, but that did not solve it. Now I do not see any ESP AP, so cannot connect and configure.
Hardware: 'WeMos' nodeMCU clone (see #1337 for a picture of this device)
ESP Easy version: mega-20180510 (ESP82xx Core 2_4_1, NONOS SDK 2.2.1(cfd48f3), LWIP: 2.0.3)
Extra info
I also flashed mega-20180510 into a Wemos D1 mini.
Just like in item #1337, wifi works normally in this Wemos D1 mini.
The text was updated successfully, but these errors were encountered: