You can configure this using the AT+SYSMSG command. You can set it with AT+SYSMSG=4. If the connected hotspot disconnects, the serial port will report "WIFI DISCONNECT\r\n".

Yes, it's possible. The ESP32 shares a single antenna for both Wi-Fi and Bluetooth LE, and you can configure it using the AT+RFPOWER command.

ESP-AT currently does not support ESP-WIFI-MESH.

When the main MCU sends AT commands to the ESP32 device, it is necessary to include an end-of-line character. The correct format in the program is "AT\r\n." You can refer to this for verifying whether the AT firmware has been successfully flashed.

You can set the maximum timeout using the <jap_timeout> parameter with AT+CWJAP. The "busy" prompt indicates that the system is processing the previous command and cannot respond to the current input. AT command processing is linear, meaning it can only accept the next command after completing the previous one.

Reason: The internal configuration paths are different, so it's necessary to clear the previous file configurations first.

Solution 1: Open the files in VSCode, then click on the trash can icon below to clear them, and finally recompile the firmware.

Solution 2: Delete the "build" folder in the project files, and then recompile.

That's possible; however, the standard AT firmware currently doesn't have this feature enabled. To enable this feature, you need to enable the driver's functionality in the ESP-AT framework and then recompile and flash the new firmware. (Note: SPI, I2C, PWM, and other functionalities can be used, but you won't be able to configure the pins as regular GPIOs.)

Yes, there are Modbus demo examples in the ESP-IDF code for ESP32.