<?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>Custom bluetooth profile structure help</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/12008/custom-bluetooth-profile-structure-help</link><description>I&amp;#39;ve been thinking recently about how to structure the custom profile for some hardware I&amp;#39;m developing, which has a a few sensor components and a button onboard. 
 What I&amp;#39;d like to have in terms of functionality is this: 
 
 Read data from 4 different</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 22 Feb 2016 15:04:32 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/12008/custom-bluetooth-profile-structure-help" /><item><title>RE: Custom bluetooth profile structure help</title><link>https://devzone.nordicsemi.com/thread/45459?ContentTypeID=1</link><pubDate>Mon, 22 Feb 2016 15:04:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5e9c20ed-79cf-4cac-9a3f-cc84022b0c79</guid><dc:creator>MartinBL</dc:creator><description>&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/question/68882/custom-bluetooth-profile-structure-advice/"&gt;Duplicate&lt;/a&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>