[GH-ISSUE #335] Static IP does not work after reboot #281

Closed
opened 2026-02-28 01:24:29 +03:00 by kerem · 7 comments
Owner

Originally created by @bobybobybob on GitHub (Mar 21, 2017).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/335

Hello,
the "AutoConnectWithStaticIP" Excampel does not work very good.

Default IP in Arduinoscript is 192.168.1.50

When I set in webconfig (192.168.4.1) the 192.168.1.66 as new IP it is OK

But power off, it go back to 192.168.1.50

Look like a big Bug. I use ESP8266 EPS-12E and Arduino IDE 1.8.1

The "AutoConnectWithFSParametersAndCustomIP" works better but it contains some unknow MQTT??? Dont know what that is


Next Problem

First use of Wifi Manager, it connect imediately with correct WLAN but i have never used wifi Manager before, only other ESP-Stuff with hardcoded WLAN SSID and Password.


Maybee you have time to fix the excampel script. And I will pray for your soul. Alleluia Jesus loves ESP8266 too.

Originally created by @bobybobybob on GitHub (Mar 21, 2017). Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/335 Hello, the "AutoConnectWithStaticIP" Excampel does not work very good. Default IP in Arduinoscript is 192.168.1.50 When I set in webconfig (192.168.4.1) the 192.168.1.66 as new IP it is OK But power off, it go back to 192.168.1.50 Look like a big Bug. I use ESP8266 EPS-12E and Arduino IDE 1.8.1 The "AutoConnectWithFSParametersAndCustomIP" works better but it contains some unknow MQTT??? Dont know what that is -------------------- Next Problem First use of Wifi Manager, it connect imediately with correct WLAN but i have never used wifi Manager before, only other ESP-Stuff with hardcoded WLAN SSID and Password. ------------------- Maybee you have time to fix the excampel script. And I will pray for your soul. Alleluia Jesus loves ESP8266 too.
kerem closed this issue 2026-02-28 01:24:29 +03:00
Author
Owner

@telanoc commented on GitHub (Mar 30, 2017):

I'm not tzapu, but maybe I can answer your "next problem" part. The ESP keeps track of the last AP and password that it connected to. It can then connect back up to it easily. WiFiManager comes into play when that "last-connected" value isn't set, or if that particular AP isn't around to connect to.

You can call WiFi.disconnect(true); once in your code to have the ESP wipe out its idea of that last connected AP (and disconnect you from it at the same time). Then WiFiManager will kick in the next time you restart.

<!-- gh-comment-id:290306824 --> @telanoc commented on GitHub (Mar 30, 2017): I'm not tzapu, but maybe I can answer your "next problem" part. The ESP keeps track of the last AP and password that it connected to. It can then connect back up to it easily. WiFiManager comes into play when that "last-connected" value isn't set, or if that particular AP isn't around to connect to. You can call `WiFi.disconnect(true);` once in your code to have the ESP wipe out its idea of that last connected AP (and disconnect you from it at the same time). Then WiFiManager will kick in the next time you restart.
Author
Owner

@yovanfowdar commented on GitHub (Apr 19, 2017):

bobybobybob , you are right this is exactly the same issue I am having, after setting the IP on the wifi manager page , everything ok until I reboot . I have tried with both block1 and block2, after reboot the IP address is not stored and used for the next connection. I hope a solution is found soon . Tzapu and guys working on this project , grateful if you could look into that .
Thanks

<!-- gh-comment-id:295410633 --> @yovanfowdar commented on GitHub (Apr 19, 2017): bobybobybob , you are right this is exactly the same issue I am having, after setting the IP on the wifi manager page , everything ok until I reboot . I have tried with both block1 and block2, after reboot the IP address is not stored and used for the next connection. I hope a solution is found soon . Tzapu and guys working on this project , grateful if you could look into that . Thanks
Author
Owner

@tzapu commented on GitHub (Apr 20, 2017):

hi guys, like the extra fs/eeprom parameters, you are responsible for storing the ip configuration somewhere and restoring it at next boot.

the sdk does not store it and wifimanager by itself, does not store anything.

i hope this helps
alex

On 19 Apr 2017, at 22:48, yovanfowdar notifications@github.com wrote:

bobybobybob , you are right this is exactly the same issue I am having, after setting the IP on the wifi manager page , everything ok until I reboot . I have tried with both block1 and block2, after reboot the IP address is not stored and used for the next connection. I hope a solution is found soon . Tzapu and guys working on this project , grateful if you could look into that .
Thanks


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/tzapu/WiFiManager/issues/335#issuecomment-295410633, or mute the thread https://github.com/notifications/unsubscribe-auth/AC2FkJaOSCKGBh0a6OrC2aYGXJAR7nAuks5rxmUagaJpZM4MkGDX.

<!-- gh-comment-id:295625108 --> @tzapu commented on GitHub (Apr 20, 2017): hi guys, like the extra fs/eeprom parameters, you are responsible for storing the ip configuration somewhere and restoring it at next boot. the sdk does not store it and wifimanager by itself, does not store anything. i hope this helps alex > On 19 Apr 2017, at 22:48, yovanfowdar <notifications@github.com> wrote: > > bobybobybob , you are right this is exactly the same issue I am having, after setting the IP on the wifi manager page , everything ok until I reboot . I have tried with both block1 and block2, after reboot the IP address is not stored and used for the next connection. I hope a solution is found soon . Tzapu and guys working on this project , grateful if you could look into that . > Thanks > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub <https://github.com/tzapu/WiFiManager/issues/335#issuecomment-295410633>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AC2FkJaOSCKGBh0a6OrC2aYGXJAR7nAuks5rxmUagaJpZM4MkGDX>. >
Author
Owner

@yovanfowdar commented on GitHub (Apr 20, 2017):

Thank you for your reply Tzapu , that shed more light , I guess we were all expecting that the entered static data IP address, subnet mask and gateway were being stored on the fs , which is not the case . This reply will surely help us in understanding how the wifi manager for static configuration works. A nice enhancement would be having the static data be stored on the eprom. Cheers

<!-- gh-comment-id:295696850 --> @yovanfowdar commented on GitHub (Apr 20, 2017): Thank you for your reply Tzapu , that shed more light , I guess we were all expecting that the entered static data IP address, subnet mask and gateway were being stored on the fs , which is not the case . This reply will surely help us in understanding how the wifi manager for static configuration works. A nice enhancement would be having the static data be stored on the eprom. Cheers
Author
Owner

@bobybobybob commented on GitHub (Apr 20, 2017):

Hello dear friends,
Can it be that the error is dependent on the eeprom manufacture? With some ESP12E everything works wonderfully, with ESP-07 with start-up problems then OK, with ESP-01 not at all and with some ESP12E and an ESP12F it did not go either. The ESPs at 12E have different manufacturers of the Eeprom.

<!-- gh-comment-id:295968796 --> @bobybobybob commented on GitHub (Apr 20, 2017): Hello dear friends, Can it be that the error is dependent on the eeprom manufacture? With some ESP12E everything works wonderfully, with ESP-07 with start-up problems then OK, with ESP-01 not at all and with some ESP12E and an ESP12F it did not go either. The ESPs at 12E have different manufacturers of the Eeprom.
Author
Owner

@bobybobybob commented on GitHub (Jan 26, 2018):

tablatronix closed this 10 hours ago

have you fix the problem?

<!-- gh-comment-id:360788499 --> @bobybobybob commented on GitHub (Jan 26, 2018): tablatronix closed this 10 hours ago have you fix the problem?
Author
Owner

@mrgadotti commented on GitHub (Mar 8, 2021):

I did have the same problem. After change IP adress on from Web portal, it's work fine. After reboot, the board use the IP from sketch. The same issue happens on ESP-07 and ES-12E.

<!-- gh-comment-id:792799061 --> @mrgadotti commented on GitHub (Mar 8, 2021): I did have the same problem. After change IP adress on from Web portal, it's work fine. After reboot, the board use the IP from sketch. The same issue happens on ESP-07 and ES-12E.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/WiFiManager#281
No description provided.