I have changed one line to ensure that I always start provisioning.
Provisioning starts Ok, but when I use the ESP Soft Ap Provisioning App from Google Play to connect to the AP it fails with
Code: Select all
I (868) wifi_prov_mgr: Provisioning started with service name : PROV_014E3E I (868) app: Provisioning started I (52168) wifi: new :<1,0>, old:<1,1>, ap:<1,1>, sta:<0,0>, prof:1 I (52168) wifi: station : 92:44:c8:a6:90:fe join, AID=1, bgn, 20 I (52288) esp_netif_lwip: DHCP server assigned IP to a station, IP is: 192.168.4.2 W (52708) wifi:<ba-add>idx:4 (ifx:1, 92:44:c8:a6:90:fe), tid:0, ssn:16, winSize:64 W (54378) httpd_uri: httpd_uri: URI '/' not found W (54388) httpd_txrx: httpd_resp_send_err: 404 Not Found - This URI does not exist E (54398) httpd_txrx: httpd_resp_send_err: error calling setsockopt : 22
Or is it post provisioning when the ESP32 is trying to connect to the target AP? I suspect not because there is no long indicating that the EP32 has returned STA or has finished provisioning.
The 2 warnings before the error are concerning too.
So what's going on?
Once the client connects the SoftAP to provide provisioning info, what are the endpoints it should hit up to provide that info? I'm asking because we want some control over the provisioning.
I've tried using the endpoints described here https://docs.espressif.com/projects/esp ... oning.html without much luck. Can I assume that proto-ver is a HTTP POST and the 3 others are HTTP GET?
How can I hook into the callbacks for those endpoints on the ESP32 so I can take alternate action?