<?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>[Zigbee] Attribute subscription to multi-endpoint device breaks nvram</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/61260/zigbee-attribute-subscription-to-multi-endpoint-device-breaks-nvram</link><description>Hello. 
 I&amp;#39;m using Zigbee SDK 4.1.0 with custom pca10059-compatible debug board with nrf52840. 
 Binding and subscribing to attributes on a multiple endpoint device appears to clear or prevent loading NVRAM memory. The device forgets the state of pairing</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 11 Aug 2020 09:41:54 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/61260/zigbee-attribute-subscription-to-multi-endpoint-device-breaks-nvram" /><item><title>RE: [Zigbee] Attribute subscription to multi-endpoint device breaks nvram</title><link>https://devzone.nordicsemi.com/thread/263992?ContentTypeID=1</link><pubDate>Tue, 11 Aug 2020 09:41:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:60fb1590-2fc8-4b8c-9de5-938ac6851bf3</guid><dc:creator>happy_nordic_user</dc:creator><description>&lt;p&gt;Hello.&lt;/p&gt;
&lt;div class="text-wrap tlid-copy-target"&gt;
&lt;div class="result-shield-container tlid-copy-target"&gt;&lt;span class="tlid-translation translation" lang="en"&gt;&lt;span class="" title=""&gt;Thank you for the answer.&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span title=""&gt;Unfortunately, for more than three months no one could help me with this issue.&lt;/span&gt; &lt;span class="" title=""&gt;I am deeply disappointed with the level of support from both Nordic and DSR company.&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span class="" title=""&gt;I switched to Thread (OpenThread) protocol, my life became much easier.&lt;/span&gt;&lt;/span&gt;&lt;span class="tlid-translation-gender-indicator translation-gender-indicator"&gt;&lt;/span&gt;&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: [Zigbee] Attribute subscription to multi-endpoint device breaks nvram</title><link>https://devzone.nordicsemi.com/thread/263981?ContentTypeID=1</link><pubDate>Tue, 11 Aug 2020 09:20:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0e886c45-1a86-44a4-b4cd-b1c79fb97fe9</guid><dc:creator>Marjeris Romero</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I have now an answer for you, I am very sorry for the delay. The ZBOSS stack has a limit on the number of active reporting configurations to 10 entries. This limitation cannot be change inside the application. The only way to mitigate this in the application is to change the size of the reporting table inside the endpoint declaration.&lt;/p&gt;
&lt;p&gt;In case of our Thingy example, we have 3 endpoints, which gives us a maximum of 3 active reporting configurations. In order to apply the mitigation please change the value of ZB_ZCL_COLOR_CONTROL_REPORT_ATTR_COUNT to three:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;#define ZB_ZCL_DECLARE_COLOR_DIMMABLE_LIGHT_EP(ep_name, ep_id, cluster_list)        \

    ZB_ZCL_DECLARE_COLOR_DIMMABLE_LIGHT_SIMPLE_DESC(                                \

        ep_name,                                                                    \

        ep_id,                                                                      \

        ZB_HA_COLOR_CONTROL_IN_CLUSTER_NUM,                                         \

        ZB_HA_COLOR_CONTROL_OUT_CLUSTER_NUM);                                       \

    ZBOSS_DEVICE_DECLARE_REPORTING_CTX(reporting_info## ep_name,                    \

        (3));                                  \

    ZBOSS_DEVICE_DECLARE_LEVEL_CONTROL_CTX(cvc_alarm_info## ep_name,                \

        ZB_ZCL_COLOR_DIMMABLE_LIGHT_CVC_ATTR_COUNT);                                \

    ZB_AF_DECLARE_ENDPOINT_DESC(                                                    \

        ep_name,                                                                    \

        ep_id,                                                                      \

        ZB_AF_HA_PROFILE_ID,                                                        \

        0,                                                                          \

        NULL,                                                                       \

        ZB_ZCL_ARRAY_SIZE(                                                          \

            cluster_list,                                                           \

            zb_zcl_cluster_desc_t),                                                 \

        cluster_list,                                                               \

        (zb_af_simple_desc_1_1_t*)&amp;amp;simple_desc_## ep_name,                          \

       3,                                     \

        reporting_info## ep_name,                                                   \

        ZB_ZCL_COLOR_DIMMABLE_LIGHT_CVC_ATTR_COUNT,                                 \

        cvc_alarm_info## ep_name)
&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;The issue with the limitation on the number of reporting configurations to 10 is reported to DSR (provider of ZBOSS stack).&lt;/p&gt;
&lt;p&gt;Again, I am very sorry for the delay in this case.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Marjeris&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: [Zigbee] Attribute subscription to multi-endpoint device breaks nvram</title><link>https://devzone.nordicsemi.com/thread/254840?ContentTypeID=1</link><pubDate>Sat, 13 Jun 2020 21:21:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a0dd1145-11ee-4ca2-a78e-e1a688b95d6f</guid><dc:creator>happy_nordic_user</dc:creator><description>&lt;p&gt;Hi. Yet a&lt;span class="tlid-translation translation" lang="en"&gt;&lt;span title=""&gt;nother month has passed.&lt;/span&gt; &lt;span class="" title=""&gt;I hope there is news on this topic that you accidentally forgot to write &lt;span class="emoticon" data-url="https://devzone.nordicsemi.com/cfs-file/__key/system/emoji/1f642.svg" title="Slight smile"&gt;&amp;#x1f642;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: [Zigbee] Attribute subscription to multi-endpoint device breaks nvram</title><link>https://devzone.nordicsemi.com/thread/249726?ContentTypeID=1</link><pubDate>Wed, 13 May 2020 12:40:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b05939ac-8ea6-4ae0-8918-eb7e8e6fda1f</guid><dc:creator>Marjeris Romero</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Sorry for the late reply. I will try to reproduce the case and send to our Zigbee team for analysis.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Marjeris&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>