Javier Peletier

@lux4rd0: Yes, it is normal that when you add `- -Wframe-larger-than=100` you get lots of warnings for other functions. We are just adding this flag with a very low threshold...

@lux4rd0 Thank you for your feedback, of which I have extracted interesting conclusions after testing. TL;DR: It is the framework upgrade to 2.0.2 that fixes `setup()` stack problem, **but because...

Thanks @jesserockz, I have updated the recommendation above.

Hello @OttoWinter > Indeed the compiler allocates the stack storage for the local variables for the entire setup function, which results in this issue. Not only the storage for the...

> Yes it takes 4 byte per STA, but tbh I don't think that's enough to warrant that change IMHO Uh!, I am extremely, extremely conservative regarding memory usage in...

Hi @OttoWinter, what should I do? I see two alternatives: **Alternative 1**. Reconsider as per [this comment](https://github.com/esphome/esphome/pull/3577#issuecomment-1160849994). Notice you won't be able to refer to a variable created with `with_local_Pvariable`...

@quentinmit can I look at your yaml?

@OttoWinter the way I solved this, please take a look at the code: 1. Implemented `with_local_variable()` in a simple way. **The callback cannot be async, thus preventing any code interleaving**....

@lux4rd0: The modifications required for this PR (changes to code generation) make it unsuitable to use it as-is standalone until it is merged. Sorry for the inconvenience. Therefore, I have...

🎉🎉