<?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>Manufacturer data in BLE5 advertisements</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/70329/manufacturer-data-in-ble5-advertisements</link><description>Hello I am working on an application which is based on the ble_thread_dyn_mtd_coap_cli_pca10056_s140 example. I then used the ble_app_rscs example so that I could add Bluetooth 5 to my application. 
 In my advertisements, I use the manufacturer data to</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 11 Jan 2021 21:50:12 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/70329/manufacturer-data-in-ble5-advertisements" /><item><title>RE: Manufacturer data in BLE5 advertisements</title><link>https://devzone.nordicsemi.com/thread/288492?ContentTypeID=1</link><pubDate>Mon, 11 Jan 2021 21:50:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b153081f-263d-4277-9634-967cf0d4f922</guid><dc:creator>Joakim Jakobsen</dc:creator><description>&lt;p&gt;Hi.&lt;/p&gt;
&lt;p&gt;Bluetooth 5 is just a superset of Bluetooth 4. That is, when you are advertising with bluetooth 5, it looks exactly like a bluetooth 4 advertisement, so there is no way for nRF Connect to know whether it is bluetooth 4 or 5.&lt;/p&gt;
&lt;p&gt;As long as you can see your extended advertising (or any other BLE5 features) and not facing any issues, you can ignore this.&lt;/p&gt;
&lt;p&gt;Br, &lt;br /&gt;Joakim&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>