<?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>How does the client  receive RSSI value from servers?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/34917/how-does-the-client-receive-rssi-value-from-servers</link><description>Hi, when I provisioned the client and servers via provisioner to create mesh network, I can receive RSSI value from provisionee ,but after the provisionee disconnect to power and reconnect to it or after reset the provisionee, I can&amp;#39;t receive RSSI value</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 30 May 2018 13:24:24 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/34917/how-does-the-client-receive-rssi-value-from-servers" /><item><title>RE: How does the client  receive RSSI value from servers?</title><link>https://devzone.nordicsemi.com/thread/134046?ContentTypeID=1</link><pubDate>Wed, 30 May 2018 13:24:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b5c23560-e568-4ccd-96ac-88f4d34e82f9</guid><dc:creator>zhengrui</dc:creator><description>&lt;p&gt;Thanks&amp;nbsp; all of you ,now I have solved this bug by using the patch to replace the codes in access.c although I still know the reason.&lt;/p&gt;
&lt;p&gt;Thank you Bjorn and leonwj.&lt;/p&gt;
&lt;p&gt;BR.&lt;/p&gt;
&lt;p&gt;Zhengrui&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How does the client  receive RSSI value from servers?</title><link>https://devzone.nordicsemi.com/thread/134015?ContentTypeID=1</link><pubDate>Wed, 30 May 2018 11:52:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fc8ecd41-1223-4a5a-94c1-8e9996189554</guid><dc:creator>leonwj</dc:creator><description>&lt;p&gt;hello,&lt;/p&gt;
&lt;p&gt;Based upon the limited description of your error, I believe this pertains to the server health status messages (with RSSI values) no longer propagating after powering off and re-connection...&lt;/p&gt;
&lt;p&gt;I believe that this bug is a carry over from Mesh v1.0.1 that was not fixed going into v2.0.1 and is described in this &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/29611/mesh-health-model#post-id-189330" rel="noopener noreferrer" target="_blank"&gt;post&lt;/a&gt;. Once you follow the instructions provided by &lt;a href="https://devzone.nordicsemi.com/members/joaooliveira" rel="noopener noreferrer" target="_blank"&gt;Jo&amp;atilde;o Oliveira&lt;/a&gt;&amp;nbsp;you should find that the&amp;nbsp;mesh health model state (and subsequent messages) is restored on reboots.&lt;/p&gt;
&lt;p&gt;In essence the following needs to be implemented in access.c...&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;// bug in Mesh sdk v1.01 - https://devzone.nordicsemi.com/f/nordic-q-a/29611/mesh-health-model#post-id-189330
// suggested patch applied

static inline void restore_publication_period(access_common_t * p_model) {      // WJL - patch function - see  below
    if(p_model-&amp;gt;model_info.publication_period.step_num != 0){
        access_publish_period_set(&amp;amp;p_model-&amp;gt;publication_state, p_model-&amp;gt;model_info.publication_period.step_res, p_model-&amp;gt;model_info.publication_period.step_num);
    }
}

static inline bool restore_models(void)
{
    if (restore_flash_data(FLASH_GROUP_MODEL, ACCESS_MODEL_COUNT, restore_acquired_model) &amp;lt;= 0)
    {
        return false;
    }

    for (access_model_handle_t i = 0; i &amp;lt; ACCESS_MODEL_COUNT; ++i)
    {
        if (m_model_pool[i].model_info.element_index != ACCESS_ELEMENT_INDEX_INVALID)
        {
                restore_addresses_for_model(&amp;amp;m_model_pool[i]);
                restore_publication_period(&amp;amp;m_model_pool[i]);       // WJL - patch line
        }
    }

    return true;
}&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;Once you have tried the patch, post back to let us know how you got on and we can help you further if required.&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How does the client  receive RSSI value from servers?</title><link>https://devzone.nordicsemi.com/thread/134005?ContentTypeID=1</link><pubDate>Wed, 30 May 2018 11:02:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:54a60398-9e70-4a5f-8e47-c63eef254dd3</guid><dc:creator>Bj&amp;#248;rn Kvaale</dc:creator><description>&lt;p&gt;Have you tried restarting the rtt viewer instance? I often find that if I reset the board, the rtt viewer program will need to be closed &amp;amp; restarted before the logging begins again.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Regarding receiving RSSI values on the client, I would check how the provisioner implements this &amp;amp; do something similar on the client. Take a look at the app_health_event_cb() function in main.c of the provisioner light switch example in mesh sdk v2.0.1.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>