<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://test-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 window covering current endpoint is always zero</title><link>https://test-devzone.nordicsemi.com/f/nordic-q-a/88351/zigbee-window-covering-current-endpoint-is-always-zero</link><description>Hi, i am developing Zigbee window covering device on nrf connect sdk 1.9.1v which has 2 endpoints, but i am face issue when zigbee command is received and 
 
 device_interface_cb is called and i get the endpoint as zero for both endpoint 1 and 2</description><dc:language>en-US</dc:language><generator>Telligent Community 13 Non-Production</generator><lastBuildDate>Tue, 31 May 2022 09:58:25 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://test-devzone.nordicsemi.com/f/nordic-q-a/88351/zigbee-window-covering-current-endpoint-is-always-zero" /><item><title>RE: Zigbee window covering current endpoint is always zero</title><link>https://test-devzone.nordicsemi.com/thread/370159?ContentTypeID=1</link><pubDate>Tue, 31 May 2022 09:58:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fa694b62-ef2f-4b38-813e-498e60fcc02c</guid><dc:creator>user91787</dc:creator><description>&lt;p&gt;Thank you, now the problem is solved&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Zigbee window covering current endpoint is always zero</title><link>https://test-devzone.nordicsemi.com/thread/369961?ContentTypeID=1</link><pubDate>Mon, 30 May 2022 11:33:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:dafda3aa-0882-4426-9674-e8cad251d7f0</guid><dc:creator>user91187</dc:creator><description>&lt;p&gt;Update: This could be a ZCL layer bug,&lt;br /&gt;&lt;br /&gt;Assuming that&amp;nbsp;you use Production version of ZBOSS libraries, this is what should fix the issue:&lt;/p&gt;
&lt;p&gt;Change zb_zcl_window_covering_invoke_user_app() function in nrxlib/zboss/production/src/zcl/zcl_window_covering.c:172 :&lt;br /&gt;&lt;br /&gt;From:&lt;br /&gt;&lt;pre class="ui-code" data-mode="text"&gt;static zb_ret_t zb_zcl_window_covering_invoke_user_app(zb_uint8_t param,
                                                       const zb_zcl_parsed_hdr_t *cmd_info,
                                                       zb_zcl_device_callback_id_t user_cb_id,
                                                       void *payload)
      {
  zb_ret_t ret = RET_OK;
  TRACE_MSG(TRACE_ZCL1, &amp;quot;&amp;gt; zb_zcl_window_covering_invoke_user_app cb_id %d&amp;quot;, (FMT__D, user_cb_id));
  ZB_ZCL_DEVICE_CMD_PARAM_INIT_WITH(param, user_cb_id, RET_OK, cmd_info, payload, NULL);
  if (ZCL_CTX().device_cb != NULL)
  {
    (ZCL_CTX().device_cb)(param);
      }&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;To:&lt;br /&gt;&lt;pre class="ui-code" data-mode="text"&gt;static zb_ret_t zb_zcl_window_covering_invoke_user_app(zb_uint8_t param,
                                                       const zb_zcl_parsed_hdr_t *cmd_info,
                                                       zb_zcl_device_callback_id_t user_cb_id,
                                                       void *payload)
      {
  zb_ret_t ret = RET_OK;
  TRACE_MSG(TRACE_ZCL1, &amp;quot;&amp;gt; zb_zcl_window_covering_invoke_user_app cb_id %d&amp;quot;, (FMT__D, user_cb_id));
  ZB_ZCL_DEVICE_CMD_PARAM_INIT_WITH(param, user_cb_id, RET_OK, cmd_info, payload, NULL);
  /* Set endpoint meant to receive this command. */
  ZB_ZCL_DEVICE_CMD_PARAM(param)-&amp;gt;endpoint = ZB_ZCL_PARSED_HDR_SHORT_DATA(cmd_info).dst_endpoint;
  if (ZCL_CTX().device_cb != NULL)
  {
    (ZCL_CTX().device_cb)(param);
      }&lt;/pre&gt;&lt;br /&gt;&lt;br /&gt;Regards,&lt;br /&gt;Jonathan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Zigbee window covering current endpoint is always zero</title><link>https://test-devzone.nordicsemi.com/thread/369876?ContentTypeID=1</link><pubDate>Mon, 30 May 2022 07:03:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d26d1b72-d0a3-4974-bca8-53b77536796e</guid><dc:creator>user91187</dc:creator><description>&lt;p&gt;Hi,&lt;br /&gt;&lt;br /&gt;Nothing apparent in you code you have shared that would indicate what the issue could be.&lt;br /&gt;&lt;br /&gt;So issue might be with the command that is being send or it could be how you declarer endpoints. So here here a couple of things that you can do to further debug.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;To check if the issue lies within the command used:&lt;br /&gt;&amp;nbsp;- Do a sniffer log of the commands, can use &lt;a href="https://infocenter.nordicsemi.com/index.jsp?topic=%2Fug_sniffer_802154%2FUG%2Fsniffer_802154%2Fintro_802154.html"&gt;nRF Sniffer for 802.15.4&lt;/a&gt;, then shar the log with us as a pcap file. Make sure that the sniffer is started before the coordinator starts the network so that the sniffer has the network key.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Ckeck the endpoint:&lt;br /&gt;- Using Zigbee shell you can see if both endpoints are on the device. So add a extra device\DK to the network by programming the &lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.9.1/nrf/samples/zigbee/shell/README.html"&gt;Zigbee: Shell&lt;/a&gt;&amp;nbsp; &amp;nbsp; and set it up so that it joins the same network as the other devices. Then you can use the &lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.9.1/nrf/libraries/zigbee/shell.html#zdo-active-ep"&gt;zdo active_ep&lt;/a&gt; command to se what endpoints are on&amp;nbsp; the device you have.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;- Share the code where you declarer the endpoints.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;Regards,&lt;br /&gt;Jonathan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>