using notification priorities leads to wrong characteristic being configured

TorstenRobitzki / bluetoe

C++ Framework to build Bluetooth LE Server (GATT)

MIT License

142 stars 29 forks source link

using notification priorities leads to wrong characteristic being configured #20

Closed TorstenRobitzki closed 6 years ago

TorstenRobitzki commented 6 years ago

Similar to #17: when using notification priorities, the reordering of the client characteristic index leads to the wrong characteristic beeing configured when ATT read / writes are used to access the CCCD.

TorstenRobitzki commented 6 years ago

Fixed by passing the mapping from cccd index -> cccd position to the cccd attribute access function.