<?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>Broadcast in Mesh 2.0.1</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/35271/broadcast-in-mesh-2-0-1</link><description>Hi, 
 I&amp;#39;m working with the light_switch example on Mesh 2.0.1 and I would like to modify the simple_on_off_client_set_unreliable function to broadcast to all servers in the network, no matter they are odd or even. 
 I had a look at this post , but it</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 18 Jun 2018 11:16:23 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/35271/broadcast-in-mesh-2-0-1" /><item><title>RE: Broadcast in Mesh 2.0.1</title><link>https://devzone.nordicsemi.com/thread/136530?ContentTypeID=1</link><pubDate>Mon, 18 Jun 2018 11:16:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5b7c606a-a402-4548-9c07-760a809aba10</guid><dc:creator>FormerMember</dc:creator><description>&lt;p&gt;Yes, ODD and EVEN are just examples of groups. If the address of your group is 0xCAFE,&amp;nbsp; the following will have to be added/modified in example_network_configh.h node_setup.c in the light switch provisioner example.&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;example_network_config.h

#define GROUP_ADDRESS_CUSTOM  (0xCAFE)
 
******************************************


node_setup.c


typedef enum
{
    ...
    // Add the node for belonging to the group CUSTOM (given address GROUP_ADDRESS_CUSTOM)
    NODE_SETUP_CONFIG_PUBLICATION_CUSTOM_CLIENT,
    NODE_SETUP_CONFIG_SUBSCRIPTION_CUSTOM_SERVER,
    ...
} config_steps_t;

/* Sequence of steps for the client nodes */
static const config_steps_t client_config_steps[] =
{
   ...
   // Add configuration of node CUSTOM to the client configuration sequence.
    NODE_SETUP_CONFIG_PUBLICATION_CUSTOM_CLIENT,
    ...
};

/* Sequence of steps for the server nodes */
static const config_steps_t server_config_steps[] =
{
    ...
    // Add configuration of node CUSTOM to the server configuration sequence.
    NODE_SETUP_CONFIG_SUBSCRIPTION_CUSTOM_SERVER,
    ...
};

/** Step execution function for the configuration state machine. */
static void config_step_execute(void)
{

...

// Configuration for the server
 case NODE_SETUP_CONFIG_SUBSCRIPTION_CUSTOM_SERVER:
 {
     ...
      address.value  = GROUP_ADDRESS_CUSTOM;
     ...
 }

// Configuration for the client
case NODE_SETUP_CONFIG_PUBLICATION_CUSTOM_CLIENT:
{
    config_publication_state_t pubstate = {0};
    client_pub_state_set(&amp;amp;pubstate,
                         m_current_node_addr + ELEMENT_IDX_CUSTOM_CLIENT,
                         GROUP_ADDRESS_CUSTOM);
    retry_on_fail(config_client_model_publication_set(&amp;amp;pubstate));

    static const uint8_t exp_status[] = {ACCESS_STATUS_SUCCESS};
    expected_status_set(CONFIG_OPCODE_MODEL_PUBLICATION_STATUS, sizeof(exp_status), exp_status);
    break;
}

...

}
&lt;/pre&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Broadcast in Mesh 2.0.1</title><link>https://devzone.nordicsemi.com/thread/136033?ContentTypeID=1</link><pubDate>Thu, 14 Jun 2018 05:07:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:efdef089-a8d5-454c-b5e8-e2963be5e3b1</guid><dc:creator>Arya</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I am follwing &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/29836/send-and-receive-a-string-via-access-layer/118550#118550" rel="noopener noreferrer" target="_blank"&gt;this link &lt;/a&gt;to do the same thing (broadcasting a simple message through the nodes) in mesh 2.0.1.&lt;/p&gt;
&lt;p&gt;Could you suggest me the steps to be followed or differences in it when we are doing it in mesh 2.0.1?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Broadcast in Mesh 2.0.1</title><link>https://devzone.nordicsemi.com/thread/136006?ContentTypeID=1</link><pubDate>Wed, 13 Jun 2018 19:21:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:59b3c77e-41b0-43e5-88a7-413a672f203b</guid><dc:creator>Paulo.Zacarias</dc:creator><description>&lt;p&gt;Hi Kristin,&lt;/p&gt;
&lt;p&gt;If I understood correctly, in this Mesh version 2.0.1 we don&amp;#39;t have this broadcast address 0xCAFE. I looked at the function &lt;strong&gt;config_step_execute()&lt;/strong&gt; int he &lt;strong&gt;node_setup.c&lt;/strong&gt; on the provisioner side and we assign 2 group addresses, EVEN and ODD.&lt;/p&gt;
&lt;p&gt;Should I, as first step, change this code to attribute only the address 0xCAFE as group address to all nodes, regardless they are even or odd?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Broadcast in Mesh 2.0.1</title><link>https://devzone.nordicsemi.com/thread/135721?ContentTypeID=1</link><pubDate>Tue, 12 Jun 2018 11:07:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:31fce380-cd40-4208-94fb-5acf3456f7ea</guid><dc:creator>FormerMember</dc:creator><description>&lt;p&gt;First, please have a look at&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/29879/subscribe-a-group-address-for-the-mesh-message/118809#118809"&gt; this post,&lt;/a&gt; it shows how to assign a group address.&lt;/p&gt;
&lt;p&gt;After adding the group address and group handle to &lt;code&gt;dsm_address_publish_add()&lt;/code&gt;, I would think you should be able to add the necessary parameters to simple_on_off_client_set_unreliable().&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>