Software Update: Home Assistant Core 0.107.0

Version 0.107 of Home Assistant Core has been released. Home Assistant Core is an open source home automation platform that runs under Python 3. It runs via Hassbian on a Raspberry Pi 3 or a Linux, macOS or Windows computer. It supports detecting devices, such as Nest thermostats, Philips Hue, Belkin WeMo switches, Mr. Coffee makers, the smart switches from IKEA and the mqtt protocol. In addition, where possible, it can control these devices and apply automation. For more information, please refer to this page and our Forum. The announcement for this release can be found below.

0.107: Multiple Lovelace Dashboards, adds helpers, new media player card

This release brings a crazy amount of awesome new features and beautiful improvements to the frontend.

Bye old State UI

As announced with 0.105, the old States UI is now removed from Home Assistant. If you are using Home Assistant for a year or less, you might not have an idea what it is, since the “new” Lovelace UI has been the default. It’s the UI we used before Lovelace.

If you are up for a flashback, maybe it is worth reading the release notes for Home Assistant 0.7 were the revamped (and now removed) States UI was originally announced. Now exactly 100 releases later, it is time to say goodbye to the states UI that has been with us for a long, long time…

As we announced the deprecation of the old States UI in 0.105, not everybody seemed to be that happy about it. So we surveyed to see what one would miss from States UI and learned that it is mostly used as an overview of all entities (besides having a nice layout that can be made in Lovelace).

In this release, we bring you a Lovelace solution for that and added a bit more…

Hello multiple Lovelace dashboards

You are now able to create multiple Lovelace configurations, called: Lovelace Dashboards!

You can have a dashboard with your main layout, one that is auto-generated (like the old State UI), one for experimenting, one for admins, one for your wall-mounted tablet, etc.

And, yes, you can even mix and match multiple YAML mode managed Lovelace Dashboard, UI managed Lovelace Dashboards and auto-generated Lovelace Dashboards at the same time.

Each dashboard can be added to the menu sidebar as well, with a configurable title and icon. Furthermore, it is possible to limit access to a dashboard to admin users only.

An unlimited amount of dashboards can be created right from the UI in the new Lovelace configuration panel, and YAML dashboards can be set up in configuration.yaml, see the documentation.

This awesome new feature comes with a deprecation if you use Lovelace in manual YAML mode: You need to move the resource section from your ui-lovelace.yaml to the lovelace: section in configuration.yaml. It’s not a breaking change yet; we still load them from the previous location if we didn’t find anything in the lovelace: section, however, this fallback is being removed in a future version.

If you manage your Lovelace via the frontend, we automatically migrate your resources. Please note that resources are not in the raw Lovelace configuration editor anymore, but in the Lovelace configuration panel.

New media player card

@zsarnett is back on the frontend team and is not planning on letting that happen unnoticed. He did a ton of work on the frontend and created a beautiful new media control card for Lovelace.

It is inspired by the media control widget in Android and changes color based on the artwork of the played media. We think it looks absolutely gorgeous!

Helpers Configuration Panel

When you create advanced automations, you often need a helper. Like a toggle, to save a state, or another input field. Until now, you always had to define them in YAML and are known as the input_* fields/integrations.

We now have a UI to add and manage these Helper elements; this allows non-expert users, or anybody that prefers the frontend to manage their system, to also access this functionality.

thanks @Adminiuga, for implementing the backend features that made this frontend change possible! Not only that, if you prefer YAML, these changes made by @Adminiuga also made it possible to reload the input_* YAML configuration without restarting Home Assistant.

Improvements to Lovelace editing experience

@zsarnett changed the looks of our card picker, instead of a simple button to pick a card, you now get a live preview with your own entities. @thomasloven added a UI editor for the horizontal and vertical stack cards and the conditional card.

Other noteworthy changes

• @Misiu added a UI to set the visibility per user for views.
• Data tables, for example, the Entities configuration panel, are now lightning fast! Just on mobile ?.
• The logbook had some speed improvements, thanks @KapJI!
• @bdraco just went all-in on the August integration, making it a top-notch integration! Awesome job there!
• Initial support for HomeKit enabled televisions and support for occupancy sensors was added by @Jc2k.
• @tulindo added support for newer Samsung TV models.
• Alexa now supports starting and canceling timers, thanks to @Tho85.

New Integrations

• Add platform Ezviz (@BaQs – #30378) (ezviz docs) (new integration)
• Add Avri waste collection sensor (@timvancann – #31134) (avri docs) (new integration)
• Add Tankerkoenig integration (@guillempages – #28661) (tankerkoenig docs) (new integration)
• Add QVR Pro integration (@oblogic7 – #31173) (qvr_pro docs) (new integration)
• Add edl21 component for SML-based smart meters (@mtdcr – #27962) (edl21 docs) (new integration)
• Add IamMeter integration(@lewei50 – #30465) (iammeter docs) (new integration)
• Add griddy integration (@bdraco – #32591) (griddy docs) (new integration)

New Platforms

• Add Config flow to august (@bdraco – #32133) (August docs) (new platform)
• Add Dynalite switch platform (@ziv1234 – #32389) (dynalite docs) (new platform)
• Add support for MELCloud Air-to-Water devices (@vilppuvuorinen – #32078) (melcloud docs) (new platform)