# NodeMCU does not create a wifi network
**URL:** https://forum.sensor.community/t/nodemcu-does-not-create-a-wifi-network/1983
**Category:** Uncategorized
**Created:** [April 4, 2023, 8:56pm UTC](https://forum.sensor.community/t/nodemcu-does-not-create-a-wifi-network/1983 "2023-04-04T20:56:02Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@JangleGumps](https://forum.sensor.community/u/JangleGumps)
#### Post date: [April 4, 2023, 8:56pm UTC](https://forum.sensor.community/t/nodemcu-does-not-create-a-wifi-network/1983/1 "2023-04-04T20:56:02Z")
When I boot my NodeMCU sensor, with all my WiFi networks disabled, it does not create it’s own WiFi network that allows me to change the settings.
In the log, it spends a long time (minutes) at the “`Starting Webserver... (IP unset)`” stage, and then displays “`WiFi connected, IP is: (IP unset)`”.
When I then look for the WiFi network it should have created (because the WiFi network it used to try to connect to is completely disabled), it hasn’t created its own WiFi network.
Any ideas as to how to solve this?
The log is
> Connected.
> failed to open config file.
> output debug text to displays…
> Connecting to Freifunk-disabled
> …
> output debug text to displays…
> Starting WiFiManager
> AP ID: airRohr-12623506
> Password:
> scan for wifi networks…
> AP Password is:
> Starting Webserver… (IP unset)
> Connecting to Freifunk-disabled
> ---- Result Webconfig ----
> WLANSSID: Freifunk-disabled
> PPD: 0
> SDS: 1
> PMS: 0
> HPM: 0
> SPS30: 0
> DHT: 1
> DS18B20: 0
> HTU21D: 0
> BMP: 0
> DNMS: 0
> SensorCommunity: 1
> Madavi: 1
> CSV: 0
> Autoupdate: 1
> Display: 0
> LCD 1602: 0
> Debug: 3
> …
> WiFi connected, IP is: (IP unset)
> Starting Webserver… (IP unset)
> ChipId: 12623506
> MAC Id: ecfabcc09e92
> Read SDS…:
> Stopping SDS011…
> Read DHT…
> Send to :
> sensor.community
> [Madavi.de](http://Madavi.de)
> Auto-Update active…`
---
### Author:  [@ricki-z](https://forum.sensor.community/u/ricki-z)
#### Post date: [April 5, 2023, 12:26am UTC](https://forum.sensor.community/t/nodemcu-does-not-create-a-wifi-network/1983/2 "2023-04-05T00:26:37Z")
There is a line ‘Starting WiFiManager’, followed by the ID and the password. How long does the debug output stops there? There is a configurable timeout, the default is 600 seconds. After that timeout the config mode will stop and the firmware continues with the the values set before or the default values. So if the timeout for the config mode was changed then this mode may stop to fast to configure anything.
---
### Author:  [@pjg](https://forum.sensor.community/u/pjg)
#### Post date: [April 5, 2023, 4:39am UTC](https://forum.sensor.community/t/nodemcu-does-not-create-a-wifi-network/1983/3 "2023-04-05T04:39:43Z")
In that case, erase everything with the flasher and flash again.
---
### Author:  [@JangleGumps](https://forum.sensor.community/u/JangleGumps)
#### Post date: [April 5, 2023, 12:49pm UTC](https://forum.sensor.community/t/nodemcu-does-not-create-a-wifi-network/1983/4 "2023-04-05T12:49:36Z")
The log is after erasing and flashing again with the 3.2 flasher.
There is an approx 1 second pause around the ‘Starting WiFiManager’ line.
There is a long (minutes) pause at the Starting Webserver… (IP unset) line.
---
### Author:  [@ricki-z](https://forum.sensor.community/u/ricki-z)
#### Post date: [April 5, 2023, 9:24pm UTC](https://forum.sensor.community/t/nodemcu-does-not-create-a-wifi-network/1983/5 "2023-04-05T21:24:17Z")
@JangleGumps So it’s like described. The config mode is configured to run only a second (or none …). Directly after that the device tries to connect to the default wifi network, won’t get a connection and with that no ip address (‘ip not set’).
The newer Flashing Tool versions should have a function to erase the locally saved config file. With that the configuration will be reset and you can start over.