Closed teixeluis closed 4 years ago
Looks like its loading blank strings from NVS. Uncomment lines 47 & 48 of app_main.c to reset NVS. That should cause whatever defaults you have in sdkconfig to be saved to NVS at next bootup. You'll then need to comment those lines out again to be able to change those settings from the web interface.
Ok thanks. Would it make sense to first read the nvs and check the variables, initializing it with values from the firmware (the two commented lines) in case these are blank, and otherwise not touching these? It would eventually have the side-effect of loading the defaults if we would set the SSID and password as blank strings though..
Cheers
Now it registered to the network and is working as expected.
Thanks!
Cheers
Yeah I'll do that
I will close this ticket, as the obstacle was solved by proceeding as you suggested.
Thanks
Cheers
Hello,
I have defined my home WiFi details via menuconfig, prior to building the firmware image. While running the device, it never seems to associate to the WiFi AP (cannot see it obtain a DHCP lease) nor fallback to its own AP mode. I have double checked the WiFi details and these are correct. Looking at the debug output from the serial port, it seems as if it is not assuming the values defined during menuconfig (blank SSID and password):
Is there anything else that needs to be done or configured, in order to make sure that the WiFi credentials are stored in the device (if it is the case that these are not being passed during the build)?
Adding the sdkconfig file.
sdkconfig.txt
Cheers