Open wladwnt opened 3 years ago
Hi @wladwnt, I'm sorry to tell you the passage of Philbowles (~ a year ago).
And happy to inform you with maintaining and continuation of his work.
You can check H4AsyncMQTT for the MQTT, and you can check for the other stack members within a complete PlatformIO environment in H4Plugins_Env
ESP32: I had issues with 0.9 Version, but with 1.0.1 it is worser. I do lot of stress tests, enabling/disabling many times WLAN router, killing MQTT server, emulating very poor WiFi signal etc. V1.0.1 crashes (causing ESP_RST_PANIC) much oftner than V0.9 did. In total, it happens approximately each 50st. event, so definately not each time and is not really reproducable (that why is hard to trace what exactely happens). Yes, I publish only if WiFi is connected, only when free heap is enough, only if TXQ size is not too big, hav payloads length only max. 128 bytes, ..... Maybe the issue is the AsyncTCP used by PangolinMQTT, I dont know.
So, for now, I mooved back to original ESP-IDF v3.3 MQTT implementation. It has some disadvantages, but absolutely stable. PangolinMQTT is basicaly great Lib, but at least fro ESP32 must reach higher maturity.