I am using ESP32 with IDF v3.2
I followed through ESP IDF Guide to create a minimal binary and flashed successfully. The ESP32 starts up in AP mode due to first two 0 parameters in mDashStartWithWifi
v
oid app_main()
{
// Initialize NVS
esp_err_t ret = nvs_flash_init();
if (ret == ESP_ERR_NVS_NO_FREE_PAGES || ret == ESP_ERR_NVS_NEW_VERSION_FOUND)
{
ESP_ERROR_CHECK(nvs_flash_erase());
ret = nvs_flash_init();
}
ESP_ERROR_CHECK( ret );
mDashStartWithWifi(0, 0, DEVICE_ID, DEVICE_PASS);
}
Then, I followed the instructions to create a PWA app and load into the mobile phone browser. Then I have switched the mobile to the ESP32 WiFi (AP), and tried to scan for new device.
First, the SCAN timed out - my assumption is that the mobile app could not resolve the symbolic links in the app.js scripts (mdash.net and provisioning.mdash.net).
Then in app.js I changed those links to 192.168.4.1- which is the IP of the ESP32 (the IP of the mobile phone is 192.168.4.2). Then the scanning stops with a message that the access key cannot be stored.
At the console I see a log message ssl conn_handshake error with error 0xffff8880. I assume this is the reason while the PWA cannot fetch the access key for device and thus prevents the PWA app to discover the device.
Is anybody seeing similar issues?
Istvan.