I think the root problem is ESP8266/32 being an inexpensive WiFi solution is just not powerful enough to handle concurrent or consecutive network requests. When it is busy, it appears to non-responding, and therefore Mbed thinks it has lost connection.
Related topics
Topic | Replies | Views | Activity | |
---|---|---|---|---|
Having trouble getting an ESP8266 module to connect to router using WIFI API | 9 | 1477 | March 12, 2022 | |
ESP32/WiFi not working under certain conditions with Mbed-OS-6 | 4 | 32 | December 12, 2024 | |
How to get past -3005 NSAPI_ERROR_NO_SOCKET returned from socket->connect() | 1 | 677 | September 18, 2020 | |
Did anyone get hardware flow control of ESP8266 to work on NUCLEO-F091RC to work? | 0 | 426 | November 29, 2019 | |
SIGABRT: Abnormal termination using Mbed-http | 1 | 628 | January 8, 2020 |