[BUG]No AP showing up when the sensor can't connect to known SSID

[hrikken]

Describe the bug
I connected the ESP32S3 16/8 PSRAM to a local Wifi SSID. No problems. I moved it to another building where that SSID doen't exist. Then the AP mode is not enabled and I can't change the Wifi settings

To Reproduce
Steps to reproduce the behavior:

1. Flash the ESP32-S3
2. Connect to the AP
3. Configure the local Wifi
4. Move to another building with a different SSID
5. Wait for the AP mode
6. Noting happens.....

Expected behavior
I expect the usual AP SSID of the ESP to appear in the network list in order to configure the new Wifi.

Screenshots
Not applicable

Used platform (please complete the following information):

• ESP type: ESP32-S3 16/8 PSRAM
• Build version: ESP_Easy_mega_20240414_max_ESP32s3_16M8M_LittleFS_OPI_PSRAM_CDC_ETH Apr 14 2024
• Build set Max

Platform Specifics (when applicable, please complete the following information):

• Flash size: 16M
• Brand/Model: Lolin S3
• Browser + OS : Chrome

Additional context
I flashed with the webflasher on td-er.nl/ESPEasy

[tonhuisman]

Duplicate for #4655

[danielPaggio]

Is there any hint how to fix? I try more than 6 months old build on 8266 or esp32s2 and esp32 boards and same issue .there was a hint compile without custom.h but I cant find this file in project..

[TD-er]

Nope, I need to fix this in the ESPEasy networking logic.
I did push this task forward to wait for the major networking refactoring in the Arduino code which has been merged less than a month ago.
The last 8 or 9 months I have been working hard on implementing ESP-IDF 5.x changes.

[danielPaggio]

Thanx for explanation root of the problem.

[danielPaggio]

By the way.... Is there any progress? Only for sure I ask.

[TD-er]

There is some work-in-progress, but it will not yet be fixed in the next upcoming build.
I aim for the build after for this to be dealt with.

[danielPaggio]

Waiting patiently. 😁Thanx👍