add ESP32-C3 Supermini to webflasher and platformio.ini

[Wolfgang1982]

Is your feature request related to a problem? Please describe.

It seems that (not all) ESP-C3 Supermini Boards are not supported.

Flashing via WebFlasher was not possible: Errormessage: Your type of C3 is not supported.

It is this ESP32-C3 Supermini:
https://de.aliexpress.com/item/1005008810581307.html?spm=a2g0o.productlist.main.15.722172b2Ja2NLD&algo_pvid=a156f75a-3c0e-4e09-a487-7de947adb516&algo_exp_id=a156f75a-3c0e-4e09-a487-7de947adb516-14&pdp_ext_f=%7B%22order%22%3A%22129%22%2C%22eval%22%3A%221%22%7D&pdp_npi=6%40dis%21EUR%216.90%213.24%21%21%2156.20%2126.41%21%40211b80e117559840200442732ee86b%2112000046761541732%21sea%21AT%212603135881%21X%211%210%21n_tag%3A-29919%3Bd%3A28969f83%3Bm03_new_user%3A-29895&curPageLogUid=YlenK24Un4Lc&utparam-url=scene%3Asearch%7Cquery_from%3A%7Cx_object_id%3A1005008810581307%7C_p_origin_prod%3A

Describe the solution you'd like

How did I fix it?
I forked it on github and added the following lines in platformio.ini:

custom_ci_action = generic,generic_esp32,generic_esp32s3,generic_esp32s3_usb,esp32c3_supermini

...

[env:esp32c3_supermini]
board = esp32-c3-devkitm-1
build_flags = ${env.build_flags}
-DPIN_MAPPING_REQUIRED=1

The I flashed the new *bin to my ESP-C3

Maybe it's not the best solution since I'm new to this stuff...but right now it works....at least now for 1 hour.

My PINout in *json is:
"nrf24": {
"miso": 5,
"mosi": 6,
"clk": 4,
"irq": 2,
"en": 3,
"cs": 7
}

Describe alternatives you've considered

No response

Additional context

No response

[Wolfgang1982]

since my ESP32-C3_Supermini is powererd by a battery (via 5V USB) powerconsumption is very important for me.
What I noticed (without any background knowledge):
when ESP is powered on, the consumption is "pretty" high: about 110 mA (=approx. 0.6W)
also the Chiptemperature is real high: about 65-70°C - I was really worried about my board.
This phase continues for about 5 minutes...then suddenly the temperature and powerconsumption decreases to normal 45°C and only 50-70 mA (=approx. 0.3 W) This includes regular communication to iobroker (interval 10 seconds) plus live checking the webinterface.

So this "startup-phase" has obviously nothing to do with WiFicommunication..all data are visible after about 20-30sec after boot...is there a lot of background activity in openDTU after startup for 5 minutes? Or has it something to do with my (totally amateurish) workaround for the C3 Supermini?

[spcqike]

https://www.opendtu.solar/firmware/wifi_setup/

When OpenDTU is connected to a configured Wi-Fi AP as a client, the "OpenDTU-*" Access Point is closed after 3 minutes (timeout is configurable).

i gues, its the AP mode after startup.