https://devzone.nordicsemi.com/f/nordic-q-a/51067/nrf-thread-roleHi Nordic engineer: When I used examples\multi protocol\ble thread\ble_thread_dyn_mtd_coap_cli, I found that the device could not automatically assign LEADER, Router, and CHILD roles. &lt;info&gt; app: Thread version: OPENTHREAD/20180926-00632-g2279ef61;en-USTelligent Community 13Mon, 19 Aug 2019 07:08:03 GMThttps://devzone.nordicsemi.com/thread/204642?ContentTypeID=1Mon, 19 Aug 2019 07:08:03 GMT137ad170-7792-4731-bb38-c0d22fbe4515:2dd06543-92f1-4f34-8fcf-e17d53a24529NOA-BEN<p>Hi Hung Bui,</p> <p>&nbsp; &nbsp; &nbsp; Thank you very much, I set some parameters and some libraries, successfully set up as MTD devices.&nbsp;</p> <p>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/204552?ContentTypeID=1Fri, 16 Aug 2019 15:01:28 GMT137ad170-7792-4731-bb38-c0d22fbe4515:b12e7ea9-aea6-489a-89fc-a9edd7f1b9adHung Bui<p>Hi Noa,&nbsp;</p> <p></p> <p>As the name suggested, it can only act as MTD device (Minimum Thread Device). It can&#39;t take the role of Leader or router.&nbsp;</p> <p>It&#39;s defined <a href="https://openthread.io/guides/thread-primer/node-roles-and-types">here</a>:&nbsp;</p> <h3>Minimal Thread Device</h3> <p>A Minimal Thread Device does not subscribe to multicast traffic and forwards all messages to its Parent. There are two types of MTDs:</p> <ul> <li>Minimal End Device (MED) — transceiver always on, does not need to poll for messages from its parent</li> <li>Sleepy End Device (SED) — normally disabled, wakes on occasion to poll for messages from its parent</li> </ul> <p>An MTD can only operate as an End Device (Child).</p> <p>It would need to have a router to assign it as a child.&nbsp;</p><div style="clear:both;"></div>