PURPOSES OF THE GUIDE:
SOFTWARE COMPONENTS USED:
PHYSICAL DEVICES USED:
GUIDE more indicated for:
Notes and disclaimer
|Driving review: 1.0|
His majesty ZigBee.
As 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.
More 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.
To 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" it is pienamecan be integrated with Home Assistant and it can be installed on different operating systems (even not on the same computer on which it is running Home Assistant).
In this guide we will see what are the steps to integrate it into Home Assistant (installed as applicensee - users HASSIO must refer to this other guide) by installing and configuring deCONZ at Raspbian (then on Raspberry Pi).
The guide is divided into three macro specific phases: the installation of deCONZ configuration of such BRIDGE/Gateway and finally integration of the latter (with its wealth of resources) with Home Assistant.
First of all it is necessary install the ConBee / RaspBee antenna correctly.
In the case of ConBee simply insert the key on any of the computer's USB / Raspberry ports and turn on or restart the computer.
The use of RaspBee provides not only physical installation of the module on Raspberry Pi (cold, so first prosee to turn off the Raspberry), but also to make a change to the file config.txt present in the root of profirst Micro SD. To do this it is necessary to remove the Micro SD card from the Raspberry Pi and mount it on an adapter, finally connecting it to a computer appOggio.
|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.|
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:
Su Raspberry Pi 3B + and above:
After the modification, save the file, replace the Micro SD card on the Raspberry Pi and turn it back on.
To install deCONZ you need to log in via SSH al proprio Raspberry Pi.
Once connected it is necessary, first of all, to attribute access rights to the USB (command to be performed only in case of use of an antenna ConBee):
sudo gpasswd -a $USER dialout
and then import the public key of proPhoscon producer:
wget -O - http://phoscon.de/apt/deconz.pub.key | \ sudo apt-key add -
Then add the Phoscon repository to the list of those present on the operating system:
sudo sh -c "echo 'deb http://phoscon.de/apt/deconz \ $(lsb_release -cs) main' > \ /etc/apt/sources.list.d/deconz.list"
Finally, perform the next onenamepackages and deCONZ installation:
sudo apt update sudo apt install deconz
At the end of the procedura, deCONZ will have been installed on the Raspbian operating system.
Profinally see to the execution of the service and its configuration in automatic start through the following commands:
sudo systemctl enable deconz sudo systemctl start deconz
Now (and for the future) it is possible to access the web interface of deCONZ (called Phoscon) via browser App). this appWeb location is used for:
- configure the accessories ZigBee connected to deCONZ;
- provide access to deCONZ for integrations (what we will do now);
- configure the gateway in a simple and intuitive way.
After starting the deCONZ service (previous step), theapp is available at:
|Nb Please note:: in case on Raspberry Pi there other services that use the 80 port obviously the address above will not work. To change the door used by Phoscon App you need to run the following command:|
sudo nano /lib/systemd/system/deconz.service
and change the line:
ExecStart=/usr/bin/deCONZ -platform minimal --http-port=80
indicating an alternative door, for example the "40850"(Or a free one anyway):
ExecStart=/usr/bin/deCONZ -platform minimal --http-port=40850
exit by saving (CTRL + X, Y, enter), then execute the following two commands:
sudo systemctl daemon-reload sudo systemctl restart deconz
and finally connect via broweser to the new address:
Once access to the deCONZ interface is obtained, the latter will perform the search for the antenna / e:
and then ask the creation of a proyour local personal account:
Once you have access, deCONZ 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 perform the pairing manual of any components not registered automatically but compatible with deCONZ.
Leave the browser open on this site, because we will need it for integration with Home Assistant.
We are finally pronti to integrate deCONZ with Home Assistant. To do this you can either use automatic discovery or go directly and manually to the "deCONZ" entry under the menu "Settings">"Integrations"
Save e restart Home Assistant.
At the end of the restart in notifications appa voice will appear which indicates the automatic recognition of new integrations:
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"
At this point Home Assistant tells the user to "unlock" the gateway so that it accepts integration from Home Assistant:
To do as requested, go to the Phoscon website App (seen above) at the menu item "Settings">"Gateway"And then, below, icon"Advanced"
Finally click on the "authenticated app"
Appen clicked, come back up Home Assistant and click (within 60 seconds) on the item "Submit” appburned first.
At the end of the proprocedure, Home Assistant will confirm the integration:
From here on in the menu "Settings">"Integrations” appthe entry for BRIDGE/Gateway ZigBee deCONZ:
Where it will be possible view the details related to BRIDGE/Gateway and resources connected to it (and therefore to the entity arising from it):
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.
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 web interface (Phoscon App) of deCONZ: the effect at Home Assistant it will be immediate starting from the first restart of the latter.
deCONZ, implemented as explained in this guide, is an operational environment particularly easy to use. Despite this, the installation not only allows integration with Home Assistant (and other HUB), but also to the detailed configuration of the network components ZigBee thus defined, starting from the antenna (s) ConBee / RaspBee and, subsequently, all the connected components.
To do this it is necessary access to GUI deCONZ, which is available from the VNC desktop environment offered by Raspberry Pi, Raspbian. This desktop environment can:
- be present and in execution;
- be present but not running;
- not be present.
To check which condition you are in, you need to perform the following command:
Once opened the graphic menu, go to the item "Interfacing options">"VNC”And answer yes to the service activation request. If it had already been active, nothing will change; in case it is not, it will be activated. If the service is not available, answer yes to the automatic service installation request.
At this point, set aside SSH and connect via VNC al proprio Raspberry Pi.
Once connected, adjust the best screen resolution (from the Raspberry menu, click on the raspberry icon, then “Preferences">"Raspberry Pi Configuration">"Set resolution") And then access the desired deCONZ management environment by clicking on the lamppost-shaped icon, then"Programming">"Deconz". The management interface appwill appear after a few moments:
Once the antenna is chosen, the user will be taken to the main interface, which allows, as anticipated, a punctual configuration of the device ZigBee was originally the pronetwork, as well as the topography of the network:
|ATTENZIONE: 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.|