Just to be sure, no trailing spaces in the name/setting?

Nope. And I'm not sure about casing on the ap name. But I matched that as well.

I upgraded this node MCU from an older version, could it be that it is stuck on some old config? I already erased the flash and did a factory reset. Any thing else I can do?

You did flash it with a 4MB blank bin file?

Yes, also did that

Other ESP Easy units, do they connect?

Yes, but they are way older version.

Any you haven't tried another unit with the a new version? Please do!

I have same issue. I've been trying to solve it for several days. It only happens with Wemos NodeMCU modules:

Log:
312 : EVENT: System#Wake
333 : WIFI : Set WiFi to STA
365 : WIFI : Connecting lada attempt #0
478 : EVENT: System#Boot
1832 : WD : Uptime 0 ConnectFailures 0 FreeMem 26224

11276 : WIFI : Connecting lada attempt #1

26789 : EVENT: WiFi#Disconnected
26804 : WIFI : Disconnected! Reason: '(200) Beacon timeout' Connected for 15 s
27276 : WIFI : Connecting lada1 attempt #2
30133 : EVENT: WiFi#Disconnected
30147 : WIFI : Disconnected! Reason: '(201) No AP found' Connected for 2856 ms
30276 : WIFI : Connecting lada1 attempt #3
31832 : WD : Uptime 1 ConnectFailures 0 FreeMem 26192
33133 : EVENT: WiFi#Disconnected
33148 : WIFI : Disconnected! Reason: '(201) No AP found' Connected for 2857 ms
33276 : WIFI : Connecting lada attempt #4
36133 : EVENT: WiFi#Disconnected
36147 : WIFI : Disconnected! Reason: '(201) No AP found' Connected for 2856 ms
36276 : WIFI : Connecting lada attempt #5
41027 : EVENT: WiFi#Disconnected
41044 : WIFI : Disconnected! Reason: '(4) Assoc expire' Connected for 4751 ms
41276 : WIFI : Set WiFi to AP+STA
42197 : WIFI : AP Mode ssid will be NodeMCU7_47 with address 192.168.4.1
42197 : WIFI : Connecting lada1 attempt #6
45055 : EVENT: WiFi#Disconnected
45075 : WIFI : Disconnected! Reason: '(201) No AP found' Connected for 2856 ms
45277 : WIFI : AP Mode ssid will be NodeMCU7_47 with address 192.168.4.1
45277 : WIFI : Connecting lada1 attempt #7
48134 : EVENT: WiFi#Disconnected
48150 : WIFI : Disconnected! Reason: '(201) No AP found' Connected for 2857 ms
48277 : WIFI : AP Mode ssid will be NodeMCU7_47 with address 192.168.4.1
48277 : WIFI : Connecting lada attempt #8

Wemos D1 mini and clone D1 mini modules work well.

I got that one pictured (at my office) I might be able to test it myself on Friday when I'm back.

Can you give the information from the sysinfo page?
Just to check if there is some difference in the nodes.

Oh and could you maybe try to set the wifi credentials using the (latest) version of @Grovkillen flash tool (included in the zip) and als try to set the IP settings to static. (in a second attempt)

I've just upgrade to mega-20181107 (file ESP_Easy_mega-20181107_normal_ESP8266_4096.bin) and set the wifi credentials using the (latest) version of @Grovkillen flash tool (included in the zip) and now it's working.

Sysinfo page:

Unit: | 47
-- | --
Local Time: | 2018-11-07 16:15:12
Uptime: | 0 days 0 hours 5 minutes
Load: | 3.30% (LC=12452)
Free Mem: | 17320 (14984 - sendContentBlocking)
Free Stack: | 3584 (1728 - ExecuteCommand)
Boot: | Manual reboot (7)
Reset Reason: | External System
Network ❔
Wifi: | 802.11N (RSSI -49 dB)
IP config: | DHCP
IP / subnet: | 192.168.44.192 / 255.255.255.0
GW: | 192.168.44.1
Client IP: | 192.168.44.150
DNS: | 1.0.0.1 / 1.1.1.1
Allowed IP Range: | All Allowed
STA MAC: | 60:01:94:35:C8:BC
AP MAC: | 62:01:94:35:C8:BC
SSID: | lada (06:18:D6:C1:B0:03)
Channel: | 1
Connected: | 5 m 9 s
Last Disconnect Reason: | (1) Unspecified
Number reconnects: | 0
Firmware
Build:⋄ | 20102 - Mega
Libraries:⋄ | ESP82xx Core 2_4_2, NONOS SDK 2.2.1(cfd48f3), LWIP: 2.0.3
GIT version:⋄ | mega-20181107
Plugins:⋄ | 46 [Normal]
Build Md5: | 9ea46e7428c174166f90298a7ed1a5f2
Md5 check: | passed.
Build time:⋄ | Nov 7 2018 03:33:40
Binary filename:⋄ | ESP_Easy_mega-20181107_normal_ESP8266_4096.bin
System Status
Syslog Log Level: | None
Serial Log Level: | Debug
Web Log Level: | None
ESP board
ESP Chip ID: | 3524796 (0x35C8BC)
ESP Chip Freq: | 80 MHz
ESP Board Name: | PLATFORMIO_ESP12E
Storage
Flash Chip ID: | Vendor: 0xEF Device: 0x4016
Flash Chip Real Size: | 4096 kB
Flash IDE Size: | 4096 kB
Flash IDE speed: | 40 MHz
Flash IDE mode: | DIO
Flash Writes: | 2 daily / 2 boot
Sketch Size: | 744 kB (2324 kB free)
SPIFFS Size: | 934 kB (860 kB free)

So we can close this issue then? :+1:

Yesterday I was testing mega-20181023 version that did not work and mega-20181022 version that did work. Now I'm going to test mega-20181106 version...

please, do not close it yet

Downgrade to mega-20181106 version via OTA ==> WiFi don't work

Flash ESP_Easy_mega-20181106_normal_ESP8266_4096.bin with ESP Easy Flasher ==> WiFi don't work

So yesterdays release is misbehaving. What have changed between those two releases? Not much?

I changed a lot of strings to reduce amount of space used.

But you changed it to work?

But you changed it to work?

Yesterday I only merged the commits regarding OTA updates
So it should mainly be string related.

I hope I did proper search/replace queries, but maybe something may have changed, regarding wifi setup.

Today's release seems to work, yesterdays don't. Weird, build related perhaps.

Ah, maybe I fixed something too in the process ;)
Sorry, those things may happen..

ESP_Easy_mega-20181107_normal_ESP8266_4096 flashed via OTA ==> WiFi works OK

So today's release seems to work, but no. I've compiled from sources in the zip file and WiFi doesn't work again.
I've flashed my compiled version on D1 mini and WiFi works OK.

Have you tried to compile it twice before flashing? (assuming you're using PlatformIO)
And there seems to be a difference in alignment of data when building on Windows or Linux (according to threads on Tasmota/Espruna issues lists)

No, I haven't. I use PlatformIO with VS code on Windows 10.
OK, I'm going to compile twice and try it. I tell you.

@TD-er I 've runned task PlatformIO: Build (normal_ESP8266_4096) twice and get this log. Do you mean this?

Executing task: C:Userssalva.platformiopenvScriptsplatformio.exe run --environment normal_ESP8266_4096 <

Processing normal_ESP8266_4096 (framework: arduino; platform: [email protected]; board: esp12e)

Verbose mode can be enabled via -v, --verbose option
CONFIGURATION: https://docs.platformio.org/page/boards/espressif8266/esp12e.html
PLATFORM: Espressif 8266 > Espressif ESP8266 ESP-12E
SYSTEM: ESP8266 80MHz 80KB RAM (4MB Flash)
Converting ESPEasy.ino
C:/Users/salva/Documents/GitHub/ESPEasy_mega-20181107/source/src/_P016_IR.ino:72:0: warning: "P016_TIMEOUT" redefined [enabled by default]

define P016_TIMEOUT 15U // Suits most messages, while not swallowing many repeats.

^
C:/Users/salva/Documents/GitHub/ESPEasy_mega-20181107/source/src/_P016_IR.ino:68:0: note: this is the location of the previous definition

define P016_TIMEOUT 50U // Some A/C units have gaps in their protocols of ~40ms.

^
Library Dependency Finder -> http://bit.ly/configure-pio-ldf
LDF MODES: FINDER(chain) COMPATIBILITY(soft)
Collected 56 compatible libraries
Scanning dependencies...
Dependency Graph
|-- 1.0
| |-- 1.0
| |-- 1.0
| | |-- 1.0
|-- 2.0.0
| |-- 3.3.1
|-- 1.0
|--
|-- 1.0
|-- 1.0.0
| |-- 1.0
|-- 5.13.2
|-- 1.0.2
|-- 3.2.7
| |-- 1.0
| |-- 1.0
|--
| |-- 1.0
|-- 1.0
|-- 0.0.1
| |-- 3.3.1
|-- 0.0.1
|-- 1.0
|-- | |-- 1.0
|-- 1.0.2
| |-- 1.0.2
| |-- 1.0
|-- 1.0
| |-- 1.0
| |--
| | |-- 1.0
|-- |-- 3.3.1
|-- 1.4.2
| |-- 1.0
|--
| |-- 1.0
|-- 1.0.4
| |-- 1.0
|-- 2.6
|-- 1.0.1
| |-- 1.0
|-- 1.1.0
| |-- 1.0
|--
| |-- 1.0
|--
| |-- 1.0
|-- 1.0.0
|-- 1.0
| |-- 1.0
|--
| |-- 1.0
|-- 1.0.6
|--
|-- 0.0.1
| |-- 1.0
Compiling .pioenvsnormal_ESP8266_4096libdc8pubsubclientPubSubClient.cpp.o
Compiling .pioenvsnormal_ESP8266_4096srcESPEasy.ino.cpp.o
Linking .pioenvsnormal_ESP8266_4096firmware.elf
Retrieving maximum program size .pioenvsnormal_ESP8266_4096firmware.elf
Building .pioenvsnormal_ESP8266_4096firmware.bin
Checking size .pioenvsnormal_ESP8266_4096firmware.elf
Memory Usage -> http://bit.ly/pio-memory-usage
DATA: [====== ] 55.4% (used 45376 bytes from 81920 bytes)
PROGRAM: [======= ] 73.2% (used 764896 bytes from 1044464 bytes)
============================================== [SUCCESS] Took 57.89 seconds ==============================================

======================================================= [SUMMARY] =======================================================
Environment esp-wrover-kit_test_1M8_partition [SKIP]
Environment esp32dev [SKIP]
Environment esp32test_1M8_partition [SKIP]
Environment normal_ESP8266_1024 [SKIP]
Environment minimal_ESP8266_1024_OTA [SKIP]
Environment minimal_ESP8285_1024_OTA [SKIP]
Environment normal_core_241_ESP8266_1024 [SKIP]
Environment normal_ESP8285_1024 [SKIP]
Environment normal_WROOM02_2048 [SKIP]
Environment normal_ESP8266_4096 [SUCCESS]
Environment normal_core_241_ESP8266_4096 [SKIP]
Environment normal_IR_ESP8266_4096 [SKIP]
Environment test_ESP8266_1024 [SKIP]
Environment test_ESP8285_1024 [SKIP]
Environment test_WROOM02_2048 [SKIP]
Environment test_ESP8266_4096 [SKIP]
Environment test_ESP8266_4096_VCC [SKIP]
Environment dev_ESP8266_1024 [SKIP]
Environment dev_ESP8285_1024 [SKIP]
Environment dev_WROOM02_2048 [SKIP]
Environment dev_ESP8266_4096 [SKIP]
Environment dev_ESP8266PUYA_1024 [SKIP]
Environment dev_ESP8266PUYA_1024_VCC [SKIP]
Environment hard_SONOFF_POW [SKIP]
Environment hard_SONOFF_POW_R2_4M [SKIP]
Environment hard_Shelly_1 [SKIP]
Environment hard_Ventus_W266 [SKIP]
============================================== [SUCCESS] Took 57.94 seconds ==============================================

Las tareas reutilizarán el terminal, presione cualquier tecla para cerrarlo.

Executing task: C:Userssalva.platformiopenvScriptsplatformio.exe run --environment normal_ESP8266_4096 <

Processing normal_ESP8266_4096 (framework: arduino; platform: [email protected]; board: esp12e)

Verbose mode can be enabled via -v, --verbose option
CONFIGURATION: https://docs.platformio.org/page/boards/espressif8266/esp12e.html
PLATFORM: Espressif 8266 > Espressif ESP8266 ESP-12E
SYSTEM: ESP8266 80MHz 80KB RAM (4MB Flash)
Converting ESPEasy.ino
C:/Users/salva/Documents/GitHub/ESPEasy_mega-20181107/source/src/_P016_IR.ino:72:0: warning: "P016_TIMEOUT" redefined [enabled by default]

define P016_TIMEOUT 15U // Suits most messages, while not swallowing many repeats.

^
C:/Users/salva/Documents/GitHub/ESPEasy_mega-20181107/source/src/_P016_IR.ino:68:0: note: this is the location of the previous definition

define P016_TIMEOUT 50U // Some A/C units have gaps in their protocols of ~40ms.

^
Library Dependency Finder -> http://bit.ly/configure-pio-ldf
LDF MODES: FINDER(chain) COMPATIBILITY(soft)
Collected 56 compatible libraries
Scanning dependencies...
Dependency Graph
|--
|-- 1.0
| |-- 1.0
| |-- 1.0
| | |-- 1.0
|-- 1.0
|-- 0.0.1
| |-- 1.0
|-- 1.0.2
| |-- 1.0.2
| |-- 1.0
|-- 1.0.0
| |-- 1.0
|-- 5.13.2
|-- 1.0.2
|-- 3.2.7
| |-- 1.0
| |-- 1.0
|--
| |-- 1.0
|-- 1.0
|-- 0.0.1
| |-- 3.3.1
|-- 1.0
|-- 0.0.1
|-- 2.0.0
| |-- 3.3.1
|-- 1.0
|-- | |-- 1.0
|-- 1.0.6
|-- 1.0
| |-- 1.0
| |--
| | |-- 1.0
|-- |-- 3.3.1
|-- 1.4.2
| |-- 1.0
|--
| |-- 1.0
|-- 1.0.4
| |-- 1.0
|--
|-- 1.0.1
| |-- 1.0
|-- 1.1.0
| |-- 1.0
|--
| |-- 1.0
|--
| |-- 1.0
|-- 1.0.0
|-- 1.0
| |-- 1.0
|--
| |-- 1.0
|-- 2.6
Compiling .pioenvsnormal_ESP8266_4096srcESPEasy.ino.cpp.o
Linking .pioenvsnormal_ESP8266_4096firmware.elf
Retrieving maximum program size .pioenvsnormal_ESP8266_4096firmware.elf
Building .pioenvsnormal_ESP8266_4096firmware.bin
Checking size .pioenvsnormal_ESP8266_4096firmware.elf
Memory Usage -> http://bit.ly/pio-memory-usage
DATA: [====== ] 55.4% (used 45368 bytes from 81920 bytes)
PROGRAM: [======= ] 73.2% (used 764896 bytes from 1044464 bytes)
============================================== [SUCCESS] Took 55.91 seconds ==============================================

======================================================= [SUMMARY] =======================================================
Environment esp-wrover-kit_test_1M8_partition [SKIP]
Environment esp32dev [SKIP]
Environment esp32test_1M8_partition [SKIP]
Environment normal_ESP8266_1024 [SKIP]
Environment minimal_ESP8266_1024_OTA [SKIP]
Environment minimal_ESP8285_1024_OTA [SKIP]
Environment normal_core_241_ESP8266_1024 [SKIP]
Environment normal_ESP8285_1024 [SKIP]
Environment normal_WROOM02_2048 [SKIP]
Environment normal_ESP8266_4096 [SUCCESS]
Environment normal_core_241_ESP8266_4096 [SKIP]
Environment normal_IR_ESP8266_4096 [SKIP]
Environment test_ESP8266_1024 [SKIP]
Environment test_ESP8285_1024 [SKIP]
Environment test_WROOM02_2048 [SKIP]
Environment test_ESP8266_4096 [SKIP]
Environment test_ESP8266_4096_VCC [SKIP]
Environment dev_ESP8266_1024 [SKIP]
Environment dev_ESP8285_1024 [SKIP]
Environment dev_WROOM02_2048 [SKIP]
Environment dev_ESP8266_4096 [SKIP]
Environment dev_ESP8266PUYA_1024 [SKIP]
Environment dev_ESP8266PUYA_1024_VCC [SKIP]
Environment hard_SONOFF_POW [SKIP]
Environment hard_SONOFF_POW_R2_4M [SKIP]
Environment hard_Shelly_1 [SKIP]
Environment hard_Ventus_W266 [SKIP]
============================================== [SUCCESS] Took 55.96 seconds ==============================================

Yep, building/compiling it twice before flashing.

Since uploading will also compile it, you can also build it and then flash it via serial. (upload ... in platformIO)

Sorry, WiFi still doesn't work

How do you set the settings, serial or through AP?

With your tool: ESP Easy Flasher

Ok, then that's not the problem 😎

I've to disconnect now. I will connect again this night.

Hi

I have couple of these modules and i have a same problem with them. No AP found, Beacon Timeout, Assoc expire errors, but the scanwifi serial command is presents my AP on the list.

Usually i update the firmware to the latest on the the modules when the new firmware is released.

If i update, some fw release are working fine some not. If the module can't connect i need to rollback to the previous fw. Sometimes I need to erase the module (blank_4MB.bin). Usually then i upload the 20180818 release which is always working fine. And after i upload the latest OK release.

I'm away from home but at the weekend i can test which fw is ok and which isn't. Maybe it helps to investigate and fix the problem.

Thx
T

Can someone make a detailed picture of the ESP chip?
I have had some discussion in the background via email and one reports the module has some "ECO Plug" label on it.
One of the suggestions was to add a number of delay(1) calls until the wifi connection is made.

If someone could make a really detailed image of the module (e.g. using a flatbed scanner, rotate module in several orientations compared to the scan direction), then please also make a detailed picture of the 3.3v and GND PCB traces to the ESP module and the voltage regulator.

I flashed the firmware of today: mega-20181107 (ESP82xx Core 2_4_2, NONOS SDK 2.2.1(cfd48f3), LWIP: 2.0.3)
First I flashed the blank and then the actual. Wifi works again :-)

I use this module as a temp sensor (DHT22)
The sensor works, but MQTT does not. Also the log page is and stays empty.

@ymoona what is your setting for weblog level - None?

Btw mqtt does work. Just not without credentials, probably a config issue on my broker.

Logging is configured for debug but it shows nothing. But everything else works. So I am ok with closing the issue

Hello

Images as promised.

I hope I'll have a time Tomorrow to test the firmwares which is ok which not.

Thx
T

If possible, can you try to power one of the problematic nodes with 5V from the GND/Vin pin (not the USB port) ?

Some of my modules powered with 3.3v through the Vin some uses the USB. All of these modules behaving similar.

5V tested: No joy :-(

Off: The 1024 VCC fw is disappeared from the last release. Is it possible compile for the future?

Thx
T

I only removed the PUYA builds.
If that was the only 1 MB VCC build, then we could add some other for that.

ESP_Easy_mega-20181110_test_ESP8266_4096_VCC.bin

>wifiscan
WIFI : SSID Scan start
WIFI : 4 networks found
WIFI : 1: eir90963965-2.4G 58:D7:59:5B:E0:70 Ch:2 (-82dBm) WPA/WPA2/PSK
WIFI : 2: TNCAPE8A29B C4:EA:1D:C3:BC:7F Ch:8 (-88dBm) WPA/WPA2/PSK
WIFI : 3: VM8BD6864 AC:22:05:79:96:58 Ch:11 (-87dBm) WPA/WPA2/PSK
WIFI : 4: Horizon Wi-Free AE:22:15:79:96:58 Ch:11 (-92dBm) 


Ok
215912 : Command: wifiscan
219603 : WIFI : AP Mode ssid will be Test21_WMD1_21 with address 192.168.4.1
219604 : WIFI : Connecting TNCAPE8A29B attempt #38
221806 : EVENT: WiFi#Disconnected
221811 : WIFI : Disconnected! Reason: '(201) No AP found' Connected for 2199 ms

@redskinhu So it isn't fixed and the same nodes are still problematic and the ones that worked fine still work?

Hi

Homework is done....

I tested this WeMos D1 clone. 5V power supply, external serial TTL USB connection. Couple NG fw is tested an another D1 module (same result).

Method:

1. Full erase (serial): blank_4MB.bin
2. Upload (serial) the ESP_Easy_mega-20180818_test_ESP8266_4096_VCC.bin, setup AP and NTP if necessary (this firmware is tested, always can connect)
3. OTA upload the next desired fw (test 4096 VCC): ESP_Easy_mega-20180221_test_ESP8266_4096.bin - ESP_Easy_mega-20181111_test_ESP8266_4096_VCC.bin
4. If the firmware can connect go to step 3.
5. If the updated fw can't connect to the AP after ~10 attempt go to step 2.

Results:

• OK - Connected to the WiFi
• NG - "No AP found" message, but the AP on the list of the AP's (serial wifiscan)
• NG* - Beacon timeout, Assoc leave, Auth expire errors
• NG** - Connected, PING ok but ERR_EMPTY_RESPONSE error in the browser
• NG* - Connected, couple PING reply after start but after "Request timeout" and/or "Destination host is unreachable"

I hope someone can see the pattern....

FW Date | Result |   | FW Date | Result |   | FW Date | Result
-- | -- | -- | -- | -- | -- | -- | --
20180221 | NG* |   | 20180501 | NG |   | 20180903 | OK
20180224 | OK |   | 20180502 | NG |   | 20180904 | OK
20180228 | OK |   | 20180503 | NG* |   | 20180908 | NG*
20180302 | OK |   | 20180504 | OK |   | 20180909 | OK
20180303 | OK |   | 20180505 | OK |   | 20180910 | OK
20180304 | OK |   | 20180506 | OK |   | 20180914 | NG
20180305 | OK |   | 20180507 | OK |   | 20180922 | NG
20180307 | OK |   | 20180510 | OK |   | 20180923 | NG
20180308 | OK |   | 20180511 | NG |   | 20180924 | OK
20180309 | NG |   | 20180512 | NG |   | 20180927 | OK
20180310 | OK |   | 20180513 | NG* |   | 20180930 | NG
20180311 | OK |   | 20180515 | OK |   |   |  
20180312 | OK |   | 20180516 | OK |   |   |  
20180313 | OK |   | 20180517 | OK |   | 20181001 | NG
20180314 | OK |   | 20180518 | NG |   | 20181002 | OK
20180315 | OK |   | 20180519 | OK |   | 20181003 | OK
20180316 | OK |   | 20180522 | NG |   | 20181004 | OK
20180319 | NG* |   | 20180524 | NG |   | 20181007 | OK
20180320 | NG |   |   |   |   | 20181008 | OK
20180321 | NG |   |   |   |   | 20181011 | OK
20180322 | NG* |   | 20180609 | OK |   | 20181014 | NG
20180323 | OK |   | 20180611 | NG |   | 20181015 | OK
20180324 | OK |   | 20180613 | NG |   | 20181016 | NG
20180326 | OK |   | 20180614 | NG* |   | 20181017 | OK
20180327 | OK |   | 20180615 | OK |   | 20181020 | OK
20180328 | OK |   | 20180618 | OK |   | 20181021 | OK
20180329 | OK |   | 20180619 | OK |   | 20181022 | OK
20180330 | OK |   | 20180621 | OK |   | 20181023 | OK
20180331 | OK |   | 20180624 | NG |   | 20181025 | NG
  |   |   | 20180625 | NG |   | 20181026 | OK
  |   |   |   |   |   | 20181027 | OK
20180402 | NG |   |   |   |   | 20181028 | NG
20180403 | NG* |   | 20180708 | OK |   | 20181030 | OK
20180405 | NG* |   | 20180710 | OK |   | 20181031 | OK
20180409 | NG* |   | 20180712 | OK |   |   |  
20180410 | NG* |   | 20180714 | OK |   |   |  
20180413 | NG |   | 20180716 | OK |   | 20181101 | OK
20180414 | NG |   | 20180719 | OK |   | 20181105 | NG
20180415 | NG |   | 20180720 | OK |   | 20181106 | OK
20180416 | OK |   | 20180722 | OK |   | 20181107 | OK
20180417 | OK |   | 20180723 | NG |   | 20181108 | NG
20180418 | NG |   |   |   |   | 20181109 | NG
20180419 | NG* |   |   |   |   | 20181110 | NG
20180420 | NG |   | 20180801 | OK |   | 20181111 | NG
20180421 | NG |   | 20180802 | OK |   | 20181112 | NG
20180422 | NG* |   | 20180804 | OK |   | 20181117 | NG 
20180423 | NG |   | 20180808 | NG |   | 20181120 | NG
20180424 | NG |   | 20180809 | OK |   | 20181121 | NG
20180426 | OK |   | 20180815 | OK |   | 20181122 | OK  
20180428 | NG |   | 20180818 | OK |   | 20181123 | OK
20180429 | NG |   | 20180822 | NG |   | 20181124 | OK
20180430 | OK |   | 20180826 | OK |   | 20181125 | NG 

OK, that must have been the post which took the most preparation ever!
Between March and somewhere in May we had issues with the nightly builds and those builds resulted in lots of WiFi issues.
One of the most frustrating moments in development, since I was also working on the event based WiFi and the reports were totally not reproducible.

My initial thought on such random looking OK/NG reports is there must be some kind of string/char-array which is just allocated 1 byte too short, or not null-terminated.
It is then up to the compiler and the semi random behavior of the memory allocation to move around blocks, which may yield an extra unused byte after that faulty reserved block.

How long is the SSID of your network and how long your key?
Do they contain spaces or other "strange" characters?

SSID: TNCAPE8A29B
Key: 9 char, 2 capital letters and numbers, nothing strange.

Yes, I got the first modules when the event based WiFi was presented. And i had many "non working" modules... I thought my new shiny modules are faulty and i spent lots of time to find the solution. And one thing about these modules. They are looks slower than the generic esp07/12 modules (ex: webpage loading). Switching between pages ~3-5s, on ESP07/12 ~1s. Maybe it helps.

Maybe you can compare the flash types?

I can imagine the flash chip also returns some reading/writing parameters which are used by the core libraries.
It may correlate with the number of disconnect occurrences, but I doubt it will have effect on the "cannot even connect" symptom you are experiencing.

I removed the shield one of my ESP07: W25Q32JVSIQ
WeMos D1 clone: GD25Q32CSIG

The 2nd is slightly slower 120 vs 133Mhz. I think it is not too big to cause this speed difference.

I have couple W25Q32BVSIG, if i replace the GD25Q32CSIG on the board it could help to investigate?

It is always nice to try, but then you also take away a reproducible node to check if a future fix is working.

I have some unopened spare.... too. :-)

Maybe you can also see on the (new) timing stats page how long a write action takes.

Remember, the stats are reset when you load the page.

• load timing stats page
• perform some write (e.g. change some setting in a plugin)
• load timing stats page and check the max. time needed to save a file.

@redskinhu nice work, maybe this is related to poor antenna connection?
Try host AP with your mobile phone and connect to it with ESP.

I think this problem isn't related to the antenna. The module was on a same location when I made the tests. If one fw can connect and an another is not it could be sw related error.

One of my modules sitting beside the router and it is behaving similar. And i tried the connect to my phone mobile hotspot which was about 2cm away when i did the early investigation. No joy.

I have one ESP01 PUYA and ESP07S beside me. I setup the same config on that modules too (ESP_Easy_mega-20181107). I checked the write timings (I saved the same generic sysinfo task on all modules.):

WeMos D1 clone

Description | Function | #calls | call/sec | min (ms) | Avg (ms) | max (ms)
-- | -- | -- | -- | -- | -- | --
Save File |   | 3 | 0.14 | 29.616 | 42.094 | 64.698

ESP07S

Description | Function | #calls | call/sec | min (ms) | Avg (ms) | max (ms)
-- | -- | -- | -- | -- | -- | --
Save File |   | 3 | 0.26 | 24.505 | 44.575 | 64.832

ESP01

Description | Function | #calls | call/sec | min (ms) | Avg (ms) | max (ms)
-- | -- | -- | -- | -- | -- | --
Save File |   | 3 | 0.01 | 268.785 | 399.269 | 660.206

• Behaving the ESP01 is obvious for me: PUYA. But this module is same fast like ESP07S.
• But the two other behaving similar, so i think not the flash cause the speed difference.

I replaced the flash but the new looks not compatible. :-(
So i put back the old. It works. :-)

That's all for today.

ESP_Easy_mega-20181112 tested: NG

Any suggestion to do to continue the investigation?

Still using the test_ESP8266_4096_VCC.bin build?

yes

@redskinhu ERROR log please

@TD-er it is really hard to understand wifi connection/management code.
I could try to move all stuff to one place first (EspEasyWifi.ino) and next we can think how to modify this part of code to be more readable, what do you think?

Hello

Small explanation about this Log:

• Log level: Debug dev
• ESP_Easy_mega-20181107_test_ESP8266_4096_VCC.bin was installed. It booting and connecting to the AP and MQTT publishing the IP and MAC .
• After I started the OTA upload to ESP_Easy_mega-20181112_test_ESP8266_4096_VCC.bin.
• Module reboots and tries to connect to the AP. After 10 retries I stopped the logging.

INIT : Booting version: mega-20181107 (ESP82xx Core 2_4_2, NONOS SDK 2.2.1(cfd48f3), LRuleDebug: 101: publish home/%sysname%/ipaddress,%ip%
WRuleDebug: 101: publish home/%sysname%/macaddress,%mac%
IP: 2.0.3)mode : sta(84:f3:eb:8e:61:8c)
add if0
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug: 100: time#initialized do

100 : INIT : Warm boot #3 - Restart Reason: Software/System restart
102 : FS   : Mounting.RuleDebug: 101: publish home/%sysname%/ipaddress,%ip%
..RuleDebug: 101: publish home/%sysname%/macaddress,%mac%

127 : FS   : Mount successful, used 76053 bytes of 957314
502 : CRC  : program checksum       ...OK
513 : CRC  : SecuritySettings CRC   ...OK 
616 : INIT : Free RAM:25384
617 : INIT : I2C
617 : INIT : SPI not enabled
652 : INFO : Plugins: 73 [Normal] [Testing] (ESP82xx Core 2_4_2, NONOS SDK 2.2.1(cfd48f3), LWIP: 2.0.3)
653 : EVENT: System#Wake
697 : WIFI : Set WiFi to STA
731 : WIFI : Connecting TNCAPE8A29B attempt #0
844 : EVENT: System#Boot
2196 : WD   : Uptime 0 ConnectFailures 0 FreeMem 23128
scandone
state: 0 -> 2 (b0)
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 20
cnt 

connected with TNCAPE8A29B, channel 8
dhcp client start...
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug: 100: time#initialized do
5574 : WIFI : Connected! AP: TNCAPE8A29B (C4:EA:1D:C3:BC:7F) Ch: 8 Duration: 4842 ms
5575 : ERuleDebug: 101: publish home/%sysname%/ipaddress,%ip%
VENRuleDebug: 101: publish home/%sysname%/macaddress,%mac%
T: WiFi#ChangedAccesspoint
ip:192.168.1.247,mask:255.255.255.0,gw:192.168.1.1
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug: 100: time#initialized do
5691 : WIFI : DHCP IP: 192.168.1.247 (Test20-WMD1-20) GW: 192.168.1.1 SNRuleDebug: 101: publish home/%sysname%/ipaddress,%ip%
: 255.RuleDebug: 101: publish home/%sysname%/macaddress,%mac%
255.255.0   duration: 117 ms
5703 : EVENT: WiFi#Connected
5722 : Webserver: start
5723 : WIFI  : Arduino wifi status: WL_CONNECTED ESPeasy internal wifi status: ESPEASY_WIFI_SERVICES_INITIALIZED
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug: 100: time#initialized do
5803 : MQTT : Intentional reconnect
5805 : Read settings: ControllerSettings index: 0
5877 : MQRuleDebug: 101: publish home/%sysname%/ipaddress,%ip%
TT RuleDebug: 101: publish home/%sysname%/macaddress,%mac%
: Connected to broker with client ID: Test20_WMD1_20
5880 : Subscribed to: home/Test20_WMD1/#
5882 : EVENT: MQTT#Connected
5905 : EVENT: MQTT#Connected Processing time:23 milliSeconds
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug: 110: time#initialized do
6640 : NTP  : NTP host 193.1.31.66 (193.1.31.66) queried
6682 : NTP  : NTP replRuleDebug: 111: publish home/test20_wmd1/ipaddress,192.168.1.247
ied: delay 41 mSec Accuracy increased by 0.370 seconds
6684 : Current Time Zone:  DST time staRuleDebug: 111: publish home/test20_wmd1/macaddress,84:f3:eb:8e:61:8c
rt: 2018-03-25 02:00:00 offset: 60 minSTD time start: 2018-10-28 03:00:00 offset: 0 min
6687 : EVENT: Time#IniRuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug: 100: time#initialized do
tialized
RuleDebug: 101: publish home/%sysname%/ipaddress,%ip%

RuleDebug: 101: publish home/%sysname%/macaddress,%mac%
6698 : ACT  : Publish home/Test20_WMD1/IPaddress,192.168.1.247
6713 : ACT  : Publish home/Test20_WMD1/MACaddress,84:F3:EB:8E:61:8C
6722 : EVENT: Time#Initialized Processing time:34 milliSeconds
6723 : EVENT: Clock#Time=Mon,22:23
6742 : EVENT: Clock#Time=Mon,22:23 Processing time:19 milliSeconds
6747 : Command: publish
6751 : Command: publish
10981 : UDP  : B4:E6:2D:14:AE:F5,192.168.1.215,15
Update: ESP_Easy_mega-20181112_test_ESP8266_4096_VCC.bin
sleep disable
................................pm open,type:0 0
...................................................................................................................................................................................................................................................................................................................................................................................................Update Success: 857648
Rebooting...

 ets Jan  8 2013,rst cause:2, boot mode:(3,6)

load 0x4010f000, len 1384, room 16 
tail 8
chksum 0x2d
csum 0x2d
vbb28d4a3
@cp:0
ld
⸮Urules1.txt 1
rules2.txt 0
rules3.txt 0
rules4.txt 0
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug: 100: time#initialized do

RuleDebug: 101: publish home/%sysname%/ipaddress,%ip%
RuleDebug: 101: publish home/%sysname%/macaddress,%mac%
mode : sta(84:f3:eb:8e:61:8c)
add if0
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug: 100: time#initialized do
RuleDebug: 101: publish home/%sysname%/ipaddress,%ip%
RuleDebug: 101: publish home/%sysname%/macaddress,%mac%
13048 : WD   : Uptime 0 ConnectFailures 0 FreeMem 18912
scandone
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug: 100: time#initialized do
14449 : EVENT: WiFi#Disconnected
RuleDebug: 101: publish home/%sysname%/ipaddress,%ip%
RuleDebug: 101: publish home/%sysname%/macaddress,%mac%
14462 : WIFI : Disconnected! Reason: '(201) No AP found' Connected for 2860 ms
14495 : WIFI : Connecting TNCAPE8A29B attempt #1
scandone
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug: 100: time#initialized do
17355 : EVENT: WiFi#Disconnected
RuleDebug: 101: publish home/%sysname%/ipaddress,%ip%
RuleDebug: 101: publish home/%sysname%/macaddress,%mac%
17368 : WIFI : Disconnected! Reason: '(201) No AP found' Connected for 2859 ms
17495 : WIFI : Connecting TNCAPE8A29B attempt #2
scandone
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug: 100: time#initialized do
20356 : EVENT: WiFi#Disconnected
RuleDebug: 101: publish home/%sysname%/ipaddress,%ip%
RuleDebug: 101: publish home/%sysname%/macaddress,%mac%
20369 : WIFI : Disconnected! Reason: '(201) No AP found' Connected for 2860 ms
20494 : WIFI : Connecting TNCAPE8A29B attempt #3
scandone
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug: 100: time#initialized do
23356 : EVENT: WiFi#Disconnected
RuleDebug: 101: publish home/%sysname%/ipaddress,%ip%
RuleDebug: 101: publish home/%sysname%/macaddress,%mac%
23368 : WIFI : Disconnected! Reason: '(201) No AP found' Connected for 2860 ms
23495 : WIFI : Connecting TNCAPE8A29B attempt #4
scandone
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug: 100: time#initialized do
26356 : EVENT: WiFi#Disconnected
RuleDebug: 101: publish home/%sysname%/ipaddress,%ip%
RuleDebug: 101: publish home/%sysname%/macaddress,%mac%
26368 : WIFI : Disconnected! Reason: '(201) No AP found' Connected for 2860 ms
26495 : WIFI : Connecting TNCAPE8A29B attempt #5
scandone
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug: 100: time#initialized do
29356 : EVENT: WiFi#Disconnected
RuleDebug: 101: publish home/%sysname%/ipaddress,%ip%
RuleDebug: 101: publish home/%sysname%/macaddress,%mac%
29369 : WIFI : Disconnected! Reason: '(201) No AP found' Connected for 2860 ms
mode : sta(84:f3:eb:8e:61:8c) + softAP(86:f3:eb:8e:61:8c)
add if1
dhcp server start:(ip:192.168.4.1,mask:255.255.255.0,gw:192.168.4.1)
bcn 100
bcn 0
del if1
add if1
dhcp server start:(ip:192.168.4.1,mask:255.255.255.0,gw:192.168.4.1)
bcn 100
29495 : WIFI : Set WiFi to AP+STA
30419 : WIFI : AP Mode ssid will be Test20_WMD1_20 with address 192.168.4.1
30419 : WIFI : Connecting TNCAPE8A29B attempt #6
scandone
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug: 100: time#initialized do
33281 : EVENT: WiFi#Disconnected
RuleDebug: 101: publish home/%sysname%/ipaddress,%ip%
RuleDebug: 101: publish home/%sysname%/macaddress,%mac%
33295 : WIFI : Disconnected! Reason: '(201) No AP found' Connected for 2860 ms
33495 : WIFI : AP Mode ssid will be Test20_WMD1_20 with address 192.168.4.1
33495 : WIFI : Connecting TNCAPE8A29B attempt #7
scandone
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug: 100: time#initialized do
36358 : EVENT: WiFi#Disconnected
RuleDebug: 101: publish home/%sysname%/ipaddress,%ip%
RuleDebug: 101: publish home/%sysname%/macaddress,%mac%
36371 : WIFI : Disconnected! Reason: '(201) No AP found' Connected for 2863 ms
36494 : WIFI : AP Mode ssid will be Test20_WMD1_20 with address 192.168.4.1
36495 : WIFI : Connecting TNCAPE8A29B attempt #8
scandone
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug: 100: time#initialized do
39357 : EVENT: WiFi#Disconnected
RuleDebug: 101: publish home/%sysname%/ipaddress,%ip%
RuleDebug: 101: publish home/%sysname%/macaddress,%mac%
39369 : WIFI : Disconnected! Reason: '(201) No AP found' Connected for 2861 ms
39494 : WIFI : AP Mode ssid will be Test20_WMD1_20 with address 192.168.4.1
39495 : WIFI : Connecting TNCAPE8A29B attempt #9
scandone
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug: 100: time#initialized do
42357 : EVENT: WiFi#Disconnected
RuleDebug: 101: publish home/%sysname%/ipaddress,%ip%
RuleDebug: 101: publish home/%sysname%/macaddress,%mac%
42370 : WIFI : Disconnected! Reason: '(201) No AP found' Connected for 2861 ms
43048 : WD   : Uptime 1 ConnectFailures 0 FreeMem 16272
43495 : WIFI : AP Mode ssid will be Test20_WMD1_20 with address 192.168.4.1
43495 : WIFI : Connecting TNCAPE8A29B attempt #10
scandone

@uzi18 I agree the current wifi code has become too complicated (again)
So I agree we should have a look at it, when I'm back home (just arrived in Stockholm)

@redskinhu just ERROR please :)

@TD-er we realy need log filtering and when enabled log all <= setted level - as some infos are on different levels.

Same test method like before just the Log level is Error. As requested. :-)

It looks connected but it isn't.

```

reboot

ets Jan 8 2013,rst cause:2, boot mode:(3,6)

load 0x4010f000, len 1384, room 16
tail 8
chksum 0x2d
csum 0x2d
vbb28d4a3
~ld
⸮U98 :

INIT : Booting version: mega-20181107 (ESP82xx Core 2_4_2, NONOS SDK 2.2.1(cfd48f3), LWIP: 2.0.3)
99 : INIT : Warm boot #3 - Restart Reason: Software/System restart
101 : FS : Mounting...
126 : FS : Mount successful, used 76053 bytes of 957314
501 : CRC : program checksum ...OK
538 : CRC : SecuritySettings CRC ...OK
640 : INIT : Free RAM:25384
641 : INIT : I2C
641 : INIT : SPI not enabled
676 : INFO : Plugins: 73 [Normal] [Testing] (ESP82xx Core 2_4_2, NONOS SDK 2.2.1(cfd48f3), LWIP: 2.0.3)
677 : EVENT: System#Wake
712 : WIFI : Set WiFi to STA
745 : WIFI : Connecting TNCAPE8A29B attempt #0
858 : EVENT: System#Boot
4800 : MQTT : Intentional reconnect

Update: ESP_Easy_mega-20181112_test_ESP8266_4096_VCC.bin
sleep disable
.............pm open,type:0 0
.......................................................................................
.......................................................................................
.......................................................................................
.......................................................................................
..........................................................
Update Success: 857648
Rebooting...

ets Jan 8 2013,rst cause:2, boot mode:(3,6)

load 0x4010f000, len 1384, room 16
tail 8
chksum 0x2d
csum 0x2d
vbb28d4a3
@cp:0
ld
⸮U

wifiscan
WIFI : SSID Scan start
WIFI : 3 networks found
WIFI : 1: eir90963965-2.4G 58:D7:59:5B:E0:70 Ch:2 (-74dBm) WPA/WPA2/PSK
WIFI : 2: eir_WiFi 58:D7:59:5B:E0:71 Ch:2 (-73dBm) open
WIFI : 3: TNCAPE8A29B C4:EA:1D:C3:BC:7F Ch:8 (-66dBm) WPA/WPA2/PSK
Ok
wificonnect
Ok

ESPEasy_mega-20181117 to 21 tested: NG

I was just reading on several of these issues.
It appears Tasmota has some issues too with some modules when connecting to WiFi and their approach to solve it was to do not start reading sensors etc. until wifi connection was made and making lots of delay() calls to lower power consumption of the CPU.
this suggests the power supply of these modules may not be sufficient.

See: https://github.com/arendst/Sonoff-Tasmota/issues/4254

@redskinhu Could you test this PR: https://github.com/letscontrolit/ESPEasy/pull/2073
I made a build for the normal_ESP8266_4096

Good Morning

Tested and NG. (the ESPEasy_mega-20181121 is behaving same like this FW)

I got this once:

Reply from 192.168.1.185: Destination host unreachable.
Reply from 192.168.1.247: bytes=32 time=2954ms TTL=255
Request timed out.

But the answer is most of the time:

Destination host unreachable.

See the log:

INIT : Booting version:  (ESP82xx Core 2_4_2, NONOS SDK 2.2.1(cfd48f3), LWIP: 2.0.3 PUYA support)
100 : INIT : Warm boot #8 - Restart Reason: External System
102 : FS   : Mounting...
126 : FS   : Mount successful, used 76053 bytes of 957314
465 : CRC  : program checksum       ...OK
477 : CRC  : SecuritySettings CRC   ...OK 
478 : CRC  : binary has changed since last save of Settings
578 : INIT : Free RAM:24472
579 : INIT : I2C
579 : INIT : SPI not enabled
611 : INFO : Plugins: 46 [Normal] (ESP82xx Core 2_4_2, NONOS SDK 2.2.1(cfd48f3), LWIP: 2.0.3 PUYA support)
613 : EVENT: System#Wake
649 : WIFI : Set WiFi to STA
681 : WIFI : Connecting TNCAPE8A29B attempt #0
796 : EVENT: System#Boot
>debug 4

Ok
scandone
state: 0 -> 2 (b0)
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 17
cnt 

connected with TNCAPE8A29B, channel 8
dhcp client start...
5519 : WIFI : Connected! AP: TNCAPE8A29B (C4:EA:1D:C3:BC:7F) Ch: 8 Duration: 4835 ms
5521 : EVENT: WiFi#ChangedAccesspoint

pm open,type:2 0



bcn_timout,ap_probe_send_start
32140 : WD   : Uptime 1 ConnectFailures 0 FreeMem 21312
ip:192.168.1.247,mask:255.255.255.0,gw:192.168.1.1
36085 : WIFI : DHCP IP: 192.168.1.247 (Test20-WMD1-20) GW: 192.168.1.1 SN: 255.255.255.0
36099 : EVENT: WiFi#Connected
36114 : Webserver: start
36114 : WIFI  : Arduino wifi status: WL_CONNECTED ESPeasy internal wifi status: ESPEASY_WIFI_SERVICES_INITIALIZED
36199 : MQTT : Intentional reconnect
36245 : MQTT : Connected to broker with client ID: ESPClient_84:F3:EB:8E:61:8C
36248 : Subscribed to: home/Test20_WMD1/#
36250 : EVENT: MQTT#Connected
36261 : EVENT: MQTT#Connected Processing time:11 milliSeconds
36585 : NTP  : NTP host 193.1.31.66 (193.1.31.66) queried
36617 : NTP  : NTP replied: delay 30 mSec Accuracy increased by 0.808 seconds
36619 : Current Time Zone:  DST time start: 2018-03-25 02:00:00 offset: 60 minSTD time start: 2018-10-28 03:00:00 offset: 0 min
36621 : EVENT: Time#Initialized
36631 : ACT  : Publish home/Test20_WMD1/IPaddress,192.168.1.247
36643 : ACT  : Publish home/Test20_WMD1/MACaddress,84:F3:EB:8E:61:8C
36651 : EVENT: Time#Initialized Processing time:30 milliSeconds
36652 : EVENT: Clock#Time=Thu,09:07
36659 : EVENT: Clock#Time=Thu,09:07 Processing time:7 milliSeconds
36663 : Command: publish
36666 : Command: publish

ap_probe_send over, rest wifi status to disassoc
state: 5 -> 0 (1)
rm 0
pm close 7
45099 : EVENT: WiFi#Disconnected
45107 : WIFI : Disconnected! Reason: '(200) Beacon timeout' Connected for 39 s
45289 : MQTT : Connection lost, state: Connection lost
45289 : EVENT: MQTT#Disconnected
45587 : WIFI : Connecting TNCAPE8A29B attempt #0
scandone
48449 : EVENT: WiFi#Disconnected
48457 : WIFI : Disconnected! Reason: '(201) No AP found' Connected for 2862 ms
48586 : WIFI : Connecting TNCAPE8A29B attempt #1
50587 : EVENT: Clock#Time=Thu,09:08
scandone
51449 : EVENT: WiFi#Disconnected
51456 : WIFI : Disconnected! Reason: '(201) No AP found' Connected for 2860 ms
51588 : WIFI : Connecting TNCAPE8A29B attempt #2
scandone
54449 : EVENT: WiFi#Disconnected
54457 : WIFI : Disconnected! Reason: '(201) No AP found' Connected for 2859 ms
54586 : WIFI : Connecting TNCAPE8A29B attempt #3
scandone
57443 : WIFI : Connecting TNCAPE8A29B attempt #4
57448 : EVENT: WiFi#Disconnected
57455 : WIFI : Disconnected! Reason: '(201) No AP found' Connected for 2855 ms
scandone

These modules are looks too slow to me.
I have a plan, i would like compare the speed of this module and one bare ESP12F.

https://www.instructables.com/id/ESP8266-NodeMCU-CPU-Speed-Test/

I'll test both modules whitout change the CPU freq.

Or any idea to compare the speed of the modules?

If the wifi reception is poor, a lot of re-transmits may occur and you would not see it.
Can you measure the 3.3V over the ESP when it is trying to connect to WiFi?
Preferably with a scope.
If that voltage is unstable, it will also affect the RF calibration performed right before connection is made.
This calibration takes a much higher current, so if the traces on the PCB are too thin, or the power supply itself isn't capable of handling this higher current, you may end up with unstable WiFi connection since the calibration is off.
Last few days I've been reading a lot on the WiFi on the ESP8266.

You could also try to add a small capacitor close to the 3.3V of the ESP, just to allow to keep this voltage stable on large variations of the current.
Not sure what would be the best capacity for the capacitor.
Maybe 10 uF? You may also not want to make the capacitor too large, since it will appear as a "short" to the power supply when initially charged. So it may also prevent the ESP from booting when too large.

Edit:
You're not using the ESP12e module, but just the bare ESP8266

I am not sure if all the red marked pins are connected.
But maybe you can find a spot where the 3.3V is, close to the chip?

Hi

I think this problem couldn't related to the voltages, because one fw is working fine and an another isn't on the same module which have same power supply and same location from the wifi AP and the test is happening almost same time.

Anyway the mega-20181122 is tested and OK.

What is the difference between 21 vs 22 fw?

I tried to do the test but it was unsuccessful, see: https://github.com/letscontrolit/ESPEasy/issues/2076

Anyway the mega-20181122 is tested and OK.

What is the difference between 21 vs 22 fw?

The only difference is in a plugin.
So it has nothing to do with the wifi part or timing.
I guess if you do a factory reset (or blank flash) and try the 20181122 version again, it may fail.

I think it was a fresh install.
I'll will try it when i get home.
Sadly, I need to work... :(

mega-20181122/23 uploaded to blank module: OK

I now have one module which seems to be as strange as you describe.
The strange thing is, a clean of the build (make clean) and rebuild may fix the wifi connection issues.
So there is something strange going on in the linking.

I will not merge any code today. Only docs changes are merged today.
So if tomorrows build is failing again, we have proof it is something in the linking process.

Maybe also nice to test.
For those times the node has a hard time to connect, it looks like it is only reporting to be connected but no reports of received IP or NTP updates.
It is then not reachable from the network.

After some minutes, all seems to be fine and the unit is then running fine.

Just another thought.
Do you have multiple accesspoints with the same SSID/passwd? (e.g. repeater or a mesh layout)
I tested here with my two accesspoint nodes (in mesh layout, both visible from my desk) and if I make the initial connection to the weakest one, I get a lot of timeouts, but after a while I have a very responsive unit.
Without the node reconnecting (or at least doesn't show up in the log)

Yes, sometimes the module needs couple of tries to connect to the AP after start/reboot. But after working fine.

I'll try this multiple AP thing on Tuesday.

I will have a look to see if we can set the BSSID locked.
This has been discussed before.
Do you have multiple access points with the same SSID running?

I just added a build flag to the common section in platformio.ini.
See this commit: https://github.com/letscontrolit/ESPEasy/commit/44a23fb5740e2cd74ea63a119d968832fe4d1be6

I will make a test build for this so we can test the effect on multiple nodes.

I just made a test build with this flag active.

Can you test it?

Test build tested: NG
mega-20181124: OK (i saw the changelog, nothing has changed since 22)

I have couple of routers hanging around. Could you explain this multiple AP thing? I know the router side. How should i configure the ESPEasy? What is the fallback SSID? Same like the the primary? How can i force the ESPEasy to connect the weaker AP first? I can try it on Tuesday maybe Monday.

There are some circumstances when you may have multiple accesspoints with the same SSID.
For example:

• Using a repeater
• WiFi mesh setup

At this moment you can only define the SSID/passwd in ESPeasy, but at initial configuration you can select one from a WiFi scan result.
It is also possible to give the BSSID at connection in the Arduino libraries. So it could very well be possible to differentiate on different access points, even when they have the same SSID.

So there may be the possibility the ESP module is connecting to the weakest one when making the initial connect. But if we add some BSSID to the settings, we can make sure it is only trying to connect to the preferred one.
So if you could try to connect to one accesspoint which is not sharing the SSID with another one, you also know for sure it is only attempting to connect to that only one AP.

Ok, everything is clear now. Test on Tuesday.

mega-20181125 tested: NG

2088 Looks same issue to me...

Hi

Test results of the ESPEasy_mega-20181121-10-g58278ab (and ESPEasy_mega-20181127 too):

• I can't connect to the "ESP_Easy_0" AP hence the "Authentication error occured" error. WPA key: configesp
• I tried to change the key using the WifiAPKey command but i got "Unknown command!" error on many releases, i didn't tested all.
• I tested the always good ESPEasy_mega-20180818, I can connect to the "ESP_Easy_0" AP with the configesp key and after the AP setup everything is working fine. Except the WifiAPKey command.

So i couldn't test this multiple AP thing :-(

I haven't used this EasySetup thing for a long time (serial is easier to me). Meanwhile is the default WPAkey has changed?

Off:
In the docs the "WiFi#ChangedAccesspoint" section is wrong.
The example is:on MQTTimport#Connected do

hi. the connection to wifi ESP_Easy_mega-20181231_normal_ESP8266_4096 works with post flash action static ip but the ESP_Easy_mega-20181231_normal_IR_ESP8266_4096 and any other ir bin up to xxx09 does not work (even if you flash it over with working bin but if you flash over non working bin with working bin it still will not work). is it posible to replace working wifi bin code to ir bin?

Hi

The latest fw which can connect to the wifi is: 20181124.

I tested the all of which has issued after that: no joy. :(

T

Hi

I saw this new fw with some wifi changes so i tested them 2.4.2 and 2.5.0 too:

Originally installed: 20181124 (working fine)

Results:

Start after OTA ESP_Easy_mega-20190116_test_ESP8266_4096_VCC.bin
Webpage sometimes reachable sometimes not. Mostly not.

Log:

Rebooting...

 ets Jan  8 2013,rst cause:2, boot mode:(3,7)

load 0x4010f000, len 1384, room 16
tail 8
chksum 0x2d
csum 0x2d
vbb28d4a3
@cp:0
     ld
       ▒U11498 :

INIT : Booting version: mega-20190116 (ESP82xx Core 2_4_2, NONOS SDK 2.2.1(cfd48f3), LWIP: 2.0.3 PUYA support)
11498 : INIT : Cold Boot - Restart Reason: Software/System restart
11501 : FS   : Mounting...
11526 : FS   : Mount successful, used 76555 bytes of 957314
11934 : CRC  : program checksum       ...OK
11971 : CRC  : SecuritySettings CRC   ...OK
11973 : CRC  : binary has changed since last save of Settings

Build changed!
12081 : SaveToFile: free stack: 3696
12159 : FILE : Saved config.dat
12160 : SaveToFile: free stack after: 3696
12163 : SaveToFile: free stack: 3696
12199 : FILE : Saved security.dat
12200 : SaveToFile: free stack after: 3696
12201 : INIT : Free RAM:23656
12203 : INIT : SPI not enabled
12245 : INFO : Plugins: 74 [Normal] [Testing] (ESP82xx Core 2_4_2, NONOS SDK 2.2.1(cfd48f3), LWIP: 2.0.3 PUYA support)
12246 : EVENT: System#Wake
12311 : WIFI : Set WiFi to STA
12344 : WIFI : Connecting APNAME attempt #0
12345 : IP   : Static IP : 192.168.1.230 GW: 192.168.1.1 SN: 255.255.255.0 DNS: 192.168.1.1
12461 : EVENT: System#Boot
12483 : SW   : State 1.00
12486 : EVENT: Flash#Button=1.00
12546 : SW  : GPIO=0 State=1 Output value=0
12548 : EVENT: Flash#Button=0.00
12739 : SYS  : 0.00,100.00,2.99,20512.00
12743 : EVENT: SysInfo#Uptime=0.00
12759 : EVENT: SysInfo#Load=100.00
12772 : EVENT: SysInfo#VCC=3.40
12787 : EVENT: SysInfo#Free_RAM=20512.00
13809 : WD   : Uptime 0 ConnectFailures 0 FreeMem 20520
17235 : WIFI : Connected! AP: APNAME (XX:XX:79:94:XX:XX) Ch: 1 Duration: 4789 ms
17237 : EVENT: WiFi#ChangedAccesspoint
17254 : IP   : Static IP : 192.168.1.230 GW: 192.168.1.1 SN: 255.255.255.0 DNS: 192.168.1.1
17255 : WIFI : Static IP: 192.168.1.230 (Test30-WMD1-30) GW: 192.168.1.1 SN: 255.255.255.0   duration: 120 ms
17269 : EVENT: WiFi#Connected
17286 : Webserver: start
17316 : NTP  : NTP replied: delay 21 mSec Accuracy increased by 0.272 seconds
17318 : Time adjusted by -1547663626978.76 msec. Wander: -429906563.05 msec/second
17319 : Current Time Zone:  DST time start: 2019-03-31 02:00:00 offset: 60 minSTD time start: 2019-10-27 03:00:00 offset: 0 min
17323 : EVENT: Time#Initialized
17335 : ACT  : TimerSet,1,7
17347 : Command: timerset
17361 : EVENT: Clock#Time=Wed,18:34
17380 : MQTT : Intentional reconnect
17782 : MQTT : Connected to broker with client ID: Test30_WMD1_30
17786 : Subscribed to: home/Test30_WMD1/#
17789 : EVENT: MQTT#Connected
17930 : SW   : State 0.00
17934 : EVENT: Flash#Button=0.00
18318 : SYS  : 0.00,52.10,2.99,14736.00
18323 : EVENT: SysInfo#Uptime=0.00
18339 : EVENT: SysInfo#Load=52.10
18354 : EVENT: SysInfo#VCC=3.40
18369 : EVENT: SysInfo#Free_RAM=14736.00
25253 : EVENT: Rules#Timer=1
25269 : ACT  : Publish home/Test30_WMD1/MACaddress,5C:CF:7F:A4:51:EC
25279 : Command: publish
25287 : ACT  : Publish home/Test30_WMD1/UnitName,Test30_WMD1
25297 : Command: publish
25305 : ACT  : Publish home/Test30_WMD1/UnitNr,30
25315 : Command: publish
25322 : ACT  : Publish home/Test30_WMD1/IPaddress,192.168.1.230
25336 : Command: publish
25340 : ACT  : Notify 1
25350 : Command: notify
25465 : Email: To [email protected]
25520 : EMAIL: Connection Closed Successfully
26291 : EVENT: WiFi#Disconnected
26307 : WIFI : Disconnected! Reason: '(200) Beacon timeout' Connected for 9055 ms
26326 : MQTT : Connection lost, state: Connection lost
26327 : EVENT: MQTT#Disconnected
26345 : WIFI : Connecting APNAME attempt #0
26347 : IP   : Static IP : 192.168.1.230 GW: 192.168.1.1 SN: 255.255.255.0 DNS: 192.168.1.1
28299 : WIFI : Connected! AP: APNAME (XX:XX:79:94:XX:XX) Ch: 1 Duration: 1852 ms
28301 : IP   : Static IP : 192.168.1.230 GW: 192.168.1.1 SN: 255.255.255.0 DNS: 192.168.1.1
28302 : WIFI : Static IP: 192.168.1.230 (Test30-WMD1-30) GW: 192.168.1.1 SN: 255.255.255.0   duration: 103 ms
28317 : EVENT: WiFi#Connected
28430 : NTP  : NTP replied: delay 90 mSec Accuracy increased by 0.350 seconds
28431 : Time adjusted by -57.78 msec. Wander: -0.02 msec/second
28435 : EVENT: Time#Set
28457 : MQTT : Intentional reconnect
28962 : MQTT : Connected to broker with client ID: Test30_WMD1_30
28966 : Subscribed to: home/Test30_WMD1/#
28969 : EVENT: MQTT#Connected
29296 : SW   : State 0.00
29300 : EVENT: Flash#Button=0.00
29498 : SYS  : 0.00,52.10,2.99,12232.00
29504 : EVENT: SysInfo#Uptime=0.00
29521 : EVENT: SysInfo#Load=52.10
29536 : EVENT: SysInfo#VCC=3.40
29553 : EVENT: SysInfo#Free_RAM=12232.00
37559 : EVENT: WiFi#Disconnected
37575 : WIFI : Disconnected! Reason: '(200) Beacon timeout' Connected for 9257 ms
37675 : MQTT : Connection lost, state: Connection lost
37676 : EVENT: MQTT#Disconnected
38254 : WIFI : Connecting APNAME attempt #0
38255 : IP   : Static IP : 192.168.1.230 GW: 192.168.1.1 SN: 255.255.255.0 DNS: 192.168.1.1
38556 : WIFI : Connected! AP: APNAME (XX:XX:79:94:XX:XX) Ch: 1 Duration: 200 ms
38557 : IP   : Static IP : 192.168.1.230 GW: 192.168.1.1 SN: 255.255.255.0 DNS: 192.168.1.1
38559 : WIFI : Static IP: 192.168.1.230 (Test30-WMD1-30) GW: 192.168.1.1 SN: 255.255.255.0   duration: 103 ms
38574 : EVENT: WiFi#Connected
38674 : MQTT : Intentional reconnect
39091 : MQTT : Connected to broker with client ID: Test30_WMD1_30
39095 : Subscribed to: home/Test30_WMD1/#
39098 : EVENT: MQTT#Connected
39239 : SW   : State 0.00
39243 : EVENT: Flash#Button=0.00
39313 : NTP  : NTP replied: delay 20 mSec Accuracy increased by 0.270 seconds
39314 : Time adjusted by -61.77 msec. Wander: -0.02 msec/second
39318 : EVENT: Time#Set
39627 : SYS  : 0.00,52.10,2.99,12288.00
39633 : EVENT: SysInfo#Uptime=0.00
39650 : EVENT: SysInfo#Load=52.10
39665 : EVENT: SysInfo#VCC=3.40
39682 : EVENT: SysInfo#Free_RAM=12288.00
43810 : WD   : Uptime 1 ConnectFailures 0 FreeMem 13128
47901 : EVENT: WiFi#Disconnected
47918 : WIFI : Disconnected! Reason: '(200) Beacon timeout' Connected for 9344 ms
48056 : MQTT : Connection lost, state: Connection lost
48057 : EVENT: MQTT#Disconnected
48253 : WIFI : Connecting APNAME attempt #0
48255 : IP   : Static IP : 192.168.1.230 GW: 192.168.1.1 SN: 255.255.255.0 DNS: 192.168.1.1
48479 : EVENT: WiFi#Disconnected
48495 : WIFI : Disconnected! Reason: '(201) No AP found' Connected for 122 ms
50253 : WIFI : Connecting APNAME attempt #1
50254 : IP   : Static IP : 192.168.1.230 GW: 192.168.1.1 SN: 255.255.255.0 DNS: 192.168.1.1
54339 : WIFI : Connected! AP: APNAME (XX:XX:79:94:XX:XX) Ch: 1 Duration: 3983 ms
54340 : IP   : Static IP : 192.168.1.230 GW: 192.168.1.1 SN: 255.255.255.0 DNS: 192.168.1.1
54342 : WIFI : Static IP: 192.168.1.230 (Test30-WMD1-30) GW: 192.168.1.1 SN: 255.255.255.0   duration: 103 ms
54357 : EVENT: WiFi#Connected
54449 : NTP  : NTP replied: delay 71 mSec Accuracy increased by 0.398 seconds
54450 : Time adjusted by -65.32 msec. Wander: -0.02 msec/second
54454 : EVENT: Time#Set
54479 : MQTT : Intentional reconnect
54884 : MQTT : Connected to broker with client ID: Test30_WMD1_30
54889 : Subscribed to: home/Test30_WMD1/#
54891 : EVENT: MQTT#Connected
55033 : SW   : State 0.00
55037 : EVENT: Flash#Button=0.00
55421 : SYS  : 1.00,18.10,2.99,11504.00
55426 : EVENT: SysInfo#Uptime=1.00
55443 : EVENT: SysInfo#Load=18.10
55459 : EVENT: SysInfo#VCC=3.40
55475 : EVENT: SysInfo#Free_RAM=11504.00
68069 : EVENT: WiFi#Disconnected
68085 : WIFI : Disconnected! Reason: '(200) Beacon timeout' Connected for 13 s
68206 : MQTT : Connection lost, state: Connection lost
68207 : EVENT: MQTT#Disconnected

Start after OTA ESP_Easy_mega-20190116_test_core_250_beta_ESP8266_4096_VCC.bin
No connection.

INIT : Booting version: mega-20190116 (ESP82xx Core 2.5.0-beta2, NONOS SDK 3.0.0-dev(c0f7b44), LWIP: 2.1.2 PUYA support)
11692 : INIT : Cold Boot - Restart Reason: Software/System restart
11696 : FS   : Mounting...
11727 : FS   : Mount successful, used 76555 bytes of 957314
12154 : CRC  : program checksum       ...OK
12167 : CRC  : SecuritySettings CRC   ...OK 
12169 : CRC  : binary has changed since last save of Settings

Build changed!
12278 : SaveToFile: free stack: 3696
12394 : FILE : Saved config.dat
12395 : SaveToFile: free stack after: 3696
12399 : SaveToFile: free stack: 3696
12452 : FILE : Saved security.dat
12453 : SaveToFile: free stack after: 3696
12455 : INIT : Free RAM:20464
12457 : INIT : SPI not enabled
12509 : INFO : Plugins: 74 [Normal] [Testing] (ESP82xx Core 2.5.0-beta2, NONOS SDK 3.0.0-dev(c0f7b44), LWIP: 2.1.2 PUYA support)
12510 : EVENT: System#Wake
12585 : WIFI : Set WiFi to STA
12621 : WIFI : Connecting APNAME attempt #0
12622 : IP   : Static IP : 192.168.1.230 GW: 192.168.1.1 SN: 255.255.255.0 DNS: 192.168.1.1
12741 : EVENT: System#Boot
12779 : SW   : State 1.00
12782 : EVENT: Flash#Button=1.00
12857 : SW  : GPIO=0 State=1 Output value=0
12860 : EVENT: Flash#Button=0.00
12997 : SYS  : 0.00,100.00,2.99,16336.00
13003 : EVENT: SysInfo#Uptime=0.00
13028 : EVENT: SysInfo#Load=100.00
13050 : EVENT: SysInfo#VCC=3.40
13075 : EVENT: SysInfo#Free_RAM=16336.00
14103 : WD   : Uptime 0 ConnectFailures 0 FreeMem 16344
23547 : WIFI : Connecting APNAME attempt #1
23548 : IP   : Static IP : 192.168.1.230 GW: 192.168.1.1 SN: 255.255.255.0 DNS: 192.168.1.1
44101 : WD   : Uptime 1 ConnectFailures 0 FreeMem 16600
45550 : WIFI : Connecting APNAME attempt #2
45551 : IP   : Static IP : 192.168.1.230 GW: 192.168.1.1 SN: 255.255.255.0 DNS: 192.168.1.1
60565 : EVENT: Clock#Time=Thu,00:01
68549 : WIFI : Connecting APNAME attempt #3
68551 : IP   : Static IP : 192.168.1.230 GW: 192.168.1.1 SN: 255.255.255.0 DNS: 192.168.1.1
72607 : SW   : State 0.00
72611 : EVENT: Flash#Button=0.00
74102 : WD   : Uptime 1 ConnectFailures 0 FreeMem 16600
83265 : EVENT: WiFi#Disconnected
83287 : WIFI : Disconnected! Reason: '(7) Not assoced' Connected for 14 s
83546 : WIFI : Connecting APNAME attempt #4
83547 : IP   : Static IP : 192.168.1.230 GW: 192.168.1.1 SN: 255.255.255.0 DNS: 192.168.1.1
84772 : EVENT: WiFi#Disconnected
84794 : WIFI : Disconnected! Reason: '(2) Auth expire' Connected for 1123 ms
86547 : WIFI : Connecting APNAME attempt #5
86548 : IP   : Static IP : 192.168.1.230 GW: 192.168.1.1 SN: 255.255.255.0 DNS: 192.168.1.1
87784 : EVENT: WiFi#Disconnected
87806 : WIFI : Disconnected! Reason: '(4) Assoc expire' Connected for 1134 ms
89547 : WIFI : Set WiFi to AP+STA
90472 : EVENT: WiFi#APmodeEnabled
90501 : WIFI : AP Mode ssid will be Test30_WMD1_30 with address 192.168.4.1
90502 : WIFI : Connecting APNAME attempt #6
90503 : IP   : Static IP : 192.168.1.230 GW: 192.168.1.1 SN: 255.255.255.0 DNS: 192.168.1.1
90728 : EVENT: WiFi#Disconnected
90755 : WIFI : Disconnected! Reason: '(201) No AP found' Connected for 122 ms
93546 : WIFI : Connecting APNAME attempt #7
93548 : IP   : Static IP : 192.168.1.230 GW: 192.168.1.1 SN: 255.255.255.0 DNS: 192.168.1.1
96524 : EVENT: WiFi#Disconnected
96547 : WIFI : Disconnected! Reason: '(201) No AP found' Connected for 2873 ms
96558 : WIFI : Connecting APNAME attempt #8
96559 : IP   : Static IP : 192.168.1.230 GW: 192.168.1.1 SN: 255.255.255.0 DNS: 192.168.1.1
100544 : EVENT: WiFi#Disconnected
100568 : WIFI : Disconnected! Reason: '(4) Assoc expire' Connected for 3883 ms
100580 : WIFI : Connecting APNAME attempt #9
100581 : IP   : Static IP : 192.168.1.230 GW: 192.168.1.1 SN: 255.255.255.0 DNS: 192.168.1.1
104102 : WD   : Uptime 2 ConnectFailures 0 FreeMem 14480
104562 : EVENT: WiFi#Disconnected

The ball is on your side now... ;-)

Thanks
T

Hmm too bad :(
I had really good hopes for this one as soon as I saw the commit on the Arduino repository.

Yes the 2.5.0 looks worse than 2.4.2, but i dont give up. I tried every release anyway. The last working release is 20181124.

20190121 2.5.0 / 2.4.2 tested, same like 20190116.

I found the same problem with the same board .. last working fw , that I found till today, is ESP_Easy_mega-20190212_dev_ESP8266_4096.bin

i have same problem with same board :(

The current code in the mega branch does have issues connecting to WiFi.
I've been working on it for almost the entire Sunday but it is not fixed yet.
It is almost like a very timing critical bug which may prevent it to connect to WiFi.
There is one somewhat unique timing factor in the connection procedure. Some delay is used based on the last byte of the MAC address to introduce some randomness to prevent a DDOS-like attack on a server/broker after the power has been restored for lots of nodes.

But right now it almost feels random whether a node can connect to WiFi. (just pick another core version or number of plugins included and it may fail or succeed)

Just started with ESPEasy, I cant connect to WiFi also.
Using the build 09.08.2019 and one before, flashed blank Image before, tried with or without mesh WiFi (Fritzbox 7590), add WiFi credentials via ESP Easy Flash Tool
Always get the "beacon timeout" every 1000ms in a loop

Is there a older version i could use?

443329 : WIFI : Disconnected! Reason: '(200) Beacon timeout' Connected for 8609 ms
443582 : WIFI : Connecting mywifi attempt #0
443587 : WIFI : WiFi.status() = WL_DISCONNECTED  SSID: mywifi
444806 : WIFI : Connected! AP: mywifi (E0:22:6D:44:DC:53) Ch: 11 Duration: 1048 ms
444808 : WIFI : DHCP IP: 192.168.178.129 (PressureESP-0) GW: 192.168.178.1 SN: 255.255.255.0   duration: 170 ms
452116 : WD   : Uptime 8 ConnectFailures 0 FreeMem 23448 WiFiStatus 3

You may try setting up a AP using your phone and see if the problem still persists.

Things to check: (we should make a link for this somewhere)

• Power stability (add capacitors, good USB cable, etc), newer modules do have low power voltage regulators.
• No metal near the WiFi antenna
• Try sending ping packets to the ESP node from another host

WiFi credentials seem OK, since you do get a connection.

You can try a build from around begin 2018 to be sure the module is OK.
Those versions did not use newer core versions and were not as fast, so less demanding of the ESP at startup.

Thanks for your quick answer. I have tested with 3 different HWs (Wemos NodeMCUs), Used Laptop USB Port as Powersupply but also tried external Power (no debug, but no connect to hotspot also). Tried different cable. Tried to test directly in front of the hotspot. No ping replies received from node MCU.

On Tablet Hotspot I'll get every 2853ms:
3803 : WIFI : Disconnected! Reason: '(201) No AP found' Connected for 2852 ms

will test with older builds

Here is the new Status:
Version from 28.02.2018 works as expected.
Latest Version does not work, WiFi connects and disconnects every second:

connected with mywifi, channel 11
dhcp client start...
82812 : WIFI : Connected! AP: mywifi (E0:26:6F:55:EC:63) Ch: 11 Duration: 1059 ms
ip:192.168.178.116,mask:255.255.255.0,gw:192.168.178.1
84684 : WIFI : DHCP IP: 192.168.178.116 (PressureESP-0) GW: 192.168.178.1 SN: 255.255.255.0   duration: 2001 ms
bcn_timout,ap_probe_send_start
92126 : WD   : Uptime 2 ConnectFailures 0 FreeMem 23160 WiFiStatus 3
pm open,type:2 0
ap_probe_send over, rest wifi status to disassoc
state: 5 -> 0 (1)
rm 0
pm close 7
93210 : WIFI : Disconnected! Reason: '(200) Beacon timeout' Connected for 10 s

Hi

I moved to ESPHome. These boards are works perfectly with it.

If you're using Homeassistant maybe worth it to try.

Bye
T

I will close this, open if its still a valid issue.