Open Thalley opened 1 year ago
Hi @Thalley,
This issue, marked as an Enhancement, was opened a while ago and did not get any traction. It was just assigned to you based on the labels. If you don't consider yourself the right person to address this issue, please re-assing it to the right person.
Please take a moment to review if the issue is still relevant to the project. If it is, please provide feedback and direction on how to move forward. If it is not, has already been addressed, is a duplicate, or is no longer relevant, please close it with a short comment explaining the reason.
Thanks!
This is still valid
Is your enhancement proposal related to a problem? Please describe. Most of the MCS characteristics only optionally support notifications. This should be reflected in the MCS and MCS client implementations, and configurable by either Kconfigs or on a per-instance (if dynamically registered) approach.
Describe the solution you'd like Each characteristic where notification are optional should be optional in the implementation of MCS. The MCS client should also only optionally subscribe to the notifications, and then only if the server supports it.
Describe alternatives you've considered N/A
Additional context N/A