You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an existing ESP32-S3 app that has been running with HTTP, fetch web pages via Wi-Fi. Recently, I added the BLE-Gamepad functionality into my app. With BLE Gamepad working, the https.GET() function is now failing. The WiFi Client access library calls to certificate the https site passed okay, but then https.GET() to fetch the webpage contents would return HTTPC_ERROR_CONNECTION_FAILED status.
Is there any known issue of using BLE-Gamepad with ESP32 http client ops?
Thank you.
The text was updated successfully, but these errors were encountered:
I have yet tried to use WiFi/http stack at the same time, could be an idea for OTA updates.
But from playing with ESPHome, I have seen alot of suggestions to be very careful about using Bluetooth and WiFi together on the ESP32 devices. Reason been that the limited memory of the ESP32 and the Bluetooth stack is pretty big, adding the WiFi and http stack might run into out of memory situations. The other reason I have seen too, is that the Bluetooth and WiFi use the same radio, which can also run into problem, if not managed correctly.
Maybe try plain http requests at first and see if the bigger requirements of https request might not work. Just an idea and guessing.
Hope this helps and you can move forward with your project.
I have an existing ESP32-S3 app that has been running with HTTP, fetch web pages via Wi-Fi. Recently, I added the BLE-Gamepad functionality into my app. With BLE Gamepad working, the https.GET() function is now failing. The WiFi Client access library calls to certificate the https site passed okay, but then https.GET() to fetch the webpage contents would return HTTPC_ERROR_CONNECTION_FAILED status.
Is there any known issue of using BLE-Gamepad with ESP32 http client ops?
Thank you.
The text was updated successfully, but these errors were encountered: