Using HttpClient on core 1 causes core 0 to wait under certain circonstances

RomeHein / ESPecial

ESP32 automation with web interface and telegram bot

GNU General Public License v3.0

111 stars 17 forks source link

Using HttpClient on core 1 causes core 0 to wait under certain circonstances #14

Closed RomeHein closed 4 years ago

RomeHein commented 4 years ago

Step to reproduce:

set in the web interface : an I/O with a touchsensor
set an automation that is event triggered with at least one condition based on the touchsensor
disable Telegram Bot
restart the esp32
reload the web interface

Result: The function "readPins" is not call anymore as any other code running on the core 0

Idea: This issue happens when the web interface is reloaded. Which triggers the retrieving of the firmware list via a blocking http call (HttpClient).

RomeHein commented 4 years ago

interesting read: https://github.com/espressif/esp-iot-solution/blob/master/documents/touch_pad_solution/touch_sensor_design_en.md#41-the-impact-of-wi-fi-enabling-on-touch-sensor

Thanks to the Jitter Filter Solution, it's possible to avoid doing a for loop with hundreds of touchRead, which was blocking the core 0 of the esp32.