[Test build] Testers for new upcoming build (feb '24)

[TD-er]

I've just uploaded the latest GH Actions build to the web flasher

So I would like to summon the very appreciated testing crew :) @fly74 @ghtester @chemmex @alex-kiev @iz8mbw @Wookbert @Dickesplumpel

Just as a reminder:

• ESP32-xx LittleFS builds are based on ESP-IDF 5.x code
• ESP32-xx SPIFFS builds are based on ESP-IDF 4.4

Known issues to be fixed before new release:

• [x] ESP32 does seem to take upto 2 minutes to connect to WiFi when it needs to scan to (re)connect (mainly on LittleFS builds)
• [x] GPIO boot state vs. pull-up checkbox in tasks. (#4800)
• [x] Support for W5500 SPI Ethernet without IRQ pin connected (e.g. on M5Stack AtomPOE with AtomS3)
• [x] Show active Ethernet chip in sysinfo/JSON
• [x] Add note to configure pull-up on Hardware tab
• [x] Remove max. rules file limit on rules editor page
• [x] No longer crashing on WiFi disconnect or wifi power off (except for wifimode,off command on web page)
• [x] No longer "unable to connect due to unprocessed disconnect event"
• [ ] http server is not reachable in AP mode (ESP32-C3/C6)

I also would like to know what you guys think about the new download "artifacts" on the GH Actions builds (not the releases) as Ton needed to change stuff due to changes in how GH Actions operates. I personally like the single large download for uploading it to the webflasher, but I really dislike the download speeds offered by GH. (takes 5 - 10 minutes to download the full zip)

Not sure if Ton even could change it as how it is done now, but it is nice to know if there are some likes/dislikes about the current situation.

[iz8mbw]

Do you have still the State flapping between 1 and 0 as you reported here?

More, when you press the button you provide 3V3 to the PIN or you provide GND to the PIN?

[TD-er]

Unfortunately this don't work. After pressing it stays 1 and don't fall to 0 after release.

How is the button wired?

It is best to have some current flowing when the button isn't pressed. Since the button is over the GPIO pin and GND, I guess it makes sense to have some physical pull-up resistor between GPIO and 3V3 and set the boot state of that GPIO to pull-down. The internal pull resistors are of quite high resistance, like 50k - 100k So if you put a physical resistor of a few k (e.g. 4k7 ... 10k, whatever you have laying around, not less than 1k) between the GPIO and 3V3 then it has a strong pull-up and a weak pull down, so the logic level is high. When pressing the button you have a strong pull-down (stronger than the resistor) and thus a logic low level.

As this will result in some current flowing through the resistor and the internal pull-down resistor in the ESP, you need a much stronger noise signal to change the pin state.

[fly74]

But isn't the sense of having internal pullup/-down to avoid external resistors?

[fly74]

Do you have still the State flapping between 1 and 0 as you reported here?

More, when you press the button you provide 3V3 to the PIN or you provide GND to the PIN?

No flapping, but only one switch after reboot is possible.

Wiring is switch provide GND to GPIO23.

Config is this:

[chemmex]

Testing ESP8266, ESP32, C3 and C6 (normal LittleFS builds only for 32-xx). Clean install Found some unexpected behaviour: on C3 and C6, could not get http server start captive portal. Neither via Android's internal helper nor directly via browser. Tried with both phone and PC With 8266 and ESP32 everything as expected Nothing suspicious in the log Will check further

[tonhuisman]

Found some unexpected behaviour:

Using GH Actions builds or self-built?

[chemmex]

GH Actions, normal builds

[Dickesplumpel]

@fly >But isn't the sense of having internal pullup/-down to avoid external resistors?

As far as I know: No. In most cases when one of my "constructions" has state-flapping a pull-down or pull-up resistor of 4-5k ends it. You never know what "noise" you are catching from wherever (power supply, radio over cables, ...). When I remember right the motion sensor HC-SR-501 has a 4k7 pull-down build in.

[Dickesplumpel]

I remembered wrong,motion sensor HC-SR-501 hasn't a 4k7 pull-down build in, I've done it. :-)

[chemmex]

Probably something like this (without the stack decoding)

00:06:58.222 : (186348) Info   : WIFI : Disconnecting...
00:06:58.242 : (191120) Info   : WiFi : WifiDisconnect()
Guru Meditation Error: Core  0 panic'ed (Load access fault). Exception was unhandled.

Got something like this once when tried to reset the C3 from the web interface.

00:01:24.701 : (204296) Info   : NVS  : Load FacDefPref
RESET: Resetting factory defaults... using default settings
RESET: Warm boot, reset count: 1
RESET: formatting...
RESET: formatting done...
00:01:28.910 : (204360) Info   : SaveToFile: ControllerSettings index: 0
00:01:28.913 : (204360) Info   : SaveToFile: free stack: 7208
00:01:31.015 : (204976) Info   : FILE : Saved config.dat offset: 8192 size: 820
00:01:31.017 : (204912) Info   : SaveToFile: free stack after: 7208
00:01:31.020 : (205000) Info   : NVS  : Load UnitName
00:01:31.021 : (204420) Info   : NVS  : Load WIFI_SSID1
00:01:31.023 : (204368) Info   : NVS  : Load WIFI_PASS1
00:01:31.025 : (204320) Info   : NVS  : Load WIFI_AP_PASS
00:01:31.026fo   : NVS  : Load WIFI_Flags
00:01:31.028 : (204224) Info   : NVS  : Load WiFI_IP
00:01:31.030 : (204176) Info   : NVS  : Load ETH_IP
00:01:31.031 : (204128) Info   : NVS  : Load ETH_HW_CONF
00:01:31.032 : (204088) Info   : NVS  : Load Log
00:01:31.034 : (204040) Info   : NVS  : Load Console
00:01:31.038 : (202992) Info   : ESPEasy console using ESPEasySerial
00:01:31.060 : (202928) Info   : ESPEasy console fallback enabled
00:01:31.064 : (202880) Info   : SaveToFile: free stack: 7336
00:01:33.350 : (203328) Info   : FILE : Saved config.dat offset: 0 size: 3028
00:01:33.353 : (203264) Info   : SaveToFile: free stack after: 7336
00:01:33.355 : (203216) Info   : SaveToFile: freeGuru Meditation Error: Core  0 panic'ed (Load access fault). Exception was unhandled.

Core  0 register dump:
MEPC    : 0x40043d16  RA      : 0x4210a776  SP      : 0x3fc9f910  GP      : 0x3fc8b400
TP      : 0x3fc79578  T0      : 0x40386bbe  T1      : 0x40387358  T2      : 0x72617764
S0/FP   : 0x3fcdf86c  S1      : 0x3fce0000  A0      : 0x00000000  A1      : 0x3fcacd46
A2      : 0x3fc9f93c  A3      : 0x3fc9fcc0  A4      : 0x3fc96000  A5      : 0x00000000
A6      : 0x3fc9263c  A7      : 0x00000000  S2      : 0x00000000  S3      : 0x3fc93b78
S4      : 0x00000000  S5      : 0x00000036  S6      : 0x3fcacd46  S7      : 0x00000000
S8      : 0x00000006  S9      : 0x00000000  S10     : 0x00000000  S11     : 0x00000000
T3      : 0x3fcad488  T4      : 0x00000006  T5      : 0x00000000  T6      : 0x00000006
MSTATUS : 0x00001881  MTVEC   : 0x40380001  MCAUSE  : 0x00000005  MTVAL   : 0x00000018
MHARTID : 0x00000000

And one more observation: resetting (from wherever) doesn't clean the wifi settings, it still connects to the same AP

[iz8mbw]

Do you have still the State flapping between 1 and 0 as you reported here? More, when you press the button you provide 3V3 to the PIN or you provide GND to the PIN?

No flapping, but only one switch after reboot is possible.

Wiring is switch provide GND to GPIO23.

Config is this:

OK, so the GPIO flapping issue is resolved thanks to the ESP32 internal Pullup resistor. About your GPIO23, did you set "Input pullp" as show here: ?

When switch is not pressed, did you check (with a meter) if you provide 3V3 to GPIO23? When switch is pressed, did you check (with a meter) if you provide GND to GPIO23?

[iz8mbw]

@TD-er tested "ESP_Easy_mega_20240214_custom_ESP32_4M316k_LittleFS Feb 14 2024" and "ESP_Easy_mega_20240214_max_ESP32_16M8M_LittleFS Feb 14 2024" with no issues. Thanks!

[TD-er]

And one more observation: resetting (from wherever) doesn't clean the wifi settings, it still connects to the same AP

That might be due to a checkbox on the "Factory reset" page?

Any checkbox here does store the related settings outside the file system in the NVS partition. This way a complete format (e.g. when changing from SPIFFS to LittleFS or vice verse) will keep those settings.

[chemmex]

I flashed LittleFS version initially. Every "Keep" was unchecked. And reset command from the terminal did not clear wifi settings either

[TD-er]

OK, I will check if I missed some erasing of the NVS stored settings.

[Dickesplumpel]

3 already mentioned issues an old sonoff basic with ESP8266-1M: slow wifi connection, mqtt disconnections every 10-20 minutes and state flapping on gpio14 although there is an 5k pull-down resitor at HC-SR-501. Back to 20231225 everything is working well.

[TD-er]

I just updated the latest GH actions build: https://td-er.nl/ESPEasy/latest/ It also has a link to the all.zip file.

This should fix nearly all crashes and slow WiFi (re)connects when calling wifidisconnect or wifimode,off. That last one may (not always) still result in a crash when calling it from the command field on the tools page, but I'm working on it.

[fly74]

/latest/:

[Dickesplumpel]

I have had that too with espeasy instead of ESPEasy.

[Dickesplumpel]

ESP8266-1M on old sonoff basic no issues so far (40 minutes) after clean install, update from 20231225 can connect to AP but get no wifi connection after wifi configuration.

[TD-er]

@Dickesplumpel So if you do a clean install with the latest build on an old Sonoff Basic, all is working fine? If so, then it is a matter of RF calibration data messing up the WiFi stability.

[Dickesplumpel]

So far yes. RF calibration? 433MHz?

[TD-er]

Nope, WiFi. The ESP8266 does have a small section on the flash reserved to store some internal parameters regarding its WiFi. It must compensate for badly tuned antenna due to several factors.

For example components close by and the ABS of the enclosure can detune an antenna and the ESP must compensate for this.

However this tuning/calibration is also sometimes working against it. Clearing this forces a new calibration and that's what may have happened on your node.

[TD-er]

The build on the web flasher is now updated with the (hopefully) last changes before the next build.

• Support for W5500 SPI Ethernet without IRQ pin connected (e.g. on M5Stack AtomPOE with AtomS3)
• Show active Ethernet chip in sysinfo/JSON
• Add note to configure pull-up on Hardware tab
• Remove max. rules file limit on rules editor page
• No longer crashing on WiFi disconnect or wifi power off (except for wifimode,off command on web page)
• No longer "unable to connect due to unprocessed disconnect event"

[chemmex]

Both problems I mentioned remain so far (on C3 and C6 LittleFS)

• http server is not reachable in AP mode
• reset is partial, system name and WiFi settings are not cleared. Devices are, though

[TD-er]

HTTP not being reachable is for sure a breaking issue, so will look into that. The partial reset can wait till later as it will be dealt with when switching to this "safeboot" way I mentioned before.

[Dickesplumpel]

ESP8266-1M web-ui after short time way slower than web-ui on 20131225 build and sometimes not reacting. After a certain time (~30 minutes) changes made on web-ui are not stored and web-ui not rechable for about 20 seconds after pressing submit button. Flashed 2 times, same result, 20231225 build works well after hours. On 4M1M no such problems but web-ui feels slower than 20231225 build.

[TD-er]

It is possible the previous build you were running still had the bug where the "force B/G" option was inverted. So please have a look at it and see if actually forcing it to use 802.11b or 802.11g mode does make it more stable and responsive.

[Dickesplumpel]

No. The first 1-2 minutes it works well and then it goes slower and slower as if on a computer memory gets full and you have only swap space left on an old hard drive.

[TD-er]

Both problems I mentioned remain so far (on C3 and C6 LittleFS)

• http server is not reachable in AP mode

I can reach the setup page on a C3 while in initial setup, but there is for sure something really funky going on. Right after a power cycle (first power cycle after flashing + erasing) it was all a lot more smooth.

[Dickesplumpel]

Ok, this I have seen too. First powercycle after flash on usb-cable everything seems to be o.k.. After disconnecting from PC and power on with 230V power connector in another room it gets slow.

[chemmex]

I can reach the setup page on a C3 while in initial setup, but there is for sure something really funky going on. Right after a power cycle (first power cycle after flashing + erasing) it was all a lot more smooth.

I caught http server on C6 once

[TD-er]

I did try on a few more nodes and noticed you sometimes need to slide down on the browser to refresh the page. So I guess the webserver may not be online (or maybe restarted) when you connect and are redirected by the captive portal.

The only thing I can think of is that the webserver is restarted when you receive an IPv6 address. So is it possible you were running a "max" build or "custom" build? As those are the only ones at this moment which have IPv6 support included.

[chemmex]

A good guess, but no, I used the normal build and always received 192.168.4.2 from the ESP.

Few minutes ago, when I deleted WiFi credentials from the config page of already connected unit, I restarted the board and the ESPEasy setup page opened via the helper. Then I erased the flash with esptool, reflashed the same C3 20240215 normal build, and this time it restarted a couple more times with the following log:

Build changed!
ESP-ROM:esp32c3-api1-20210207
Build:Feb  7 2021
rst:0x1 (POWERON),boot:0x8 (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
mode:DOUT, clock div:1
load:0x3fcd5820,len:0x48
load:0x403cc710,len:0x644
load:0x403ce710,len:0x2294
SHA-256 comparison failed:
Calculated: 0c0480ed6fc3e18c0caa198de07def35a2e5fbd537d3d4cbc161bbff681e2b77
Expected: ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
Attempting to boot anyway...
entry 0x403cc710
ЄU00.207 : (272172) Info   :

INIT : Booting version: ESP_Easy_mega_20240215_normal_ESP32c3_4M316k_LittleFS_CDC, (GitHub Actions) mega_dfe2bda (ESP32 SDK 5.1.2.240206)
00.210 : (272028) Info   : INIT : Free RAM:272028
00.211 : (271948) Info   : INIT : Cold Boot - Restart Reason: CPU0: Vbat power on reset
00.212 : (271836) Info   : FS   : Mounting...
00.223 : (269844) Info   : FS   : LittleFS mount successful, used 16384 bytes of 323584

Build changed!
00.367 : (269188) Info   : ESPEasy console using ESPEasySerial
00.389 : (268596) Info   : ESPEasy console fallback enabled
00.412 : (268480) Error  : CRC  : SecuritySettings CRC...FAIL
00.427 : (268432) Info   : INIT : SPI not enabled
00.428 : (268384) Info   : Set Network mode: WiFi
00.531 : (268336) Info   : WIFI : Set WiFi to STA
00.674 : (229716) Info   : WiFi : Start network scan all channels
08.090 : (228092) Info   : WiFi : Scan finished, found: 18
08.094 : (228548) Info   : WiFi : Start network scan all channels
15.110 : (227132) Info   : WiFi : Scan finished, found: 16
15.114 : (227852) Info   : Setup: Scan all channels

PID:0
Version:0
INIT : Incorrect PID or version!
RESET: Resetting factory defaults... using default settings
RESET: Warm boot, reset count: 0
RESET: formatting...
RESET: formatting done...
20.369 : (226616) Info   : SaveToFile: ControllerSettings index: 0
20.371 : (226608) Info   : SaveToFile: free stack: 7344
22.606 : (226784) Info   : FILE : Saved config.dat offset: 8192 size: 820
22.607 : (226720) Info   : SaveToFile: free stack after: 7344
22.612 : (226268) Info   : ESPEasy console using ESPE22.633 : (226204) Info   : ESPEasy console fallback enabled
22.636 : (226156) Info   : SaveToFile: free stack: 7472
24.960 : (226076) Info   : FILE : Saved config.dat offset: 0 size: 3028
24.962 : (226012) Info   : SaveToFile: free stack after: 7472
24.964 : (225960) Info   : SaveToFile: free stack: 7408
25.046 : (225880) Info   : FILE : Saved security.dat offset: 0 size: 593
25.048 : (225816) Info   : SaveToFile: free stack after: 7408
RESET: Successful, rebooting. (you might need to press the reset button if you've just flashed the firmware)
26.050 : (225236) Info   : WiFi : WifiDisconnect()
26.254 : (225176) Info   : WIFI : Disconnected! Reason: '(1) Unspecified'
26.256 : (225008) Info   : WIFI : Arduino wifi status: WL_DISCONNECTED 6 ESPeasy internal wifi status: DISCONNECTED
26.368 : (224976) Info   : WiFi : WifiDisconnect()
26.570 : (224900) Info   : WIFI : Disconnected! Reason: '(1) Unspecified'
26.672 : (224284) Info   : WIFI : Set WiFi to OFF
ESP-ROM:esp32c3-api1-20210207
Build:Feb  7 2021
rst:0x3 (RTC_SW_SYS_RST),boot:0x8 (SPI_FAST_FLASH_BOOT)
Saved PC:0x40048b82
SPIWP:0xee
mode:DOUT, clock div:1
load:0x3fcd5820,len:0x48
load:0x403cc710,len:0x644
load:0x403ce710,len:0x2294
SHA-256 comparison failed:
Calculated: 0c0480ed6fc3e18c0caa198de07def35a2e5fbd537d3d4cbc161bbff681e2b77
Expected: ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
Attempting to boot anyway...
entry 0x403cc710
ЄU00.212 : (272128) Info   :

INIT : Booting version: ESP_Easy_mega_20240215_normal_ESP32c3_4M316k_LittleFS_CDC, (GitHub Actions) mega_dfe2bda (ESP32 SDK 5.1.2.240206)
00.214 : (271984) Info   : INIT : Free RAM:271984
00.216 : (271808) Info   : INIT : Soft Reboot #1 Last Action before Reboot: Intended Reboot: ResetFactory Last systime: 26 - Restart Reason: CPU0: Software reset digital core
00.217 : (271728) Info   : FS   : Mounting...
00.225 : (269736) Info   : FS   : LittleFS mount su51552 bytes of 323584
00.243 : (268472) Info   : CRC  : Settings CRC...OK
00.249 : (268280) Info   : ESPEasy console using ESPEasySerial
00.271 : (268744) Info   : ESPEasy console fallback enabled
00.282 : (268628) Info   : CRC  : SecuritySettings CRC...OK
00.293 : (268508) Info   : NVS  : Save FacDefPref
00.295 : (268460) Info   : NVS  : Save UnitName
00.297 : (268412) Info   : NVS  : Save WIFI_Flags
00.298 : (268364) Info   : NVS  : Save WIFI_SSID1
00.300 : (268316) Info   : NVS  : Save WIFI_PASS1
00.302 : (267212) Info   : NVS  : Save WIFI_AP_PASS
00.305 : (267688) Info   : NVS  : Save WiFI_IP
00.307 : (267640) Info   : NVS  : Save ETH_IP
00.308 : (267592) Info   : NVS  : Save ETH_HW_CONF
00.309 : (267560) Info   : NVS  : Save Log
00.310 : (267512) Info   : NVS  : Save Console
00.311 : (267536) Info   : INIT : SPI not enabled
00.312 : (267488) Info   : Set Network mode: WiFi
00.413 : (267440) Info   : WIFI : Set WiFi to STA
00.559 : (228820) Info   : WiFi : Start network scan all channels
07.776 : (226500) Info   : WiFi : Scan finished, found: 20
07.781 : (227012) Info   : WiFi : Start network scan all channels
15.198 : (225260) Info   : WiFi : Scan finished, found: 20
15.202 : (226852) Info   : Setup: Scan all channels
15.208 : (226788) Info   : ESPEasy console using ESPEasySerial
15.229 : (226716) Info   : ESPEasy console fallback enabled
15.231 : (226668) Info   : INIT : Free RAM:226716
15.235 : (226604) Info   : ESPEasy console using ESPEasySerial
15.257 : (226540) Info   : ESPEasy console fallback enabled
15.259 : (225900) Info   : INFO : Plugins: 47 ["Normal"] (ESP32 SDK 5.1.2.240206)
15.262 : (225960) Error  : WIFI : No valid wifi settings
15.265 : (225896) Info   : WiFi : WiFiConnected(), start AP
15.266 : (225836) Info   : WiFi : WifiDisconnect()
15.469 : (225820) Info   : WIFI : Disconnected! Reason: '(1) Unspecified'
15.472 : (225660) Info   : WIFI : Arduino wifi status: WL_DISCONNECTED 6 ESPeasy internal wifi status: DISCONNECTED
15.571 : (225660) Info   : WIFI : Set WiFi to OFF
15.781 : (248544) Info   : WIFI : Set WiFi to AP
16.862 : (220868) Info   : WIFI : AP Mode enabled. SSID: ESP-Easy IP: 192.168.4.1 ch: 1
16.864 : (220804) Info   : WiFi : Start network scan all channels
26.388 : (217172) Info   : WiFi : Scan finished, found: 21
26.392 : (218832) Info   : WiFi : Start network scan all channels
35.715 : (217172) Info   : WiFi : Scan finished, found: 19
35.718 : (218616) Info   : WIFI : Arduino wifi status: WL_DISCONNECTED 6 ESPeasy internal wifi status: DISCONNECTED
35.723 : (213788) Info   : Webserver: start
37.067 : (213580) Info   : WD   : Uptime 0  ConnectFailures 0 FreeMem 213724 WiFiStatus: WL_DISCONNECTED 6 ESPeasy internal wifi status: DISCONNECTED
50.122 : (211496) Info   : AP Mode: Client connected: 20:48:A16:32:5D:44 Connected devices: 1

Again, I was able to open the setup page.

On next erase/reflash cycle, it doesn't open anymore. And it pings, so that's definitely an http issue.

[TD-er]

Ton has made a PR to hopefully fix the slowlyness ( #4978 ) Problem is that I'm not seeing such an extreme slowdown as the rest of you experience. But at least he was positive about the initial results when testing it.

[TD-er]

I put the build from Ton's PR on https://td-er.nl/ESPEasy/latest/ If that doesn't work, I have some other thought of things to revert, but that's something for after a good night sleep.

[chemmex]

Ok, tried C3 with Ton's recent build.

It seems there were some more successful captive portal openings, but still with random pattern. I got it successfully opened several times on a PC with Chrome, and there was a difference when it opened automatically via helper (pointing to http://www.msftconnecttest.com/redirect) and when I entered 192.168.4.1 directly. In the first case, ESPEasy did send css and favicon, and in the second it didn't. On Android phone, it never opened successfully, although the helper window sometimes popped up with ERR_CONNECTION_ABORTED

[Dickesplumpel]

The estreme slowdown is only on the 1M build, the 8266-4M and the ESP32-C3 are not much slower New 1M build much better than previous build because it seems that it is only sometimes getting slower, sometimes changes were submitted and sometimes not. When the changes were not made the comitted message shows up emediatly after pushing the button (not 1-3 seconds later as on my items usually) and firefox gets connection error: "Fehler: Verbindung unterbrochen Die Verbindung zum Server wurde zurückgesetzt, während die Seite geladen wurde." and web-ui is not reachable for about 20 seconds. Log shows " ConnectFailures 0"

[TD-er]

Good to know the changes Ton made also affect the ESP8266 as this means I don't have to look into going back in changes specific to ESP32.

I now only need to focus on what I may have changed regarding starting of services (and restarting them)

[TD-er]

I just tried running on a normal build for 4M ESP8266 on a Wemos D1 mini like unit. Completely wiped and flashed from the web-flasher with the latest one I put up there with Ton's PR code. It is running just fine so far.

I could set it up using my mobile just without any hassle.

However it is sad to see how little free RAM there is available on the ESP8266. (less than 5k on the root page)

[chemmex]

I can connect to ESP8266 and ESP32-LittleFS without problems. The troubled builds are SDK 5.1-based ESP32-C3 and ESP32-C6

[TD-er]

Is it still troubling and which C3/C6 builds do you actually use?

[chemmex]

ESP_Easy_mega_20240216_normal_ESP32cx_4M316k_LittleFS_CDC. Flashed through web flasher with full erase.

It is almost the same as the previous build

[TD-er]

Will look into it...

[Dickesplumpel]

Yes, after a while running the sonoff basic has same issues like previous build, after a reboot it seems getting more worse. ESP-8285 seems not having these issues, running for 15 minutes now, made a few reboots, everything all right, I keep watching.

[TD-er]

There is a build in progress to test mainly for ESP82xx as it does try to be a bit easy on the memory while serving web pages. I never understood why especially the "normal" builds on ESP8266 were consuming so much more memory compared to those with LIMIT_BUILD_SIZE enabled. But now I added an extra flush and delay call right after serving the web template pages which 'restores' free memory and I had on the same node 10k more free memory (from 9k to 19k in the system info plugin and from 5k to 15k on the root page) N.B. this will not make a similar jump on the other builds like from 16k free to 26k free as it is probably related to LWIP not freeing buffers once they were needed.

For the C3 I have seen a node struggling and showing massive slowdowns when running the 'normal' build, so I will now focus on this. I think it may have been a recent change in either Arduino or IDF code.

[TD-er]

@chemmex Can you try disabling the serial console? Or at least not use the USB to serial as a serial console?

I got the impression this may become blocking when the buffers are not read. (thus no terminal reading the USB serial port)

[chemmex]

Not much difference. Rregardless of serial setting, loop duration deviates from 120 ms to this:

[TD-er]

There is a GH Actions build running, so as soon as your required bin is done you can download it from here: https://github.com/letscontrolit/ESPEasy/actions/runs/7942526241

The one I meant was about the "Console" lines in the timing stats The WiFi scan does always take 6 - 8 sec and thus the longest loop run will also be this long.

[TD-er]

Hmm the build failed, so will fix that but in the mean time you could try this build I made on my PC Is a zip file containing both the factory and the non-factory bin file.