0.90
New Features
- Camera Stream Component Huge feature in this release is the ability to stream cameras to the Home Assistant front-end, as well as other devices.Jason Hunter, who has done an amazing job will be joining us in the next episode to help us break down this feature. https://github.com/home-assistant/home-assistant/pull/21473
- Areas can now be targeted in service calls Want to turn all the lights in a room off? Now you can! https://github.com/home-assistant/home-assistant/pull/21472
- Time of Flight Sensor Spoiler alert: Doesn’t tell you the time of a flight! Adds a sensor to Home Assistant, allowing you to use an invisible laser to measure distance with millimeter resolution. https://github.com/home-assistant/home-assistant/pull/21230
Other Noteworthy Updates
- Direct binding for remotes and lights for ZHA If you’re managing your Zigbee network directly from Home Assistant, you’ll now be able to define direct binding between remotes and lights. This allows you to set remotes like a Philips Hue wireless dimmer switch to directly control a Zigbee light, even if Home Assistant is offline. https://github.com/home-assistant/home-assistant/pull/21498
- Support for multiple Playstation 4 devices https://github.com/home-assistant/home-assistant/pull/21302
- RainMachine irrigation controllers can now be paused and unpaused https://github.com/home-assistant/home-assistant/pull/21548
Breaking Changes
- Http.api_password has been deprecated If you manually configure auth providers and want to use legacy_api_password auth provider, you need to configure the API password there instead of under the http section in your config. If you just put it under http, know that it deprecated and you will need to move to the auth provider if you still want to use api_password as authentication in the future.Jason Hu (Awarecan) noticed that most people still using API password was because of the manual skill. He updated the documentation to show how you can actually use the Home Assistant auth to authenticate. https://github.com/home-assistant/home-assistant/pull/21884
- Support for multiple Netatmo thermostats and valves Configuration for the Netatmo platform has been changed to support multiple devices, and multiple homes as well. If you’re using this component, you’ll need to update your config. https://github.com/home-assistant/home-assistant/pull/19407
- Netatmo climate operation_mode instead of boiler status current_operation will no longer return the the boiler status, but the operation_mode, making this component more standard with Home Assistant climate platforms. https://github.com/home-assistant/home-assistant/pull/21633
- Nanoleaf_aurora has been renamed to nanoleaf You’ll need to update your config to use the correct platform name https://github.com/home-assistant/home-assistant/pull/21913
- Firetv has been renamed to androidtv The firetv integration has been renamed to androidtv. Users will need to change – platform: firetv to – platform: androidtv in their configuration.This is necessary to avoid having near-duplicate integrations for androidtv and firetv. It makes more sense to call the combined integration androidtv, hence the renaming. https://github.com/home-assistant/home-assistant/pull/21944
Home Assistant Remote Access
- From Home Assistant 0.90, Home Assistant Cloud subscribers will have the ability to remotely access their local Home Assistant installation via a Nabu Casa URL.
- Using Home Assistant cloud remote access, connections to your local Home Assistant installation are secured using SSL out-of-the-box. No more fiddling with Let’s Encrypt and opening special ports.
User Permissions
- Starting with Home Assistant 0.90, their is basic user interface restrictions based on user permissions.
Twitter Questions
Would you please just thank him for me? Thanks for putting so much time into a product that so many use – for free. Thanks for both listening to and putting up with the community. And thanks for developing a system with privacy and local support build into it's core. #thanks
— Bob (@hmmbob) March 12, 2019
Thinking about the future of Home Assistant, if I am correct, 0.99 will be out on July 24 as long as two-week pattern holds on. After 0.99, will there be 0.100 or 1.0 on August 7?
— Grayson Peddie (@GraysonPeddie) March 11, 2019
Thank @balloob for such great software! Also, is the long term vision to move away from editing YAML? If not, some UX improvements like auto checking and error highlighting the YAML would help
— Greg Schwartz (@uxgreg) March 14, 2019
Is there work being done on a new zwave backend?
— Magnus Øverli (@magnuso) March 11, 2019
Home Assistant Android app? ?
— JuanMTech (@JuanMTech) March 11, 2019
At what point will home assistant outgrow the rpi as a platform? Has it already happened?
— Kevin Goff (@Chump) March 12, 2019
Lots of complaints with recent release breaking components which haven't been noted in the release notes. Seems the transition away from yaml config to stored managed config isn't so straight forward. Will the situation get worse before it gets better?
— Jason Glynn (@justjase) March 11, 2019
Any plans to support multiple yaml files for Lovelace? Love to have one for PC, one for wall display and one for phones.
— Pete Stothers (@xbmcnut) March 12, 2019
