Whatever it is the installation chosen for the proprio Home Assistant (one of the best known HUB for personal domotics), at the first start such personale HUB will basically be empty.
At most, if you have home automation components already configured on profirst network, it is possible that Home Assistant recognize them automatically and present the integration interfaces directly at the frontend interface.
It's normal: since the domotic entities present depend on the configuration, at the first start Home Assistant will present an elementary configuration file, which prepares:
- the "name" of the domotic environment;
- the geographical position;
- elevation above sea level;
- the unit of measurement in use;
- the time zone;
- a series of meteorological sensors;
- the inclusion of sidecar files;
- the text-to-speech on the Google platform.
The key that opens the "configuration.yaml" file is roughly this:
homeassistant: # Name of the location where Home Assistant is running name: Home # Location required to calculate the time the sun rises and sets latitude: 41.8904 longitude: 12.5124 # Impacts weather/sunrise data (altitude above sea level in meters) elevation: 0 # metric for Metric, imperial for Imperial unit_system: metric # Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones time_zone: Europe/Rome # Customization file customize: !include customize.yaml
The element "homeassistant:"Opens the block, which contains the basic information - inextricable - of the proprio Home Assistant.
Which, in detail, are:
|name||Contains the name of the environment Home Assistant. It is advisable to leave "home“, Since the name that will then be displayed at the frontend can be decided - differently - through Lovelace. In terms of configuration it often refers to "home", so it is convenient to leave this setting as it is (at least for uniformity with the guides found on inDomus as well as throughout the Internet).|
|Rapplatitude and longitude of the proyour home automation environment. Simply identify it by Google Maps and write down these coordinates to then report them in the configuration. This geographical setting is necessary a Home Assistant to automatically determine sunrise and sunset (for use, for example, in automations).|
|elevation||It indicates the elevation of the domotic environment compared to sea level by an integer value.|
|unit_system||The measurement system. Obviously we Europeans set "metric"|
|time_zone||The time zone. For Italy, set “Europe/Rome"|
|customize||The relative default setting to the sidecar file containing customizations related to the entities as defined above Home Assistant, or "customize.yaml"|
# Configure a default setup of Home Assistant (frontend, api, etc) default_config: # Show the introduction message on startup. introduction: # Uncomment this if you are using SSL/TLS, running in Docker container, etc. # http: # base_url: example.duckdns.org:8123 # Sensors sensor: # Weather prediction - platform: yr # Text to speech tts: - platform: google group: !include groups.yaml automation: !include automations.yaml script: !include scripts.yaml
It's a voice to leave as it is. It is a meta-component which, if present (and which should be present) in configuration, at start up Home Assistant upload the following components:
It is used to indicate a welcome message when accessing the frontend.
This block is certainly important for any administrator Home Assistant: it serves any configuration whatsoever entity of type "Sensor". Any child platform of this component that wants to be included in the configuration must be inserted in this block.
The configuration included by default prepares the integration of the platform "yr", which provides weather forecasts for the geographic coordinates relative to the proinstance Home Assistant (indicated in the block “homeassistant“).
This block is used to define the platforms related to the component "text-to-speech", Which allows Home Assistant... to speak.
At this juncture we do not dwell on the detailed explanation; we will dedicate an ad hoc focus to the issue at the due time.
At the end of the file Home Assistant, by default, adds references to three sidecar file:
The first is used for the grouping of entities (trivially, to create a group "Family" containing the various type entities "Device Tracker"). The second, instead, will contain the automations, while the last, the script.
First things to do
We have dealt with the theme in the extended form "things to do". Nevertheless we recommend:
- configure the geographic coordinates;
- add the field:
in order to allow the automatic discovery (if possible) of any domotic components already present and configured on the profirst network.
- configure DDSN, SSL and remote access (here a guide for installation on Raspbian);
- configure any "areas"
Please note that after each modification of the configuration.yaml file environment restart is required.
Once this is done, it will be necessary begin to integrate the prohome automation components: first of all a list will be drawn up, understanding what is available and then, as the necessary additions will be added to the configuration file, they will begin to model the profirst home automation environment.
|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.|