h2zero

You cannot set a custom public mac address, only a random static, resolvable, or non-resolvable. See this for details: https://novelbits.io/bluetooth-address-privacy-ble/

Yes the `esp_base_mac_addr_set` function is the only way to set the public address as far as I know. This is the address the the NimBLE stack retrieves from the controller...

It looks to me like the pairing has failed. What is the peer device you're connecting to, do you have access to it's code?

Can you provide a log from the server when this happens?

Thanks for the update, I was not able to reproduce this, but I know there have been a few bad chips in the past that users had trouble with.

I think this is possible but I have not attempted it. The NimBLE stack code is present to work with l2cap so you would need to use the lower level...

@ClaesClaes Sorry for the late response, I think this would benefit you without using L2CAP #283. I've seen others get above 35kB/s by using this.

Looks like the watch disconnects after a certain time to preserve battery power. That's just my guess, I do not have one to test with.

I don't know why this connection is failing as the logs do not contain the reason code (only LL_TERMINATE_IND, possibly the value 28 on that line is the indicator, may...

Sorry, I was assuming you had removed the MTU exchange as you had stated that previously, so I was looking for the connection failure reason. The feature request and link...