Post Considerations update 0.96.x of Home Assistant

2 minutes of reading

If not all the donuts come out of the hole, the greater onenamento 0.96.x di Home Assistant is one of these. It is indeed undeniable as this revision of the popular personale HUB open source has brought with it a series of prodirect and indirect problems.

Yes indeed they are line up some planets:

  • the exit of Raspberry Pi 4B model;
  • the release of the new Raspian operating system Buster;
  • the important changes to the component "Climate” di Home Assistant, father of all the integration platforms for climate components (thermostats, air conditioners, etc.);
  • the imminent abandonment of Python 3.5 support by Home Assistant.

The first, big one proproblem encountered by many is linked to changes applook at some services and paradigms linked to the component "Climate"Of Home Assistant. This has meant that practically all climate systems integration platforms have been updated (or are being updated)namento), forcing users to vary (even minimally) the configurations relating to profirst automations / scripts (see detailed article). Some platforms have even proved to be malfunctioning, but i proproblems to this proare slowly re-entering (prothe minor came out yesterday update 0.963).

Secondly, the installations of Home Assistant on Raspbian Stretch (users HASSIO/HASSIO@Docker they are not in fact impacted) have encountered a fairly annoying error:

ImportError: /usr/lib/arm-linux-gnueabihf/ version `OPENSSL_1_1_1' not found (required by /srv/homeassistant/lib/python3.7/site-packages/cryptography/hazmat/bindings/

which is caused by an incompatibility of PiWheel with the versions present on Raspbian Stretch (and Jessie). Result: all SSL-based integrations (how many? The 95%?) Have stopped working.

An example of this? SmartIR, the popular custom component to generate virtual climate entities useful for controlling traditional air conditioners using infrared rays, va ko.

To solve possible roads they are two: upgrade the operating system to Raspbian Buster or disable the pre-built PiWheel packages on Raspbian Stretch. We obviously recommend la before road, if only because in doing so you also get the indirect result of update Python to a newer version - what anyway necessary to guarantee a Home Assistant to continue to operate from the prossima 0.95 version (Python 3.5 support will be abandoned). Anyone wishing to simply disable PiWheel and update Python while maintaining Raspbian Stretch can understand how here e here.

HASSIO-Docker-logoEven users HASSIO they had the procross first - or rather, users in becoming in the use of this distribution. Users that already use HASSIO they can in fact sleep between two pillows.

The advent of the new version of the Raspbian Buster operating system has indeed caused proproblems for those who opt for the installation of HASSIO on Docker, which is perhaps the favorite among the installation possibilities. To install HASSIO on Docker in turn installed on Raspbian It is a must: allows you to take full advantage of the convenience of distribution HASSIO while maintaining the flexibility of the Raspbian operating system.

Unfortunately the installation script commonly used for the installation seems - at the time of writing - to malfunction: on the weekend we found a solution and so we updated the installation guide dedicated to this methodology.

As always, in case of proproblems we gather on forum and we talk about it together.

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.

inDomus telegram channel