https://devzone.nordicsemi.com/f/nordic-q-a/126245/custom-beacon-type-idJust a quick one as I couldn&#39;t find it on google. I&#39;m going to implement a beacon like broadcaster but one not based on location. It&#39;ll probably be a uuid, a random identifier and a byte. static uint8_t m_beacon_info[APP_BEACON_INFO_LENGTH] = { APP_DEVICE_TYPEen-USTelligent Community 13Mon, 22 Dec 2025 11:55:52 GMThttps://devzone.nordicsemi.com/thread/557515?ContentTypeID=1Mon, 22 Dec 2025 11:55:52 GMT137ad170-7792-4731-bb38-c0d22fbe4515:455d4a64-c78b-4223-b535-d2ead17192b8snoopy20<p>I think APP_DEVICE_TYPE which is 0x02 for &#39;beacon&#39; is the Apple format (I could be wrong) and so is indicating a format. While I could use it the data will be different and still available to real beacons. I&#39;d like to tell real beacons this is something else, &#39;ignore me&#39;.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/557511?ContentTypeID=1Mon, 22 Dec 2025 10:44:36 GMT137ad170-7792-4731-bb38-c0d22fbe4515:a9ee9748-2895-4a61-9416-faf9cdd094f2Kenneth<p>Hello,</p> <p>Not entirely sure I follow the question, there exists a few &quot;standardized&quot; beacon formats (e.g. iBeacon, Eddystone), so if you use any of them you need to follow those specific requirements. If you want to make your own proprietary beacon then you are free to do whatever works for you, but make sure you are not using a company identifier that belong to anyone else.</p> <p>Kenneth</p><div style="clear:both;"></div>