You can go with MicroMsg or EspTouch App for smartconfig tests.

In the present, because of 2.4G-5G mixed WiFi and WiFi6 routers, AirKiss protocol is no longer easy to use, even unusable, and using EspTouch and EspTouch V2 protocol requires additional installation of app, I'm afraid that many people don't like to use smartconfig now, but I think there should still be such a function, and it only takes up about 40K of firmware space :)

Rebase all commits to single one, and append document for smartconfig.

Hi @projectgus, I didn't keep working on #4404 , because the ESP32 port requires ESP-IDF v5, which is a lot different than before, so I chose to start over.

According to PR #13763 removed all STATIC macro in source files.

It looks like a nice feature, though I hadn't come across it before. I presume you've tested it? :)

I would guess that the maintainers would prefer this to be an optional component (even if it default to on by default).

To save folks from looking at the docs you've created (which are good, nice job!), they can read about this feature by looking at the Espressif SmartConfig documentation.

@mattytrentini thanks for your review.

I would guess that the maintainers would prefer this to be an optional component (even if it default to on by default).

About the optional component, here is my thoughts:

1. Keep the modification of ports/esp32/esp32_common.cmake

2. Add a macro definition to (every) ports/esp32/boards/XXX/mpconfigboard.h, looks like:

   #define MICROPY_ENABLE_SMARTCONFIG (1)

3. Finally, surround a preprocessor command to the whole modsmartconfig.c file, looks like:

   #if MICROPY_ENABLE_SMARTCONFIG
   ...
   ...
   #endif // MICROPY_ENABLE_SMARTCONFIG

I have tried these steps, #define MICROPY_ENABLE_SMARTCONFIG (1) and #define MICROPY_ENABLE_SMARTCONFIG (0) can make this component optionally appear or disappear. Please let me know if I'm correct, thanks~

they can read about this feature by looking at the Espressif SmartConfig documentation.

I see what you mean, aligning the function names in the component to the function names in the idf documentation.

But I can't fully agree with you, even if you do align the function names, there're still some differences between them, for example, the IDF API doesn't directly return the information, such as ssid and password, as well as the status of the smartconfig process, so you still have to refer to the component's documentation.

This is a amazing PR, thank you guys!

The following changes were made in this update:

• Added version(), timeout(), fast_mode() and v2_key() functions.
• Renamed function rvd_data() to v2_data().
• Change the return value type of v2_data() to str.
• Make module optional (already selected by default)

Hope this will add to normal Micropython too!

@PIBSAS thanks for your reply.

Code size report:

   bare-arm:    +0 +0.000% 
minimal x86:    +0 +0.000% 
   unix x64:    +0 +0.000% standard
      stm32:    +0 +0.000% PYBV10
     mimxrt:    +0 +0.000% TEENSY40
        rp2:    +0 +0.000% RPI_PICO_W
       samd:    +0 +0.000% ADAFRUIT_ITSYBITSY_M4_EXPRESS
  qemu rv32:    +0 +0.000% VIRT_RV32

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.57%. Comparing base (e5eeaa7) to head (06a72b3).
Report is 12 commits behind head on master.

@@           Coverage Diff           @@
##           master   #13658   +/-   ##
=======================================
  Coverage   98.57%   98.57%           
=======================================
  Files         164      164           
  Lines       21336    21336           
=======================================
  Hits        21031    21031           
  Misses        305      305           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

I have no idea why there are 4 more files in the file changed list and the number of checks has increased to 67 and one of them fails....