Integrate ConBee / RaspBee with Home Assistant (HASSIO) via deCONZ

5 minutes of reading
PURPOSES OF THE GUIDE:
  • To integrate un BRIDGE/Gateway ZigBee↔︎TCP/IP ConBee/RaspBee with Home Assistant (distribution HASSIO) through the adoption of its software counterpart deCONZ. This integration makes it possible to integrate components ZigBee of several producers a Home Assistant.
  • Difficulty level: medium low
CONCEPTS FACED:
  • Software use and configuration
SOFTWARE COMPONENTS USED:
Prerequisites:
PHYSICAL DEVICES USED:
GUIDE more indicated for:

All environments

Notes and disclaimer
  • qualsiasi modifica all'impianto elettrico dev'essere effettuata da personale qualificato;
  • any changes implemented in probefore is a propersonal responsibility as well as a profirst risk and danger (this guide is for educational purposes only);
  • any changes implemented in probefore a device will void the warranty.
Driving review: 1.0

Abstract

His majesty ZigBee.

ConBee IIAs sappIAMO the interoperability with desktop between components based on this protocollo but of different typology and different proproducers it is often - indeed, almost always - a proBlema. There are indeed very interesting components but very different lines between them and, not being able to think of buying a BRIDGE/Gateway for each of the lines proonce you have learned, you are often faced with the choice of having to "settle" for a line promade by giving up perhaps other single components that we would be interested in introducing in home automation.

Other proof this situation is often the impossibility of integrating the BRIDGE/Gateway (and therefore the components ZigBee connected to it) with proprio personale HUB, as in the case of that of the line LUMI Aqara - were it not that, fortunately, the (very valid) components of this line are manageable even from the gateway Xiaomi Mijia, who can be integrated with Home Assistant. When of the components ZigBee they are not otherwise controllable if not with "proprio " gateway (maybe not integrable with ours Home Assistant), essentially they become useless, if not in the context of proits ecosystem and its proman app phones.

RaspBeeTo save goat and cabbage exists a great solution, or that of implementing a BRIDGE/Gateway ZigBee↔︎TCP/IP divorced from the logic of the individual proproducers: the answer is given by the synergy of deCONZ (software component) e ConBee / RaspBee (hardware component), a combination that allows to survey the highest number of components ZigBee possible bypassing i proproblems mentioned above. Obviously, this BRIDGE/Gateway "Standard" is pienamecan be integrated with Home Assistant.

In this guide we will see what are the steps to integrate it on Home Assistant in distribution HASSIO. Those who use an installation Home Assistant How applicense (on Raspbian, Windows, macOS or other operating systems) must refer to this other guide.

The guide is divided into three specific phases: antenna installation definition (installation and configuration) of such BRIDGE/Gateway and finally integration of the latter (with its wealth of resources) with Home Assistant.

It starts

Install the antenna

First of all it is necessary install the ConBee / RaspBee antenna correctly.

CONBEE

In the case of ConBee simply insert the key on one of the computer's USB / Raspberry ports and perform a controlled restart (menu item “HASS.io">"SYSTEM">"REBOOT") While with RaspBee it is necessary to make a change to the config.txt file present in the root of the propria Micro SD mounted on the Raspberry.

RASPBEE

The use of RaspBee provides not only physical installation of the module on Raspberry Pi (cold, so first turn off the Raspberry via the menu item "HASS.io">"SYSTEM">"Shutdown"), But also to make a change to the file config.txt present in the root of profirst Micro SD.

Nb this proprocedure it is not mandatory. You can go directly to the next step ("Post-installation verification") and see if RaspBee has been recognized automatically or not. If not, the proprocedure described here must necessarily be carried out.

To make this change to the file config.txt (in case there is not, it must be created) you can follow two ways: mount the Micro SD card on an adapter on a computer appobject, access it and make the change or, alternatively, install theadd-on SSH which allows us to connect from a computer of appOggio, for the same purpose.

The change to be made includes the addition of the following code at the end of the file (take care to add an empty line after the two lines of code):

Su Raspberry Pi 3B and lower:

enable_uart=1
dtoverlay=pi3-disable-bt

Su Raspberry Pi 3B + and above:

enable_uart=1
dtoverlay=pi3-miniuart-bt

After editing, save the file and start (or restart) the Raspberry Pi.

POST-INSTALLATION CHECK

After installing the antenna and starting up Raspberry Pi e HASSIO, access the latter and, under the menu item "HASS.io">"SYSTEM">"HARDWARE”Check if, in the list of installed hardware, appbe it or not the component, usually a voice of this type:

/ Dev / serial / by-id / usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II

In case appat the installation will be considered valid; write down the string to one side.

Nb Sometimes the antenna is simply recognized as / Dev / ttyAMA0 .

Install deCONZ

For start the deCONZ server (which in fact rappwill resent ours BRIDGE/Gateway ZigBee↔︎TCP/IP) is necessary in the field HASSIO, use the very comfortable add-on "DeCONZ" present on the internal Store a Home Assistant. Who was not familiar with the installation of add-on presso HASSIO can refer to this guide.

As mentioned, at the Store HASSIO theadd-on deCONZ:

HASSIO - Installation deCONZ

Once clicked "INSTALL"It will be sufficient to wait for the installation to take place.

Once the latter is over, go to the bottom of the page of theadd-on and identify the box "Config“, In which a JSON payload similar to the following will be found:

{
  "device": "",
  "vnc_password": ""
}

protherefore see to modify it inserting between the apices of the voice "device”The string obtained from the verification of the installation of the antenna mentioned above, for example:

{
  "device": "/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II",
  "vnc_password": ""
}

Click on "Save”And return to the top of the page; finally click on “START"To start" deCONZ ". Startup completed appa new button will appear on the right, or "OPEN WEB UI". Click on it.

Configure deCONZ

Click on "OPEN WEB UI”Provides access to the web interface probefore deCONZ at which to configure the antennas and components ZigBee connected to them. This web app is known as "Phoscon App".

Nb The address that is contacted could be - in case you have configured remote access to HASSIO - the external one, or something like https://indirizzo_personale.duckdns.org:40850. Since the door "40850"It will be closed at the home router, obviously this address will not be reachable and will give an error. It's perfectly normal.

To solve the possible solutions there are two:

  1. open the door on the router (HIGHLY discouraged for security reasons);
  2. point to the IP address of the Raspberry Pi, replacing the FQDN proplaced by the interface HASSIO (Eg. https://192.168.1.100:40850)

Once access to the deCONZ interface is obtained, the latter will perform the search for the antenna / e:

deCONZ - first access

and then ask the creation of a proyour local personal account:

deCONZ - Account creation

Once it is turned on, CONCZ will perform an automatic verification looking for any components ZigBee compatible with proits operating environment; at the end of procedura (and in any case at any later time) will be possible access the menu and, under the three headings "Lights ""Switches "and"Sensors "click on" ADD "to carry out the manual pairing of any components not registered automatically but compatible with deCONZ.

deCONZ - Web operating environment
deCONZ web configuration interface.

Integration Home Assistant

We are pronti to integrate deCONZ with Home Assistant. To do this you can either use automatic discovery or go directly and manually to "deCONZ" under the menu of HASSIO "Settings">"Integrations"

To enable discovery, simply add to the configuration file (maybe using 'sadd-on "Configurator") the following entry (where not already present):

discovery:

Save e restart Home Assistant (menu item "HASS.io">"SYSTEM">"REBOOT“).

At the end of the restart in notifications appa voice will appear which indicates the automatic recognition of new integrations:

Home Assistant - Discovery notification

Follow the link proplace ("Check it out") And, once the form that lists the discovered discoveries is displayed, click onConfigure"Under the heading"Gateway Zigbee deCONZ"

Home Assistant - Integration of CONC

At the end of the proprocedure, Home Assistant will confirm the integration:

Home Assistant - Integration deCONZ OK

From here on under the menu of HASSIO "Settings">"Integrations” appthe entry for BRIDGE/Gateway ZigBee deCONZ:

Home Assistant - Integration of CONZ - ListWhere it will be possible view the details related to BRIDGE/Gateway and resources connected to it (and therefore to the entity arising from it):

Home Assistant - Integration of CONZ - List

As noted in the example image, on the right (last box) are listed the entities deriving from the integration of a sensor ZigBee (in particular a temperature sensor LUMI Aqara), the same integrated sensor as an example at deCONZ.

Use

At this point the entity generated by this integration can be used for ordinary uses at theHUB (consultation via frontend, use in scenes e groups, But also as trigger/condition/action at the proprie automations e script.

For add / remove components ZigBee it will be sufficient to operate at the deCONZ web interface: the effect at Home Assistant it will be immediate starting from the first restart of the latter.


Home Assistant Official LogoATTENZIONE: remember that there is on our FORUM community an ad hoc section dedicated to Home Assistant, for any doubt, question, information on the specific merit of these components.


Please comment below