home-assistant/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-12-11 02:43:28 -06:00
Code Issues Packages Projects Releases Wiki Activity
home-assistant.io/source/_posts/2019-04-03-release-91.markdown
Paulus Schoutsen e6d313df66 Add ESPHome Cam demo
2019-04-02 15:22:49 -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.91: Streaming, streaming, streaming TBD - UPDATE DATE 2019-03-27 00:11:03 April 3, 2019 Paulus Schoutsen balloob true Release-Notes /images/blog/2019-04-release-91/components.png

Streaming:

  • Recording
  • Google Assistant support, "Hey Google, show the baby room"
  • More supported platforms

Finished the great migration. All built-in platforms are now in their own folder. If you still have platforms in your custom_components/ directory in the old file format, like sensor/my_platform.py, rename it to my_platform/sensor.py. It will not be supported in a future release.

ESPHome Camera support

Trusted users added to trusted networks auth provider. Including auto log in if only one user matching.

If you run hass.io on an Intel NUC and haven't seen it yet, check out the VS Code add-on by Frenck

I'm so excited to release this add-on 😃

Today I give you the Visual Studio Code!! add-on for @home_assistant! 🎉

The full VSCode experience in your HA frontend including the HA VSCode extension preconfigured out of the box!https://t.co/7bQ6JIF8yQ#InternetOfThings #hassio pic.twitter.com/8CwTfKVJvV

— Franck Nijhof (@Frenck) March 26, 2019

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

  • Z-Wave - The usb_path in configuration.yaml now overrides config entry usb_path. This is potentially a breaking change if people have a stale usb_path setting in configuration.yaml that's no longer accurate. This should help reduce the number of people that need to manually edit the storage/core.config_entries file if their usb_path changes. (@cgarwood - #22038) (zwave docs)

  • iOS - Improves the text description of ATTR_BATTERY_STATE_UNPLUGGED from Unplugged to Not Charging as many new iOS devices now use Wireless charging and there is no concept of "Plugging In". This is potentially a breaking change if you have automations making use of "unplugged". (@FattusMannus - #22152) (ios docs)

  • Iliad Italy - Removed - This was removed because it uses webscraping and Iliad is conducting a/b testing on their web pages, making it not stable for use in production. (@eliseomartelli - #22175) (iliad_italy docs)

  • Netgear lte - The previous three components (network, notify, and sensor) now fall under one netgear_lte component. Check the updated documentation for more information. (@amelchio - #22105) (netgear_lte docs)

  • API streams sensor - Removed - This sensor component was designed to count connected front-end clients. However, it depended on the implementation details of other components, and has therefore been broken since 0.80, so it has been removed. The replacement sensor is now the websocket_api sensor, which does basically the same thing apart from the rename. (@Swamp-Ig - #22200) (api_streams docs) (websocket_api docs)

  • Public Transit (GTFS)

    • The state for this sensor component was a countdown in minutes. If the next departure was in a few hours, this number became quite large and a tad harder to rapidly calculate mentally (463 minutes anyone?). The sensor's state output has been changed from minutes to an ISO 8601 UTC timestamp, which allows the UI to interpret the state as needed. (@renemarc - #21053) (gtfs docs)
    • Sensor updates were running many database queries to populate attributes, on top of the bus schedule queries themselves. This is doubled with two sensors. That led to a lot of slowdowns for everything else when using an SD card! Considering that some data never changes (agency, routes...) and that others like departure times are good until invalidated, now we fetch such metadata at first and then only when relevant changes do occur. GTFS sensor attributes are now named using the standard snake_case format. (@renemarc - #20966) (gtfs docs)

  • Yeelight - This is now its own component and has been broken out from the light platform. More Yeelights are being released with more features and this will make if possible to support them. Examples would be adding sensors for a ceiling light, getting the current power mode (daylight/nightlight), or supporting switches to turn moonlight on or off without having to use a service call. Make sure to visit the updated documentation. (@zewelor - #21593) (yeelight docs)

  • Axis - Events supplied from component might differ. Events will not be configurable in the beginning but will instead provide a subset set of events supported per device. This will be configurable in a later stage when config entry options are available. Configuration.yaml support for Axis component will be removed in the future so make sure to remove references to Axis component after upgrade. (@Kane610 - #18543) (axis docs)

  • HTTP - Lower severity level of log messages from http.view (@thomasloven - #21091) (http docs)

  • Dark Sky - Dark Sky provides hourly forecasts for various monitored conditions. This change creates new sensors for each hourly forecasted condition with suffix _<hour>h while adding the suffix _<day>d to the daily forecasted conditions. For example, now a sensor.dark_sky_summary_<day>d and sensor.dark_sky_summary_<hour>h will be created if the forecast and hourly_forecast parameters are populated. (@rtclauss - #21820) (darksky docs)

  • Konnected - This will change the internal unique_id for Konnected switches (i.e. siren, buzzer, generic switch). Users will need to manually remove the orphaned switch entities from the entity registry after updating and re-configure any changes stored in the entity registry (i.e. name and entity_id), as their unique IDs will change. (@heythisisnate - #22389) (konnected docs)

  • Mopar - The mopar sensor platform has been broken up into a base component with sensor, switch, and lock platforms. The sensor.mopar_remote_command service has been removed since the functionality has been folded into the new platforms and the new mopar.sound_horn service. Please view the documentation to see the new setup instructions. (@rohankapoorcom - #21526) (mopar docs)

{% linkable_title All changes %}