AN1089: Using Installation Codes with Zigbee Devices
This application note provides an overview of using installation codes with Zigbee devices. It also explains (with the help of examples) how to use the EM3xx utilities or Simplicity Commander to check, write, verify, and erase installation codes on Silicon Labs EM3x and Wireless Gecko (EFR32™) devices. Finally, it provides a complete example of how to join a Z3 network with an installation code-derived link key.
Silicon Labs recommends that you be familiar with creating example applications and using the Network Analyzer, as described in QSG106: Getting Started with EmberZNetPRO.
KEY POINTS:
• Concepts of the Zigbee installation code.
• Programming examples for installation codes on EM3x and EFR32 devices.
• Checking, writing, verifying, and erasing installation codes on target devices.
• Joining a Z3 network with an installation code-derived link key.
Zigbee installation codes, sometimes also referred to as "install codes," are provided as a means for a device to join a Zigbee network in a reasonably secure fashion. The installation code itself is a random value installed on the joining device at manufacturing time, and is used to encrypt the initial network key transport from the Zigbee network’s centralized Trust Center device (the coordinator) to the joining device. With the creation of the Zigbee 3.0 standard in late 2016, all Zigbee devices capable of joining networks (as opposed to forming them) must support the use of installation codes during joining, as this is a requirement for Zigbee 3.0 compliance.
The installation code can be thought of as similar to the PIN code on Bluetooth devices when two devices are paired. The PIN code is provided as an authorization code for the parent device so that the joining device knows it is receiving information securely, such as when a hands-free headset is paired to a smartphone.
The installation code is typically printed on the case or packaging of the device, either as a hexadecimal string or in an encoded fashion such as a barcode or QR code, and provided through an out-of-band mechanism to the Trust Center device or its associated web/cloud interface, along with the 64-bit IEEE MAC address ("EUI64") of the device. If this device-specific data is stored on a remote web server or cloud-based system, that remote system then securely transports that information to the Trust Center to establish security credentials for the joining device in advance of the in-band joining process.
|
|
|
|
|
|
|
Application note & Design Guide |
|
|
|
|
Please see the document for details |
|
|
|
|
|
|
|
|
|
|
|
English Chinese Chinese and English Japanese |
|
|
2018/09/25 |
|
|
Rev. 0.2 |
|
|
AN1089 |
|
|
662 KB |
- +1 Like
- Add to Favorites
Recommend
- Wirepas Mesh 2.4GHz Firmware v5.4 and Silicon Labs EFR32MG24: A Powerful Combination for IoT Applications
- Silicon Labs Simplifies IoT Development with Simplicity Studio 5
- Wirepas and the Silicon Labs’ EFR32FG23 Sub-GHz SoC are taking on India’s Smart Metering Challenge
- Silicon Labs Multiprotocol Wireless SoCs EFR32MG24 Team up with Wirepas to Expand Industrial Mesh Network Solutions
- Unlocking Wireless Home Security Capabilities with Wyze Lock Bolt smart door lock that is based on Silicon Labs’EFR32MG21 2.4GHz Wireless SoC
- Silicon Labs Strengthens Isolated Gate Driver Portfolio
- Introducing the EFM8BB50: A New Addition to SILICON LABS 8-bit MCU Family
- Software Speeds Development of IEEE 1588 System Integration | Silicon Labs
All reproduced articles on this site are for the purpose of conveying more information and clearly indicate the source. If media or individuals who do not want to be reproduced can contact us, which will be deleted.
Integrated Circuits
Discrete Components
Connectors & Structural Components
Assembly UnitModules & Accessories
Power Supplies & Power Modules
Electronic Materials
Instrumentation & Test Kit
Electrical Tools & Materials
Mechatronics
Processing & Customization
