Yeah, I've scratched my head because of the GPL, but I intend to make an attempt at porting it anyway, as an intermediate step. Then based on that, make a proper C only adaptation with my own approach. That library is nice and stuff, but has lots of "what the hell man?!" I mean, tons of magic number...

The USB shield for Arduino has code for Bluetooth dongles, and some implementation for layers, including HID keyboard and mouse.

Cutting out the part needed, throw out USB dongle behaviour, change HCI command sending/receiving with the ESP32 functions and callbacks and there you go.
Easy-peasy

I'm not much of a HW guy, but my guess would be the speed. Maybe there is a bounce, but for the Due it's so fast it's negligible.
The ESP32 may "sample" a bit faster, so it gets more sensitive to that.
I'm just basing this on the clock speed.
But the oscilloscope will show everything though.

If you are interested in a particular profile, then as a workaround until the IDF doesn't support it yet, you can write it manually, the "esp_vhci*" can be used for this. At least a bare minimum of profile stacks for testing purposes can be written, if you're just waiting for it to be available. And...

Thanks for the feedback!
I've added attribution to the page, hope it is good.

I can't find an image which has the same layout as in the "ESP32 Module Reference Design" documentation for the ESP-WROOM-32 module.
The pin labels were updated, and I'll think of something about the image.

I've been working on a very simple tool for myself to make project planning easier: https://hubberthus.github.io/ The general idea was to have a tool for different kinds of modules using ESP32, and play visually with the pinout until I'm satisfied with the result. Different boards route out differen...