Problem with wifi persistance

[betux69]

hi,

I’m building a sensor that measures CO₂, temperature and ambient light, with plans to add VOC monitoring later.
All five prototype boards configure correctly, but once they switch from AP to STA mode they become unreachable after a few minutes—no ping replies and no access to the web UI. They do briefly appear in AP mode.

Typical log entry:
WD : Uptime 15 | ConnectFailures 0 | FreeMem 20952 | WiFiStatus: 3 | ESPeasy internal Wi-Fi status: Conn. IP Init

The project uses an SCD41 for temperature and CO₂, which I now realize may not be ideal. In Hardware I set both Clock speed and Slow device Clock Speed to 50 kHz and left I²C ClockStretchLimit at 0. In the SCD41 settings, Force Slow I²C speed is disabled and Low-power measurement is enabled.

Thanks for your help.

regards

System Info
Unit Number:	0
Local Time:	2025-07-01 17:52:51
Time Source:	NTP
Time Wander:	0.000 [ppm]
Uptime:	00h23m
Load:	12.08 [%] (LC=9840)
CPU Eco Mode:	false
Reset Reason:	Power On
Last Action before Reboot:	Background Task
SW WD count:	0
Boot:	Cold Boot (0)
Memory
Free RAM:	15208 [byte]
Free Stack:	3680 [byte]
Network
IP Config:	Static
IP / Subnet:	10.26.201.181 / 255.240.0.0
Gateway:	10.20.0.254
Client IP:	10.21.116.2
DNS:	10.20.0.2 / (IP unset)
Allowed IP Range:	All Allowed
Connected:	00:23:07.177
Number Reconnects:	0
WiFi ?
WiFi Connection:	802.11n (RSSI -57 dBm)
SSID:	Robin (34:FC:B9:A0:A0:23)
Channel:	1
Encryption Type:	WPA2/PSK
Last Disconnect Reason:	(1)
Configured SSID1:	Robin
Configured SSID2:
STA MAC:	8C:4F:00:40:4B:1F
AP MAC:	8E:4F:00:40:4B:1F

WiFi Settings
Force WiFi B/G: | false
Restart WiFi Lost Conn: | false
Force WiFi No Sleep: | false
Periodical send Gratuitous ARP: | false
Connection Failure Threshold: | 0
Max WiFi TX Power: | 17.50 [dBm]
Current WiFi TX Power: | 9.00 [dBm]
WiFi Sensitivity Margin: | 3 [dB]
Send With Max TX Power: | false
Extra WiFi scan loops: | 0
Use Last Connected AP from RTC: | false
Extra Wait WiFi Connect: | false
Hidden SSID Slow Connect: | true
Include Hidden SSID: | true
Enable SDK WiFi Auto Reconnect: | false
Firmware
Build:⋄ | 20250430 - Mega
System Libraries:⋄ | ESP82xx Core 2843a5ac, NONOS SDK 2.2.2-dev(38a443e), LWIP: 2.1.2 PUYA support
Git Build:⋄ | mega-20250430
Plugin Count:⋄ | 68 ["Climate","No Debug Log"]
Build Origin: | GitHub Actions
Build Time:⋄ | Apr 30 2025 19:48:23
Binary Filename:⋄ | ESP_Easy_mega_20250430_climate_ESP8266_4M1M
Build Platform:⋄ | Linux-6.11.0-1012-azure-x86_64-with-glibc2.39
Git HEAD:⋄ | HEAD_4c405c7
System Status
Syslog Log Level: | None
Serial Log Level: | Info
Web Log Level: | None
Enable Serial Port Console: | true
Console Serial Port: | HW Serial0 RX:3 TX:1 @ 115200 baud
Network Services
Network Connected: | ✔
NTP Initialized: | ✔
ESP Board
ESP Chip ID: | 4213535 (0x404B1F)
ESP Chip Frequency: | 80 [MHz]
ESP Chip Model: | ESP8266EX
ESP Chip Cores: | 1
ESP Board Name: | Espressif Generic ESP8266 ESPEasy 4M Flash 1M FS
Storage
Flash Chip ID: | Vendor: 0x85 (PUYA, supported) Device: 0x2016
Flash Chip Real Size: | 4096 [kB]
Flash IDE Size: | 4096 [kB]
Flash Chip Speed: | 40 [MHz]
Flash IDE Speed: | 40 [MHz]
Flash IDE Mode: | DOUT
Flash Writes: | 0 daily / 0 boot
Sketch Size: | 1014 [kB] (5 kB not used)
Max. OTA Sketch Size: | 1019 [kB] (1044464 bytes)
OTA possible: | true
OTA 2-step Needed: | false
SPIFFS Size: | 934 [kB] (873 kB free

[tonhuisman]

First thing to check is the power supply and power-wiring for the ESP. If WiFi is shaky/unstable, it's very often caused by a poor or unstable power supply.

[TD-er]

Second is testing this test build, for which I am working on a complete rewrite of the WiFi code.
https://github.com/letscontrolit/ESPEasy/actions/runs/15948897150

N.B. this one is still in beta, so please test on reachable nodes.
Also this is having only LittleFS builds for ESP32-xx builds, so you may want to check this on how to upgrade to LittleFS if your node doesn't already use LittleFS (only for ESP32-xx, ESP8266 is still using SPIFFS)

[TD-er]

Hmm just noticed something in the info you gave...

Why do you need such a large subnet?

10.26.201.181 / 255.240.0.0

[tonhuisman]

IP / Subnet: 10.26.201.181 / 255.240.0.0

Hmm, that's quite some IP addresses you're expecting here, not sure if the poor ESP will handle that stable 🤔

[betux69]

First thing to check is the power supply and power-wiring for the ESP. If WiFi is shaky/unstable, it's very often caused by a poor or unstable power supply.

thanks for your answer i try 4 power supply one very good and i try to put a capacitor.
I've a lot of esp8266 with espeasy for my project and version 1 is fine with same power and i'have more components.

I bought my esp on amazon and aliexpress : Can you have bad ESP streaks?

[betux69]

You are right about my subnet but forget it it's not my choice ;o)
ESP are working fine with this subnet.

[betux69]

Second is testing this test build, for which I am working on a complete rewrite of the WiFi code. https://github.com/letscontrolit/ESPEasy/actions/runs/15948897150

N.B. this one is still in beta, so please test on reachable nodes. Also this is having only LittleFS builds for ESP32-xx builds, so you may want to check this on how to upgrade to LittleFS if your node doesn't already use LittleFS (only for ESP32-xx, ESP8266 is still using SPIFFS)

i try this one i don't know if it's the good one ;o)
ESP_Easy_mega_20250628_climate_ESP8266_4M1M.bin

[TD-er]

For ESP8266 there is no need to worry about used file systems as that hasn't changed in years and will not change as ESP8266 is practically end-of-life (about 5 years ago by Espressif)

[betux69]

What will be the replacement for the ESP 8266? I love the 8266. ;o)

[betux69]

Is this the version you want me to test?
ESP_Easy_mega_20250628_climate_ESP8266_4M1M.bin

[TD-er]

What will be the replacement for the ESP 8266? I love the 8266. ;o)

Pick your variant: https://espeasy.readthedocs.io/en/latest/ESPEasy/ESPchips.html

ESP32-C5 is already running on my desk as test, but not yet ready for release.
ESP32-C61 is waiting on my desk till Espressif will finally release any documentation for it so I can start implementing support.
ESP32-H2/H21 will probably never be supported in ESPEasy as those have no WiFi.
ESP32-P4 is a completely different type of ESP as it is quite a powerful machine with quad-core CPU running at 400 MHz, high speed display and camera support etc. (not yet supported in ESPEasy)

Still enough left.

There are lots of ESP32-variants with similar form factors as the NodeMCU or Wemos D1-mini and even way smaller ones.

[TD-er]

Is this the version you want me to test? ESP_Easy_mega_20250628_climate_ESP8266_4M1M.bin

Sure, if you are currently running a build with "climate_ESP8266_4M1M.bin" in the name, then that's a good choice :)

[TD-er]

Also can you post a bit more info on what you have configured, are you using rules, etc.

• What tasks/plugins
• Which controller(s)
• If using rules, please post them
• Do you use syslog?
• Have you tried setting the WiFi to "Force B/G only" mode ?(tools->advanced page)

[betux69]

On System#Boot do
rtttl,14:d=10,o=6,b=180,c,e,g,c,e,g
endon

on CO2S#PPM do
if [CO2S#PPM]>3400
gpio,12,1
else
gpio,12,0
endif
endon

On Clock#Time=All,00:50 do
Reboot
endon

[betux69]