<?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 request and response</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/42171/zigbee-attribute-request-and-response</link><description>Hi and happy new year everyone, 
 I am a developer for Raytheon Ansch&amp;#252;tz GmbH in Kiel Germany and working on a Zigbee mesh sensor network. Unfortunately I am an absolute beginner for Zigbee and have a lot of basic questions I can not figure out the the</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 10 Jun 2019 03:38:16 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/42171/zigbee-attribute-request-and-response" /><item><title>RE: Zigbee Attribute request and response</title><link>https://devzone.nordicsemi.com/thread/191766?ContentTypeID=1</link><pubDate>Mon, 10 Jun 2019 03:38:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5e72f275-5edf-4a3b-b1da-d75c8ff7ac78</guid><dc:creator>AnnaR</dc:creator><description>&lt;p&gt;Hi Tomchy,&lt;/p&gt;
&lt;p&gt;Many thanks for your advice and explanation.&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: Zigbee Attribute request and response</title><link>https://devzone.nordicsemi.com/thread/191765?ContentTypeID=1</link><pubDate>Mon, 10 Jun 2019 03:33:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c2038155-5024-43b1-a978-dfd8056df75b</guid><dc:creator>AnnaR</dc:creator><description>&lt;p&gt;Hi Edvin,&lt;/p&gt;
&lt;p&gt;Thank you for your concern, Andreas answered my question.&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: Zigbee Attribute request and response</title><link>https://devzone.nordicsemi.com/thread/191151?ContentTypeID=1</link><pubDate>Wed, 05 Jun 2019 13:55:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0a3ff89f-b70d-4f31-a5d9-365271e48ba8</guid><dc:creator>tomchy</dc:creator><description>&lt;p&gt;Hi Anna,&lt;/p&gt;
&lt;p&gt;you may attach a default reporting configuration via&amp;nbsp;zb_zcl_put_default_reporting_info (unfortunately - present in header files, but excluded form the official documentation via&amp;nbsp;internals_doc flag).&lt;/p&gt;
&lt;p&gt;You may also send the same command as in CLI to the device itself (looks like a more generic solution).&lt;/p&gt;
&lt;p&gt;When it comes to the min/max intervals - you still have to specify them. Just please take a look at ZCLv7 specification, section 2.5.7.1.6. It simply says, that you should:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;set min != 0xFFFF&lt;/li&gt;
&lt;li&gt;set max == 0x0000&lt;/li&gt;
&lt;li&gt;provide a Reportable Change Field to specify on how huge changes you would like to receive reports.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Best Regards,&lt;/p&gt;
&lt;p&gt;Tomchy&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Zigbee Attribute request and response</title><link>https://devzone.nordicsemi.com/thread/191150?ContentTypeID=1</link><pubDate>Wed, 05 Jun 2019 13:54:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6dcb79d5-688d-425f-8d7e-87aee91e1fc0</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/members/annar"&gt;AnnaR&lt;/a&gt;,&lt;/p&gt;
&lt;p&gt;I see that you have a &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/48175/how-to-configure-attribute-changes-notifications-on-binding-zigbee" rel="noopener noreferrer" target="_blank"&gt;separate ticket&lt;/a&gt; that my colleague, Andreas replied to. Does that answer your question?&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Zigbee Attribute request and response</title><link>https://devzone.nordicsemi.com/thread/190732?ContentTypeID=1</link><pubDate>Tue, 04 Jun 2019 10:49:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:84d47534-664e-440e-9348-ca6673ddad6f</guid><dc:creator>AnnaR</dc:creator><description>&lt;p&gt;Hi Tomchy,&lt;/p&gt;
&lt;p&gt;Could you please explain, what do you mean by p. 8 (Implement a piece of logic, that enables reporting locally, at device setup).&lt;/p&gt;
&lt;p&gt;I was successful with p.1-7, but I cannot setup sending the actual values of attributes on their change just after binding, so without the configure reporting command.&lt;/p&gt;
&lt;p&gt;The commercial devices we are tested send their attributes (on change) just after successful Bind Request from coordinator. I need to realize such a functionality too but have no idea, how to do it using the ZBOSS stack. If I will configure reporting on device (router in my case) side, I have to provide the lowest and greatest reporting times, but I need just to send new attribute value on change without the periodic reporting even each 600s.&amp;nbsp;&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: Zigbee Attribute request and response</title><link>https://devzone.nordicsemi.com/thread/171232?ContentTypeID=1</link><pubDate>Thu, 14 Feb 2019 19:52:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:af751427-f1a4-46ca-b681-4a8f040a66b5</guid><dc:creator>Marco</dc:creator><description>&lt;p&gt;Thank you Tomchy for your advice. I am very busy at the moment but will definitely have a look into the cli example.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards&lt;/p&gt;
&lt;p&gt;Marco&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Zigbee Attribute request and response</title><link>https://devzone.nordicsemi.com/thread/170200?ContentTypeID=1</link><pubDate>Fri, 08 Feb 2019 22:53:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cb20d03d-ad71-4d63-a633-c9e5f4e022bf</guid><dc:creator>tomchy</dc:creator><description>&lt;p&gt;Hi Marco,&lt;/p&gt;
&lt;p&gt;I hope the full answer will come soon, but do not forget about the CLI example. It definitely can be used as a reference to send read attribute requests/parse responses as well as configure reporting on a remote device.&lt;/p&gt;
&lt;p&gt;I&amp;#39;d personally suggest to start with read attribute requests, than switch to reporting as it will automatically generate packets with measured values in regular time intervals (e.g. implement application logic similar to the one in &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/33683/zigbee-coordinator-with-xiaomi-devices/170184#170184"&gt;Xiaomi devices&lt;/a&gt;).&lt;/p&gt;
&lt;p&gt;More details about the reporting feature may be found in &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/40371/zigbee-ha-atrribute-reporting" rel="noopener noreferrer" target="_blank"&gt;this thread&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;If your plan is just to make a sensor, the CLI is the perfect tool for you to test your implementation. Generally - from the moment you properly include the cluster and readable attribute definition, you shall be able to read it.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;My plan for you would be:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Try to read something which is well defined and copied from Nordic&amp;#39;s examples, such as attributes inside Basic cluster.&lt;/li&gt;
&lt;li&gt;Add a new cluster, initialize its values.&lt;/li&gt;
&lt;li&gt;Test if you can read initial values through CLI commands.&lt;/li&gt;
&lt;li&gt;Implement logic that updates values inside attributes.&lt;/li&gt;
&lt;li&gt;Test if you can read new values through CLI.&lt;/li&gt;
&lt;li&gt;Configure reporting remotely via CLI.&lt;/li&gt;
&lt;li&gt;Check if you can see reports upon attribute updates (it may be tricky - you have to use a macro to update them).&lt;/li&gt;
&lt;li&gt;Implement a piece of logic, that enables reporting locally, at device setup.&lt;/li&gt;
&lt;li&gt;Test it with CLI configured as a Zigbee coordinator. You shall receive periodic attribute updates without issuing commands to configure reporting.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;I hope that using those points as a reference in informing about your implementation progress will help &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;/p&gt;
&lt;p&gt;I hope Edvin will get some information about it, but it is likely that macros &amp;quot;ZB_ZCL_CLUSTER_ID_TEMP_MEASUREMENT_CLIENT_ROLE_INIT()&amp;quot; / &amp;quot;ZB_ZCL_CLUSTER_ID_TEMP_MEASUREMENT_SERVER_ROLE_INIT()&amp;quot; are called automatically by the stack and you do not have to worry about them.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best Regards,&lt;/p&gt;
&lt;p&gt;Tomchy&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Zigbee Attribute request and response</title><link>https://devzone.nordicsemi.com/thread/168409?ContentTypeID=1</link><pubDate>Tue, 29 Jan 2019 09:59:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:47650027-7dff-45cd-9364-3c1149d88cd4</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello Marco,&lt;/p&gt;
&lt;p&gt;I am sorry that this has taken so long. I am still waiting for the response from our ZigBee team. I received an email last week saying that they will look into it this week, so hopefully I will have an answer for you soon. I just wanted you to know that this ticket is not forgotten.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Zigbee Attribute request and response</title><link>https://devzone.nordicsemi.com/thread/165965?ContentTypeID=1</link><pubDate>Wed, 16 Jan 2019 12:36:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:431dcfdb-1764-4241-9422-79eb072c1e28</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello Marco,&lt;/p&gt;
&lt;p&gt;sorry for the late reply. I am working on this. I haven&amp;#39;t actually tried to set up a &amp;quot;custom&amp;quot; cluster in ZigBee before, and the lack of a proper gateway is making it a bit difficult. I am waiting for some hardware to act as a BLE to ZigBee gateway. If you intend to do development, I recommend this. Thus, you can set up a zigbee network, connect the temperature sensor that you are developing, and then use a ZigBee app to check the sensor values, just to make sure that the sensor is set up correctly.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I will keep this ticket open until I have a better answer to you.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Zigbee Attribute request and response</title><link>https://devzone.nordicsemi.com/thread/164783?ContentTypeID=1</link><pubDate>Wed, 09 Jan 2019 18:47:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e33e9746-8854-4798-abec-21dea6347b93</guid><dc:creator>Marco</dc:creator><description>&lt;p&gt;Hi Edvin,&lt;/p&gt;
&lt;p&gt;Thank you for your effort. I attached a projects dir that should reside in the top level of the SDK, next to examples. The coordinator, router and enddevice folders are based on the light_bulb_switch zigbee example.&lt;/p&gt;
&lt;p&gt;You are right. The coordinator should request sensor data from the router. I tried the the temp_measurement first but need to read voltage levels as well.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards&lt;/p&gt;
&lt;p&gt;Marco&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/8765.projects.zip"&gt;devzone.nordicsemi.com/.../8765.projects.zip&lt;/a&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Zigbee Attribute request and response</title><link>https://devzone.nordicsemi.com/thread/164701?ContentTypeID=1</link><pubDate>Wed, 09 Jan 2019 12:17:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f0fc598d-9c5e-4737-8fb8-499f00632581</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello Marco,&lt;/p&gt;
&lt;p&gt;I am sorry. I am not able to compile your projects, and it seems like it is because of something you either have in your project settings, or something you have in some other files, but I am not sure what files that would be.&lt;/p&gt;
&lt;p&gt;Is it possible to send both of these projects, so that I can run a test?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Is it correct that it is the ZigBee coordinator that you are trying to poll the data to from the sensor/server?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Zigbee Attribute request and response</title><link>https://devzone.nordicsemi.com/thread/164622?ContentTypeID=1</link><pubDate>Wed, 09 Jan 2019 07:58:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:88215b46-ba6b-42f9-afd2-5761763209dc</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;I am sorry for the late reply. I will try to run your projects today, and see if I can figure out what is missing.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>