<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic ZigBee, JN5169, Match Descriptor in Wireless MCU</title>
    <link>https://community.nxp.com/t5/Wireless-MCU/ZigBee-JN5169-Match-Descriptor/m-p/752997#M4387</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello!&lt;BR /&gt;After the connection to ZC, the ED sends out a broodcast (0xFFFD) Match_Descriptor_Request.&lt;BR /&gt;Is it possible to use the ZigbeeNodeControlBridge_JN5169.bin file and ZGWUI.exe to respond to this request (send Match_decre_res)? In TI (in the Z-stack, ZNP + Z-tools), this was solved by registering the EndPoint with the corresponding cluster.&lt;BR /&gt;I use:&lt;BR /&gt; &lt;EM&gt;JN5169-001-M00-2&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt; JN-AN-1223-ZigBee-IoT-Gateway-Control-Bridge-v1014 &lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt; JN-SW-4168&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 13 Mar 2018 09:49:42 GMT</pubDate>
    <dc:creator>egorzmushko</dc:creator>
    <dc:date>2018-03-13T09:49:42Z</dc:date>
    <item>
      <title>ZigBee, JN5169, Match Descriptor</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/ZigBee-JN5169-Match-Descriptor/m-p/752997#M4387</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello!&lt;BR /&gt;After the connection to ZC, the ED sends out a broodcast (0xFFFD) Match_Descriptor_Request.&lt;BR /&gt;Is it possible to use the ZigbeeNodeControlBridge_JN5169.bin file and ZGWUI.exe to respond to this request (send Match_decre_res)? In TI (in the Z-stack, ZNP + Z-tools), this was solved by registering the EndPoint with the corresponding cluster.&lt;BR /&gt;I use:&lt;BR /&gt; &lt;EM&gt;JN5169-001-M00-2&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt; JN-AN-1223-ZigBee-IoT-Gateway-Control-Bridge-v1014 &lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt; JN-SW-4168&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Mar 2018 09:49:42 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/ZigBee-JN5169-Match-Descriptor/m-p/752997#M4387</guid>
      <dc:creator>egorzmushko</dc:creator>
      <dc:date>2018-03-13T09:49:42Z</dc:date>
    </item>
    <item>
      <title>Re: ZigBee, JN5169, Match Descriptor</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/ZigBee-JN5169-Match-Descriptor/m-p/752998#M4388</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Egor,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please take as reference the &lt;A href="https://www.nxp.com/docs/en/user-guide/JN-UG-3101.pdf?fsrch=1&amp;amp;sr=2&amp;amp;pageNum=1"&gt;ZigBee PRO Stack User Guide&lt;/A&gt;&lt;/P&gt;&lt;P&gt;API&amp;nbsp;ZPS_eAplZdpMatchDescRequest&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Mario&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Mar 2018 01:01:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/ZigBee-JN5169-Match-Descriptor/m-p/752998#M4388</guid>
      <dc:creator>mario_castaneda</dc:creator>
      <dc:date>2018-03-21T01:01:46Z</dc:date>
    </item>
  </channel>
</rss>

