Hi drsrikanthb, the peer data is not stored in NVS unless you did so in your firmware. There is no other way to keep peer data unless storing it in NVS and set it from NVS after waking up from deep sleep.

I don't think you have set channel in the right way. You should set it like this, memcpy(config.sta.bssid, bssid, sizeof(config.sta.bssid)); config.sta.bssid_set = 1; memcpy(config.sta.ssid, ssid, strlen(ssid)); memcpy(config.sta.password, password, strlen(password)); config.sta.channel = channel; e...

`esp_wifi_set_channel()` does not work for fast connection. To accelerate connection, you should specify `channel` field of `wifi_sta_config_t` to that of AP instead.
ESP32 is different with ESP8266, it can not accelerate connection with BSSID and WIFI_FAST_SCAN specified.

We have document WiFi.rst for how to get channel state information. But we haven't document or example for how to use it to measure distance. Distance measurement is just one of the specific applications of channel state information, so it is not much possible to describe it in IDF.

Would you like to use WiFi RTT for distance measurement? ESP32 does not support it and there is no plan to implement it now. We suggest to use channel state information which can also be used to measure distance. And it is already supported in esp-idf.

Is there any comparison with other CPUs?

esp-idf has supported channel state information which is the basis of WiFi RTT since idfv3.1. But protocol stack of WiFi RTT is not supported yet. For channel state information, please refer to WiFi documentation wifi.rst in esp-idf directory.

ESP32 do not support to receive packets on 5GHz band. That means if router is 5GHz only, smartconfig will never succeed. If smart phone connects to 5G, Smart config works if the following conditions are satisfied: 1. The SSIDs of 2.4G and 5G are the same. 2. Update IDF to v3.2 which will be released...

I guess that it may be caused by the IP address. In IDF v2.1, IP address is lost once WiFi disconnects. But in IDF v3.0, IP address keeps unchanged in 120 seconds after WiFi disconnects. Due to IP address is unchanged, TCP connections bound on it are not changed.

First, you need a WiFi card which can capture WiFi packets. Second, install software Omnipeek or Wireshark on your PC. Then you can use it to capture WiFi packets. The disconnect reason can be obtained when receiving SYSTEM_EVENT_STA_DISCONNECTED event. It is defined in struct in esp_event.h: typede...