Rahul

Hi @ahammouri , Please use: Component config → Log output → Default log verbosity --> Set to Debug Component config → Bluetooth → NimBLE Options → NimBLE Host log verbosity...

Hi @BestBot7 , The service change characteristic should be exposed from server side. Only then client will subscribe to it and when notification is sent on that characteristic the client...

Hi @BestBot7 , 1. For debug logs : For nrf side, you can opt for verbose mode logging that gives some information of information received For esp device side, you...

Hi @BestBot7 , On server side, can you share your code changes where you have sent notification ? Please also share esp device side debug logs. You can enable debug...

Hi @BestBot7 , I saw the image on nrf , that you have uploaded. We do see "Cache refreshed" . This indicates nrfconnect app has done refetch of services. So...

> How did your client refresh the services? Did you manually clicked on the refresh services option as I did or the server indicated the service change and it did...

Hi @BestBot7 , comment [here](https://github.com/espressif/esp-nimble/issues/72#issuecomment-2261968952) has the changes i did and i used examples/provisioning/wifi_prov for testing purpose. Reattaching the patch here for reference. [service_change.txt](https://github.com/user-attachments/files/16465898/service_change.txt)

Per spec, it is sent to all connected devices. The recipient has to have the intelligence whether to process it or drop it.

> Is there a way to make some changes in the server side to allow automatic subscription to the characteristics by client? No, because there is no such functionality mentioned...

Hi @BestBot7 , may i request you to please share debug enabled logs for esp device side. The error 35 seems to be specific to nrfConnect and hence not able...