esp32-camera VS bluetooth-proxies

Espressif's esp-cam library explicitly supports the OV5640 but doesn't mention the OV5647. I believe the OV5647 uses the same connector but from what I've read elsewhere it program slightly different from the OV5640, so it's not likely that an OV5640 driver will work with it.

esp32-camera -> This is the component I am using to provide the driver for the camera of T-Camera S3.

I am working on the with esp32-camera to support the camera I am using. I was wondering if I had to use a camera not supported by this library. How can I go about it? Does this mean that the only camera sensors available for esp32 are the ones in the library?

The software is at github.

https://github.com/espressif/esp32-camera/issues/330 I guess the camera is faulty

If you look at the esp32 camera driver github it lists the supported camera's.

If you're already using Home Assistant, you can install ESPHome on any ESP32-based device and use it as a Bluetooth Proxy hub. I already had some smartplugs and bulbs flashed with ESPHome, so it was as simple as adding a couple more lines of code to get a few BLE Proxy hubs, with no additional hardware required for the hub.

Home Assistant and Bluetooth Proxy is probably your best bet: https://esphome.github.io/bluetooth-proxies/

where can I find the yaml configuration file? I flashed the esp32 directly with the bluetooth proxy wizard, hence I never touched the yaml file myself. Is it stored somewhere in HA?

Yep, these are the way to go. Small and with a case, so ready to put around the house.

Using just your browser you can transform these into Bluetooth proxies for Home Assistant with https://esphome.github.io/bluetooth-proxies/

I think the sequence when using the web installer from here is that it first installed a basic EXPHome WiFi connector and once done, supposed to autmomagically install the BT Proxy software but it fails. It gives you the chance to rename it to something more appropriate but then you get some other 'web' ESP device pop up?

ESPHome uses a yaml file as input from which to generate the binary firmware file for your ESP. Flashing via their github as you did means it will use one of these predefined yaml files. Because you chose generic esp, it will be using this one. As you can see it already has the api: line in there (line 21).

with framework set to esp-idf (as per https://github.com/esphome/bluetooth-proxies/blob/main/gl-s10.yaml), the device logs stop at "Starting scheduler on APP CPU"