-
Notifications
You must be signed in to change notification settings - Fork 82
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
Wifi credentials cannot be changed #587
Comments
same issue for me. I use esptool to erase completely the data |
I seem to have missed this issue - sorry about that! WiFi initialization in SensESP is a bit hairy. The basic idea is that SSID and password entered using WiFiManager (or modified with the web UI) are stored on the SPIFFS filesystem and have precedence over hard-coded values. Since the SPIFFS contents are retained during normal reflashing, this means that changing the hard-coded values don't have an effect. Erasing the flash either using PlatformIO's "Erase Flash" command or Having said this, if SensESP saves hard-coded credentials to SPIFFS without user interaction, that does sound like a bug that needs to be fixed. It might take a bit of time until I can do it myself, though... |
Hello Matti, thank you very much for your feedback. This has clarified my concern. Thank you very much! Many greetings |
I'll reopen this because I think the raised point(s) are real issues and should be addressed. That is:
|
i've stumbled over this as well. for those searching for a quick-fix, the exact command to erase the flash is:
is there a link to the hardware button solution already? |
While programming the ESP32 with the SensESP library I encounter the error that the access data of the WIFI on the board can no longer be changed.
The background is that I have two WIFI access points (lab and production environment).
If I store the respective WIFI credentials in the code and load the program on the board, the ESP32 still tries to establish a connection with the WIFI credentials previously entered in the code. However, the problem does not occur with the hostname or the SignalK server.
Is a problem of this kind already known or can someone tell me a way to completely reset an ESP32?
The text was updated successfully, but these errors were encountered: