Factory Reset operation failure in ESP-Matter When Wi-Fi Is Unavailable during device boot up and post matter commissioning (CON-1952)

[aggaddam]

Describe the bug
It has been observed that the ESP-Matter factory reset does not work as expected when the device is not connected to a Wi-Fi router post matter commissioning and at boot time. In this scenario, the factory reset fails to fully clear fabric and other persistent states, resulting in stale information being retained.

Test Case 1 – Expected Behavior (Pass)

1. Commission the Matter device using the chip tool.
2. Verify that commissioning completes successfully and the device is connected to the Wi-Fi network.
3. After successful commissioning, trigger a Matter factory reset.
4. The device enters standard commissioning mode (advertising over BLE) after the factory reset.

Test Case 2 – Expected Behavior (Pass)

1. Commission the Matter device using the chip tool.
2. Verify that commissioning completes successfully and the device is connected to the Wi-Fi network.
3. After successful commissioning, switch off the Wi-Fi network.
4. The device disconnects from Wi-Fi and periodically attempts to reconnect.
5. Trigger the Matter factory reset.
6. The device enters standard commissioning mode (advertising over BLE) after the factory reset.

Test Case 3 – Unexpected Behavior (Fail)

1. Commission the Matter device using the chip tool.
2. Verify that commissioning completes successfully and the device is connected to the Wi-Fi network.
3. After successful commissioning, switch off the Wi-Fi network.
4. Reboot the device.
5. After reboot, the device repeatedly attempts to reconnect to the Wi-Fi network.
6. Trigger the Matter factory reset.
Expected: The device should enter standard commissioning mode (advertising over BLE).
Actual: The device does not enter commissioning mode. Some factory reset operations fail, fabric information is not cleared, and the device continues attempting to reconnect to the Wi-Fi network even after the factory reset.

Log:

I (13028) pp: pp rom version: 9387209
I (13032) net80211: net80211 rom version: 9387209
I (13038) wifi:wifi driver task: 3fcbe71c, prio:23, stack:6656, core=0
I (13055) wifi:wifi firmware version: 79fa3f41ba
I (13055) wifi:wifi certification version: v7.0
I (13055) wifi:config NVS flash: enabled
I (13056) wifi:config nano formatting: disabled
I (13060) wifi:Init data frame dynamic rx buffer num: 32
I (13065) wifi:Init static rx mgmt buffer num: 5
I (13069) wifi:Init management short buffer num: 32
I (13074) wifi:Init dynamic tx buffer num: 32
I (13078) wifi:Init static tx FG buffer num: 2
I (13082) wifi:Init static rx buffer size: 2212
I (13086) wifi:Init static rx buffer num: 10
I (13090) wifi:Init dynamic rx buffer num: 32
I (13094) wifi_init: rx ba win: 6
I (13098) wifi_init: accept mbox: 6
I (13102) wifi_init: tcpip mbox: 32
I (13106) wifi_init: udp mbox: 6
I (13110) wifi_init: tcp mbox: 6
I (13113) wifi_init: tcp tx win: 5760
I (13118) wifi_init: tcp rx win: 5760
I (13122) wifi_init: tcp mss: 1440
I (13126) wifi_init: WiFi IRAM OP enabled
I (13131) wifi_init: WiFi RX IRAM OP enabled
I (13144) chip[DL]: NVS set: chip-counters/reboot-count = 2 (0x2)
I (13146) BLE_INIT: BT controller compile version [d74042a]
I (13149) BLE_INIT: Bluetooth MAC: 84:f7:03:29:08:62
I (13155) phy_init: phy_version 1200,2b7123f9,Feb 18 2025,15:22:21
I (13196) NimBLE: GAP procedure initiated: stop advertising.

I (13197) CHIP[DL]: BLE host-controller synced
I (13699) chip[DL]: Configuring CHIPoBLE advertising (interval 25 ms, connectable)
I (13699) NimBLE: GAP procedure initiated: advertise; 
I (13702) NimBLE: disc_mode=2
I (13705) NimBLE:  adv_channel_map=0 own_addr_type=1 adv_filter_policy=0 adv_itvl_min=40 adv_itvl_max=40
I (13715) NimBLE: 

I (13719) chip[DL]: CHIPoBLE advertising started
I (13723) chip[DL]: Starting ESP WiFi layer
I (13730) wifi:mode : sta (84:f7:03:29:08:60) + softAP (84:f7:03:29:08:61)
I (13735) wifi:enable tsf
I (13737) wifi:Total power save buffer number: 16
I (13741) wifi:Init max length of beacon: 752/752
I (13746) wifi:Init max length of beacon: 752/752
I (13750) chip[DL]: Posting ESPSystemEvent: Wifi Event with eventId : 43
W (13757) wifi:Haven't to connect to a suitable AP now!
I (13762) chip[DL]: Attempting to connect WiFi station interface
I (13764) chip[DL]: Posting ESPSystemEvent: Wifi Event with eventId : 2
I (13776) chip[DL]: Posting ESPSystemEvent: Wifi Event with eventId : 43
I (13783) chip[DL]: Posting ESPSystemEvent: Wifi Event with eventId : 12
I (13772) chip[DL]: WiFi station state change: NotConnected -> Connecting
I (13798) chip[DL]: Done driving station state, nothing else to do...
I (13805) chip[SVR]: Initializing subscription resumption storage...
I (13813) chip[SVR]: Server initializing...
I (13817) chip[TS]: Last Known Good Time: 2023-10-14T01:16:48
I (13827) chip[FP]: Fabric index 0x1 was retrieved from storage. Compressed FabricId 0xD77074AC6AE155B2, FabricId 0x0000000000000001, NodeId 0x0000000000000001, VendorId 0xFFF1
I (13840) chip[DMG]: AccessControl: initializing
I (13844) chip[DMG]: Examples::AccessControlDelegate::Init
I (13851) chip[DMG]: AccessControl: setting
I (13855) chip[DMG]: DefaultAclStorage: initializing
I (13862) chip[DMG]: DefaultAclStorage: 1 entries loaded
I (13867) chip[SVR]: WARNING: mTestEventTriggerDelegate is null
I (13900) esp_matter_cluster: Cluster plugin init common callback
I (13905) chip[DMG]: AccessControlCluster: initializing
I (13906) chip[SVR]: Fabric already commissioned. Disabling BLE advertisement
I (13910) chip[IN]: CASE Server enabling CASE session setups
I (13917) chip[SVR]: Joining Multicast groups
I (13923) chip[SVR]: Server Listening...
I (13926) chip[DL]: WIFI_EVENT_STA_START
W (13930) wifi:Haven't to connect to a suitable AP now!
I (13935) chip[DL]: Attempting to connect WiFi station interface
E (13941) wifi:sta is connecting, return error
E (13945) chip[DL]: esp_wifi_connect() failed: UNKNOWN ERROR
I (13952) NimBLE: GAP procedure initiated: stop advertising.

I (13959) chip[DL]: CHIPoBLE advertising stopped
I (13964) NimBLE: GAP procedure initiated: stop advertising.

I (13972) MATT_APP: Matter Start - success
W (13974) MATT_APP: fab count = 1
I (14029) chip[DL]: Posting ESPSystemEvent: Wifi Event with eventId : 3
I (14030) chip[DL]: Posting ESPSystemEvent: Wifi Event with eventId : 13
I (14033) chip[DL]: WIFI_EVENT_STA_STOP
I (14037) chip[DL]: Starting ESP WiFi layer
E (14042) chip[DL]: esp_wifi_start() failed: UNKNOWN ERROR
I (14049) wifi:flush txq
I (14050) wifi:stop sw txq
I (14053) wifi:lmac stop hw txq
W (14106) M_HELPER: Apply last saved wifi cred
I (14106) wifi:(2.4G)set country: cc=IN schan=1 nchan=13 policy=1
I (14108) wifi:mode : sta (84:f7:03:29:08:60)
I (14109) wifi:enable tsf
I (14112) chip[DL]: Posting ESPSystemEvent: Wifi Event with eventId : 43
I (14120) chip[DL]: Posting ESPSystemEvent: Wifi Event with eventId : 2
I (14126) chip[DL]: WIFI_EVENT_STA_START
W (14131) wifi:Haven't to connect to a suitable AP now!
I (14136) chip[DL]: Attempting to connect WiFi station interface
I (14144) chip[DL]: Done driving station state, nothing else to do...
E (14149) wifi:sta is connecting, return error
I (14153) PAL: WAITING FOR WIFI 0x3fcb2a88
I (15713) chip[DL]: Posting ESPSystemEvent: Wifi Event with eventId : 5
I (15713) chip[DL]: WIFI_EVENT_STA_DISCONNECTED
I (15714) chip[DL]: WiFi station state change: Connecting -> Connecting_Failed
W (15723) wifi:Haven't to connect to a suitable AP now!
E (15727) chip[DL]: Failed to get configured network when updating network status: Error ESP32:0x0500300F
W (15738) wifi:Haven't to connect to a suitable AP now!
I (15742) chip[DL]: WiFi station state change: Connecting_Failed -> NotConnected
W (15750) wifi:Haven't to connect to a suitable AP now!
E (15755) chip[DL]: Failed to get configured network when updating network status: Error ESP32:0x0500300F
I (15765) chip[DL]: Next WiFi station reconnect in 5000 ms
I (15771) chip[DL]: Done driving station state, nothing else to do...
I (15972) chip[DL]: BLE deinit successful and memory reclaimed
W (20772) wifi:Haven't to connect to a suitable AP now!
I (20773) chip[DL]: Attempting to connect WiFi station interface
I (20774) chip[DL]: WiFi station state change: NotConnected -> Connecting
W (20780) wifi:Haven't to connect to a suitable AP now!
E (20785) chip[DL]: Failed to get configured network when updating network status: Error ESP32:0x0500300F
I (20795) chip[DL]: Done driving station state, nothing else to do...
I (22344) chip[DL]: Posting ESPSystemEvent: Wifi Event with eventId : 5
I (22344) chip[DL]: WIFI_EVENT_STA_DISCONNECTED
I (22345) chip[DL]: WiFi station state change: Connecting -> Connecting_Failed
W (22353) wifi:Haven't to connect to a suitable AP now!
E (22358) chip[DL]: Failed to get configured network when updating network status: Error ESP32:0x0500300F
W (22368) wifi:Haven't to connect to a suitable AP now!
I (22373) chip[DL]: WiFi station state change: Connecting_Failed -> NotConnected
W (22381) wifi:Haven't to connect to a suitable AP now!
E (22386) chip[DL]: Failed to get configured network when updating network status: Error ESP32:0x0500300F
I (22396) chip[DL]: Next WiFi station reconnect in 5000 ms
I (22402) chip[DL]: Done driving station state, nothing else to do...
W (27403) wifi:Haven't to connect to a suitable AP now!
I (27404) chip[DL]: Attempting to connect WiFi station interface
I (27405) chip[DL]: WiFi station state change: NotConnected -> Connecting
W (27411) wifi:Haven't to connect to a suitable AP now!
E (27416) chip[DL]: Failed to get configured network when updating network status: Error ESP32:0x0500300F
I (27426) chip[DL]: Done driving station state, nothing else to do...
I (28975) chip[DL]: Posting ESPSystemEvent: Wifi Event with eventId : 5
I (28975) chip[DL]: WIFI_EVENT_STA_DISCONNECTED
I (28976) chip[DL]: WiFi station state change: Connecting -> Connecting_Failed
W (28984) wifi:Haven't to connect to a suitable AP now!
E (28989) chip[DL]: Failed to get configured network when updating network status: Error ESP32:0x0500300F
W (28999) wifi:Haven't to connect to a suitable AP now!
I (29004) chip[DL]: WiFi station state change: Connecting_Failed -> NotConnected
W (29012) wifi:Haven't to connect to a suitable AP now!
E (29017) chip[DL]: Failed to get configured network when updating network status: Error ESP32:0x0500300F
I (29027) chip[DL]: Next WiFi station reconnect in 5000 ms
I (29033) chip[DL]: Done driving station state, nothing else to do...
W (34034) wifi:Haven't to connect to a suitable AP now!
I (34035) chip[DL]: Attempting to connect WiFi station interface
I (34036) chip[DL]: WiFi station state change: NotConnected -> Connecting
W (34042) wifi:Haven't to connect to a suitable AP now!
E (34047) chip[DL]: Failed to get configured network when updating network status: Error ESP32:0x0500300F
I (34057) chip[DL]: Done driving station state, nothing else to do...
I (34706) DEV_CTRL: Reset ac params
I (34709) PAL: Factory reset requested
I (34709) NVM_STORE: devstate_e sz = 4
I (34723) chip[DL]: Posting ESPSystemEvent: Wifi Event with eventId : 3
I (34723) chip[DL]: WIFI_EVENT_STA_STOP
I (34723) chip[DL]: Starting ESP WiFi layer
E (34728) chip[DL]: esp_wifi_start() failed: UNKNOWN ERROR
I (34734) wifi:flush txq
I (34736) wifi:stop sw txq
I (34739) wifi:lmac stop hw txq
I (310) cpu_start: Unicore app

Environment

• ESP-Matter Commit Id: 75775c0 (release/v1.5)

• ESP-IDF Commit Id: 4c2820d377d1375e787bcef612f0c32c1427d183 (v5.4.1)

• SoC (eg: ESP32 or ESP32-C3): ESP32-C3

• Device Logs (Please attach the log file): Shared above

• Host Machine OS: Ubuntu

• Host Machine Python version: 3.10/3.11

• Commissioner app and versions if present: NA

• Home hub app and versions if present: NA

• Commissioner's logs if present: NA

Any additional details
...

[VaishaliAvhale]

Hi @aggaddam,

I tried the test case mentioned above, but I was unable to reproduce the issue at my end. After rebooting the DUT, I attempted a factory reset using both methods—long-pressing the boot button and the matter esp factoryreset command—and both worked as expected.

Attached are the logs for your reference.

esp-matter-Issue-1682.log

Could you please share more details on how you are triggering the factory reset? That will help us understand the issue better and assist you more effectively.

Thanks!

[aggaddam]

@VaishaliAvhale I am calling esp_matter::factory_reset(); upon button trigger .If you need detailed logs, let me know. I can get the logs during the factory reset operation.

I am seeing these logs for failed and success case.

Failed case:
I (34723) chip[DL]: Posting ESPSystemEvent: Wifi Event with eventId : 3
I (34723) chip[DL]: WIFI_EVENT_STA_STOP
I (34723) chip[DL]: Starting ESP WiFi layer
E (34728) chip[DL]: esp_wifi_start() failed: UNKNOWN ERROR
I (34734) wifi:flush txq
I (34736) wifi:stop sw txq
I (34739) wifi:lmac stop hw txq

Success Case:
I (72820) chip[TS]: Pending Last Known Good Time: 2023-10-14T01:16:48
I (72821) chip[TS]: Previous Last Known Good Time: 2023-10-14T01:16:48
I (72825) chip[TS]: Reverted Last Known Good Time to previous value
I (72872) chip[FP]: Fabric (0x1) deleted.
I (72872) chip[ZCL]: OpCreds: Fabric index 0x1 was removed
I (72873) chip[DIS]: Updating services using commissioning mode 0
I (72879) chip[DIS]: CHIP minimal mDNS started advertising.
I (72962) chip[DL]: Performing factory reset
I (72980) wifi:flush txq
I (72980) wifi:stop sw txq
I (72980) wifi:lmac stop hw txq
I (73073) chip[DL]: System restarting

[shubhamdp]

Button Press handler (long press)

esp-matter/examples/common/app_reset/app_reset.cpp

Lines 28 to 35 in ccad0a9

	static void button_factory_reset_released_cb(void *arg, void *data)
	{
	if (perform_factory_reset) {
	ESP_LOGI(TAG, "Starting factory reset");
	esp_matter::factory_reset();
	perform_factory_reset = false;
	}
	}

Click to view logs

I (42664) app_driver: Toggle button pressed
I (42664) esp_matter_attribute: ********** W : Endpoint 0x0001's Cluster 0x00000006's Attribute 0x00000000 is 0 **********
I (42684) led_driver_ws2812: led set r:0, g:0, b:0
I (44824) chip[DL]: Posting ESPSystemEvent: Wifi Event with eventId : 5
I (44824) chip[DL]: WIFI_EVENT_STA_DISCONNECTED
I (44824) chip[DL]: WiFi station state change: Connecting -> Connecting_Failed
W (44834) wifi:Haven't to connect to a suitable AP now!
E (44834) chip[DL]: Failed to get configured network when updating network status: Error ESP32:0x0500300F
W (44844) wifi:Haven't to connect to a suitable AP now!
I (44844) chip[DL]: WiFi station state change: Connecting_Failed -> NotConnected
W (44854) wifi:Haven't to connect to a suitable AP now!
E (44864) chip[DL]: Failed to get configured network when updating network status: Error ESP32:0x0500300F
I (44874) chip[DL]: Next WiFi station reconnect in 100 ms
I (44884) chip[DL]: Done driving station state, nothing else to do...
W (44984) wifi:Haven't to connect to a suitable AP now!
I (44984) chip[DL]: Attempting to connect WiFi station interface
I (44984) chip[DL]: WiFi station state change: NotConnected -> Connecting
W (44994) wifi:Haven't to connect to a suitable AP now!
E (44994) chip[DL]: Failed to get configured network when updating network status: Error ESP32:0x0500300F
I (45004) chip[DL]: Done driving station state, nothing else to do...
I (47394) chip[DL]: Posting ESPSystemEvent: Wifi Event with eventId : 5
I (47394) chip[DL]: WIFI_EVENT_STA_DISCONNECTED
I (47394) chip[DL]: WiFi station state change: Connecting -> Connecting_Failed
W (47404) wifi:Haven't to connect to a suitable AP now!
E (47404) chip[DL]: Failed to get configured network when updating network status: Error ESP32:0x0500300F
W (47414) wifi:Haven't to connect to a suitable AP now!
I (47424) chip[DL]: WiFi station state change: Connecting_Failed -> NotConnected
W (47434) wifi:Haven't to connect to a suitable AP now!
E (47434) chip[DL]: Failed to get configured network when updating network status: Error ESP32:0x0500300F
I (47444) chip[DL]: Next WiFi station reconnect in 100 ms
I (47454) chip[DL]: Done driving station state, nothing else to do...
W (47554) wifi:Haven't to connect to a suitable AP now!
I (47554) chip[DL]: Attempting to connect WiFi station interface
I (47554) chip[DL]: WiFi station state change: NotConnected -> Connecting
W (47564) wifi:Haven't to connect to a suitable AP now!
E (47574) chip[DL]: Failed to get configured network when updating network status: Error ESP32:0x0500300F
I (47584) chip[DL]: Done driving station state, nothing else to do...
I (47684) app_reset: Factory reset triggered. Release the button to start factory reset.
I (49304) app_reset: Starting factory reset
I (49324) chip[TS]: Pending Last Known Good Time: 2023-10-14T01:16:48
I (49324) chip[TS]: Previous Last Known Good Time: 2023-10-14T01:16:48
I (49324) chip[TS]: Reverted Last Known Good Time to previous value
I (49384) chip[FP]: Fabric (0x1) deleted.
I (49384) chip[ZCL]: OpCreds: Fabric index 0x1 was removed
I (49384) chip[DIS]: Updating services using commissioning mode 0
I (49394) chip[DIS]: CHIP minimal mDNS started advertising.
I (49454) app_main: Fabric will be removed
I (49464) app_main: Fabric removed successfully
I (49464) chip[DIS]: Updating services using commissioning mode 1
I (49464) chip[DIS]: CHIP minimal mDNS started advertising.
I (49474) chip[DIS]: Advertise commission parameter vendorID=65521 productID=32768 discriminator=3840/15 cm=1 cp=0 jf=0
I (49484) chip[DIS]: CHIP minimal mDNS configured as 'Commissionable node device'; instance name: F62DDF5783BFEB0B.
I (49484) chip[DIS]: mDNS service published: _matterc._udp
I (49504) chip[DL]: Performing factory reset
I (49514) wifi:flush txq
I (49514) wifi:stop sw txq
I (49514) wifi:lmac stop hw txq
I (49574) chip[DL]: System restarting

Console handler (matter esp factoryreset)
https://github.com/espressif/esp-matter/blob/main/components/esp_matter_console/esp_matter_console_factory_reset.cpp#L25-L28

Click to view logs

W (204404) wifi:Haven't to connect to a suitable AP now!
E (204404) chip[DL]: Failed to get configured network when updating network status: Error ESP32:0x0500300F
W (204414) wifi:Haven't to connect to a suitable AP now!
I (204414) chip[DL]: WiFi station state change: Connecting_Failed -> NotConnected
W (204424) wifi:Haven't to connect to a suitable AP now!
E (204434) chip[DL]: Failed to get configured network when updating network status: Error ESP32:0x0500300F
I (204444) chip[DL]: Next WiFi station reconnect in 100 ms
I (204454) chip[DL]: Done driving station state, nothing else to do...
> matter esp factoryreW (204554) wifi:Haven't to connect to a suitable AP now!
I (204554) chip[DL]: Attempting to connect WiFi station interface
I (204554) chip[DL]: WiFi station state change: NotConnected -> Connecting
W (204564) wifi:Haven't to connect to a suitable AP now!
E (204564) chip[DL]: Failed to get configured network when updating network status: Error ESP32:0x0500300F
I (204584) chip[DL]: Done driving station state, nothing else to do...

> matter esp factoryreset

Done
I (205064) chip[TS]: Pending Last Known Good Time: 2023-10-14T01:16:48
I (205064) chip[TS]: Previous Last Known Good Time: 2023-10-14T01:16:48
I (205074) chip[TS]: Reverted Last Known Good Time to previous value
                                                                                                                                                                                            I (205124) chip[FP]: Fabric (0x1) deleted.
I (205124) chip[ZCL]: OpCreds: Fabric index 0x1 was removed
I (205124) chip[DIS]: Updating services using commissioning mode 0
I (205134) chip[DIS]: CHIP minimal mDNS started advertising.
> I (205204) app_main: Fabric will be removed
I (205204) app_main: Fabric removed successfully
I (205204) chip[DIS]: Updating services using commissioning mode 1
I (205204) chip[DIS]: CHIP minimal mDNS started advertising.
I (205214) chip[DIS]: Advertise commission parameter vendorID=65521 productID=32768 discriminator=3840/15 cm=1 cp=0 jf=0
I (205224) chip[DIS]: CHIP minimal mDNS configured as 'Commissionable node device'; instance name: FB16597801EAED3E.
I (205244) chip[DIS]: mDNS service published: _matterc._udp
I (205244) chip[DL]: Performing factory reset
I (205254) wifi:flush txq
I (205254) wifi:stop sw txq
I (205254) wifi:lmac stop hw txq
I (205304) chip[DL]: System restarting

Can you enable debug logging and share the logs, or if you are doing anything different for factory reset the device? Can you share the code snippet around this API to better understand this.

[aggaddam]

@shubhamdp I am sharing the code snippet here. matter_helperfcn_factory_reset() will be called when factory reset is invoked either by button or command received from other main micro controller connected to WiFi module over UART. Mean while, I will get the detailed logs

Can Wi-Fi driver errors prevent the factory reset operation from completing, given that our application uses the same Wi-Fi STA default interface for both Matter and our IoT cloud?

For example:

IoT cloud first → Matter later:
The device is onboarded to our IoT cloud first. It initializes the Wi-Fi STA default interface, then updates the station interface with Wi-Fi credentials via the Matter SDK, and advertises itself over mDNS to support the Matter platform.

Matter first → IoT cloud later:
The device is commissioned to a Matter fabric first and later onboarded to our IoT cloud using the same Wi-Fi credentials established during Matter commissioning. On every reboot, after Matter starts successfully, the device initializes the Wi-Fi STA default interface using the last saved Wi-Fi credentials.

In both scenarios, the same Wi-Fi driver and STA interface are used and updated by Matter and the IoT cloud.

void matter_helperfcn_factory_reset(void)
{
    // Schedule the factory rest
    PlatformMgr().ScheduleWork(matter_helper_do_esp_factory_reset,
                               reinterpret_cast<intptr_t>(nullptr));
}

static void matter_helper_do_esp_factory_reset(intptr_t context)
{
    // Factory reset matter info stored in device followed by soft reset
    esp_matter::factory_reset();
}

[aggaddam]

@shubhamdp
The issue occurs only when the device is Matter-commissioned and rebooted while not connected to a Wi-Fi network, and a factory reset is initiated in this disconnected state. If the device reconnects to Wi-Fi after reboot and then a factory reset is initiated, it works as expected. So, I am suspecting wifi driver errors might be causing the factory reset operation to fail.

Here is the detailed log for the factory reset failed scenario.

I (53071) DEV_CTRL: Reset ac params
D (53071) nvs: nvs_open_from_partition storage 1
D (53071) nvs: nvs_set_str NANOEG off
D (53072) nvs: nvs_close 79
D (53075) nvs: nvs_open_from_partition storage 1
D (53079) nvs: nvs_set bzr_st 1 1
D (53083) nvs: nvs_close 80
D (53085) nvs: nvs_open_from_partition storage 1
D (53090) nvs: nvs_set_blob sleep_state 200
D (53094) nvs: nvs_close 81
D (53097) nvs: nvs_open_from_partition storage 1
D (53101) nvs: nvs_set_blob cmf_profile 848
D (53106) nvs: nvs_close 82
D (53108) nvs: nvs_open_from_partition Lifestyle 1
D (53113) NVS_PROV: Open (NVS) hdl Done
D (53117) nvs: nvs_set_str PROD_SN 
D (53122) NVS_PROV: Set PSN Done
D (53123) wifi:scan end: arg=0x3fca6eb4, status=0, ss_state=0x3
D (53129) wifi:perform scan: ss_state=0x9, chan<10,0>, dur<0,120>
D (53136) NVS_PROV: NVS commit, status - Done 
D (53139) nvs: nvs_close 83
I (53142) PAL: Factory reset requested
D (53147) nvs: nvs_open_from_partition storage 1
I (53151) NVM_STORE: devstate_e sz = 4
D (53155) nvs: nvs_set_blob dev_state 4
D (53160) nvs: nvs_set_blob last_sate 4
D (53163) nvs: nvs_set_blob mqtt 688
D (53167) nvs: nvs_set_blob iam_cred 584
D (53171) efuse: BLK1 REG1 [8-15], len=8 bits
D (53175) efuse: BLK1 REG1 [0-7], len=8 bits
D (53179) efuse: BLK1 REG0 [24-31], len=8 bits
D (53184) efuse: BLK1 REG0 [16-23], len=8 bits
D (53188) efuse: BLK1 REG0 [8-15], len=8 bits
D (53193) efuse: BLK1 REG0 [0-7], len=8 bits
D (53197) nvs: nvs_set_blob tpug_adap 104
D (53210) nvs: nvs_set_blob dev_id 50
D (53210) nvs: nvs_set_blob end_point 128
D (53211) nvs: nvs_open_from_partition Lifestyle 1
D (53214) nvs: nvs_set fab_count 1 0
D (53218) nvs: nvs_close 85
D (53220) nvs: nvs_close 84
D (53223) nvs: nvs_open_from_partition storage 1
D (53227) nvs: nvs_set_blob lc_info 80
D (53231) nvs: nvs_close 86
D (53234) wifi:connect status 1 -> 0
D (53237) wifi:Start wifi disconnect
D (53240) wifi:connect status 0 -> 0
D (53243) wifi:cancel previous scan, ss_state=0x3, just_scan=0
D (53249) wifi:scan end: arg=0x3fca6eb4, status=4, ss_state=0x0
D (53254) wifi:stop scan timer and scan, ss_state=0x0
D (53259) wifi:filter: set rx policy=4
D (53263) wifi:first chan=1
D (53265) wifi:handoff_cb: status=1
D (53268) wifi:clear scan ap list
D (53271) wifi:filter: set rx policy=8
D (53274) wifi:filter: set rx policy=2
D (53278) wifi:clear scan ap list
D (53281) wifi:clear blacklist
D (53283) wifi:clear rc list
D (53286) event: running post WIFI_EVENT:3 with handler 0x420e4bda and context 0x3fcbda88 on loop 0x3fcbb02c
D (53296) esp_netif_handlers: esp_netif action stopped with netif0x3fcbd834 from event_id=3
D (53304) esp_netif_lwip: check: remote, if=0x3fcbd834 fn=0x420e219e
D (53310) esp_netif_lwip: call api in lwip: ret=0x5002, give sem
D (53316) event: running post WIFI_EVENT:3 with handler 0x42071c12 and context 0x3fcbffe0 on loop 0x3fcbb02c
I (53326) chip[DL]: Posting ESPSystemEvent: Wifi Event with eventId : 3
I (53333) chip[DL]: WIFI_EVENT_STA_STOP
I (53338) chip[DL]: Starting ESP WiFi layer
E (53343) chip[DL]: esp_wifi_start() failed: ESP_ERR_WIFI_STOP_STATE
I (53350) wifi:flush txq
I (53352) wifi:stop sw txq
I (53354) wifi:lmac stop hw txq
D (53357) wifi:filter: set rx policy=0
I (325) cpu_start: Unicore app
D (325) cpu_start: Pro cpu up
D (333) clk: RTC_SLOW_CLK calibration value: 3486080
D (338) cpu_start: calling init function: 0x420001dc on core: 0

Refer to this attachment for the full log

Factory_reset_failed.txt