TI E2E Community
Low Power RF & Wireless Connectivity
Low Power RF ZigBee® Software & IEEE 802.15.4 Forum
Ember & Texas Instrument : compatibility issue when Home Automation security is activated?
We have observed an incompatibility case during secured authentification process between the plug & switch on Ember stack & our coordinator on Texas Instrument stack. In a secured network, after a device have made an association with a router, this router sends an APS Update Device command to the coordinator (the Trust Center in our case) in order to authentificate the new incoming device. We observed that Ember router sends this APS Update Device with NWK & APS security activated whereas Texas Instrument router sends this message with only NWK security activated. Please observed following 'incompatibility texas & ember.pcap' log file 8688.incompatibility texas & ember.zip : use following network key : 0dbf0590034cc31513ef0facc69d9389 At frame 299 : we made a succesfull association & authentification process with a Texas Instrument secured router. At frame 818, 847 & 857 : we made an association with a Ember router but the authentification failed.
The difference concerns the Zigbee Application Support Layer : the security is activated on Ember and is not on Texas Instrument. I wouldn't say if Ember or Texas Instrument is right or wrong, but as we are in Home Automation Security (Residential Security mode), is it not just the Zigbee Network Layer concerned about security?
the issue you're facing comes from a different interpretation of the ZigBee specification r17, which was not clear about the encryption methods on APS layer to send the UPDATE-DEVICE.
Hence, different technology vendors have implemented this procedure differently; which led to the interop problem you're reporting. This issue has been identified in the errata of the ZigBee spec and is corrected in next r20 version, which is currently being finalized within the ZigBee Alliance but not yet completed.
When r20 the profile is ratified and completed, we will publish a release which supports those feature and hence automatically solves the item above.
We of course have a solution which works-around this issue but I recommend the full r20 compliant release if your project timing allows for it.
Please let us know if this works for you and in case contact your local TI-representative if you need information on Z-stack roadmap.
Thanks a lot for this answer.
It is quite bad news for us.
Are all the stacks (Ember, Jennic...) are impacted by this issue or only Texas Instrument Z-Stack ?
Do you know when the next r20 version should be ratified ?
How many time do we have approximatively to wait before next Z-Stack release? (3 months, 6 months, 1 year or more ?)
We understood that you already have a "solution which works-around this issue", should it be possible to test it before?
We are facing the same issue when using MSP430 + CC2520 as coordinator, the "update device" packet with NWK and APS security is sent from the router (Ember Based) and acknowledged by the Coordinator, but there is no response. We understand you are having a work around for this, kindly provide the solution for the same. We are using the latest ZStack available.
I have encountered what looks like the same problem, where a ZigBee certified light switch will not connect to a TI coordinator. The switch joins an Ember network correctly, and the difference is that the APS security is enabled on the Ember when it sends the security key to the switch. How do I get the patch for this? I am using the CC2530-2.5.0 stack.
Well, I contacted TI support to get a workaround for this and this is the reply I got.
'Due to the nature of your inquiry, we recommend you use our TI E2E™ Community Support Forums where you can post questions, search for answers and collaborate with fellow engineers and TI experts.'
I also tried the recently released CC2530-2.5.1 stack, but it behaves the same way. So the situation is that we can not sell our TI based product because it is not interoperable with ZigBee certified products. As pointed out earlier, this may be an Ember issue, but in any case we are developing with TI and this is the side we need to change to make this work.
If anyone has a patch for this, please let me know.
We wonder if the Zigbee spec r20 version is currently implemented with ZStack-CC2530-2.5.1-a?
the Zstack which has support for r20 is Z-stack Home 1.1.0.
2.5.1a does not support r20.
I basically have the same problem and I would like to know if TI will tell us what is the workaround for this issue.
In my case, the problem I had trying to join an Ember coordinator was solved by adding TC_LINKEY_JOIN definition to the project.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.