home-assistant/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-12-10 14:46:47 -06:00
Code Issues Packages Projects Releases Wiki Activity
home-assistant.io/source/_posts/2019-06-05-release-94.markdown
Paulus Schoutsen bd1fcf5e1b Add video
2019-06-04 08:45:36 -07:00

42 KiB
Raw Blame History

layout, title, description, date, date_formatted, author, author_twitter, comments, categories, og_image
layout title description date date_formatted author author_twitter comments categories og_image
post 0.94: TBD - update date TO DO. 2019-05-29 04:11:03 June 5, 2019 Paulus Schoutsen balloob true Release-Notes /images/blog/2019-06-release-94/google-ui.png

It is time for the 0.94 release and there is some seriously good stuff in this release. We're working hard on polishing everything and getting ready for the big Home Assistant 1.0 release. And we're getting closer. So close actually, that this is the first release that can be installed and configured without touching a text editor! Onboard, configure integrations, manage automations and scripts all from the UI.

This milestone has been achieved thanks to the hard work by @emontnemery who contributed the ability to store the core config in storage: name, location, unit system, time zone. We still allow users to store their core configuration in configuration.yaml, which will take precedent when defined. This means that it is a non-breaking change. Core config is now set during onboarding and can be edited in the general page of the config panel.

Another cool new feature is the total revamp of how you manage which entities are exposed to Google Assistant via Home Assistant Cloud. From the cloud UI you can now click "Manage Entities" and you are brought to the Google Assistant entity manager. From here you can enable which entities are exposed and, if you deem appropriate, choose to disable the two factor authentication on your garage door (the asking for a pin).

Screenshot of the new user interface to manage which entities are exposed to Google Assistant. Screenshot of the new user interface to manage which entities are exposed to Google Assistant.

{% linkable_title Discovery %}

Discovery has been mordernized thanks to @Kane610 and with the input from @Jc2k. Each integration is now able to specify how they can be discovered in their manifest, and the new zeroconf and ssdp integrations will do the rest. The new discovery is non-obtrusive: no devices are set up without approval by the user. Instead, you will need to approve each discovered integration. You can find them in the discovered section of the integrations page in the config. Only a handful of integrations have been migrated to the new approach in this release.

The new discovery is now part of the default config. If you are not using the default config, add ssdp: and zeroconf: to your configuration.yaml.

{% linkable_title Deprecating Python 3.5 support %}

This release has deprecated support for the almost 4 year old version 3.5 of Python. The first Home Assistant release after August 1 will drop support. This is part of our newly adopted Python support approach.

This will only impact you if you are running a custom installation of Home Assistant. This will not impact anyone using Hass.io or Docker. If you are using hassbian, you can upgrade Python by following these instructions.

{% linkable_title Modernizing the device tracker %}

This release also introduces a long overdue overhaul of how the device tracker works. We are introducing this overhaul piece by piece, focusing first on device tracker platforms that push their updates to Home Assistant: mobile app, OwnTracks, GeoFency, GPSLogger and Locative.

These integrations will no longer use known_devices.yaml but instead use entities, like all other integrations in Home Assistant. You can change the name and entity ID via the UI. It is no longer posible to merge the devices with other device tracker entities. This was flaky at best. You should now use the new person integration for this.

{% linkable_title Improved hass.io builds %}

We have been working hard on improving Hass.io builds. A build can now be online in as little as 30 minutes after a new release has been tagged. This is thanks to a new wheel-based infrastructure build by @pvizeli with input from @frenck. With Python wheels, we will build all the requirements of integrations ahead of time, and only download them to your hass.io installation when you update your Home Assistant version.

We changed how packages are installed when running Home Assistant inside a Docker container. It will now install the packages into the Python environment inside the container, instead of storing them in the deps folder inside your config folder which lived outside the container.

Note: Because of the new way packages are installed, Home Assistant will take longer to start the first time it is launched after an upgrade. Don't worry and let it finish! We are working on making this process faster in the future.

Note 2: If you are using Hass.io or a dockerized version of Home Assistant, this release will one time clear the deps folder in your config folder.

{% linkable_title New Integrations %}

{% linkable_title New Platforms %}

{% linkable_title If you need help... %}

...don't hesitate to use our very active forums or join us for a little chat. The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.

{% linkable_title Reporting Issues %}

Experiencing issues introduced by this release? Please report them in our issue tracker. Make sure to fill in all fields of the issue template.

{% linkable_title Breaking Changes %}

{% linkable_title Beta Fixes %}

{% linkable_title All changes %}