How to use service change characteristic

RE: How to use service change characteristic

run_ar — Tue, 26 Nov 2019 08:16:49 GMT

1. As a server, Service changed indications are managed by the peer manager. See: Architecture.

2. As a client we have the GATT Service Client

RE: How to use service change characteristic

Jordan Archer — Sat, 14 Sep 2019 23:13:17 GMT

Can you enumerate on this:

1) How do I resend the indication? (An simple code example would be nice).

2) How do I trigger a refresh of the entire attributes table? (Again a simple code example would be nice).

RE: How to use service change characteristic

run_ar — Fri, 11 Nov 2016 09:52:09 GMT

Just call this after reconnecting and rebonding to a known peer. The state of the CCCD should be remembered across connection for bonded peer's so you do not have to wait for the CCCD write when reconnecting, if you get an invalid state error you will have to resend the indication after it has been reenabled (in case the peer doesn't follow the spec and remember the cccd state). The handle of the service change charateristic will not change so you can connect with a "test master" to see what handle it is using.

It's ok, and simplest, to trigger a refresh of the entire attribute table. The drawback is a slightly higher power consumption during the discovery procedure.