Pavel Brychta

> @me-no-dev please merge this pull request. Unfortunately it make no sense IMHO because upcoming release 3.0.0 of the ESP8266 Core drops out AXTLS support. It seems like we do...

Default trace size is 0x200 - see https://github.com/krzychb/EspSaveCrash/blob/fd7cc2ccb40117431311b3a93e73984eb143bae3/src/EspSaveCrash.h#L84 You can try to use `EspSaveCrash(0x10, 0x400);` to give more space for saving...

This is **Async** library, based on AsyncTCP so there is nothing in the loop() and given callbacks are called asynchronously. There are some limitations in this approach (no delay() in...

And what is the problem EXACTLY? As I said to you before - this library rely on asyncTCP, which rely on internal LWIP. If the LWIP stack is working with...

+1 for this. I also suggest that the `payload` should be of type `const uint8_t *` instead of plain `char *` which is little confusing for newbies.

Well, actually after 3.0.0 Core release for the ESP8266 the whole SSL thing with ESPAsyncTCP is broken down. Your solution for ESP32 is good, but I think that the best...

Let me guess - you treat the message in the ESP8266 side as C string, right? If so you have missing the terminating /0 character, because the message payload doesn't...

:D so it is as I expected. The `char *payload` is not C string. Actually it is `uint8_t *payload` with the length of the message in `size_t len` (it's little...

```cpp void onMqttMessage(char* topic, char* payload, AsyncMqttClientMessageProperties properties, size_t len, size_t index, size_t total) { char dummy[128]; if (len < sizeof(dummy)) { memcpy(dummy, payload, len); dummy[len] = 0; Serial.println(dummy); }...

Can you please post your code?