<?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>Mesh without servers and combine provisioner with client in one device.</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/34643/mesh-without-servers-and-combine-provisioner-with-client-in-one-device</link><description>Hello, I use light switch example (nrf52832, mesh sdk 2.0.1) 
 
 Can I create mesh network without servers? (clients will send messages to each other and process them) 
 And can I also make the one of clients act as provisioner? Like combine client and</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 23 May 2018 23:18:48 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/34643/mesh-without-servers-and-combine-provisioner-with-client-in-one-device" /><item><title>RE: Mesh without servers and combine provisioner with client in one device.</title><link>https://devzone.nordicsemi.com/thread/133116?ContentTypeID=1</link><pubDate>Wed, 23 May 2018 23:18:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:35aa33ae-e9a5-497a-8447-3f326a836b4d</guid><dc:creator>leonwj</dc:creator><description>&lt;p&gt;hello,&lt;/p&gt;
&lt;p&gt;the first link seems to be functional now..&lt;/p&gt;
&lt;p&gt;On the provisioner side of things, yes it&amp;#39;s certainly possible to include the provisioning functionality in the same device as your other functionality. In fact, if you look at the &lt;a href="http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.meshsdk.v1.0.1%2Fmd_examples_light_switch_README.html&amp;amp;cp=4_1_1_5_0" rel="noopener noreferrer" target="_blank"&gt;light-switch example&lt;/a&gt; from v1.0x versions of the Mesh SDK you will find that the provisioner and the client node were the same. (I believe that they were separated in v2.0x to show that they didn&amp;#39;t have to be on the same device :-)&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Mesh without servers and combine provisioner with client in one device.</title><link>https://devzone.nordicsemi.com/thread/132941?ContentTypeID=1</link><pubDate>Wed, 23 May 2018 09:21:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9ceea734-0e1d-448c-9140-da0b72aef6c3</guid><dc:creator>Anar</dc:creator><description>&lt;p&gt;The first link is no longer exists.&lt;br /&gt;&lt;br /&gt;So I can make all devices the same and send messages to each other in one mesh network, okay.&lt;br /&gt;&lt;br /&gt;So what about provisioner? Can I make the one of devices in mesh network act as provisioner, but with the same functions as other devices, so all devices in mesh network will be the same, but one device will have also functions for provisioning?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Mesh without servers and combine provisioner with client in one device.</title><link>https://devzone.nordicsemi.com/thread/132841?ContentTypeID=1</link><pubDate>Tue, 22 May 2018 22:15:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8bf3d7b7-d055-4760-af1b-13bab411451f</guid><dc:creator>arunbm123</dc:creator><description>&lt;p&gt;dear &lt;a href="https://devzone.nordicsemi.com/members/anar"&gt;anar&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;As per ur Reply its understandable that client requests Status from Server, and server returns status ..&lt;/p&gt;
&lt;p&gt;But if I want to send sensor Data using Mesh.and sensor data is not status&lt;/p&gt;
&lt;p&gt;kindly explain&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Mesh without servers and combine provisioner with client in one device.</title><link>https://devzone.nordicsemi.com/thread/132839?ContentTypeID=1</link><pubDate>Tue, 22 May 2018 22:07:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:758ce8b3-0477-4fed-a487-5feb3005d13b</guid><dc:creator>leonwj</dc:creator><description>&lt;p&gt;hello Anar,&lt;/p&gt;
&lt;p&gt;Given the premise of your question, I would suggest that you read the following &lt;a href="http://blog.bluetooth.com/the-fundamental-concepts-of-bluetooth-mesh-networking-part-1" rel="noopener noreferrer" target="_blank"&gt;link&lt;/a&gt;. And then possibly follow-up by reading &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/31179/how-to-make-multiple-sensor-node-that-takes-data-from-sensor-and-send-to-single-relay-node-in-ble-mesh-networking/123137#123137" rel="noopener noreferrer" target="_blank"&gt;this&lt;/a&gt;..&lt;/p&gt;
&lt;p&gt;In short, mesh devices aren&amp;#39;t clients or servers in the traditional sense (i.e. follow a client-server architecture)...&amp;nbsp;that is, a&amp;nbsp;Bluetooth SIG compliant mesh device/node can expose client models, server models or both within the same device. So a client model would send a request to a server model (which in turn, will either return a status or perform some action).&lt;/p&gt;
&lt;p&gt;Hopefully, the links above will provide the required information backdrop but post back if you require any further insight.&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>