Larger configuration objects could overrun the rather limited JSON configuration object buffer sizes in the HTTP server code. This was an issue for CurveInterpolator in particular. Those buffer sizes have now been increased.
The fix is taken almost as-is from the code provided by Bjarne Hansen in Issue #415. Only defining DYNAMIC_JSON_DOCUMENT_SIZE didn't work because the related headers were included earlier on during compilation. But luckily, AsyncCallbackJsonWebHandler constructor accepts the maximum buffer size as a constructor argument.
Larger configuration objects could overrun the rather limited JSON configuration object buffer sizes in the HTTP server code. This was an issue for
CurveInterpolatorin particular. Those buffer sizes have now been increased.The fix is taken almost as-is from the code provided by Bjarne Hansen in Issue #415. Only defining
DYNAMIC_JSON_DOCUMENT_SIZEdidn't work because the related headers were included earlier on during compilation. But luckily,AsyncCallbackJsonWebHandlerconstructor accepts the maximum buffer size as a constructor argument.I've tested this with https://github.com/hatlabs/SH-ESP32-engine-hat-firmware with CurveInterpolators up to over 20 samples.
Fixes #415.