<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Why can notifications get sent before they are enabled if devices have been previously Bonded?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/67544/why-can-notifications-get-sent-before-they-are-enabled-if-devices-have-been-previously-bonded</link><description>I&amp;#39;m developing a Peripheral with a rather intricate connection process and doing a lot of testing. 
 I find that if a Central connects, and then the Peripheral tries to send a notification via sd_ble_gatts_hvx() before the Central has enabled notifications</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 26 Oct 2020 11:36:19 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/67544/why-can-notifications-get-sent-before-they-are-enabled-if-devices-have-been-previously-bonded" /><item><title>RE: Why can notifications get sent before they are enabled if devices have been previously Bonded?</title><link>https://devzone.nordicsemi.com/thread/276841?ContentTypeID=1</link><pubDate>Mon, 26 Oct 2020 11:36:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:08c0b851-7608-41de-a55b-8e1bab05a48f</guid><dc:creator>mrono</dc:creator><description>&lt;p&gt;The server needs to remember if a bonded client has enabled notifications earlier. So if the central left the notification enabled when it last disconnected, then it will be enabled automatically upon re-connecting.&lt;/p&gt;
&lt;p&gt;Here is the relevant snippet from the BLE core specification:&lt;/p&gt;
&lt;p&gt;&lt;em&gt;The Client Characteristic Configuration descriptor value shall be&lt;/em&gt;&lt;br /&gt;&lt;em&gt;persistent across connections for bonded devices. The Client Characteristic&lt;/em&gt;&lt;br /&gt;&lt;em&gt;Configuration descriptor value shall be set to the default value at each&lt;/em&gt;&lt;br /&gt;&lt;em&gt;connection with non-bonded devices.&lt;/em&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>