<?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>BLE GATT Services</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/4805/ble-gatt-services</link><description>Hi, 
 I have a question related to GATT Services in BLE, so not strictly a nrf51 question although it&amp;#39;s related to one of the examples. The example for the (Human) Thermometer from Github just broadcasts the data in the advertisement, since it&amp;#39;s non</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 17 Dec 2014 11:48:15 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/4805/ble-gatt-services" /><item><title>RE: BLE GATT Services</title><link>https://devzone.nordicsemi.com/thread/17000?ContentTypeID=1</link><pubDate>Wed, 17 Dec 2014 11:48:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:24835ce0-e9ef-41a1-ab3e-fa751b1cd360</guid><dc:creator>nomve</dc:creator><description>&lt;p&gt;Thank you very much for the response. After reading through the BLE documentation and giving it some thought I came to the same conclusion. A custom UUID is probably the most logical solution. However, we might use manufacturer data because a custom UUID is so large. And I don&amp;#39;t want to ask too many additional questions related to scan responses.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE GATT Services</title><link>https://devzone.nordicsemi.com/thread/16999?ContentTypeID=1</link><pubDate>Wed, 17 Dec 2014 11:40:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d07e2b7a-62c1-46e4-8310-f15dc31e7291</guid><dc:creator>Petter Myhre</dc:creator><description>&lt;p&gt;I understand that this is confusing.&lt;/p&gt;
&lt;p&gt;The example is just an example, it is not following the Health Thermometer Profile specification. But this is the one that is working with the nRF Temp apps. It shouldn&amp;#39;t use the UUID of the Health Thermometer Service, it should have used a proprietary UUID.&lt;/p&gt;
&lt;p&gt;In the SDK we have an example called ble_app_hts, this is actually following the Health Thermometer Profile specification. It doesn&amp;#39;t include the termperature in the advertising packet, and it is connectable. The Health Thermometer Profile is mainly for use in healthcare applications.&lt;/p&gt;
&lt;p&gt;I recommend you to use a proprietary UUID and define the behavior yourself.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>