Closed peterhalicky closed 4 months ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Correct me if I'm wrong, but can't you switch back to the arduino framework with something like this?
esphome:
framework:
type: arduino
Arduino framework is used by default anyway; that config won't change anything: https://esphome.io/components/esp32.html#esp32-arduino-framework
The problem
Pull request 5157 introduced a different MQTT client than what was used before on ESP32. This new client, however, uses nearly 21kB more memory than the one that was in use before (Arduino).
With commit preceding 9980b9972fcac080a1eb1987107484644e7a8d1d, I get this:
With commit 9980b9972fcac080a1eb1987107484644e7a8d1d, I get this:
This difference can mean whether a configuration will work just fine, or will be crashing horribly. The PR doesn't say why is the ESP-IDF mqtt client better - so unless there's a very good reason to use ESP-IDF mqtt client, I'd say esphome should switch back to using the Arduino library.
Which version of ESPHome has the issue?
commit 9980b997
What type of installation are you using?
Docker
Which version of Home Assistant has the issue?
No response
What platform are you using?
ESP32
Board
esp32dev
Component causing the issue
mqtt
Example YAML snippet
Anything in the logs that might be useful for us?
No response
Additional information
No response