v4.1.1.0 is released for ESP32-C2, ESP32-C3, ESP32-C6, ESP32, and ESP32-S2. The changes since the previous version are as follows.
ESP32C2-ATDocumentation for Release v4.1.1.0 is available at https://docs.espressif.com/projects/esp-at/en/release-v4.1.0.0/esp32c2/index.html. ESP32C2-AT v4.1.1.0 is a minor update for ESP32C2-AT v4.1.0.0.
The firmware:
This is the list of changes since release v4.1.0.0:
Known IssuesAT+FS
may fail after repeated read/write operationsAT+MQTTSUB
with QoS 1, triggered by a fast SUBACK response from the brokerAT+MQTTPUB
with QoS 1 or 2, AT+MQTTSUB
with QoS 1, or AT+MQTTUNSUB
, if the ESP does not receive the corresponding PUBACK, SUBACK, or UNSUBACK within 30 seconds,Documentation for Release v4.1.1.0 is available at https://docs.espressif.com/projects/esp-at/en/release-v4.1.0.0/esp32c3/index.html. ESP32C3-AT v4.1.1.0 is a minor update for ESP32C3-AT v4.1.0.0.
The firmwares:
This is the list of changes since release v4.1.0.0:
Known IssuesAT+FS
may fail after repeated read/write operationsAT+MQTTSUB
with QoS 1, triggered by a fast SUBACK response from the brokerAT+MQTTPUB
with QoS 1 or 2, AT+MQTTSUB
with QoS 1, or AT+MQTTUNSUB
, if the ESP does not receive the corresponding PUBACK, SUBACK, or UNSUBACK within 30 seconds,Documentation for Release v4.1.1.0 is available at https://docs.espressif.com/projects/esp-at/en/release-v4.1.0.0/esp32c6/index.html. ESP32C6-AT v4.1.1.0 is a minor update for ESP32C6-AT v4.1.0.0.
The firmwares:
This is the list of changes since release v4.1.0.0:
Known IssuesAT+FS
may fail after repeated read/write operationsAT+MQTTSUB
with QoS 1, triggered by a fast SUBACK response from the brokerAT+MQTTPUB
with QoS 1 or 2, AT+MQTTSUB
with QoS 1, or AT+MQTTUNSUB
, if the ESP does not receive the corresponding PUBACK, SUBACK, or UNSUBACK within 30 seconds,Documentation for Release v4.1.1.0 is available at https://docs.espressif.com/projects/esp-at/en/release-v4.1.0.0/esp32/index.html. ESP32-AT v4.1.1.0 is a minor update for ESP32-AT v4.1.0.0.
The firmwares:
This is the list of changes since release v4.1.0.0:
Known IssuesAT+FS
may fail after repeated read/write operationsAT+BLUFI=1
command, if the device was previously in SoftAP or Station+SoftAP mode, the SoftAP interface may briefly restart.AT+BLUFI
after disabling and re-enabling BLUFI without power cycling, BLE advertising may fail to start.AT+MQTTSUB
with QoS 1, triggered by a fast SUBACK response from the brokerAT+MQTTPUB
with QoS 1 or 2, AT+MQTTSUB
with QoS 1, or AT+MQTTUNSUB
, if the ESP does not receive the corresponding PUBACK, SUBACK, or UNSUBACK within 30 seconds,Documentation for Release v4.1.1.0 is available at https://docs.espressif.com/projects/esp-at/en/release-v4.1.0.0/esp32s2/index.html. ESP32S2-AT v4.1.1.0 is a major update for ESP32S2-AT v3.4.0.0.
The firmwares:
This is the list of changes since release v3.4.0.0:
Known IssuesAT+FS
may fail after repeated read/write operationsAT+SYSRAM
setup command to detail memory capacityAT+SYSROLLBACK
query command to obtain the address and version of the current and rollback firmwareAT+RFCAL
command to support RF full calibrationAT+SYSMFG
commandAT+SYSMSGFILTER
did not work when the data contained \r\n
AT+CWBANDWIDTH
command to set Wi‑Fi bandwidthAT+CWCONFIG
command to set the global inactive time and listen intervalAT+CWLAPOPT
, AT+WPS
, AT+CWSTARTSMART
and AT+BLUFI
AT+CWJAP
after connecting to an Enterprise AP with AT+CWJEAP
AT+CWHOSTNAME
AT+CWLAP
did not return valid APs when BLUFI was enabledAT+CWQAP
and AT+CWRECONNCFG
commandsAT+CWRECONNCFG
command twicenetif
parameter to the AT+CIPSERVER
commandAT+CIPSSLCCIPHER
command to configure the SSL cipher‑suite listAT+CIPSTART
and AT+CIPDOMAIN
commandsAT+CIPDNS
AT+CWDHCP
returning an incorrect DHCP state after the DHCP server was disabledAT+CIPRECVLEN?
always returned a fixed set of five connectionsAT+CIPSTATUS
returned incorrect statusesAT+CIPCLOSE
could not close a connection after reaching the maximum number of open socketsAT+CIPSTART
did not work in passive‑read modeAT+CIPRECVLEN
AT+CIPSTO
did not take effect when data transmission failedAT+MDNS
instance
, proto
, and txt
parameters to the AT+MDNS
commandAT+HTTPCFG
command to configure certificates for HTTPAT+HTTPCHEAD
commandAT+MQTTPUB
with QoS 1 or 2, AT+MQTTSUB
with QoS 1, or AT+MQTTUNSUB
, if the ESP does not receive the corresponding PUBACK, SUBACK, or UNSUBACK within 30 seconds,fatfs.bin
size and the required sizefatfs.bin
was not pre‑burned before flashingfwrite()
returned OK
but data was not written to the file systemslist
issues where the pointer fail_item
was used after free
AT+WSCFG
command to configure certificates in WebSocketesp-idf
version updated to ~v5.4.2*.defaults
pre_wakeup_callback
and process_light_sleep
hook eventsesp_at_get_netconn_count()
to esp_at_get_netconn_max_count()
esp_at_get_smartconfig_start_config()
APITCP & SSL
: TCP/SSL connections are now proactively closed immediately when their associated netif state changes (netif down, stop, or lost IP). In previous versions, the connections would remain open until a keep-alive timeout, send timeout, or max retry threshold was reached - often taking tens of seconds to close. This change significantly reduces latency in connection teardown and improves system responsiveness.esptool.py merge_bin
fatfs_to_http_server
examplehttp_get_to_fatfs
exampledocs.espressif.com/projects/esp-at
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4