RE: BLE Notify Characteristic identification in change notification callback

mkurtzsd — Fri, 15 Nov 2024 20:52:00 GMT

Einar,

Thanks for the response. Seems that having the characteristic UUID available in the call back would be very helpful to keep the code base smaller and more succinct. But, in the meantime, I've taken your advice and created a bunch of 1 line functions that delegate to a central notification config handler function and it's working just fine.

-Mike

RE: BLE Notify Characteristic identification in change notification callback

Einar Thorsrud — Fri, 15 Nov 2024 14:13:19 GMT

Hi,

I am not able to find any examples of this being done before, nor am I able to find a parameter you can filter on. While not exactly what you asked for, an option could perhaps be to use separate callback functions for each, that in turn call a common function but also pass an enum or something else you can use to determine from wher it came. That way you can still keep most of the implementation in one common function.