Best Practices for Developing Robust Custom Libraries for ESP32 Integrating Wi-Fi, Bluetooth, BLE
Hey guys @Middleware & OS Whilst developing a custom library for ESP32 aimed at integrating various wireless technologies (such as Wi-Fi, Bluetooth, and BLE) for an Industrial IoT project, I encountered issues related to hardware initialization and compatibility across different ESP-IDF framework versions. Specifically, the library functions intermittently fail to initialize the wireless modules correctly, leading to sporadic connection failures and inconsistent performance across devices. For example, the Wi-Fi module sometimes fails to connect to the network, or the Bluetooth module does not initialize properly, causing pairing issues with other devices. I am wondering if there are best practices or design patterns that should be adhered to when developing custom libraries for ESP32 to ensure robustness and compatibility? Could adopting a modular approach enhance the library's reliability, and if so, how should it be structured to support multiple wireless technologies seamlessly?
Solution
use esp-idf's built in drivers and api that offer an abstraction layer above the hardware specifics, resolves compatibility across different esp32 boards and idf versions
