0.107: Several Lovelace Dashboards, adds helper, new media-player-map

0.107: Several Lovelace Dashboards, adds helper, new media-player-card

George F. will once said:
the “The future has a way of arriving unannounced.”

Well, George, we disagree:
Announcement of the release of the Home-Assistant Core 0.107!

This Version brings a crazy amount of great new features and beautiful
Improvements to the frontend.

<, h2>
Bye old State UI

As previously announced, 0.105, the old länder UI
now far from home wizard. If you are using a Home Assistant for a year or
less, you may not have a clue what it is, because the “new” Lovelace has UI
the default setting was. It is the user interface that we have used before Lovelace.

If you are looking for a flashback, maybe it’s worth a read
the release notes for the Home-Assistant 0.7
in the revised (and now removed) States that the UI was originally announced.
Now, exactly 100 releases later, it’s time to say goodbye to the States UI,
has been with us for a long, long time…

As we announced, the deletion of the old countries
0.105, not everyone seemed to be happy
about it. So we missed to see what you would miss from the States, the UI and
learned that it is mostly like an overview of all persons (except
a nice layout that can be made in Lovelace).

In this Version, we bring you a Lovelace solution and added a bit more…

<, h2>
Hello, several of Lovelace dashboards

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

(like the old UI State), an experimental, one for the admins,
for your wall-mounted tablet, etc.

And, Yes, you can even YAML mix and match multiple-mode managed
Lovelace Dashboard, the user interface manages Lovelace Dashboards, and automatically generated
Lovelace Dashboards at the same time.

Screenshot of the new Lovelace-the configuration panel.

Each dashboard can be added to the menu bar page, as well as a configurable
Title and icon. In addition, it is possible to have access to a dashboard
the admin user only.

An unlimited number of dashboards can be created directly from the user interface in the new
Lovelace configuration panel, and YAML dashboards can be configured
the configuration.yaml, see the documentation.

This great new feature comes with a disapproval, if you are in Lovelace
Manual YAML-mode: you need to have the resource section
Your ui-lovelace.yaml of lovelace: section in the configuration.yaml.
It will be a fraction does not change; we still load them from the previous Position
if we don’t find the everything section in the lovelace:, but this fallback
will be removed in a future version.

If you have your Lovelace on the front end, we will migrate automatically
Resources. Please note that the resources are not in the raw Lovelace
The configuration editor is no more, but in the Lovelace-the configuration panel.

<, h2>
New media-player-card

@zsarnett is back on the front-end team and is
not going to happen planned unnoticed. He has a lot of work on the
the frontend and created a beautiful new media-control-map for Lovelace.

It is inspired by the media control widget in Android and change the color based
on the image material for the media played. We think it looks absolutely great!

Screenshot of the new Media Control card.

<, h2>
Helper configuration Panel

When you create advanced automations, and you often need a helper. Like a switch,
so you save a state, or any other input field. Until now, you always had to define
In YAML, and are known as the input_* – fields/integrations.

We now have a UI to add and these helpers manage elements; this allows even non-experts
User, or someone who prefers the front-end to manage your system
to access this functionality.

Screenshot-helper-configuration-dialog.

Thank you @Adminiuga for the implementation of the back-end features of this
frontend-change is possible! Not only that, if you prefer YAML, these changes
made by @Adminiuga made it also possible to load the input_*. YAML
Configuration without a reboot of the Home-the wizard.

<, h2>
Improvements Lovelace of experience in editing

@zsarnett to change the look of our map picker, instead of a simple button,
select a card, you now get a live preview with your own entities.
@thomasloven added to the UI-editor for the
horizontal and vertical stacks of cards and the related card.

Screen capture of the new map picker and batch editor.

<, h2>
Other values of changes

call
the

@Misiu added, user interface, the visibility per user for views.

the

data-tables, for example, are the elements of the configuration are lightning fast! On mobile 🚀.

the

log had some speed improvements, thanks to @KapJI!

the

@bdraco just went all-in on the August integration, making it a top-notch integration! Awesome job!

the

added the First support for HomeKit-enabled TV, and support for occupancy sensors, it was from @Jc2k.

the

@tulindo additional support for newer SamsungTV models.

the

Alexa now supports start and cancel the Timer, thanks to @Tho85.

<, h2>
New integrations

<, h2>
New platforms

<, h2>
If you are in need of help…

…do not hesitate and use our own very active forums, or join us for a little chat.

problems introduced in this Version? Please log in our issue tracker. Make sure you fill in all the fields, the Problem template.

<, h2>
Current Changes

Xfinity Gateway (Deprecated) – The Xfinity-Gateway-based integration to include web-scraping, and is out of date, away, Home Assistant Core 0.109. (Cor 0004) – (@frenck – #32017)
groups – groups are NOT removed, but the configuration, options, services, and service options in connection with the (previously deprecated and is now removed) UI-States are now removed in this Version.
This includes:

the
- The view and control – the configuration options for a group.
- The group.set_visibility service call
- The control, visible, view Option to group.set service call
Please backup your configuration and automations do not use this. – (@frenck – #32021) (group, docs)
Input Number – Adds an entity ID to input_number warning. The surrender of an out-of-range value to input_number.set_value will now raise a validation error. Increment/decrement a input_number will no longer cause warnings. – (@balloob – #32012) (input_number docs)
history Graph – The history_graph – integration has been deprecated in Home Assistant 0.105 and is now away. This integration was not for the old member States UI that is available. A Lovelace equivalent is available: The Lovelace history Graph. (@frenck – #32028)
link – The weblink integration is deprecated in 0.105.0 and now removed. This integration not only works with the old “länder” UI that is available. (@frenck – #32024)

With Lovelace, the same can be achieved with:
Environment Canada – This integration was previously by using web scraping for weather alert details. The details attribute was removed to make it compliant. (Cor 0004) – (@michaeldavie – #32077) (environment_canada docs)
units of time – time-units were standardized in all the integrations. – (@spring Stan – #32065)

If you were using a non-standard unit in automation or sensor-please change the following:

the
- µs for microseconds
- ms for milliseconds
- s for seconds
- – min minutes
- h-hours
- d for day
- w-weeks
- m for months
- y-years
HomematicIP Cloud – Moves to the HomematicIP Cloud-services-admin-services. – (@SukramJ – #32107) (homematicip_cloud docs)

The user must have the Cloud administrator role to perform this HomematicIP services:

the
- homematicip_cloud.dump_hap_config
- homematicip_cloud.reset_energy_counter
HomeKit Controller – support for HomeKit-controller-legacy-pairing data folder .homekit is deprecated and in the Home-Assistant Core release 0.109.0 we plan to remove this code. Pairings have not yet been stored this way since Home Assistant is 0.94, so that, when executed, Home-Assistant 0.94 or later on they were migrated their pairings already, to configuration entries. If you are using an older Version and run the upgrade soon, you will not be able to automatically at upgrade time to migrate your existing pair, and have to manually re-Pairing. – (@Jc2k – #32158) (homekit_controller docs)
Automation – The hide_entity – configuration option to an automation was deprecated in Home Assistant 0.105 and is not to be in this Version. It was not for the old member States UI that is available, so this option is obsolete. Please make sure your configuration is not using this option. – (@frenck – #32038) (automation docs)
IQVIA – is the configuration IQVIA by configuration.yaml, monitored_conditions – key has been deprecated and removed 0.114.0. All the sensors are now created by default. (Cor-0003) – (@bachya – #32223) (iqvia docs)

the example YAML configuration:

a
```
iqvia:
zip_code: !Secret iqvia_zip_code
```
GitHub – The Person has changed state, the return of the ‘short SHA commit hash, so automations should be based on latest_commit_sha to be adjusted. – (@Mariusthvdb – #31581) (github, Google docs)
AirVisual – AirVisual is now available to be added through the Integration of UI! If you have the configuration in configuration.yaml – you need to update to the new configuration. In addition, in order to protect the AirVisual cloud-API, scan_interval is no longer configured for this integration. – (@bachya – #32072) (airvisual docs)

for example, YAML-cConfiguration:

a
```
airvisual:
api_key: !Secret airvisual_api_key
```
IFTTT – IFTTT checks received webhook data is a dictionary (for example, ), in order to prevent Home Assistant international break. – (@balloob – #32317) (ifttt docs)
alarm decoder alarm decoder integration now uses Honeywell Immediately mode instead of Overnight for the alarm_arm_night. the Immediately mode is generally thought safer to use for the night-time, because it disables the entry delay, because the visitors expected. – (@ajschmidt8 – #32292) (alarm decoder docs)
Tibber – Updated Tibber library to 0.13.0 and some of the attributes have names that have changed. – (@Danielhi verses – #32369) (tibber docs)

the
- the currentPhase1 -> currentL1
- the currentPhase2 -> currentL2
- the currentPhase3 -> currentL3
REST – Add application/xml to convert XML to JSON automatically MIME-types for the rest of the sensors (@bdraco – #32289) (rest-docs)
certificate expiration – The name configuration option is deprecated and is no longer being used by the integration. Improved default entity & display-name schema provided. Name and entity_id overrides should be handled via the frontend. Configurations, with name marked, broken with the 0.109 release. – (@jjlawren – #32066) (cert_expiry docs)

the example YAML configuration:

a
```
 - sensor:
Platform: cert_expiry
host: google.com
```
Plex Media Player – The “show all controls” option for Plex is deprecated and will be removed in the Home Assistant Core 0.110.0 release. To download also “discovery” and ” legacy config file (in plex.conf) was removed. – (@jjlawren – #32391 #32510) (discovery docs) (plex docs)

the example YAML configuration:

a
```
plex:
media_player:
show_all_controls: True <-- out of date
```
stay – stay in retirement his legacy automations and quick actions on 28 Feb. This change removes support for legacy automations and fast actions, while adding support for CUE automations that show up in the Home-Assistant-switch (same as previous implementation). Whereabouts replacement for quick action is manually triggered CUE automations, the Home Assistant-service location.trigger_automation (previously location.trigger_quick_action). – (@shred86 – #32296) (abode docs)
deCONZ – the events on The Aqara Magic Cube have changed, so you are discriptions accordingly, with the device triggers. If you are automations for the Magic Cube to the device (device) you want to change your automation. If you configured your automations based on events from the developer tools, there is nothing to break. This also fixes the double-tap function on page 2 that don’t work, if you configured it in the page device (device) – (@Dorzel107 – #32108) (deconz-docs)
Emoncms – set type of unit_of_measurement, has changed, so you use the option for this in the source feed in Emocms. – (@borpin – #32042) (emoncms docs)

The device will now be assigned as follows:
1. remove the device from the API, if it is available
2. Otherwise, remove the device from the configuration, the given either or the default unit (W)
Vizio SmartCast TV – Adds the app support. For TVs that support apps, ‘SMARTCAST’ and ‘CAST’ sources have been replaced with SmartCast Home. All of the automations, support the need to be on the updated sources. – (@raman325 – #32432)
Onvif – added onvif PTZ-move modes. The onvif-camera-service camera.onvif_ptz has been displaced from the camera domain to the onvif domain. the onvif_ptz service has also been renamed to ptz, to the service calls will need to be updated, the onvif.ptz. – (@olijouve – #30152) (onvif-docs)

the example YAML configuration:

a
```
- type: entity-key
Unit: the camera.foscam
Symbol: mdi:arrow-left-bold-outline
show_name: false
tap_action:
Action: call service
service: onvif.ptz
service_data:
entity_id: camera.foscam
pan: LEFT
tilt:
zoom:
move_mode: continuous move
continuous_duration: 0.8
Distance: 1
```
Facebook Messenger – On October 29, 2019 Facebook announced a breaking change, the work of all the broadcast API will stop at 4. March 2020, so that BROADCAST as the destination option is now removed. – (@chmielowiec – #32517) (facebook docs)
Samsung Smart TV – Adds support for newer SamsungTV models. The specification of the port in the configuration.yaml is no longer needed, and thus the port-config-option is obsolete. – (@tulindo – #31537) (samsungtv docs)
Netatmo – The unreliable binary sensors are removed, since they are not of much value, because of their polling nature. Trigger automations, it is recommended that the event netatmo_event. – (@cgtobi – #32673) (netatmo docs)

for example, a trigger for automations:

a
```
 - trigger:
- event_data:
Type: Movement
event_type: netatmo_event
Platform: event
```
DirecTV – DirecTV is now to be added, from the integration UI. The concept of the device has been removed and now the DirecTV receiver, and all the client devices are added. It is no longer a port option as the default connection should work without problems. The name can by means of entity-UI rather than name option. – (@ctalkington – #32162) (directv docs) (directv docs)
iCloud – iCloud-family-units are no longer added automatically. You use the with_family configuration option, or re-add the integration via the frontend, want to do in the case of the use of the iCloud family of devices. – (@Quentame – #32644) (icloud, Google docs)
device Tracker – The hide_if_away – configuration of the parameters for all devices-Tracker. This option was not used, in order to hide devices Tracker from the user interface, if the device was at home. This applies to the old member States UI, which has now been removed. – (@frenck – #32705) (device_tracker docs) (breaking change) (beta Update)
Sonos – Sonos devices is now obliged to report idle instead of , if you do not have all of the current artists-meta-data. This can happen when you play playing Spotify on Sonos and the use of the Spotify app on another device. – (@balloob – #32712) (sonos-docs) (breaking change) (beta Update)

<, h2>
Beta Updates

<, h2>
Release 0.107.1 – 18. March

<, h2>
All of the changes

Released on Thu, 18 Mar 2020 00:00:00 +0000

Leave a Comment Cancel reply