I have tried this on other sensor and realized that the problem should be with this particular device on 0x17, but could not find what it should be.?
I will try with other ESP32 based board.

I have found some issue with finding i2c device on the bus. The i2c device is connected to the esp32 on address 0x17. But when I do the i2cdetect using the i2c_tools example in the esp-idf folder, I get into issues. The output has some UU UU values as shown below, which I do not get what it means FY...

My apologies for late reply. Now I got some time to test the i2c functionality on the ESP-IDF-V5 and I also realised that it is not working.
So I guess I will have to debug the issue.

Have you seen the examples folder of ESP-IDF? there are some examples for standard bluetooth and BLE.

I do not think it could be a component problem but ofcouse in your CMake file you must have nvs component. Then remember to initialise the flash with esp_flash_init() or nvs_flash_init(). This could be a problem in your code. For example wifi functions will not work without the intialization of nvs ...

In esp-idf examples folder there are sample codes in bluetooth subdirectory for various roles.

I do not know about which BLE framework, lets say esp's own(bluedroid) or NimBLE port for ESP32 you are using.? But Nimble also supports mesh network. For that you need to define a struct containing services and characteristics. Then you should have callbacks for those BLE GATT/GAP events. This is t...

No. I do not have S3 feather yet. What I do normally to test i2c is define some function to initialize the i2c. Then there are methods to do write/read transactions at particular port/pin. static esp_err_t i2c_master_init(void){ int i2c_port = CONFIG_I2C_MASTER_PORT; i2c_config_t conf = { .mode = I2...

It is a custom function which is based on STM32 API's so I need to port it to ESP32.!!

In those examples it tells to select the correct I2C SDA and SCL pins from menuconfig. Have you done that?