ConBee II (BRIDGE/Gateway USB Zigbee)

4 minutes of reading
Proconductor: Phoscon
Category: BRIDGE/Gateway ZigBee↔︎TCP/IP
Type: USB dongle
Technology: Wi-Fi / ZigBee
Installation difficulties: Bassa
Ease of use: Bassa
Availability: Amazon
Review review: 1.3

ConBee II

The "ConBee II"Of the Dresden Elektronik (revised model of the first, the"ConBee") Is small and cheap USB dongle which allows Raspberry Pi (or any traditional computer) to implement radio transmission / reception via proProtocol ZigBee. As you know, different promanufacturers have opted this procommunication protocol as standard of the profirst home automation solutions: is the case of the note line products Philips HUE, Xiaomi Aqara, Ikea TRÅDFRI and many others.

"ConBee II”It is particularly useful to solve a specific one proproblem: mounted on a computer and used in conjunction with a personale HUB (Home Assistant, Homebridge etc.), this module allows you to check different devices, of different proproducers, who use different declinations of the proProtocol ZigBee.

This module is assembled in a few seconds via USB on the computer, after which it is managed by its software - calling counterpart deCONZ - which exposes communication APIs useful to the most common HUB personal to dialogue with it, then with the antenna, then with the components ZigBee connected. ConBee II is a component low consumption procast for coverage up to 500 meters (net of any obstacles), and is compatible with any computer equipped with a standard USB port.

In fact, the ConBee + deCONZ duo makes a real e proprio BRIDGE/Gateway ZigBee↔︎TCP/IP software.


This version "ConBee II"Compared to the" ConBee ", it differs in:

  • revised design;
  • new micro-controller 32-bit ARM-Cortex-M0 instead of the 8-bit AVR;
  • il proserial tocol is at 100% backward compatible, rendering prooperating jets like Mozilla IoT and zigpy-deconz no changes needed;
  • Update Searchnamefaster firmware;
  • new bootloader and GCFFlasher, which now only use the proserial tocol and then do not need root access;
  • more powerful radio signal up to 200mt outside and 30 inside (much more powerful than CC2531, which have low coverage);
  • watchdog always operational for greater network consistency ZigBee;
  • up to a maximum of 200 devices ZigBee connected.

In particular

"ConBee"Makes available il proProtocol ZigBee to the operating environment of the computer that mounts it, thus transforming it (through the adoption of the software deCONZ) in a BRIDGE/Gateway ZigBee↔︎TCP/IP to all effects. This means that if you have home automation components based on ZigBee (which typically need, in order to be controlled, a "collector", a BRIDGE appunto) it will be possible check them directly - through HUB personal - without the need to implement the BRIDGE/Gateway solitamente proplace in havenamento.

As anticipated, the adoption of 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.

The adoption of this type of component essentially allows to avoid the hateful vendor lock-in indirectly given by the adoption a BRIDGE/Gateway different for each line prodotti, among other things not always integrable with our loved ones HUB personal.

ConBee II Schema

A ConBee it is usually preferred (by owners) Raspberry PI) the brother RaspBee due to the fact that the latter can be mounted directly on the board of the Raspberry Pi, while ConBee is a USB dongle; moreover, RaspBee costs about ten euros less. On the other hand, it is a purchase - that of RaspBee - which guarantees its use alone with Raspberry Pi, so it is less advantageous with a view to future reusability, unlike ConBee, which can in practice be mounted on any type of computer and mini computer.

ConBee II has a direct rival, the CC2531 USB dongle, which is preferred as it is cheaper. In contrast, CC2531 is a promuch more elementary, less powerful in terms of radio coverage and, above all, certainly more complicated to integrate. Moreover, if we add up the total cost of the components necessary for its necessary re-evaluationproinitial budget, then the disbursement is closer to the one required for the purchase of ConBee II.

Domotics integrability

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 web interface of deCONZ 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, you need 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 ConBee 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.

Manual

The user manual is available here.

Compatibility

The complete list (and continuously updatednamento) of the devices ZigBee compatible with deCONZ + ConBee is available here.

Availability and cost

ConBee II - Buy on Amazon


Please comment below