<?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 SDK 2.2.0 Group Address</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/39810/mesh-sdk-2-2-0-group-address</link><description>Hi Developers, 
 I am exploring the light switch examples, client, server and provisioner, every time a node is provisioned it uses a unicast address, what if I want to use different groups for different nodes functionalities 
 what changes should I do</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 09 Nov 2018 08:22:58 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/39810/mesh-sdk-2-2-0-group-address" /><item><title>RE: Mesh SDK 2.2.0 Group Address</title><link>https://devzone.nordicsemi.com/thread/156599?ContentTypeID=1</link><pubDate>Fri, 09 Nov 2018 08:22:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8c1268c9-116b-4732-84d1-9102d5b03c28</guid><dc:creator>Mttrinh</dc:creator><description>&lt;p&gt;Yes, it will be easier if you use group addresses. You should let both your clients publish to a group address and then have your end nodes(sensors) subscribe to the same address. The same should be done with your end nodes, publish to another group address and have your clients subscribe to this address. You can see &lt;a href="https://blog.bluetooth.com/the-fundamental-concepts-of-bluetooth-mesh-networking-part-2" rel="noopener noreferrer" target="_blank"&gt;here&lt;/a&gt; which group addresses that can be used.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Mesh SDK 2.2.0 Group Address</title><link>https://devzone.nordicsemi.com/thread/156039?ContentTypeID=1</link><pubDate>Mon, 05 Nov 2018 22:38:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:34ac0882-328a-4049-b069-270c690caaf2</guid><dc:creator>MeliodasD</dc:creator><description>&lt;p&gt;Hi &lt;a href="https://devzone.nordicsemi.com/members/mttrinh"&gt;Mttrinh&lt;/a&gt; that is exactly&amp;nbsp;what I want to do, all my end nodes (sensors) receiving messages from my clients and all my clients receiving messages from my end nodes, I think the easier way to do it is using groups addresses instead of unicast address, at this time it does not matter if I get duplicates on the clients nodes I am going to filter it using a high-level app&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Mesh SDK 2.2.0 Group Address</title><link>https://devzone.nordicsemi.com/thread/155999?ContentTypeID=1</link><pubDate>Mon, 05 Nov 2018 14:57:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:95ff3726-903e-4475-a2e6-fc3575a5341d</guid><dc:creator>Mttrinh</dc:creator><description>&lt;p&gt;I think you might have misunderstood how group addresses work. A group address can be published&amp;nbsp;or subscribed to, it is not assigned to a node like with unicast addresses. So, in my understanding, you want all your end nodes to receive messages from your clients and both your clients to receive from all of your end nodes?&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Mesh SDK 2.2.0 Group Address</title><link>https://devzone.nordicsemi.com/thread/154715?ContentTypeID=1</link><pubDate>Fri, 26 Oct 2018 15:58:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0c400f06-216d-4e9d-8b31-f7f496f5dcba</guid><dc:creator>MeliodasD</dc:creator><description>&lt;p&gt;Hi &lt;a href="https://devzone.nordicsemi.com/members/mttrinh"&gt;Mttrinh&lt;/a&gt;, I am&amp;nbsp;planning to have a couple of nodes being clients and 3 or 4 relaying messages (all them being e.g group address A), then all end nodes being e,g group address B, C, D...&lt;/p&gt;
&lt;p&gt;Then subscribe&amp;nbsp;all the nodes in the network to receive messages from the Group address A, and be able to receive the sensor data from all my groups in both clients (group address A)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Mesh SDK 2.2.0 Group Address</title><link>https://devzone.nordicsemi.com/thread/154696?ContentTypeID=1</link><pubDate>Fri, 26 Oct 2018 14:06:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:05b664ec-2d8e-4d5e-bf49-e13de876a549</guid><dc:creator>Mttrinh</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I might be wrong here, but what you want to do is to publish/subscribe to a group address right?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Not sure what you mean by &amp;quot;&amp;nbsp;manage multiple group address&amp;quot;? Do want to publish/subscribe to multiple group addresses?&lt;/p&gt;
&lt;p&gt;Inside node_setup.c, if you have a look at&amp;nbsp;NODE_SETUP_CONFIG_PUBLICATION_ONOFF_CLIENT1 and&amp;nbsp;NODE_SETUP_CONFIG_PUBLICATION_ONOFF_CLIENT2, you can see how the example configure the client to publish to two different group addresses. Inside&amp;nbsp;NODE_SETUP_CONFIG_SUBSCRIPTION_ONOFF_SERVER you will find how the example configure the servers to subscribe to the group addresses.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>