The ZigBee binding supports an interface to a wireless ZigBee home automation network and allows ZigBee devices from numerous manufacturers to be used without a system specific gateway.
A ZigBee Coordinator is the network controller, and is therefore the heart of the ZigBee network. It also acts as the trust centre to control security access to the network.
Coordinators need to be installed manually and the serial port and baud rate must be set. These are set to match the configuration that the dongle is in. Should you wish to use a different baud rate than the default speed of the device, you must change the configuration of the dongle using some other, and then configure the binding to match your change. If in doubt, you should leave the settings at their default values which should work in most cases.
Link Key (zigbee_linkkey)
The key is defined as 16 hexadecimal values. If not defined, this will default to the well known ZigBee HA link key which is required for ZigBee HA 1.2 devices. Do not alter this key if using with a ZigBee HA 1.2 network unless you fully understand the impact.
If defined with the word
INSTALLCODE: before the key, this will create a link key from an install code which may be shorter than 16 bytes.
5A 69 67 42 65 65 41 6C 6C 69 61 6E 63 65 30 39
INSTALLCODE:00 11 22 33 44 55 66 77
Network Key (zigbee_networkkey)
The key is defined as 16 hexadecimal values. If not defined, a random key will be created.
The following coordinators are known to be supported.
|Name and Link||Coordinator||Comment|
|Texas Instruments CC2531EMK||TI2531||Needs extra hardware and correct firmware (might be hard to find) for flashing.|
There are also cheap copies of the CC2531 Stick available on eBay, Aliexpress, etc. like this and a module to flash the firmware like this
Also CC2530, CC2538 or CC2650 may work with the correct firmware but are not suggested
|Bitron Video ZigBee USB Funkstick||Ember|
|Cortet EM358 USB Stick||Ember||Use baud rate 57600 and software flow control.|
|Nortek Security & Control HUSBZB-1||Ember||Stick contains both Z-Wave and ZigBee. Use baud rate 57600 and software flow control.|
|Telegesis ETRX357USB ZigBee® USB Stick||Telegesis|
|QIVICON ZigBee-Funkstick||Telegesis||Only working on Linux devices|
This is the Texas Instruments ZNP stack. The thing type is
TI2531 - Firmware
The TI2531 USB dongle must be flashed with the correct firmware in order to work with this binding.
The file can be downloaded from TI website archives (http://www.ti.com/tool/z-stack-archive) as part
Z-STACK-HOME v.1.2.2a package.
The file name is
CC2531ZNP-Pro-Secure_Standard.hex and its sha256 is
Flashing on Linux
It's possible to flash the dongle using Linux, using
The software has been tested and confirmed working on Ubuntu 16.10 and 17.04.
The required dependencies can be installed with
sudo apt install build-essential libusb-1.0-0-dev libboost-all-dev, and the binary compiled with
./configure && make. Do not forget to install the
udev rules, as described at https://github.com/dashesy/cc-tool/blob/master/README , or the software might not be able to access the USB programmer.
The firmware can be flashed with
./cc-tool -e -w CC2531ZNP-Pro-Secure_Standard.hex -v r. Change the path to the firmware accordingly.
Ember EZSP NCP Coordinator
The Ember EZSP NCP (Network Co-Processor) supports the Silabs EM358 or MightyGecko dongles with the standard NCP firmware. The thing type is
Note that there are generally two versions of the Ember NCP firmware in use. One operates at a baud rate of 115200 with RTS/CTS flow control (i.e. hardware flow control), the other operates at a baud rate of 57600, and XON/XOFF flow control (i.e. software flow control). If you are programming your own stick (e.g. the CEL stick) then it should be advisable to use the hardware flow control version - many commercial sticks seem to use the lower speed and software flow control (e.g. Bitron and Nortek HUSBZB-1).
The thing type is
Digi XBee X-Stick
The thing type is
coordinator_xbee. Other XBee S2C devices should also be supported.
The following devices have been tested with the binding
|Busch-Jaeger 6711 U||Relay Insert|
|Busch-Jaeger 6715 U||LED-Dimmer Insert|
|Busch-Jaeger 6735||Control Element (1-channel)|
|Busch-Jaeger 6735/01||Control Element (1-channel, battery-operated)|
|Busch-Jaeger 6736||Control Element (2-channel)|
|Hue Bulbs||Color LED Bulb|
|Hue Motion Sensor||Motion and Luminance sensor|
|SmartThings Plug||Metered Plug|
|SmartThings Motion Sensor||CentraLite 3325-S Motion and Temperature sensor|
|SmartThings Contact Sensor||Contact and Temperature sensor|
|Tradfri Motion Sensor|
|Ubisys modules||D1 Dimmer, S1/S2 Switch modules|
Note 1: Some bulbs may not work with the Telegesis dongle.
Once the binding is installed, and an adapter is added, it automatically reads all devices that are set up on the ZigBee controller and puts them in the Inbox. When the binding is put into discovery mode via the user interface, the network will have join enabled for 60 seconds.
The binding will store the list of devices that have joined the network locally between restarts to allow them to be found again later. A ZigBee coordinator does not store a list of known devices, so rediscovery of devices following a restart may not be seemless if the dongle is moved to another system.
When a ZigBee device restarts (e.g. a bulb is powered on), it will send an announcement to advise the coordinator that it is on the network and this will allow the binding to rediscover devices that have become lost. Battery devices often have a button that may also perform this function.
ZigBee 3 requires that devices use an install code to securely join the network. This must be added to the binding before the discovery starts. Install codes should be printed on the box the device came in, or possibly on the device itself. Note that there is no standard format for how these codes may be displayed on the device or its packaging. You may need to use a QR reader to read the code - again these are not standard in their format, although you should be able to find the address and install code in the displayed text.
The install code must be entered into the coordinator settings before starting the discovery process.
The format is
IEEE Address:Install Code in the following format -:
ZigBee 3 requires the install code to be 16 bytes long (8 blocks of characters) but some older systems using this method may use less bytes, but it should still be formatted as 2, 4, or 8 groups of 4 values. Note that the last four characters in the install code are the checksum and may be provided separately.
When a thing is deleted, the binding will attempt to remove the device from the network by sending the leave command on the network.
The binding will attempt to automatically detect new devices, giving them a type based on the information they report, and will read their supported clusters to define the supported channels.
Currently all ZigBee things have the same thing type of
A set of channels will be created depending on what clusters and endpoints a device supports. Channels are loosely linked to clusters in that for the majority of channels, a single cluster is used. However, some channels may utilise more than one cluster to provide the required functionality.
The following channels are supported -:
|Channel UID||ZigBee Cluster||Type||Description|
The binding will attempt to configure a connection with the device to receive automatic and instantaneous reports when the device status changes. Should this configuration fail, the binding will resort to using a fast polling (note that "fast" is approximately 30 seconds at this time).
When things don't appear to be working
When things don't appear to be working as expected you should check the logs to try and find what is happening. Debug logging can be enabled with the following Karaf commands -:
log:set debug org.openhab.binding.zigbee log:set debug com.zsmartsystems.zigbee
This will log data into the standard openhab.log file.
Note that logs can only show what is happening at a high level - it can't show all data exchanges between the device and the coordinator - just what the coordinator sends to the binding. For this reason it can be difficult to debug issues where devices are not joining the network, or other low level issues need resolving. In such cases a network sniffer log is required, which requires additional hardware and software.