Hello, The mDNS warning is expected and can be ignored. If you explicitly start mDNS, appropriate Wi-Fi provisioning mDNS service will be announced. This is for future enhancements in the phone apps, for a smoother provisioning flow. The "No Internet Connection" message is also expected since your p...

Since that code is part of an external codebase, we cannot change it as of now. However, we have aded a fix to suppress that error. Going ahead, when we move to a newer azure-iot-sdk-c , we will ensure that the error is fixed in the actual source itself.

If you are using code from the example, then on boot up, if the device is already provisioned, it will not start the BLE, and instead connect to the network directly. However, for your other use wherein you want to have a time-out and the time-out should also check for "BLE client connectivity", the...

Hello,

We will check how the events which are currently being handled in esp-idf/components/protocomm/src/simple_ble/simple_ble.c can be exposed to applications. Meanwhile, what exactly is your use case?

Hello,

The softap_prov and ble_prov examples were added before the Wi-Fi scan feature was introduced. Please use the newer "manager" example for the scan feature (https://github.com/espressif/esp-idf/tr ... ng/manager).

Hello, Re-provisioning an ESP32 already connected to a network is not an intended use case for the Unified Wi-Fi provisioning component. You must explicitly reset the ESP32's saved Wi-Fi credentials and reboot it to restart provisioning. Hope this helps. If you specify your exact use case, I can che...

We have updated https://github.com/espressif/esp-azure a couple of days back so that it can now compile with IDF 4.0. Can you check with that?

Hello Nirav, We will check what the problem is, however, the solution proposed doesn't seem the right one. The server cannot change the socket id of an accepted socket. A change in the socket id can happen only if the client initiates a new HTTP connection. In that case, the secure session establish...