esp32 NG, connect fail

[tinswf]

Checklist

• Checked the issue tracker for similar issues to ensure this is not a duplicate
• Read the documentation to confirm the issue is not addressed there and your configuration is set correctly
• Tested with the latest version to ensure the issue hasn't been fixed

How often does this bug occurs?

always

Expected behavior

if the AP power on before our device，our device can connect the AP success，
but when our device power on, the AP is power off ,
and several hours later, the esp32 change to inactive，our device can not connect the AP

Actual behavior (suspected bug)

Uploading esp32 debug.txt…

Error logs or terminal output

No response

Steps to reproduce the behavior

refer to host debug message.txt

key info:
esp32: [0xb] Command failed

Project release version

ESP-Hosted Firmware version :: 1.0.2

System architecture

ARM 32-bit (Raspberry Pi 32-bit)

Operating system

Linux

Operating system version

win10

Shell

Bash

Additional context

No response

[mantriyogesh]

Is #530 any different for current issue @tinswf ?

[tinswf]

same