-
Notifications
You must be signed in to change notification settings - Fork 4
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
Can't change WiFi mode #2
Comments
Thank you for trying it out! Which device are you using?
I hope this is helpful. Let me know what you find :) |
Thank you for the detailed answer. EDIT: After studying the code I see few dependencies from boot mode button on pin 0. I think this for NodeMCU board and not for mine Serial wifi v1.0 board. |
If the pins are connected differently on your board, that would explain this issue. Maybe the "boot mode" pin is being held low which resets the config. If the led pin does matches the code, you should see a Have you tried changing the "boot mode" pin to match your board as you mentioned? |
This is my board: The black switch (!) is for switching between uart and programming mode. I believe it is GPIO0 to gnd in prog. mode. |
Can you describe your used hardware in your documentation, especially the buttons and switches. It seems different and the reason for the nonfunctional web programming feature. |
I have experienced the problem switching to station Wi-Fi mode. I have concluded by looking at the debug output, that the reason it fails to successfully connect, is because it finds the router Wi-Fi OK and connects but the gateway address in the ESP8266 is still left set to 10.1.1.1. So the ESP8266 can not route, and the connection fails. |
I am trying to configure station mode to connect to my home network. So I put in my home SSID and the wifi key. WiFi mode selector stands with blue on "Connect to an existing access point". After Save I disconnect and started new. But the NodeMCU is still an access point 10.1.1.1.
This I made with NodeMCU prog switch and without, doesn't matter.
The text was updated successfully, but these errors were encountered: