I agree. Almost all of the other response structures sent to the callback (in the union `esp_bt_gap_cb_param_t`) include `esp_bd_addr_t bda` as their first member. Why not this one? All I can think of is to send the first request, and kick off the second request after you get the first response, etc.

I did get it to work. Make sure you check the "stat" field being 0 in the callback param before trusting the result.

I found this: https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/bluetooth/esp_gap_bt.html#_CPPv427esp_bt_gap_read_remote_name13esp_bd_addr_t But I can't get it to work. The data returned in the callback is gibberish, and varies over time. Is there an example of a successful i...

I'm running ESP32 as an A2DP sink. I am successfully streaming audio, and getting the track metadata (song, artist, etc), but I'd also like to discover the name of the device I'm connected to (like my phone, usually). Is there a way to get that?