I spoke too soon—turning off IPV6 resulted in a stable connection for a few hours, but now the connection is failing again.

Update—I've turned off IPV6, which I believe was off by default in older versions of esp-idf but is on by default in 4.4.5. I still periodically get "error read data" errors, but this seems to have fixed the issue of ping/select() timeouts. My working theory is that my main home Wi-Fi router support...

I'm having major issues with WebSocket reliability on an ESP32-S3 with esp-idf 4.4.5. When sitting idle, the WebSocket mostly just receives ping messages from the server and responds. However, in this state the WebSocket disconnects frequently. I've noticed a few things - On my main home Wi-FI netwo...

It turned out to have something to do with how I was creating the http config struct. Now I have some HTTP "Out of buffer" errors but at least the memory corruption is fixed. Before: [Codebox] esp_http_client_config_t config; config.url = url; config.cert_pem = TUNESHINE_OTA_CERT; config.event_handl...

Thanks. Heap corruption detection didn’t come up with anything, but I’ll start removing code and try to diagnose the issue. How can someone tell in this situation that the address is bogus?

I'm getting consistent `StoreProhibited` errors when starting an OTA update, seemingly related to `calloc` calls. I'm using esp-idf 4.4.3 on an esp32-s3. The error seems to happen immediately before any HTTPS connection takes place. Any suggestions for how to investigate this error would be apprecia...

I'm developing firmware for an ESP32-S3 (after switching from an ESP32-WROOM) and ever since switching to the new chip I'm unable to see stack traces for panics, which makes debugging very difficult. I've tested this out by intentionally causing a panic by accessing a member of an uninstantiated cla...