Just a quick update on this old issue (might be useful for others with similar issues). Not sure what the root-cause was, but generally all these possible symptoms were solved: * thread safety * fragmenting out messages, receiving fragmented messages * fragmenting on TLS layer (solved recently in ht...

Hi Leander,

which version of IDF and esp-mqtt are you using?
There were indeed some issues like malformed packets in some cases but with older version of the library. Simple check is to update mqtt submodule to the latest master and see if the issues still present.

Hi,

There's no official support for ESP32 MQTT Broker in IDF. You can probably find some implementations somewhere else, this is an example an ESP32 broker https://github.com/nopnop2002/esp-idf-mqtt-broker.

Hi,

No need to use event_loop to publish messages. You can just call mqtt-publish from a separate task every 10 s. I would also recommend event flags to be set on connection event and cleared on disconnect. Then you can simply run the needed API whenever you're connected.

CLion works flawlessly for me with ESP-IDF projects. I'm on macOS, but also tried windows and linux in the past and saw no issues. The only configuration needed was to setup IDF_PATH under Toolchain->CMake->Environment. Other configuration was to set the build directory to be in line with idf.py, bu...

Hi smbunn, you can connect to your WiFi just disabling [EXAMPLE_ESP_WIFI_MODE_AP](https://github.com/espressif/esp-who/blob/master/examples/single_chip/recognition_solution/main/app_wifi.c#L39) in app_wifi.c, which enables station mode. ESP-WHO references IDF 3.2, where esp-mqtt is already integrate...

Hi,

This return code means `MBEDTLS_ERR_SSL_ALLOC_FAILED`, so mbedtls failed to malloc some data.
You may want to printf available heap size with `esp_get_free_heap_size()`.

Hi, Configuring CLion with CMake IDF build system is very simple, that is: no configuration needed ;) Just open an existing project, where your project CMakeLists.txt resides, possibly set your IDF_PATH and a generation path (to be in line with `idf.py` so you can conveniently run flash/monitor from...

Hi, The best starting point would be idf 3.2, where esp-mqtt is integrated as component. If you have to stick with 3.1, then you can easily * checkout 3.2 separately and copy folders `example/protocols/mqtt/tcp` and `components/mqtt` to your idf 3.1.3 tree * go to `components/mqtt/esp-mqtt` and chec...

Hi belph86, the idf tcp_server example receives a message from a blocking socket and echos it back. if you're talking about the delay between esp32 sending the message and its reception in python, then indeed this could be Nagles algorithm. You can set the socket to nodelay mode with: int nodelay = ...