From a59fbac4cd8f56a71840685b94f4b58fac7d41e6 Mon Sep 17 00:00:00 2001 From: illuzn <57167030+illuzn@users.noreply.github.com> Date: Thu, 15 Feb 2024 22:11:51 +1030 Subject: [PATCH] Linting --- docs/customization.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/customization.md b/docs/customization.md index 7c8c15f..a27fc73 100644 --- a/docs/customization.md +++ b/docs/customization.md @@ -509,13 +509,16 @@ esp32: ``` ### Bluetooth proxy + > [!IMPORTANT] > The [ESP32 Platform](#framework-esp-idf) component should be configured to use the `esp-idf` framework, > as the `arduino` framework uses significantly more memory and performs poorly with the Bluetooth proxy enabled. > [!NOTE] + > The Bluetooth proxy component uses a significant amount of device RAM (<10k RAM free). Enabling this with other customizations/ components enabled may result in crashes due to the device running out of memory. It is known that https connections are erratic due to insufficient memory and there can be issues flashing TFT locally due to the device running out of RAM. You can either: (1) flash the device (removing bluetooth proxy) while updating TFT or, (2) flash the device from a local (http) source with a low baud rate (<9600) that will not cause an out of memory crash - do note that this will take much longer to update (~ 10 minutes). - + + ```yaml # Enable Bluetooth proxy bluetooth_proxy: