HOT: Updatenamento 0.96 for Home Assistant

4 minutes of reading

Home Assistant Official Logo

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.96.x.

CAUTION: the changes e breaking changes in this version are more than one. We advise you to read carefully also the special that we have achieved in this regard.


The component "Climate"(Crucial for the definition of platforms of integration for thermostats, air conditioners, thermostatic heads etc.) varies in this new version a series of elements which, consequently, have an impact on all the “daughter” integration platforms of the component and, consequently, of our configurations:

  • operation_mode varies in hvac_mode; this means that the service too climate.set_operation_mode varies accordingly climate.set_hvac_mode;
  • the mode "auto"Of hvac_mode it splits into auto and heat_cool. pointing heat_cool, the user now needs to indicate also which is the thermal range for the two areas ("cool" and "heat“).
  • behavior: the status of the type entities "Climate”Now always corresponds to the mode set with hvac_mode;
  • hvac_action is introduced for integrations that allow the possibility of monitoring the methods:
    • heating;
    • cooling;
    • idle;
  • set_away_mode e set_hold_mode have been collapsed into set_preset_mode, therefore now instead of using turn_away_mode_on() it is used set_preset_mode(“away”).

Variations exquisitely on the development side:

  • from today instead of setting turn_away_mode_on(), it is used set_preset_mode(“away”);
  • la proownership is_on has been removed. If a device is able to shut down, its integration must include the mode HVAC_MODE_OFF;
  • the names of proproperties have been aligned, and all that ended with "_list"Now ends with"_modes";
  • integrations can now only feature functions that can also be displayed via API. It is no longer possible to add profake mode for the away mode.

Pre-Update Tipsnament:

  • replace any calls climate.set_operation_mode in climate.set_hvac_mode in profirst automations, scripts, scenes (and related parameter operaton_mode in hvac_mode);
  • replace any calls climate.set_away_mode e climate.set_hold_mode with climate.set_preset_mode (and its parameter preset_mode in place of away_mode/hold_mode).

All our cards / guides /projets are already updated in relation to these changes.


As anticipated the other day, also the custom component "SmartIR"Has been updated based on changes in the parent component"Climate". If it is not updated in turn, the highernamento 0.96 of Home Assistant interrupts its functionnamento.

To be sure of prosell properly, we recommend the following proprocedure:

  • install HACS;
  • save the eventuals propri custom files related to the IR codes present under “/custom_components/smartir/codes/";
  • delete the folder "smartir"Below"custom_components";
  • in configuration, comment each reference to entities generated with SmartIR;
  • make any changes mentioned above relating to other entities “Climate";
  • install the HA 0.96.xe appurare that everything works (net of entities SmartIR which of course not appariranno);
  • install SmartIR 1.6.x via HACS;
  • restore in configuration the entities to be generated with SmartIR.

From this new version, Home Assistant supports for the profirst frontend a new "compact" display mode of the propria sidebar.

Home Assistant 0.96 sidebar


Presented in recent days, it is reiterated in this upgrade: the Home Assistant cast it is a very juicy new feature which we will give extensive coverage when officially available.


from prossima version - as already mentioned - Home Assistant will no longer be executed in the presence of the 3.5 version of Python: the minimum requirement will be the 3.6. This important change It will NOT affect users HASSIO o HASSIO on Docker, but only on users who have installed Home Assistant How applicativo.

To check the version installed on the proprio Raspberry Pi/ Raspbian, the command is:

python3 --version

If the version was inadequate (everything that is inferior to 3.6 is KO), Python will be updated as soon as possible, certainly before theupdate Home Assistant following the 1 August pv.

The guide for prosee morenamento is available here.

As always, various news and many i bugfix:

and so on, including several bugfixes.

Home Assistant 0.96

> All the details of this release are available here.


Procedura DI UPDATE Windows

The command (to be executed from procommand mpt) is the following:

pip3 install --upgrade homeassistant

In case you are running Python in a virtual environment, the commands are as follows:

cd homeassistant
py -m pip install --upgrade homeassistant

Procedura 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
sudo systemctl start home-assistant@homeassistant

Nb In case of error in the execution of the command:

pip3 install --upgrade homeassistant

prosee to perform - before the above sequence - the following command:

sudo apt-get install build-essential libssl-dev libffi-dev python3-dev
Procedura of UPDATE Mac

Su MAC (via terminal) the command is as follows:

pip3 install --upgrade homeassistant
Procedura of UPDATE HASSIO

Hassio is updated in the usual, simple ways: access the "" menu and, at "DASHBOARD", click on "Update”At the box indicating the availability of updatesnament:

HASSIO update

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 nextnameYou get an integration error with the iOS platform and 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, simply delete the file ".ios.conf”Present in the root of Home Assistant and then restart theHUB.

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.


Stay up to date through ours Telegram channel!