async-mqtt-client used to depend on ASYNC_TCP_SSL_ENABLED

[ayushsharma82]

The async-mqtt-client library used to depend on the SSL implementation in original AsyncTCP. How can we achieve the same with current versions of AsyncTCP?

Currently it throws an error that this file is missing:

https://github.com/marvinroger/async-mqtt-client/blob/3d93fc7f662e65366f8e2b0d88b108f874f035b9/src/AsyncMqttClient.hpp#L22

[mathieucarbou]

AsyncTCP never supported SSL, neither in original fork, neither in this repo:

• https://github.com/search?q=repo%3Amathieucarbou%2FAsyncTCP%20beginSecure&type=code
• https://github.com/search?q=repo%me-no-dev%2FAsyncTCP%20beginSecure&type=code

Only ESPAsyncTCP has these methods, and implements them:

#if ASYNC_TCP_SSL_ENABLED
    void onSslFileRequest(AcSSlFileHandler cb, void* arg);
    void beginSecure(const char *cert, const char *private_key_file, const char *password);
#endif

ASYNC_TCP_SSL_ENABLED cannot be activated on ESP32.

[mathieucarbou]

if you need a wrapper on top of it, i did one: https://github.com/mathieucarbou/MycilaMQTT to facilitate config and usage. it supports SSL, direct publish or enqueing.

[ayushsharma82]

Perfect! I'll use it.

[mathieucarbou]

Note that there is also psychicMQTT that exist in case you do not like mine ;-)

[ayushsharma82]

Yours is actually fine. I was going to use ESP-DASH along with it so that's why async-mqtt-client was my first choice. I believe espressif's mqtt / MycilaMQTT will work fine together as well.

[mathieucarbou]

yes and it supports ssl with custom server certificate, or with an integrated CA bundle of trusted authorities (examples in the project)