filzek
filzek
We have changed the semaphore so that it is only activated when needed. This update addresses the issue that was occurring frequently, and its behavior is now improved.
We did not subit it yet as it cause some other failures that we arent yet able to solve in the current design such as: ``` ======================== THREADS INFO =========================...
it seens that the client->config->host is freed somewhere among the usage and the connection could not be set, not sure why, as the task and the handler could be doing...
> Hello [@filzek](https://github.com/filzek), I'm coming back to this ticket, do you have any update to share? That version you have as us to try do not have that problem, seems...
@glmfe lets wait until next week 10 July, so I can check all logs on 2000+ devices
Hi @glmfe We are still experiencing issues with the WebSocket, although we are not certain whether the root cause is related to the Wi-Fi library or another component. So far,...
1.5.0 seems quite stable now, we are testing and there is issues only when transport layer falls
could be setup in the esp_websocket_client_config_t or with a custom handler like in the CJSON to override: memoryHook.malloc_fn = spiram_calloc; memoryHook.free_fn = spiram_free; cJSON_InitHooks(&memoryHook); // Wrapper calloc SPI RAM. void*...
I have sent an pull request proposal to the maintainers.
https://github.com/espressif/esp-protocols/pull/586 send, so, if you need to use external memory in websocket, now it is full working like a charm.,