https://devzone.nordicsemi.com/f/nordic-q-a/35170/deviceid-in-advertising-specific-dataChecking if this is possible and how to complete. For the ble_app_beacon example, I&#39;m able to reuse #define APP_DEVICE_TYPE 0x02, to be #define APP_DEVICE_TYPE 0x0E, 0x06, 0x40, 0x07, and view the new Specific data as hex for the beacon example in NRFconnecten-USTelligent Community 13Fri, 08 Jun 2018 23:05:25 GMThttps://devzone.nordicsemi.com/thread/135417?ContentTypeID=1Fri, 08 Jun 2018 23:05:25 GMT137ad170-7792-4731-bb38-c0d22fbe4515:3d99b7c1-86b8-421d-ad15-4f4455167a56Simon<p>Works the same for FICR_ADDRESS.</p> <p>-thank-you.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/135221?ContentTypeID=1Thu, 07 Jun 2018 14:57:07 GMT137ad170-7792-4731-bb38-c0d22fbe4515:f23299f6-7b6f-4d9f-a1b7-566fab9f5406tesc<p>Hi,</p> <p>Referring to the ble_app_beacon example you will see that those defines are used to initialize the <code>m_beacon_info</code> variable, which is a static array of type <code>uint8_t</code>. You should be able to fill any bytes in that array similarly to how it is done with <code>major_value</code> and <code>minor_value</code> in <code>advertising_init()</code>. There the values are initially fetched from <code>UICR_ADDRESS</code>, defined as <code>0x10001080</code> (which is <code>CUSTOMER[0]</code>), but fetching the data from <code>DEVICEID[0]</code> should work the same.</p> <p>Regards,<br />Terje</p><div style="clear:both;"></div>