Closed fabltd closed 6 months ago
Did you read the issue template? Hardware? TLS?
My appogies
ESP32-WROOM-32D yes using TLS = espMqttClientSecure mqttClient;
I guess it's the TLS client. The underlying "client context" is created in heap memory. Not much I can do here.
There are some ways to reduce the TLS client memory any idea where I would set this?
I don't know, never explored this area.
@fabltd if you are on ESP32 there is no easy way AFAIK, because the MBEDTLS_SSL_MAX_CONTENT_LEN
constant is compile time constant used in all SSL connections and came from CONFIG_MBEDTLS_SSL_MAX_CONTENT_LEN
from sdkconfig.h
(that is why i love BearSSL much more over mbedTLS). So the only chance I see is to reconfigure the SDK and rebuild all libraries.
BearSSL on an ESP32 has a much lighter footprint than MbedTLS (45kB vs 150kB). Tasmota has a trimmed down arduino/espressif32 core you can use that uses BearSSL. Try replacing the platform in your PIO ini with
platform = https://github.com/tasmota/platform-espressif32.git
or a specific version like
When using this libiary I am seeing a sizable reduction in heapsize.
Any suggestions on how to reduce this.
I am also trying to use the HTTPS OTA but this is crashes due to insufficant free heap.
Help...
Thanks