<?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>&amp;quot;Intermediate Temperature&amp;quot; characteristic is not coded</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/11745/intermediate-temperature-characteristic-is-not-coded</link><description>The &amp;quot;Intermediate Temperature&amp;quot; characteristic is not coded in the ble_hts.c file. 
 How could I do to implement this characteristic and maintain the compliance with Nordic Semiconductor ASA’s Bluetooth profile qualification listings ?</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 26 Jul 2017 12:11:57 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/11745/intermediate-temperature-characteristic-is-not-coded" /><item><title>RE: "Intermediate Temperature" characteristic is not coded</title><link>https://devzone.nordicsemi.com/thread/44427?ContentTypeID=1</link><pubDate>Wed, 26 Jul 2017 12:11:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bb50a698-be74-4f28-a0f0-8b2deb9866f4</guid><dc:creator>Nivetha</dc:creator><description>&lt;p&gt;Hi! Have you implemented the intermediate temperature characteristic in the ble_hts?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: "Intermediate Temperature" characteristic is not coded</title><link>https://devzone.nordicsemi.com/thread/44428?ContentTypeID=1</link><pubDate>Tue, 09 Feb 2016 14:28:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:454fb75a-500d-40c4-ae7e-d39baf03683b</guid><dc:creator>run_ar</dc:creator><description>&lt;p&gt;Adding support for a new characteristic will trigger a new qualification cycle. If the qualification was fairly recent or there were no changes to the test spec you could probably re-use the previous test logs for it, but at least anything related to the new characteristic would require a new test log.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>