<?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>Provisioner from light switch example to provision and configure himself as a client</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/54595/provisioner-from-light-switch-example-to-provision-and-configure-himself-as-a-client</link><description>Hello, 
 
 I am currently working on the nRF SDK for Mesh v3.1 and I am using a static provisioner as in the light switch example. I have merged the client and server functionality into one node, and my server-client nodes are perfectly able to be provisioned</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 06 Mar 2020 08:55:51 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/54595/provisioner-from-light-switch-example-to-provision-and-configure-himself-as-a-client" /><item><title>RE: Provisioner from light switch example to provision and configure himself as a client</title><link>https://devzone.nordicsemi.com/thread/238447?ContentTypeID=1</link><pubDate>Fri, 06 Mar 2020 08:55:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:da5d3ad5-6ec5-4bc9-aa53-c9bea56b7c49</guid><dc:creator>ikkie</dc:creator><description>&lt;p&gt;Hello Joakim Jakobsen.&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Can u tell me how to do about &amp;quot;Note that, for self-configuration to work properly, the config client must not be instantiated on Element 0 of the device.&amp;quot;?,&amp;nbsp;I have merged the client and&amp;nbsp;provisioner functionality into one node,&amp;nbsp;However, it seems that it can only subscribe to the configured nodes, and the publish setting was not successful&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Provisioner from light switch example to provision and configure himself as a client</title><link>https://devzone.nordicsemi.com/thread/228712?ContentTypeID=1</link><pubDate>Mon, 13 Jan 2020 07:03:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:76b1d5d7-72a4-4b74-8b42-f6456c8096a2</guid><dc:creator>Joakim Jakobsen</dc:creator><description>&lt;p&gt;Hi again.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Sorry about the delay.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Some feedback from our Mesh developers:&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;For self-provisioning of a node, you need to consider the following points:&lt;/span&gt;&lt;br /&gt;&lt;span&gt;1. Node basically needs a unicast address, device key, and a network key to be configured. This will make it behave as a provisioned node. Additionally, you can also provide custom IV index if you don&amp;#39;t want to start at the default IV index of `0`.&lt;/span&gt;&lt;br /&gt;&lt;span&gt;2. Do you want to use config client on this node to be able to configure itself using local loopback (such as configuring publication settings for self)? If yes, you will have to bind the config server to the device key handle as shown in `mesh_stack_provisioning_data_store()` function. Note that, for self-configuration to work properly, the config client must not be instantiated on Element 0 of the device. You can instantiate it on any other element on the node and this will work. If you don&amp;#39;t want to do implement self-configuration using config client, you can directly use mesh stack&amp;#39;s internal API to configure the node (e.g. model publication/subscriptions/default TTL/ etc.), refer to `config_server.c` to see how this can be implemented.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Provisioner from light switch example to provision and configure himself as a client</title><link>https://devzone.nordicsemi.com/thread/224614?ContentTypeID=1</link><pubDate>Tue, 10 Dec 2019 08:30:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1e34635c-4735-4f43-911c-629f58065395</guid><dc:creator>Joakim Jakobsen</dc:creator><description>&lt;p&gt;Hi.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;While waiting for the feedback from our developers, you might want to take a look at this previous ticket regarding the same:&amp;nbsp;&lt;br /&gt;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/44515/mesh-node-self-provisioning"&gt;https://devzone.nordicsemi.com/f/nordic-q-a/44515/mesh-node-self-provisioning&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards,&amp;nbsp;&lt;br /&gt;Joakim&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Provisioner from light switch example to provision and configure himself as a client</title><link>https://devzone.nordicsemi.com/thread/223953?ContentTypeID=1</link><pubDate>Thu, 05 Dec 2019 14:20:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:267b027e-58f0-4203-b394-8e3b3d2fe29a</guid><dc:creator>Joakim Jakobsen</dc:creator><description>&lt;p&gt;Hi.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Sorry about the delay. &lt;br /&gt;I haven&amp;#39;t gotten any feedback about this yet. I know our developers have been busy working on the latest release of the nRF5 SDK for Mesh (v.4.0.0) that was released today.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;a title="nRF5 SDK for Mesh v4.0.0" href="https://infocenter.nordicsemi.com/topic/struct_sdk/struct/sdk_mesh_latest.html?cp=6_2"&gt;nRF5 SDK for Mesh v4.0.0&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I&amp;#39;ll ask them if they can take a look at your inquiry as soon as possible.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Br,&amp;nbsp;&lt;br /&gt;Joakim&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Provisioner from light switch example to provision and configure himself as a client</title><link>https://devzone.nordicsemi.com/thread/221768?ContentTypeID=1</link><pubDate>Mon, 25 Nov 2019 09:10:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8ef1b4ea-f265-4010-9f67-daf36f671b2f</guid><dc:creator>Amadeus</dc:creator><description>&lt;p&gt;Thank you, Joakim. Have you gotten any comments yet?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Provisioner from light switch example to provision and configure himself as a client</title><link>https://devzone.nordicsemi.com/thread/221371?ContentTypeID=1</link><pubDate>Thu, 21 Nov 2019 15:05:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:baae3867-d692-4075-893f-861040721c23</guid><dc:creator>Joakim Jakobsen</dc:creator><description>&lt;p&gt;Hi.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I haven&amp;#39;t tried this myself in the latest versions of the nRF5 SDK for Mesh.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I do believe you could modify the prov_helper_provision_self() in order to achieve this, but I&amp;#39;ll ask our developers for a comment so that you get the best practice for this.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I&amp;#39;ll get back to you&amp;nbsp;when I get a comment from them.&lt;/p&gt;
&lt;p&gt;Best regards,&amp;nbsp;&lt;br /&gt;Joakim Jakobsen&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>