Issue with ESP32C3 and ESPAsyncWiFiManager.

[ShVerni]

Hello,

When using the ESP32C3 and the ESPAsyncWiFiManager library, I ran into some strange issues. I traced the problem to the ON_AP_FILTER function, which seemed to incorrectly find that the ESP32C3 wasn't in AP mode, and filtered out all requests no matter what.

I'm not sure if there's something wrong with the ON_AP_FILTER function running on the C3 or the implementation in ESPAsyncWiFiManager, but any insight would be appreciated.

Thank you!

[mathieucarbou]

I think you should ask the lib author ;-)
Here this is espasync, not the wifi manager.

[ShVerni]

Yes, and I have posted on the WiFiManager library issues as well. But as mentioned, and I'm sorry if that wasn't clear, considering the problem seems to be with the filter function in the ESPAsyncWebserver library, I wanted to ask here. If this isn't the appropriate place to discuss possible issues with the ESPAsyncWebserver library, than I apologize and would appreciate being pointed in the right direction.

[mathieucarbou]

The filtre implémentation is just an example on how to use filter. Up to library users to correctly set their implementation based on what they do.

[ShVerni]

Thanks for the clarification! I'll investigate further.

[ShVerni]

Hello,

So I'm afraid I'm still a bit confused. The ON_AP_FILTER and ON_AP_FILTER don't appear to just be example templates, but functions that are supposed to filter requests based on if the device is in AP mode or station mode. As per the example here:

https://github.com/ESP32Async/ESPAsyncWebServer/blob/main/examples/CaptivePortal/CaptivePortal.ino

These filters work as expected on an ESP32E and an ESP32-S3, but they don't work on an ESP32C3, I haven't had time to do much testing, but it seems the problem is with the line
#if SOC_WIFI_SUPPORTED || CONFIG_ESP_WIFI_REMOTE_ENABLED || LT_ARD_HAS_WIFI
which makes the function always return false.

If I replace this line from the example:

 server.addHandler(new CaptiveRequestHandler()).setFilter(ON_AP_FILTER); 

with this version that is identical to the ON_AP_FILTER function but without the #if statement, it works as expected:

 server.addHandler(new CaptiveRequestHandler()).setFilter([this](AsyncWebServerRequest *request)->bool{
        return WiFi.localIP() != request->client()->localIP();
      });

I'm sorry if I'm missing something, but other libraries, like PsychicHttp also implement the ON_AP_FILTER and ON_STA_FILTER filters in a similar way, so I don't think this is an issue with the ESPAsyncWiFiManager library. Again, please correct me if I'm misunderstanding something about these filters, and thanks so much for the help!

[mathieucarbou]

ON_AP_FILTER and ON_STA_FILTER have to be considered examples.
They were added as part of the library a long time ago, so we cannot remove them at the moment.
We wish they were not there because they are creating a coupling between the web server and the WiFi header which we do not like because some boards do not have WiFi but can optionally have ETH for example.

So please do not depend on them: write your own ones.

[ShVerni]

Aah, that makes sense! Thanks for explaining :-)