Wi-Fi Expansion
ESP32-H2 does not support Wi-Fi functionality natively, but it is possible to use the same Wi-Fi API and features using Wi-Fi expansion.
On ESP32-P4 and ESP32-H2, Wi-Fi is provided by the hosted remote backend. Current esp_hosted releases implement esp_eap_client_remote_set_ttls_phase2_method() and do not implement esp_eap_client_remote_set_phase2_method(). esp_eap_client_set_phase2_method() returns ESP_ERR_NOT_SUPPORTED on that path. The legacy setter still forwards ESP_EAP_TTLS_PHASE2_GTC through the existing RPC. Selecting EAP-GTC that way requires a backend that understands this new value; released backends predate it, so the result depends on the backend.
ESP32-H2 esp_wifi_remote
The principle of Wi-Fi Expansion operation is to add another ESP32 series, Wi-Fi capable, target connected to the ESP32-H2 in a pre-defined way. Your project could then include the esp_wifi_remote component using:
idf.py add-dependency esp_wifi_remote
Please follow the instructions described in the component documentation which is linked in the above paragraph.
To explore the Wi‑Fi Expansion functionality on ESP32-H2, you can:
Start with the built‑in MQTT over TLS example
examples/protocols/mqtt(or the MQTT 5.0 variantexamples/protocols/mqtt5) and choose Wi‑Fi connection in the project configuration menu;