AIMS OF THE GUIDE
SOFTWARE COMPONENTS USED:
PHYSICAL DEVICES USED:
GUIDE more indicated for:
Notes and disclaimer
|Driving review: 1.3|
As sappIAMO Home Assistant it's a personale HUB for the profirst equipped home automation of an immense number of components and platforms future integration of the most disparate domotic components, services and so on.
Home Assistant, however, can use also external components, additional, not directly certified by its development team, called "Custom Components". The installation of these components is usually simple: the complicated thing, often, is to keep track of any updatesnameof these components; there are also other additional elements, such as the "Phyton Scripts", rather than the "AppDaemon ”: in short, a parallel world of additional features that, if handled, can create proproblems or at least wasted time.
To solve this problema intervenes HACS, acronym of "Home Assistant Community Store". HACS is itself a custom component which allows to add to the frontend interface a simple and functional additional "control panel" useful to manage (update, delete, configure, remove) the types of additional elements illustrated above, presented as a catalog.
HACS It is very reminiscent of the official distribution store HASSIO di Home Assistant; the interesting thing is that it can be installed both HASSIO that of Home Assistant installed as applicativo (on Raspbian, Windows, Mac etc).
In this guide we will see how to install HACS on the various distribution of Home Assistant.
Adding the "Community" entry created by the presence of HACS is quite simple.
The approThere may be two:
- manual, then with manual copy of the component;
- via terminal commands.
In this case the procedura plans to download from GoHub the .zip file containing the component, unzip it and copy the folder “custom_components”Contained within it containing the folder the configuration file of Home Assistant.
This folder usually corresponds to:
- if installed as applicense on Raspbian, to the folder “/home/homeassistant/.homeassistant";
- su HASSIO, to the folder "/config/"
- su HASSIO@Docker, to the folder “/usr/share/hassio/
Alternatively, to avoid having to copy files in some way, you can use Linux commands (obviously this section is not suitable for users Windows - The proposito! still use Windows? Install HA on Raspberry ...) to download them directly on the system and install them automatically.
Within HASSIO it is necessary to connect via SSH. If the service has not yet been installed, you can do so following this guide.
Once done, connect to the system via SSH and execute the following commands:
cd /config/ mkdir custom_components cd custom_components/ git clone https://github.com/custom-components/hacs.git hacs_temp cd hacs_temp git checkout $(git describe --tags --always $(git rev-list --tags --max-count=1000) | grep -e "[0-9]\+\.[0-9]\+\.[0-9]\+$" | head -n 1) cd ../ cp -r hacs_temp/custom_components/hacs hacs rm -R hacs_temp
At this point, restart with
HOME ASSISTANT on Raspbian
Again, as per HASSIO, but also connects via SSH.
Once connected, execute the following commands:
cd /home/homeassistant/.homeassistant sudo mkdir custom_components cd custom_components/ sudo git clone https://github.com/custom-components/hacs.git hacs_temp sudo chown -R homeassistant:homeassistant ./hacs_temp cd hacs_temp git checkout $(git describe --tags --always $(git rev-list --tags --max-count=1000) | grep -e "[0-9]\+\.[0-9]\+\.[0-9]\+$" | head -n 1) cd ../ cp -r hacs_temp/custom_components/hacs hacs rm -R hacs_temp
finally, reboot (or restart the service, it's the same):
We are halfway there.
To complete it, in fact, it is necessary to add the following entry to the configuration file of Home Assistant:
hacs: token: mio_token
where is it "mio_token”Is a personal access token obtained from GitHub.
To obtain it, go to the section Personal tokens of profirst user panel at GoHub and click on "Generate New Token".
Indicate "HACS" in the field "Notes"And, at the bottom (without clicking any more), click on" Generate Token ".
This prowill harass the profirst access token (eg "ee437a5186726118c799d124e04cecd962c965bb") Which will be indicated in the configuration, for example:
hacs: token: ee437a5186726118c799d124e04cecd962c965bb
Once the configuration is saved, restart Home Assistant.
Although this guide is not designed to illustrate how to use HACS but how to install it, it is still an occasion to mention its functional model.namento.
Once appthe voice burnedCommunity"On the frontend, clicking on it gives access to the community store. To install a new component that supports HACS (as all the main custom components are adapting, for example the 1.3.0 version of Alexa Media Player) just click on "STORE"To consult the list of components already present in the catalog (to install and configure them directly.
By clicking on "SETTINGS“, Instead, it is possible to add additional repositories for any other components that are not yet present in the catalog, so as to add them to the local one and, as above, install and configure them.
The installation of HACS also generates a new entity called "sensor.hacs“, Which shows, in its state, the number of how many update they are waiting to be installed based on the number of custom components installed via HACS. Obviously it is usable as trigger for any automations automatic notification (if they are more than 0, notify me).
More info on HACS are available on his reference site.
|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.|