The development team di Home Assistant has released a new, important updatenamento for the known HUB free software for the personal home automation, which leads to the version 0.101.x. In this new one release there are many innovations. Not profirst one release "Monstre", this: not many, in fact, the news.
We remind everyone, regardless, the importance of performing ALWAYS these updatesnameNTI.
Python
Deprecated use of the 3.6 version of Python: those who still adopt this version prothey see, in time, to upgrade to a higher version: dai proupdatenameNTI Home Assistant those who still use the 3.6 will no longer be able to run theHUB. Obviously this variation only concerns those who use Home Assistant installed as applicensee: users HASSIOtherefore, they are not involved.
API Password
From this version it is no longer possible to use the password API to authenticate by passing it via URL.
Although the authentication support via API password has been maintained (moved under the block “auth_providers:"As" Legacy API Password ", this password can no longer be used as direct URL authentication. It goes without saying that certain implementations that use this type of direct authentication with 0.101.x stop working (eg Alexa's Flash Briefing, at least as far as we have implemented it in our guide). The guides present on inDomus who suffer from this proproblem will be updated soon.
From today onwards this type of authentication is abandoned in place of the now known "Long Live Token"Or del"webhook"
Hassbian
In Week a post has been released which illustrates the reasons for abandoning the distribution Hassbian. This means that the installation methods of Home Assistant from today it will be only two: HASSIO (smooth o on docker) is Home Assistant manually installed How applicensee in a virtual environment. The distribution Hassbian (which in the end was the second one mentioned above, but already done on behalf of the user) will no longer be updated.
Frontend
Lovelace UI it has been further updated - as in any new one release - with news and corrections.
Among the many things, the style and usability of the entity customization panel has been revised:
Breaking changes
A list of changes that could possibly cause proproblems.
- The Ecobee platform for the integration of climate systems of this brand earns the service "turn_on";
- the entities rappsensors from the IKEA Trådfri platform they gain the "battery" entity - and lose it as an attribute;
- volume management fixed of entities generated with Onkyo integration;
- removed the possibility of authenticating to Home Assistant through trusted networks using the password API as a parameter
e more.
Other
As always, news and several i bugfix:
- added the integration platform UniFi Controller;
- support for integration expanded Neato;
- added the integration platform Airly;
- added the integration platform Microsoft Teams;
- various corrections for deCONZ;
- beta fix for Microsoft TTS
e more, including several bugfixes and beta bugfixes.
> All the details of this release are available here.
UPDATE
Procedura DI UPDATE Windows
The command (to be executed from procommand mpt) is the following:
pip3 install --upgrade homeassistantIn case you are running Python in a virtual environment, the commands are as follows:
cd homeassistant
Scripts\activate.bat
py -m pip install --upgrade homeassistantProcedura DI UPDATE Linux / Raspberry
The commands for theupdate I'm:
sudo systemctl stop home-assistant@homeassistant
sudo -u homeassistant -H -s
source /srv/homeassistant/bin/activate
pip3 install --upgrade homeassistant
exit
sudo systemctl start home-assistant@homeassistant
Nb In case of error in the execution of the command:
pip3 install --upgrade homeassistantprosee to perform - before the above sequence - the following command:
sudo apt-get install build-essential libssl-dev libffi-dev python3-devProcedura of UPDATE Mac
Su MAC (via terminal) the command is as follows:
pip3 install --upgrade homeassistantProcedura of UPDATE HASSIO
Hassio is updated in the usual, simple ways: access the "Hassi.io" menu and, at "DASHBOARD", click on "Update”At the box indicating the availability of updatesnament:
First, however, we recommend using “Check Home Assistant configuration"To check - in advance - that the configuration in use is correct compared to the new version of Home Assistant.
In case after the nextnameThis results in an integration error with the iOS platform and / or an error similar to the following:
hass[1113]: 2019-05-16 00:00:00 ERROR (Thread-20) [homeassistant.util.json] Could not parse JSON content: /home/homeassistant/.homeassistant/.ios.conf
to solve it is sufficient to stop theHUB, delete the file ".ios.conf”Present in the root of Home Assistant and finally restart theHUB.
 | 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. |
