<?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>Couldn&amp;#39;t connect to Ember ZigBee endpoint</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/113208/couldn-t-connect-to-ember-zigbee-endpoint</link><description>Hi everyone, 
 I&amp;#39;m currently working on a project involving an Ember ZigBee end device and a Nordic ZigBee coordinator ( Nordic nRF52840 donngle) . I’ve encountered an issue where the Ember device sends a beacon request, and although the Nordic coordinator</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 24 Jul 2024 07:46:40 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/113208/couldn-t-connect-to-ember-zigbee-endpoint" /><item><title>RE: Couldn't connect to Ember ZigBee endpoint</title><link>https://devzone.nordicsemi.com/thread/495344?ContentTypeID=1</link><pubDate>Wed, 24 Jul 2024 07:46:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c271acf3-58cc-420d-a1b4-9220cf1f832f</guid><dc:creator>Maria Gilje</dc:creator><description>[quote user="Max123123"]The problem that the Ember device use the stack profile equal to &amp;quot;network specific&amp;quot; and the Nordic dongle use Zigbee PRO.&amp;nbsp;[/quote]
&lt;p&gt;Yes, you are completely correct. &lt;/p&gt;
&lt;p&gt;The conclusion is that the Ember device will not be compatible with the ZBOSS stack.&lt;/p&gt;
&lt;p&gt;Some explanation:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;All devices in the same network needs to have the same stack profile to be compatible. So the fact that Ember has the network specific stack profile practically makes it incompatible with all non-Ember devices.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;You can not rebuild the ZBOSS stack with the stack profile set as network specific. Even if you could you would still need to set all the parameters that Ember sets to make the two devices compatible.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Maria&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Couldn't connect to Ember ZigBee endpoint</title><link>https://devzone.nordicsemi.com/thread/495077?ContentTypeID=1</link><pubDate>Mon, 22 Jul 2024 15:54:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9e96a0e1-a472-40ab-bfdf-4933db16e44b</guid><dc:creator>Max123123</dc:creator><description>&lt;p&gt;Yeah I did. I know what is the problem but don&amp;#39;t know how can I solve it.&amp;nbsp;&lt;br /&gt;The problem that the Ember device use the stack profile equal to &amp;quot;network specific&amp;quot; and the Nordic dongle use Zigbee PRO.&amp;nbsp;&lt;br /&gt;In the old nrf for zigbee and thread SDK there was Macro inside zb_config.h file that allow you when you enable it to connect to the Ember devices it&amp;#39;s called `#define ZB_EMBER_GOLDEN_UNIT` (which in turn make the stack profile equal to network specific). I already enabled it and flashed the dongle with old firmware but still the same problem. In the last firmware version this value doesn&amp;#39;t exist inside ZBOSS.&lt;br /&gt;So this is the problem with stack profile but I don&amp;#39;t know how to change it&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Couldn't connect to Ember ZigBee endpoint</title><link>https://devzone.nordicsemi.com/thread/495076?ContentTypeID=1</link><pubDate>Mon, 22 Jul 2024 15:45:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bbee9e15-0216-4e05-b6c0-4f13502b56c8</guid><dc:creator>Maria Gilje</dc:creator><description>&lt;p&gt;Did you remember to &lt;a href="https://infocenter.nordicsemi.com/topic/sdk_tz_v4.2.0/zigbee_example_cli_agent.html?cp=9_3_3_8_5_1_2_0#zigbee_example_cli_agent_setup_zc"&gt;set the device to be the Zigbee Coordinator&lt;/a&gt; before starting the Zigbee network?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Couldn't connect to Ember ZigBee endpoint</title><link>https://devzone.nordicsemi.com/thread/494859?ContentTypeID=1</link><pubDate>Fri, 19 Jul 2024 15:40:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e20cb3f9-2c9a-4a1a-be97-49bd7d4a5463</guid><dc:creator>Max123123</dc:creator><description>&lt;p&gt;Thanks for response&amp;nbsp;&lt;br /&gt;I&amp;#39;ve use the cli example for fast test and after I initialize the ZigBee stack and start it I run `bdb legacy enable` (I believe it is the same of the call you mentioned) but still I the device refused to join the network. I&amp;#39;ve checked the network traffic and no thing changed in the Beacon response. You can see it in the attached photo&lt;br /&gt;&lt;br /&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/pastedimage1721403638545v1.png" alt=" " /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Couldn't connect to Ember ZigBee endpoint</title><link>https://devzone.nordicsemi.com/thread/494855?ContentTypeID=1</link><pubDate>Fri, 19 Jul 2024 15:29:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9a03a258-3616-4606-9337-f855f646ca23</guid><dc:creator>Maria Gilje</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;You can enable legacy support for the coordinator by adding a call to zb_bdb_set_legacy_device_support(1) after the ZBOSS stack is initialized.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Maria&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>