<?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>Add a service and characteristics to advertising data</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/7381/add-a-service-and-characteristics-to-advertising-data</link><description>Is it possible to include an existing service and characteristics on a peripheral to its advertising packets? 
 I would like to add a custom BLE service to my peripheral to be used as a status indicator. A central device would need to be able to read</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 02 Jun 2015 10:20:37 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/7381/add-a-service-and-characteristics-to-advertising-data" /><item><title>RE: Add a service and characteristics to advertising data</title><link>https://devzone.nordicsemi.com/thread/26229?ContentTypeID=1</link><pubDate>Tue, 02 Jun 2015 10:20:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0a3406c9-0962-458a-8e34-bfde2dd3028e</guid><dc:creator>MartinBL</dc:creator><description>&lt;p&gt;True. Would be the most elegant solution, i guess, if circumstances allows it.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Add a service and characteristics to advertising data</title><link>https://devzone.nordicsemi.com/thread/26228?ContentTypeID=1</link><pubDate>Tue, 02 Jun 2015 09:49:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:71f8b6ab-eb42-4aa5-bcce-b64bdcee2876</guid><dc:creator>Wojtek</dc:creator><description>&lt;p&gt;Or just do connectable/not-connectable advertising :) But this could be the solution when peripheral can decide if central has to connect. Setting Your values in manufacturer specific data is better solution - You just have to parse it properly on central to read values.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Add a service and characteristics to advertising data</title><link>https://devzone.nordicsemi.com/thread/26227?ContentTypeID=1</link><pubDate>Tue, 02 Jun 2015 09:48:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0804bac4-9dc4-4e2f-b509-d1dac80eeb4a</guid><dc:creator>MartinBL</dc:creator><description>&lt;p&gt;Hi. You can advertise what services your devices provides, but you can&amp;#39;t really advertise the service&amp;#39;s &lt;em&gt;value&lt;/em&gt; the way I think you suggest (in the service field of the advertising packet). What you can do is to add your information in the manufacturer specific data or scan response field. Then you can update your advertising data with relevant information whenever you like.&lt;/p&gt;
&lt;p&gt;If you just want to tell your central &amp;#39;yes&amp;#39; or &amp;#39;no&amp;#39; to connect (pretty much a boolean value) then maybe you can do this by manipulating the device appearance or tx power field and that way save your manufacturer specific data field for something else.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/tutorials/5/ble-advertising-a-beginners-tutorial/"&gt;Here is a tutorial&lt;/a&gt; on advertising btw.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>