franz-ms-muc

[https://github.com/Meisterschulen-am-Ostbahnhof-Munchen/Design-Patterns-GoF-on-ESP32/blob/feature/1/Structural_Patterns/Flyweight/components/Flyweight_component/GlyphFactory.cpp](https://github.com/Meisterschulen-am-Ostbahnhof-Munchen/Design-Patterns-GoF-on-ESP32/blob/feature/1/Structural_Patterns/Flyweight/components/Flyweight_component/GlyphFactory.cpp) here i will correct it so it runs in ESP32. please Double check it before take over to your Repo, because i do not check if it is running...

same Story for the delete\[\]. there is no new\[\]. so delete\[\] is wrong.  https://stackoverflow.com/questions/2425728/delete-vs-delete-operators-in-c

as an Example we can look to [https://github.com/esphome/esp-web-tools](https://github.com/esphome/esp-web-tools) [https://esphome.github.io/esp-web-tools/](https://esphome.github.io/esp-web-tools/) works quite well, but their Provisioning Standard ist somehow weird and non ESP-IDF like.

> Since there is a console serial terminal, why not run a WiFi configuration wizard on the console? I know it's not as pretty, but it's simpler and works across...

> Hello, may I ask which version of the idf you are using? I recommend trying with idf version 5.0. [**ESP-IDF Release v5.1**](https://github.com/espressif/esp-idf/releases/tag/v5.1) **let me go for a test with**...

i will test with 4.4.5 as well. .. not crash even with SPIRAM on. https://github.com/franz-ms-muc/esp-iot-bridge/tree/feature/wifi_router2 https://gist.github.com/franz-ms-muc/d26679ce9be867906195575d6d4526bc

there is still a Bug inside when using 4.4.5 see: https://github.com/franz-ms-muc/esp-iot-bridge/blob/ce247a249bc450469f42eb60fbd34b2d399e3800/main/app_main.c#L142 https://gist.github.com/franz-ms-muc/d999eb38eda77a0ab76bb2ca3220c935 after running the Sample all SPIRAM is gone, even if we have a lot before: before: `MALLOC_CAP_: 8bit...

> In general, whenever a child node connects to the hotspot of a parent node, the parent node will consume nearly 2k of memory. This is a necessary consumption on...

It is not successful scanning BLE

@leeebo i updated this to be in sync again with Master.