jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-23 01:06:52 +00:00
Code Issues Packages Projects Releases Wiki Activity
home-assistant.io/source/_posts/2019-03-20-release-90.markdown
Paulus Schoutsen 51826a9c32
Update 2019-03-20-release-90.markdown
2019-03-19 09:46:44 -07:00

44 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.90: TBD - Update date TBD 2019-03-13 00:11:03 March 20, 2019 Paulus Schoutsen balloob true Release-Notes /images/blog/2019-03-release-90/components.png

Remote connection available for Home Assistant Cloud! Check out the cloud page in config to get going.

{% linkable_title Streams %}

New stream component to stream cameras smoothly to frontend and other devices like Chromecast. Initial version only supports h264 codec. Each camera integration will need to be updated for it.

Add to config: stream:. Now there is a new camera.play_stream service.

{% linkable_title User Groups %}

User groups! Restrict admin access to users (at least UI wise)

{% linkable_title Smarter SmartThings %}

If you use Home Assistant Cloud, you will now be able to set up SmartThings without exposing your instance to the internet, by leveraging cloudhooks.

{% linkable_title Area love %}

Allow using areas in services instead of specifying entities.

Improved integration setup flow:

{% linkable_title New Platforms %}

{% linkable_title New Features %}

{% 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 %}

  • Netatmo Added support for multiple Netatmo thermostats/valves (@shanbs - #19407) (netatmo docs) (climate.netatmo docs)
  • Netatmo Return Netatmo climate operation_mode instead of boiler status (@shanbs - #21633) (netatmo docs)
  • Utility Meter - Currently the offset configuration parameter is an integer that limits daily cycles to have offsets in days, monthly cycles to have offsets in months, etc. This change increases the flexibility of offset by making it a more flexible time period that can be described in a combination of hours, days, months, etc. This makes it possible for a yearly cycle to start at a given day of a given month. Please see the updated documentation for further details. (@dgomes - #20926) (utility_meter docs)
  • KNX - An update for xknx to version 0.10.0 requires users to update their configuration by changing target_temperature_address to target_temperature_state_address. Other fixes and features:
    • Connection config can now be configured in xknx.yml.
    • Introduce a configurable rate limit which limits the number of KNX telegrams sent to the bus per second.
    • Users who configured their lights via xknx.yml no longer need to manually set min_kelvin and max_kelvin (fixes #21251) (@marvin-w - #21541) (knx docs)
  • http.api_password - Deprecated - Users who are still using api_password for authentication will need to move it under auth_providers. Please see the updated documentation for further details. Those who don't make this change will see an INFO level reminder in the Home Assistant logs until the fix is made for a time, but please note, api_password authentication will eventually be removed completely and we advise users to change to use one of the other authentication methods. (@awarecan - #21884) (api docs) (frontend docs) (hassio docs) (http docs) (mqtt docs) (websocket_api docs) (zeroconf docs) (camera.proxy docs)
  • Nanoleaf - The Nanoleaf component now supports both nanoleaf lights, Aurora and Canvas. As a result of this change the user needs to change the platform from nanoleaf_aurora to nanoleaf (@Oro - #21913) (light.nanoleaf docs)
  • FireTV- is now androidtv. Instead of having near-duplicate integrations for androidtv and firetv, the decision was made to combine them into one. Users will need to change - platform: firetv to - platform: androidtv in their configuration. (@JeffLIrion - #21944)
  • Tellstick - Some configuration cleanup. The way Tellsick sensor configuration was set up using dynamic values for named sensors will not be supported in future versions of Home Assistant. Users that have configured the optional named sensors initiated with only_named will have to update their configuration. Make sure to check the updated documentation for further details. (@endor-force - #21402) (tellstick docs)
  • MQTT - Pass Message object to MQTT message callbacks instead of topic, message and qos. Users of custom components please take note, these values are now available on the passed in message object: msg.topic, msg.message, msg.qos. The old method will continue to work for now but will print warnings. (@emontnemery - #21959) (mqtt docs)
  • Default Config - Default config no longer contains the discovery component. That is now part of the initial written configuration.yaml. If you rely on default config and want to use discovery, add discovery: back to your configuration.yaml.

{% linkable_title All changes %}