This repository contains the software needed to bring up a Managed Zigbee Gateway.
In a realistic IoT deployment of ZigBee products there are three key elements that are required for success. The ZigBee end nodes, a gateway and a management service that assists in the development, deployment and monitoring of the health of the devices at scale. In this app note, we describe how a ZigBee developer can demonstrate a complete IoT system with no new development using a simple vertical stack.
The Zentri Device Management Service (DMS) provides a range of services for managing devices, products and product data. In this demonstration a Zigbee gateway will securely connect with the DMS and authorize it for management. Zigbee end nodes that attach to the gateway are reported to the DMS as end nodes belonging to the gateway. Once the DMS becomes aware of the end nodes it will support tracking of those nodes.
To setup a managed Zigbee gateway you will need at least two Silicon Labs WSTK and EFR32MG12P radios that will act as a Zigbee mesh network.
The Zigbee gateway host software is intended to be run on:
- macOS Sierra or later (x86_64)
- Ubuntu 16.04.4 (amd64)
Note: For Windows users it is recommended to use an Ubuntu 16.04.4 (amd64) Virtual Machine under Virtual Box. A preloaded VM image has been provided here. The user name and password for this instance is developer/developer.
Note: Detailed instructions on this setup can be found in AN1144.
Clone this repo:
$ git clone https://github.com/SiliconLabs/managed-zigbee-gateway
$ cd managed-zigbee-gateway
Note: The provided binary images have been generated from the Silicon Labs Gecko SDK 2.2.2 Release and the Zigbee 6.2.3 stack.
Download Simplicity Commander and flash the WSTK/EFR32 devices using the firmware images from this repo. More information on Simplicity Commander can be found in UG162.
Note: When flashing devices, make sure only one WSTK, the one to be programmed, is connected to the computer.
One device will need to be flashed as an network co-processor (NCP) to act as the gateway to the host computer:
$ .</path/to>/commander flash --masserase \
./bin/firmware/ncp-EFR32MG12P432F1024GL125/bootloader-uart-xmodem-combined.s37 \
./bin/firmware/ncp-EFR32MG12P432F1024GL125/ncp-uart-hw.s37
One or more devices will need to be flashed as Zigbee end devices:
$ <path/to>/commander flash --masserase \
./bin/firmware/ZigbeeEndNode-EFR32MG12P432F1024GL125\
/bootloader-storage-internal-combined.s37 \
./bin/firmware/ZigbeeEndNode-EFR32MG12P432F1024GL125/ZigbeeEndNode.s37
Create a user account for the Device Management Service.
Once an account is created, login to the DMS and in the Devices section provision a new software device as type SOFT, then download the certificates.zip and take note of the UUID and Token provided. For example:
UUID fffffffaa24b7ce88d91a6ccf9e54bfb24e904c2
Token RmwxZ0hhSng2NGxlQkdKbWNCSmZlc0VD
This device will be enabled until it authenticates with the DMS.
The certificates.zip needs to be unzipped into a folder named certificates that sits next to the Z3GatewayHost Zigbee gateway executable
$ unzip <path/to>/certificates.zip -d ./bin/gateway/<os>/certificates
Plug in the NCP to the host computer and find the port associated with it. The device will be enumerated as /dev/tty.usbmodemXXXX on macOS and on /dev/ttyACMX on Ubuntu, where X is some numerical digit.
Note: If running in a Virtual Machine, the host computer is the VM itself, so don't forget to connect the WSTK device to the VM using the USB connection options before discovering the tty port.
Note: If running in Ubuntu, the following command must be run before running the gateway:
$ sudo adduser <current user> dialout
Run the Zigbee gateway (Note: If running in Ubuntu, the following command must be prepended by sudu):
$ cd bin/gateway/<platform>
$ ./Z3GatewayHost -p /dev/tty<platform specific postfix>
The gateway application will post some output, and then a Z3GatewayHost> prompt signaling it is ready for interaction.
Form a new Zigbee network:
Z3GatewayHost> network leave
Z3GatewayHost> plugin network-creator start 1
When this succeeds it will post EMBER_NETWORK_UP 0x0000.
Authenticate the gateway with the DMS using the token acquired from the provisioning step:
Z3GatewayHost> custom dms-connect "RmwxZ0hhSng2NGxlQkdKbWNCSmZlc0VD"
If successful, the device should show up as active on the DMS.
Open the network on the gateway to join a device:
Z3GatewayHost> plugin network-creator-security open-network
Power up the WSTK acting as a Zigbee end device and Press PB0 to leave any existing network and attempt to join a new one. When the device joins it will show some information about the join and post Device Joined 0x000B57FFFE491BCD.
Once this is done, close the network for joining (additionally it should close itself after a timeout period).
Z3GatewayHost> plugin network-creator-security close-network
The Zigbee gateway device on the DMS should have a matching entry for this device in the Nodes section.
Login to the DMS and in the Devices section choose the gateway device. Then go to the Files section. Find the following files in the repo, and upload them to the DMS:
<path/to/repo>/bin/firmware/ota-manifest.json
<path/to/repo>/bin/firmware/ZigbeeEndNode-EFR32MG12P432F1024GL125/ZigbeeEndNode2.ota
Once the files are in the DMS, commands can be issued on the gateway to list OTA files available and stage an OTA firmware file for devices to update from:
Z3GatewayHost> custom dms-ota-list
Manifest last updated: 2018-04-30T17:27:52.950Z
Available images:
ZigbeeEndNode2.ota
Z3GatewayHost> custom dms-ota-get "ZigbeeEndNode2.ota"
Downloading OTA image ZigbeeEndNode2.ota
Completed write of "./ota-files/ZigbeeEndNode2.ota" with size 224106
Done with OTA image download
At this point, the ZigbeeEndNode2.ota file will be downloaded to the ./ota-files directory next to the Z3GatewayHost. The end node will eventually pick this up when it queries the gateway as an OTA server for updates.
An update can be forced on the end node using the following command:
ZigbeeEndNode> plugin ota-client start
starting OTA client state machine
Bootload state: Discovering OTA Server
ZigbeeEndNode>Processing message: len=6 profile=0000 cluster=8006
Setting OTA Server to 0x0000
Bootload state: Get OTA Server EUI
OTA Cluster: setting IEEE address of OTA cluster
Last offset downloaded: 0x0003703E
Found fully downloaded file in storage (version 0x00000002).
Found file in storage with different version (0x00000002) than current version (0x00000001)
Last offset downloaded: 0x0003703E
No signature verification support, assuming image is okay.
Starting EBL verification
EBL passed verification.
Custom verification passed: 0x00
Bootload state: Waiting for Upgrade message
Sending Upgrade End request.
Processing message: len=19 profile=0104 cluster=0019
T00000000:RX len 19, ep 01, clus 0x0019 (Over the Air Bootloading) FC 19 seq 00 cmd 07 payload[02 10 00 00 02 0 0 00 00 00 00 00 00 00 00 00 00 ]
OTA Cluster: wait for 0 s
RXed timeOut 0x00000000 s, MAX timeOut 0x00000DBB s
Adding 3000 ms. delay for immediate upgrade.
Countdown to upgrade: 3000 ms
Bootload state: Countdown to Upgrade
Applying upgrade
Executing bootload callback.
To confirm the update occurred, use the following command and verify the Current Version is 0x02:
ZigbeeEndNode> plugin ota-client info
Client image query info
Manuf ID: 0x1002
Image Type ID: 0x0000
Current Version: 0x00000002
Hardware Version: NA
Query Delay ms: 300000
Server Discovery Delay ms: 600000
Download Delay ms: 0
Run Upgrade Delay ms: 600000
Verify Delay ms: 10
Download Error Threshold: 10
Upgrade Wait Threshold: 10
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent