Expose the BLE MTU, that is negotiated, between central and peripheral.

[beachcitiessoftware]

Describe the solution you'd like
Please add a property to BlessServer, which exposes the negotiated BLE MTU value. I know it exists in BleakClient, but it doesn't appear you are using that, so perhaps you can see how they're able to expose that value in BleakClient.py?

[sagimann]

any workaround?

[beachcitiessoftware]

Any possibility of this being added? Also, are you planning to update it to support newer versions of Bleak?

[kevincar]

Thanks for this suggestion. I've just merged the changes into the latest on the repo to expose the MTU.

However, there are some caveats,

The method for obtaining the negotiated MTU is slightly different for each OS backend. Regardless of backend, the MTU isn't exposed to the peripheral until some read/write/subscribe action has been taken by the central device to negotiate the MTU. Thus, the MTU cannot be known until a central either subscribes to (Windows, MacOS), or reads from/writes to (Linux) a characteristic provided by the peripheral. During those transactions the MTU can be obtained and added on to the server. After these actions, the MTU can be accessed simply as a property on the server (e.g., server.mtu).