<?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>The character string greater than 40 symbols cannot be read by the attribute read command, Zigbee</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/60715/the-character-string-greater-than-40-symbols-cannot-be-read-by-the-attribute-read-command-zigbee</link><description>While trying to read the 41 (or more) bytes length character string attribute from the device based on nRF Thread and Zigbee SDK v3.1.0 by the read attribute Zigbee command, the “Failure” status returned instead of actual string. The strings with the</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 30 Apr 2020 13:56:20 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/60715/the-character-string-greater-than-40-symbols-cannot-be-read-by-the-attribute-read-command-zigbee" /><item><title>RE: The character string greater than 40 symbols cannot be read by the attribute read command, Zigbee</title><link>https://devzone.nordicsemi.com/thread/247595?ContentTypeID=1</link><pubDate>Thu, 30 Apr 2020 13:56:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d351729b-750c-4063-848e-5c21240a9515</guid><dc:creator>AnnaR</dc:creator><description>&lt;p&gt;Hi Marjeris,&lt;/p&gt;
&lt;p&gt;Thank you for the clarification.&lt;/p&gt;
&lt;p&gt;Sincerely,&lt;/p&gt;
&lt;p&gt;Anna&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: The character string greater than 40 symbols cannot be read by the attribute read command, Zigbee</title><link>https://devzone.nordicsemi.com/thread/247577?ContentTypeID=1</link><pubDate>Thu, 30 Apr 2020 13:18:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3368af5c-d6e6-45ee-bcfd-e4afce861387</guid><dc:creator>Marjeris Romero</dc:creator><description>&lt;p&gt;Hi Anna,&lt;/p&gt;
&lt;p&gt;Please disregard my previous answer. I got and answer from the Zigbee team now:&lt;/p&gt;
&lt;div&gt;
&lt;div&gt;&amp;quot;Customer&amp;#39;s observations are correct, ZCL payload is limited to 48 bytes and it can not be changed. It is limited to this value to make sure that all optional fields of packet,if present, will fit in the single&amp;nbsp;buffer.&amp;quot;&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: The character string greater than 40 symbols cannot be read by the attribute read command, Zigbee</title><link>https://devzone.nordicsemi.com/thread/247515?ContentTypeID=1</link><pubDate>Thu, 30 Apr 2020 11:11:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f394516e-aba8-489f-ba4c-bc78dc084e60</guid><dc:creator>Marjeris Romero</dc:creator><description>&lt;p&gt;Hi Anna,&lt;/p&gt;
&lt;p&gt;Sorry for the late reply, I am looking into this, there is no a lockdown of the ZCL payload in the stack as far as I know but I have asked our Zigbee team to confirm this. Payload length will also depend for instance on the available memory of the zboss buffer, if there is not enough free memory, &amp;#39;failure&amp;#39; is returned.&lt;/p&gt;
&lt;p&gt;Do you have sniffer trace which shows the attribute read response send from the device?&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>