-
-
Notifications
You must be signed in to change notification settings - Fork 169
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to increase the stack size? #303
Comments
Sorry for the naive questions, I am not familiar with esphome/arduino ecosystem... Just in case I also clean the ".esphome" folder from time to time... Not sure if that has any impact though :) |
I don't know the answer of your question. It's possible the define doesn't work because it's for the Arduino framework only. May be the setting is different for ESP-IDF. Could you ask for help at the ESPHome discord channel and share the solution here? |
Ok, I'll try to get some info and report back. |
Sorry to hijack this thread by maybe my question fits here and I don't need to open another issue. 😬 I tried it out of curiosity. It compiled but the esp did not react after the flash anymore so I had to reflash it via USB. ;) |
In the past the Arduino framework wasn't able to handle the 300 bytes BLE notifications from the JK-BMS. It did crash on the first received message. Some people reported it does work in general now. The Arduino framework is an additional abstraction layer on top of ESP-IDF. I try to avoid additional/unnecessary layers if possible. |
Thank you for this work, this library is awesome !
I am using the 'esp32-ble-multiple' template to connect to 2 BMS (ebike batteries), and when I add too many sensors I get into the boot loop problem.
I tried increasing the stack size as you suggested here, but it did not help:
I also tried to set
DARDUINO_LOOP_STACK_SIZE
as I found a reference to this name during my search but it did not help either.Can you spot something wrong with my declaration above ?
Thank you for your help !
My esphome version (docker): 2023.3.2
The text was updated successfully, but these errors were encountered: