<?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>client + provisioner in the same board ?? mesh SDK 2.2.0</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/40591/client-provisioner-in-the-same-board-mesh-sdk-2-2-0</link><description>hello 
 i want to implement provisioner and client roles in the same board , how can i start initializing the models 
 i have implemented the same initialization of the client in the same API of model init cb so that the provisioner while initializing</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 22 Nov 2018 09:58:06 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/40591/client-provisioner-in-the-same-board-mesh-sdk-2-2-0" /><item><title>RE: client + provisioner in the same board ?? mesh SDK 2.2.0</title><link>https://devzone.nordicsemi.com/thread/158577?ContentTypeID=1</link><pubDate>Thu, 22 Nov 2018 09:58:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c0d1e835-094c-43a9-822b-eb0e7939065b</guid><dc:creator>Mttrinh</dc:creator><description>&lt;p&gt;What he means by &amp;quot;&lt;span&gt;you need to do configuration for the client locally&amp;quot;, is that you have to configure the client in the firmware. Mesh error 4 means no memory, have you allocated enough memory? &lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;I suggest you to have a look at the Mesh SDK v1.0.1, it is an old SDK but the provisioner and client was on the same board back then. The Simple OnOff model was used as well.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: client + provisioner in the same board ?? mesh SDK 2.2.0</title><link>https://devzone.nordicsemi.com/thread/158497?ContentTypeID=1</link><pubDate>Wed, 21 Nov 2018 19:31:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1e99cdd9-bc5c-4b65-adf0-1274a61be161</guid><dc:creator>turki</dc:creator><description>&lt;p&gt;what do he mean by &amp;quot;&lt;span&gt;you need to do configuration for the client locally&amp;quot;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;i tried to just add&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt; m_clients.status_cb = client_status_cb;&lt;br /&gt; m_clients.set_cb = client_publish_timeout_cb;&lt;br /&gt; ERROR_CHECK(simple_message_client_init(&amp;amp;m_clients, 0));&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;But this lead me to a mesh error 4 at 0x0002EE5D&amp;nbsp; whish is in the line of&amp;nbsp;ERROR_CHECK(simple_message_client_init(&amp;amp;m_clients, 0));&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: client + provisioner in the same board ?? mesh SDK 2.2.0</title><link>https://devzone.nordicsemi.com/thread/158032?ContentTypeID=1</link><pubDate>Mon, 19 Nov 2018 15:34:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ba1c2382-c8aa-4772-8d89-ed109ed36304</guid><dc:creator>Mttrinh</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;There have been quiet a few questions regarding this on the forum. I suggest you to have a look at this &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/34615/provisioner-control-light-in-mesh-sdk-2-0-1" rel="noopener noreferrer" target="_blank"&gt;thread&lt;/a&gt;, it points to several useful threads. The Mesh SDK v1.x mentioned can be found &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/34387/mesh-sdk-1-0-0-download" rel="noopener noreferrer" target="_blank"&gt;here&lt;/a&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>