0.108: Logos, area, sides, Lovelace Entity card, Lovelace, card history
Before we talk about everything, corresponds to the title of this blog post:
in the name of all of the work on the Home-Assistant project, we hope that you, your
Family and loved ones stay safe and healthy during this pandemic.
Our thoughts are with all those affected is still low of the current situation.
Stay strong, keep a distance from each other to wash their hands, and stay safe.
free to play game.
We have it all up to 0.107.7 the previous Version 7! patch releases.
Some have noticed and commented on the fact that we are doing a lot more patch releases
the last few months, what is right. This is not because anything has been delivered
in a defective condition, but we are trying to fix to ship any bug you as soon as
possible! Just so you don’t wait 3 weeks for something to be fixed.
So let’s talk about the elephant in the room: Home Assistant Core 0.108!
<, h2>
Martin Hjelmare & Ashton Lafferty to join Nabu Casa
We want to start with the announcement that Martin Hjelmare
the Nabu Casa!
Martin is a member of the core team for a long time, and first began
a contribution to the project through his work on the
MySensors integration
back in the home Assistant 0.11
(2016)! Most of the contributions to home-wizard, the white Martin, for his endless
the patience of the incredible code reviews he does.
in addition, Ashton Lafferty (cogneato) for work for a few hours
Help Nabu Casa, with things such as support. Most of you probably know him
of what is already, since he is very active in the support of our
Discord server.
We are happy to announce that Ashton is now together with the Nabu Casa full-time, as well!
congratulations, Martin and Ashton! 🎉
<, h2>
Integration of logos & icons
We have a new repository
on GitHub with all the brand’s icons and logos of Home Assistant is able to
integrate. These images are, for example, in our documentation.
In 0.108, we made a start with the contents of this repository in the
Home-Assistant-front-end. The device information page, a layout update, and
the integration page as well.
These pages are now matching the icons and logos-integration.
Page device information shows the hue-logo.
looking for a way to contribute to the Home-Assistant project?
We are still a lot of pictures is missing, So we are
the call for help!
<, h2>
Many of the integrations available now, furnished to the user interface
It is absolutely amazing, all the Upgrade-integrations of this Version!
Many contributors have gone and added support for a lot of integrations
in order to allow them to be configured, via the Home Assistant frontend.
the list is Not all of them ready in time for this publication; however,
amazing also:
the
-
the
- Freebox, made by @Quentame
- Monoprice, made by @OnFreund
- Roku, made by @ctalkington
- Doorbird, made by @bdraco
- Elk-M1 controller, made by @bdraco
- Logitech Harmony, made by @bdraco
- MyQ, made by @bdraco
- Network-UPS-Tools (NUT), made by @bdraco
- NuHeat, made by @bdraco
- Rachio, made by @bdraco
the
the
the
the
the
the
the
the
the
Yes, @bdraco was on fire with this release! Amazing Work!
<, h2>
Lovelace card history
Maybe not very useful during home quarantine, but a very cool feature for when
we must back out of our apartments.
@Hoytron added the ability to the history of the
Persons or devices are trackers on the Lovelace map. You can specify how many hours of history
You want to to show, and there are lines between all the points in this are
time frame.
Screenshot of the map with a history.
<, h2>
New Lovelace-card: Person
@zsarnett was a new Lovelace-card, the entity card. This card looks like the sensor card, but allows the use of all companies (not just sensors).
Illustration of the entity card.
<, h2>
The field configuration page
We have an overview page for your areas. On this page you can see all of the devices in the environment, but also the automations, scenes, and scripts on this area.
Screenshot of the area config page.
<, h2>
Horizontal stack now with different heights is better
When you create a Horizontal stack, the cards in the pile, it is not always line-up
beautiful. This has been adjusted. Horizontal stack to deal better with the
Difference in the heights of the cards on the stack.
Before and after the illustration of the Horizontal Stack improvements.
<, h2>
Other values of changes
call
-
“Alexa, show the front door camera.” 😲
Alexa now has support for the cameras, thanks to @ochlocracy! -
Select your default Lovelace-dashboard has been moved to the user
Profile-Page. -
A lot of configuration pages migrated data from tables, that is, you can
are you looking for in your automations, scenes, scripts, users, and spaces. -
Lovelace cards in the panel views can now be edited with the UI editor.
-
The graphic from the sensor card is now also available as a footer for the
Entities and entity map. -
The Markdown-map has a new
user
– variables that can be used to display the
currently logged-in user. -
create the ZHA Zigbee integration, Zigbee groups are now dynamically
Units for light, switch and fan, which are grouped together. This
allows for almost simultaneous control of a large group of lamps allows
You to turn on or off at the exact same time. Thank you @dmulcahey! -
cameras added via ONVIF integration now also automatically
use the still images provided by the camera, rather than at home Assistant
to generate a. Nice work @roleoroleo! -
WLED have been a few internal upgrades, it has new Wi-Fi
sensors and has now a service to control the impact of its WLED. -
Docker images for Home Assistant are now reduce with Jemalloc, the memory, to
Fragmentation and speed up memory allocation. So, less memory and in General
a faster home-the wizard.
<, 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
-
Lovelace topics, We discovered our theme logic was not wrong, when you specify a theme for a Lovelace map, or view. It is Standard in the backend would be selected subject, even if your local theme differently, or, in their view, a different topic was. To fix this we removed the options
default
andBackend is selected
from the Lovelace topic selection, and if it is not selected the topic, it will not be an issue. This will ensure that the element has the same theme as parent. -
Freebox – Freebox is now as the ” integration of the integrations UI! You need to re-authorize Home Assistant access to the Freebox router. – (@Quentame – #30334) (freebox docs)
-
UniFi – Manual configuration is out of date, as the UI integration now supports all currently available options, and more. Your existing YAML configuration was previously imported, so you can remove it easily. – (@Kane610 – #32699) (unifi-docs)
-
Emulates Hue – The
emulated_hue
andemulated_hue_hidden
attributes as obsolete. Instead of using the existingentities
hidden
– configuration. – (@bdraco – #32718) (emulated_hue docs)the example YAML configuration:
a
emulated_hue: host_ip: 192.168.1.186 listen_port: 8300 advertise_ip: 10.0.0.10 advertise_port: 8080 off_maps_to_on_domains: Script Scene expose_by_default: true exposed_domains: Light People: Light.bedroom_light: name: "night table lamp" Light.ceiling_lights: hidden: true
-
Roku – Roku is now available as an ” integration of the integrations UI! The
roku_scan
service has been removed, in favor of discovery viassdp
. – (@ctalkington – #31988) (roku-docs) -
MQTT – Deprecated features of MQTT platforms are now removed. – (@emontnemery – #32909) (mqtt docs)
the
-
the
- For MQTT light setup with MQTT discovery, it is not possible to specify schema when used with
platform
configuration variable. Instead, the schema must be set by theschema
configuration variable. - For MQTT
alarm_control_panel
MQTTbinary_sensor
and MQTTsensor
is no longer supported by the MQTT discovery: The undocumented implicit setting ofstate_topic
. Instead,state_topic
must be specified explicitly. - support for
json_attributes
removed from MQTT sensor,json_attributes_topic
should be used instead.
the
the
- For MQTT light setup with MQTT discovery, it is not possible to specify schema when used with
-
Harmony harmony is now as the ” integration of the integrations UI! The YAML configuration now needs a host/ip. – (@bdraco – #32919) (harmony docs)
the example YAML configuration:
a
remote: Platform: Harmony name: the bedroom host: 10.168.1.13
-
Sonos – Sonos-attributes of streams have been adjusted for the radio. – (@amelchio – #33063) (sonos-docs)
the
-
the
- Sonos entities plays radio streams used, the merging of the radio name, the artist and the song name in two parameters. You now have the
media_artist
andmedia_title
attributes, the playback of music (if any). - Radio station artwork is no longer available for Sonos persons in the polling-separate mode (i.e., in a network, the network-Home Assistant is on).
the
- Sonos entities plays radio streams used, the merging of the radio name, the artist and the song name in two parameters. You now have the
-
Monoprice – Monoprice is now available as a integration of UI! Please remove the configuration from the YAML and paste the Monoprice integration of the integrations page. – (@OnFreund – #30337) (monoprice docs)
-
Lutron Caseta – As a result of something the
device ID
andZone ID
-attributes from Lutron Caseta devices have been renamed todevice_id
andzone_id
according to the Convention for the rest of the Home-Assistant. cleanup, If you have any automation, the reference of these attributes, you will need to be updated. – (@swails – #33144) (lutron_caseta docs) -
NuHeat – NuHeat is now available as a integration of UI! The existing service has been removed and is now handled by
set_hvac_mode
(air-1.0). – (@bdraco – #32885) (nuheat docs) -
ElkM1 – ElkM1 is now available as a integration of UI! An autoconfigure mode has been introduced that avoids the need to setup complex include and exclude Filter. This functionality is still available, if the configuration of YAML for power-users who want to generate more control over the units elkm1. As the entity-IDs can now be changed, the
alarm_control_panel
attribute ischanged_by_entity_id
is nowchanged_by_keypad
and displays the name of the moose-keyboard instead of the entity ID. – (@bdraco – #33297) (elkm1 docs) -
HmIP – According to the HmIP Cloud maintenance (17.3.2020), it is possible to define labels for each channel a multi. If the labels of a multi-channel device have been changed, in the native Homemamtic IP-Cloud-App, then the names of the entities will change accordingly. – (@SukramJ – #32925) (homematicip_cloud docs)
-
Slack – The Slack-integration got an overhaul, and support for asynchronous and Slack ‘ s Block Kit. As the YAML configuration schema for this integration has changed, please read the documentation. In addition, because it is an unacceptable security risk, remote files (i.e., those not in a Whitelist directory of local home Assistant) will no longer be sent loose on this integration. – (@bachya – #33287) (slack-docs)
the example YAML configuration:
a
notify: Platform: slack api_key: !Secret slack_api_key default_channel: "#home-assistant"
-
network-UPS-Tools (NUT) – The MOTHER, the integration is now available as a integration of UI! (@bdraco – #33457) (parent docs) (breaking change)
The following sensors are no longer supported:
the
-
the
ups.Time
ups.date
ups.model
ups.mfr
ups.mfr.date
ups.serial
ups.vendorid
ups.productid
ups.firmware
ups.firmware.aux
the
the
the
the
the
the
the
the
the
<, h2>
Farewell to the following
the
-
the
- Alarm.com
- Mopar
the
These integrations have been removed. The websites for both have changed to break thus making the integrations, because they relied on web-scraping, this is not allowed (ADR-0004). – (@frenck – #33056 #33066)
<, h2>
All of the changes
Click here to see all the changes!
Published on Wed, 08 Apr 2020 00:00:00 +0000