deCONZ (BRIDGE/Gateway software ZigBee)

4 minutes of reading
Developer: Dresden Elektronik
Availability: at the Git repositoryHub (variable projets)
Category: BRIDGE/Gateway ZigBee↔︎TCP/IP
Type: software
Implementation difficulties: low

deCONZ Logo

"deCONZ”Is the software component useful for defining a BRIDGE/Gateway ZigBee↔︎TCP/IP, which hardware counterparts are the antennas ConBee e Raspbee.

In practice, the combined adoption of "deCONZ" and one (or more) of the antennas mentioned above enables the user to integration, At the profirst personal home automation, components based on standards ZigBee of different brands and lines products.

As sappin fact, we adopt the components based on the excellent home automation standard ZigBee provides also the adoption of BRIDGE/Gateway Zigbee↔︎TCP/IP of the same line products (eg. Gateway Philips HUE to check the components of the same line), except in cases of interoperability (eg the existing possibility to check components ZigBee LUMI Aqara means Gateway Xiaomi Mijia) - as well as the forced use of app furnishings apposite provided by proproducers of gateway. A hateful one vendor lock-in to always avoid, at all costs.

The adoption of deCONZ and its antenna ConBee and / or RaspBee, in association with the use of a proprio personale HUB software (eg. Home Assistant), solves all this: deCONZ acts as a connection between the'personale HUB and the component ZigBee, whatever it may be, thus achieving the goal of full integration. The (very large) list of components compatible with this operating model is available here.

It is also established as some components ZigBee that benefit from the integration through deCONZ manage to provide functionality not natively provided by theapp by the proconductor (eg. the Cube Xiaomi /LUMI manages, through this software, to manage up to 36 additional scenes not provided).

Nb. An alternative to deCONZ (same purposes, different modes) is zigbee2mqtt.

ConBee II
ConBee II, the most commonly used USB dongle with deCONZ.

How it works

deCONZ is a free software that runs in "server" mode, that is it is a proprocess perpetually running, a bit like it happens to our loved ones HUB personal.

deCONZ can be easily installed and run on:

  • Rasberry Pi equipped with Raspbian operating system;
  • Ubuntu;
  • Microsoft WIndows 7 and 10;
  • Apple macOS;
  • HASSIO (As add-on).

Once installed and configured deCONZ on the reference computer (which must obviously also have the antenna ConBee and / or Raspbee physically connected), our home network magically has ainterface to which to connect to be able to survey and manage the components ZigBee of our home automation.

deCONZ essentially "exposes" two elements: a web interface (for configuration, addition and removal of components ZigBee) is an API interface through which ours personal HUBdata can be connected in order to integrate the functionalities of the components ZigBee.

Let's see in which modes the majors personal HUBmanage to integrate deCONZ (and therefore the components ZigBee on it certificates):

HUBModalità di integrazione
Home Assistant
(distribution HASSIO)
Add-on dedicated (deCONZ server) + component of native integration Home Assistant. Simply connect the antenna on the Raspberry Pi, install theadd-on and access the deCONZ web interface to configure the components ZigBee. Finally, it is sufficient to access the "Integrations" section of Home Assistant, add "deCONZ" and finish the configuration. At the end appall will entity rapprepresenting the components mediated via deCONZ.

GUIDE TO INTEGRATION

Home Assistant
(installed as applicativo)
Regardless of where it is running Home Assistant, it is necessary to install deCONZ (the installations vary depending on the type of operating system that will host it) on the same computer or on a computer connected on the same LAN, then access the deCONZ web interface to configure the components ZigBee. Subsequently, it is sufficient to access the "Integrations" section of Home Assistant, add "deCONZ" and finish the configuration pointing it at the instance (local or present on the LAN) of deCONZ just before it started. At the end appall will entity rapprepresenting the components mediated via deCONZ.

GUIDE TO INTEGRATION

openHABRegardless of where it is running openHAB, it is necessary to install deCONZ (the installations vary depending on the type of operating system that will host it) on the same computer or on a computer connected on the same LAN, then access the deCONZ web interface to configure the components ZigBee. Subsequently it is necessary to configure the native binding openHAB towards the instance (local or present on the LAN) of deCONZ just before started. At the end appall will entity rapprepresenting the components mediated via deCONZ.
DomoticzRegardless of where Domoticz is running, it is necessary to install deCONZ (the installations vary depending on the type of operating system that will host it) on the same computer or on a computer connected on the same LAN, then access the deCONZ web interface to configure the components ZigBee. Subsequently it is necessary to configure the deCONZ plugin towards the instance (local or present on the LAN) of deCONZ just before started. At the end appall will entity rapprepresenting the components mediated via deCONZ.
HomebridgeRegardless of where Home is runningbridge, it is necessary to install deCONZ (the installations vary depending on the type of operating system that will host it) on the same computer or on a computer connected on the same LAN, then access the deCONZ web interface to configure the components ZigBee. Subsequently it is necessary to configure the home pluginbridge-platform-deconz and configure appropriatenameHomebridge towards the instance (local or present on the LAN) of deCONZ just before started. At the end appthey will come to theapp Appthe "Houses" all entity rappshowing the components mediated by deCONZ, but with limitations.
HomeyThink of using deCONZ with Homey it wouldn't make any sense: Homey it's a personale HUB hardware equipped with antenna ZigBee and of a whole series of apps to integrate a huge variety of components ZigBee.

Administration

deCONZ empowering to management and administration simplified (step-by-step guided configuration) but also - for more experienced users - to one more advanced and detailed. The software, in fact, through the propria web interface allows the punctual administration of the profirst network ZigBee, going to personalize not only the expected behaviors, but also a sort of autonomous automatism with respect to the HUB personal.

deCONZ interface

In conclusion, it is useful to specify how deCONZ can be "servant of more masters", Since its API interface allows at the same time to more reality HUB (and not only, just think of elements like Node-RED) to manage the components ZigBee attested to it.

Benefits and defects

The adoption of deCONZ has its strengths and weaknesses. Compared to the use of his "rival" zigbee2mqtt, has the disadvantage of being more expensive (the antennas ConBee/RaspBee they are on average more expensive of the antenna - and of the material used for programmarla - used with zigbee2mqtt, or CC2531); on the other hand, deCONZ is extremely easier to use for the average user compared to zigbee2mqtt. Furthermore, the ConBee / RaspBee antennas are profor use, unlike the CC2531 which must be learned to reprogrammate for the purpose.

Another important thing to know is the devices limit ZigBee manageable: in the presence of a single ConBee / RaspBee antenna, the manageable components are up to 200 (against the 25 of CC2531). Always compared to the CC2531 keys, ConBee and RaspBee have a radio range top.


Please comment below