Blog
2021.2: Z-Wave... JS!
Dear reader,
Usually, I try to write a small introduction that recaps the release, while putting a bit of my view in it as well. This release, however, I’m struggling to find the right words…
So there is DHCP discovery added, which is super nice! And some really helpful new Blueprint selectors, tons of UI tweaks! But honestly…
Have you heard about Z-Wave JS?!
Well, out of nowhere, a huge bunch of developers came together this month and spat out a completely new, full-blown, fast, slick, sexy, complete, Z-Wave integration! 🤯
So, thanks guys! An achievement beyond words, really; You all rock ❤️
Enjoy the release!
../Frenck
- Erik Montnemery joins Nabu Casa
- Python 3.7 dropped, Python 3.9 supported
- Z-Wave JS
- No more badges in auto generated dashboards
- DHCP Discovery
- New Blueprint selectors
- Cloud Text to Speech settings
- Other noteworthy changes
- New Integrations
- New Platforms
- Integrations now available to set up from the UI
- Release 2021.2.1 - February 5
- Release 2021.2.2 - February 9
- Release 2021.2.3 - February 11
- If you need help…
- Backward-incompatible changes
- Farewell to the following
- All changes
Erik Montnemery joins Nabu Casa
Today, we are proud to announce that Erik Montnemery has joined Nabu Casa to work full-time on the Home Assistant project.
Some of you might know Erik better by his GitHub handle: @emontnemery
We are excited to have you aboard Erik! Welcome!
Python 3.7 dropped, Python 3.9 supported
Support for Python 3.7 has been removed, raising the minimum Python version you need to run Home Assistant Core to Python 3.8. Python 3.7 was already deprecated since Home Assistant Core 0.116.0.
This is only a concern if you are running Home Assistant Core directly on Python. If you run Home Assistant OS, Supervised or Container, you don’t have to worry about this, as the Home Assistant project takes care of this for you.
However, say hello to: Python 3.9. As of this release, Python 3.9 is fully supported and tested.
Z-Wave JS
This release brings you the Z-Wave JS integration!
A brand new integration for Z-Wave in Home Assistant, full-blown, created in just a month by a bunch of awesome people!
More and more people were concerned about the future of Z-Wave with
Home Assistant; meanwhile the Z-Wave JS
This new integration is based on the same base principles as the OpenZWave integration: It is decoupled from Home Assistant. Instead of MQTT, the Z-Wave JS integration uses a WebSocket connection to a Z-Wave JS server.
This means, in order to use this new integration, you’ll need to run the Z-Wave JS server that sits in between your Z-Wave USB stick and Home Assistant. There are multiple options available for running the Z-Wave JS server, via Docker or manually, and there is also a Home Assistant add-on available.
If you run an installation with a Supervisor, the add-on will even be set up automatically for you.
Current state of Z-Wave JS
The new Z-Wave JS integration is amazingly complete. It supports the following platforms from the start: Binary Sensors, Climate, Covers, Fans, Lights, Locks, Sensors and Switches. Scenes are also supported!
Besides that, it is just blazing fast! ⚡️
While fast-growing, it is a new integration and there is still a lot
in progress. Of course, no doubt, there will be bugs. Bugs that will
be squashed and handled. Please, be sure to
report issues in our issue tracker
What is left? See our Z-Wave JS integration roadmap
Thanks to all
Thanks to all of the following people, the Z-Wave JS integration was able to see the light in just a month!
- @AlCalzone
- @balloob
- @bramkragten
- @cgarwood
- @firstof9
- @itewk
- @jcam
- @kpine
- @marcelveldt
- @MartinHjelmare
- @Michsior14
- @Petro31
- @pvizeli
- @raman325
- @robertsLando
Yes, that is an awful lot of people! Amazing how this all came together and incredible work!
What about the old Z-Wave integration?
The old zwave
integration has been based on
OpenZWave 1.4, which is really old and does not get any upstream updates
anymore. This also means that it is hard for us to keep it in a working state
for the upcoming future.
Therefore, as of today, the old Z-Wave is marked as being deprecated.
If one is starting with Home Assistant and Z-Wave, the zwave
integration is
no longer recommended. For existing users, we recommend migrating to the
Z-Wave JS integration. However, don’t panic,
zwave
is deprecated but not removed yet. We currently have no plans for
removing it, unless it can no longer be made to be build for the
latest Python
What about the OpenZWave beta integration?
Over a year ago, Home Assistant started working on the OpenZWave integration. Based on OpenZWave 1.6 and the OZW daemon, using MQTT as a transport. This project was promising and something we put a lot of time and effort in.
Unfortunately, the OpenZWave project itself became a bit stale as most of the upstream development is done by a single person: Justin Hammond (Fishwaldo).
Quite a few people were worried about the lesser activity on OpenZWave. Justin has responded on our forum on what is happening in his life and it is sad to read how many people have personally impacted him negatively.
Is OZW Dead - No. I’ll tinker with it, I’ll make changes as time allows, but it will be at my own pace, to scratch my own itches now.
Let us be straight here: OpenZWave is an 11 year-old project, which is used by an incredible amount of systems (besides Home Assistant) in this world, with an even greater track record. So:
Thank you Justin for all you have done in all those years!
The team that was working on the OZW integration have shifted their focus to the new Z-Wave JS integration. We don’t think the OpenZWave integration will make it out of beta. We recommend Home Assistant users migrate to the Z-Wave JS integration.
No more badges in auto generated dashboards
If you are using an auto generated Lovelace dashboard, you probably always had a ton of badges on the top of your dashboard. If there are just a few it works, but as more start to appear, it soon becomes cluttered.
Screenshot of the old badges clutter that is now gone!
We decided to no longer use badges in the auto generated Lovelace dashboards. Instead, every entity is neatly grouped by area or domain in an entities card.
If you liked the badges, you can always take control of your dashboard and add them.
DHCP Discovery
Home Assistant now listens on your network for devices that request a IP address. Based on those intercepted messages, Home Assistant can now discover integrations for you to use with the discovered devices.
This really powerful addition has been made by @bdraco
So as of this release, your Home Assistant might actually find some new
devices it can use! Thanks @bdraco
New Blueprint selectors
For our Blueprint fanatics, some new goodies to the Blueprint has been added
this release. Thanks to @thomasloven
Screenshot of the text selectors.
- An object selector: Shows an YAML editor in the UI.
- An text selector: Show a single line text input or text area for longer messages in the UI.
- Blueprint descriptions now support Markdown.
Screenshot of the object selector, giving a YAML input field.
Cloud text-to-speech settings
Nabu Casa has been offering an amazing text-to-speech service for a while now, yet it was hard to find, and even harder to setup and use.
To fix this, a new settings UI has been added where you can select the default language and gender to use for the text-to-speech service, so you no longer have to attach that to every service call. You can find it in the Home Assistant Cloud panel.
Screenshot of Cloud TTS options.
We also added the ability to try the chosen settings right in your browser. Click the try button, enter some text and click play to hear the text being spoken.
Other noteworthy changes
This release has no big new features, but we do have quite a bit of tweaks that are definitely noteworthy to mention.
- We now give you a clearer reason why your Lovelace card configuration is not
supported in the UI editor thanks to @spacegaier
. - Shelly RGB devices are now fully supported!! Nice @chemelli74
! -
@dmulcahey
Added filtering and zoom to node to the ZHA network visualization. Very useful to find you Zigbee network issues. - The deCONZ integration added support for logging basic event in the logbook.
Nicely done @Kane610
. - The Tasmota integration is out of beta! Awesome @emontnemery
! -
@spacegaier
Added support for themes on the media card. - The items in the shopping list card can be ordered using drag & drop!
Thanks @ShaneQi
! - Newly ignored discovered integrations now show a name of the item ignored. This makes it easier to undo that later.
-
@balloob
made a new framework that can detect significant changes in entities, allowing to reduce the amount of update we need to send to both Google Assistant and Alexa! - Setting up Lutron Caseta was quite a pain, but not anymore! @bdraco
added one-touch pairing to the integration set up! - If you use light profiles,
@Adminiuga
is your man. All parameters of a light profile can now be optional and default profiles are always applied. - Dropdown helpers (
input_select
) got some new service capabilities added by @l-mb. They can now cycle through the options, and service calls to jump to the first or last item have been added as well. - If you have a Foscam camera, @joe248
added a service to move to PTZ presets.
New Integrations
We welcome the following new integrations this release:
-
AirNow, added by @asymworks
-
DHCP Discovery, added by @bdraco
-
Huisbaasje, added by @denniss17
-
Ondilo ICO, added by @JeromeHXP
-
Z-Wave JS, added by @cgarwood
, @MartinHjelmare , @marcelveldt , @raman325 , @firstof9 , @balloob
New Platforms
The following integration got support for a new platform:
-
Logitech Harmony Hub now adds switches for activities,
added by @mkeesey
-
WiLight now supports fans, added by @leofig-rj
-
Hyperion now has all kinds of advanced control switches,
added by @dermotduffy
Integrations now available to set up from the UI
The following integrations are now available via the Home Assistant UI:
-
Somfy MyLink, done by @bdraco
-
Foscam, done by @skgsergio
Release 2021.2.1 - February 5
- Convert ozw climate values to correct units (@Chrisgozd
- #45369 ) (ozw docs) - Add support for iCloud 2FA (@nzapponi
- #45818 ) (icloud docs) - Don’t log missing mpd artwork inappropriately (@mweinelt
- #45908 ) (mpd docs) - Fix entities device_info property in Harmony integration (@bieniu
- #45964 ) (harmony docs) - Fix Local Media in Media Browser (@DeadEnded
- #45987 ) (media_source docs) - Bump zwave-js-server-python to 0.17.1 (@MartinHjelmare
- #45988 ) (zwave_js docs) - Bump awesomeversion from 21.2.0 to 21.2.2 (@ludeeus
- #45993 ) - Do not listen for dhcp packets if the filter cannot be setup (@bdraco
- #46006 ) (dhcp docs) - Bump zwave-js-server-python to 0.17.2 (@MartinHjelmare
- #46010 ) (zwave_js docs) - dhcp does not need promisc mode. Disable it in scapy (@bdraco
- #46018 ) (dhcp docs) - Revert aioshelly (@balloob
- #46038 ) (shelly docs) - Prevent fritzbox callmonitor phonebook_id 0 from being ignored (@obelix05
- #45990 ) (fritzbox_callmonitor docs) - Upgrade holidays to 0.10.5.2 (@fabaff
- #46013 ) (workday docs)
Release 2021.2.2 - February 9
- Fix zwave_js cover control for Up/Down and Open/Close (@natekspencer
- #45965 ) (zwave_js docs) - Fix foscam to work again with non-admin accounts and make RTSP port configurable again (@skgsergio
- #45975 ) (foscam docs) - Fix downloader path validation on subdir (@gadgetchnnel
- #46061 ) (downloader docs) - Fix deprecated method isAlive() (@cdce8p
- #46062 ) (zwave docs) - Improve deCONZ logbook to be more robust in different situations (@Kane610
- #46063 ) (deconz docs) - Fix zwave_js Notification CC sensors and binary sensors (@raman325
- #46072 ) (zwave_js docs) - Fix incorrect current temperature for homekit water heaters (@bdraco
- #46076 ) (homekit docs) - Use async_update_entry rather than updating config_entry.data directly in Axis (@Kane610
- #46078 ) (axis docs) - Handle missing value in all platforms of zwave_js (@marcelveldt
- #46081 ) (zwave_js docs) - update discovery scheme for zwave_js light platform (@marcelveldt
- #46082 ) (zwave_js docs) - Update zwave_js discovery scheme for boolean sensors in the Alarm CC (@marcelveldt
- #46085 ) (zwave_js docs) - Fix Google translate TTS by bumping gTTS from 2.2.1 to 2.2.2 (@hmmbob
- #46110 ) (google_translate docs) - Revert “Convert ozw climate values to correct units (#45369)” (@dshokouhi
- #46163 ) (ozw docs) - Enable KNX auto_reconnect for auto-discovered connections (@farmio
- #46178 ) (knx docs) - Ensure creating an index that already exists is forgiving for postgresql (@bdraco
- #46185 ) (recorder docs) - Fix Tado Power and Link binary sensors (@Noltari
- #46235 ) (tado docs) - Handle empty mylink response at startup (@bdraco
- #46241 ) (somfy_mylink docs)
Release 2021.2.3 - February 11
- Fix SNMP engine memory leak in Brother integration (@bieniu
- #46272 ) (brother docs) - Use oauthv3 for Tesla (@alandtse
- #45766 ) (tesla docs) (breaking-change) - Bump pymyq to 3.0.1 (@ehendrix23
- #46079 ) (myq docs) - Revert transmission to check torrent lists by name rather than object (@JPHutchins
- #46190 ) (transmission docs) - Update powerwall for new authentication requirements (@bdraco
- #46254 ) (powerwall docs) - Fix Lutron Integration Protocol reconnect logic (@bdraco
- #46264 ) (lutron_caseta docs) - Bump roonapi to 0.0.32 (@pavoni
- #46286 ) (roon docs) - Add guards for missing value in binary_sensor platform of zwave_js integration (@marcelveldt
- #46293 ) (zwave_js docs) - Add reauth support for tesla (@bdraco
- #46307 ) (tesla docs) - Add
already_in_progress
string to roku config flow (@bramkragten- #46333 ) (roku docs) - Restore Google/Alexa extra significant change checks (@balloob
- #46335 ) (alexa docs) (google_assistant docs) - Fix Shelly relay device set to light appliance type (@thecode
- #46181 ) (shelly docs)
If you need help…
…don’t hesitate to use our very active forums or join us for a little chat
Experiencing issues introduced by this release? Please report them in our issue tracker
Security Disclosure 2: vulnerabilities in custom integrations HACS, Font Awesome and others
This blog looks pretty much the same as the security disclosure of yesterday. However, it is a new disclosure, affecting a similar issue. We want to make sure the information is complete.
This is a disclosure about security vulnerabilities found in 3rd party custom integrations. Custom integrations are not created and/or maintained by Home Assistant. Users install them at their own risk. We want to inform you about these because the found vulnerabilities impact the security of your Home Assistant instance.
If you do not use custom integrations, your Home Assistant is not vulnerable. If you do use custom integrations, your instance might be vulnerable if you use one of the impacted integrations.
TL;DR:
- Multiple custom integrations were found that allowed an attacker to steal any file without logging in. Previously implemented fixes were not sufficient.
- Upgrade Home Assistant as soon as possible. Home Assistant Core 2021.1.5 added mitigation to prevent the issue from happening.
- Upgrade the custom integrations to a fixed version or remove them from your installation.
- If you have used any of the custom integrations with a known vulnerability, we recommend that you update your credentials.
On the morning of Saturday, January 23 2021, the Home Assistant project was informed by security researcher Nathan Brady about a security vulnerability. It provided more insight on the implementation of the fixes done for the previous security vulnerability. We learned that not all custom integrations that implement security patches are sufficient to deflect the problem.
We verified all fixes made to custom integrations that were found to be vulnerable in the previous security disclosure. The conclusion is that some custom integrations are still vulnerable to a directory traversal attack while not being authenticated with Home Assistant. It allows an attacker to access any file without having to log in. This access includes any credentials that you might have stored to allow Home Assistant to access other services.
We have responsibly disclosed these issues to the authors of those custom integrations and worked with them on fixing their integrations.
The following have been found:
-
Home Assistant Community Store
(HACS) – fixed in 1.10.1 -
Font Awesome
– fixed in 1.3.1 -
BWAlarm (ak74 edition)
– fixed in 1.12.9 -
Simple Icons
– fixed in 1.11.0
Please make sure to also read the previous security disclosure. While this specific security vulnerability might not impact them, you might be impacted by the previously found vulnerability.
Besides working with the custom integration authors, the following actions have been taken to help protect users:
- Home Assistant released Home Assistant Core 2021.1.5 with extra protection to stop directory traversal attacks before reaching the vulnerable code. This prevents the abuse of all found vulnerabilities.
- This security disclosure is shared widely and linked from banners on the Home Assistant website and forums.
- The Home Assistant Supervisor will notify the user when a possible insecure installation is found that uses custom integrations.
- The Android & iOS Apps are updated to notify the user if their Home Assistant instance is potentially insecure.
- Nabu Casa updated their feature to limit remote access via Home Assistant Cloud and block instances that run an insecure Home Assistant Core version.
- An alert has been placed at alerts.home-assistant.io.
Alright, so here we are, a day after our first major security disclosure, disclosing a second one. Surely it is not fun, but we are thankful it got reported responsibly to us. This time we were able to move quickly and got everything updated pretty fast. Therefore, we decided to disclose all information immediately.
I want to emphasize that it’s not allowed to personally harass/attack/insult the developers of these custom integrations. That would be a violation of our Code of Conduct and we will enforce this.
Paulus
FAQ
Has this vulnerability been abused?
We don’t know.
Disclosure: security vulnerabilities in custom integrations HACS, Dwains Dashboard, Font Awesome and others
This is a disclosure about security vulnerabilities found in 3rd party custom integrations. Custom integrations are not created and/or maintained by Home Assistant. Users install them at their own risk. We want to inform you about these because the found vulnerabilities impact the security of your Home Assistant instance.
If you do not use custom integrations, your Home Assistant is not vulnerable. If you do use custom integrations, your instance might be vulnerable if you use one of the impacted integrations.
TL;DR:
- Multiple custom integrations were found that allowed an attacker to steal any file without logging in.
- Upgrade Home Assistant as soon as possible. Home Assistant Core 2021.1.3 added extra protections that stops attackers from reaching the vulnerable code in custom integrations.
- Upgrade the custom integrations to a fixed version or remove them from your installation.
- If you have used any of the custom integrations with a known vulnerability, we recommend that you update your credentials.
On the morning of Thursday, January 14 2021, the custom integration Home Assistant Community Store (HACS) project was informed by security researcher Oriel Goel
We started to research what other custom integrations could be impacted and found several more. We have responsibly disclosed these issues to the authors of those custom integrations and worked with them on fixing their integrations.
The following have been found:
-
Home Assistant Community Store
(HACS) – fixed in 1.10.0 -
Dwains Lovelace Dashboard
– fixed in 2.0.1 -
Font Awesome
– fixed in 1.3.0 -
BWAlarm (ak74 edition)
– fixed in 1.12.8 -
Simple Icons
– fixed in 1.10.0 -
Custom Updater
(deprecated) – fixed in latest commit
We haven’t been able to get in touch with the authors of the following integration. You should remove this custom integration as soon as possible:
-
Custom icons
– not fixed
The following integration was discovered to be vulnerable to a variant of the above security vulnerability. It allows for a directory traversal attack but requires the attacker to be authenticated. We have been unable to reach the author:
-
Hass-album
– not fixed
If you have used any of these custom integrations, we recommend that you update your credentials.
Besides working with the custom integration authors, the following actions have been taken to help protect users:
- Home Assistant released Home Assistant Core 2021.1.3 with extra protection to stop directory traversal attacks before reaching the vulnerable code. This prevents the abuse of all found vulnerabilities.
- Home Assistant published a security bulletin strongly urging people to upgrade their Home Assistant instance. This bulletin has been shared widely and linked from banners on the Home Assistant website and forums.
- The Home Assistant Supervisor will notify the user when a possible insecure installation is found that uses custom integrations.
- The Home Assistant Companion apps for Android and iOS have been updated to notify the user if their Home Assistant instance is potentially insecure.
- Nabu Casa emailed the security bulletin to all Home Assistant Cloud subscribers and users on trial.
- Nabu Casa activated their feature to limit remote access
via Home Assistant Cloud and block instances that run an insecure version of Home Assistant.
Look. It sucks that this happened. The custom integrations we have listed are all open source, maintained by volunteers in their spare time. They often work alone on this and that’s why it’s more likely for a bug to go undetected. But more eyes doesn’t guarantee bug-free software either. From time to time, such things will happen to every piece of software.
I want to emphasize that it’s not allowed to personally harass/attack/insult the developers of these custom integrations. That would be a violation of our Code of Conduct and we will enforce this.
As Home Assistant, we could have done more to prepare for this scenario. We are currently exploring adding new opt-in features for users to be notified and allow Home Assistant to take action preemptively to patch vulnerabilities.
Paulus
Edit: 23 January 2021: Additional security vulnerabilities disclosed in this second disclosure post.
FAQ
Why didn’t you release the names of the custom integrations in the first security bulletin?
When we discovered the issues, we disclosed them to the authors of the affected custom integrations and gave them time to fix the problem and release a new version. This is a good and common practice when disclosing security vulnerabilities.
Since some of these custom integrations are quite popular, we also decided to publish a security bulletin to urge Home Assistant users to upgrade their instances. We made sure to include enough information for users to resolve the vulnerability.
Has this vulnerability been abused?
We don’t know.
Security Bulletin
It has come to our attention that certain custom integrations have security issues and could potentially leak sensitive information. Home Assistant is not responsible for custom integrations and you use custom integrations at your own risk.
The latest version of Home Assistant Core has extra protection to help secure your instance.
Update your Home Assistant instance as soon as possible.
To update Home Assistant, click on the Supervisor menu item to see if an update to 2021.1.3 (or newer) is available. If you don’t have the Supervisor menu item, follow the update instructions. Home Assistant 2021.1.3 is still compatible with Python 3.7 and an upgrade is possible.
If you cannot update Home Assistant at this time, we strongly advise you to disable all custom integrations. You can disable your custom integrations by renaming the custom_components
folder inside your Home Assistant configuration folder to something else. Please be sure to restart Home Assistant after you’ve renamed it.
If you need additional help with upgrading, we are happy to help you out on our Discord chat server.
We will provide more details about impacted custom integrations in the future.
Paulus
Edit: 15 January 2021: Blog post updated to state 2021.1.3, which added some additional checks.
Edit: 16 January 2021: Blog post updated to remove supervisor reload instructions, as latest version is now generally available. Added note that Python 3.7 is still supported.
Edit: 22 January 2021: More details are now available in the disclosure post.
Edit: 23 January 2021: Additional security vulnerabilities disclosed in this second disclosure post.
2021.1: Happy New Year!
We said goodbye to 2020, which was a weird and wild year. 2020 will be remembered because of the awful pandemic, that hopefully will get under control in 2021.
We wish you, your family, friends and everyone around you, safety, health, happiness and countless blessings for 2021!
Happy New Year!
Kicking off the year with Home Assistant Core 2021.1!
Now don’t get too excited. The 2020.12 release was jam-packed, and most of us enjoyed the holidays with our loved ones. Furthermore, we didn’t have a full release cycle, this one was shorter than usual. This is due to the delaying of the previous release cycle (for the conference) and the introduction of the new release cycle (monthly now).
As a result of that, this release starts 2021 slowly, with a light release. No big new features, no new integrations. Just fixes, tweaking and tuning.
Besides, I’m curious, what is your smart home new years resolution? Let me know in the comments!
Enjoy the release!
../Frenck
- In memoriam of Villhellm
- Home Assistant Conference Videos
- Other noteworthy changes
- New Integrations
- New Platforms
- Integrations now available to set up from the UI
- Release 2021.1.1 - January 9
- Release 2021.1.2 - January 14
- Release 2021.1.3 - January 15
- Release 2021.1.4 - January 16
- Release 2021.1.5 - January 23
- If you need help…
- Backward-incompatible changes
- Farewell to the following
- All changes
In memoriam of Villhellm
It is with sadness that we announce that one of the Jedis in our Discord Server,
@Villhellm
He had been an active member in forums, and other discord servers related to Home Automation (Dr. Zzs, DigiblurDIY, and many more.)
We want to take a moment to recognize his efforts and the support he had provided to the HA community, and may he rest in peace.
Some of his friends have set up a GoFundMe
We thank you for your support!
Home Assistant Conference Videos
A couple of weeks ago, the Home Assistant Conference of 2020 took place. We had quite a few messages and requests for making all talks held at the conference available for viewing.
We have started the process of making those available on our
YouTube Channel
All videos of the conference will be added to the
Home Assistant Conference 2020 playlist
Other noteworthy changes
This release has no big new features, but we do have quite a bit of tweaks that are definitely noteworthy to mention.
-
@spacegaier
removed the “No Area” from the device tables, reducing the clutter in those lists. - Since 2020.12, entities can be assigned to areas. Thanks to @elupus
, these areas are now sent to Google Assistant as room hints. -
Rachio now has pause and resume services, thanks to @brg468
. - A bunch of new sensors are added to Météo-France.
Additional weather conditions, UV, and wind gust, done by @mbo18
! -
@alengwenus
has been refactoring the LCN integration. While it does not bring new things to the surface, it does improve in quality and prepares for future improvements. Keep up the good work! -
Homeatic IP Cloud now supports HmIP-HDM1 and
HmIPW-DRD3, thanks to contributions by @SukramJ
. -
Accuweather now has Wind information, thanks @abmantis
! -
ReCollect Waste now has integration options,
starting by giving the option to display pickup types by their human-friendly
names. Thanks, @bachya
! -
@postlund
rewrote the Apple TV integration for 2020.12, but he is not stopping! Besides some fixes, he extended the device information and added some attributes. - The SQL Sensor now supports MSSQL, thanks to @dgomes
! - Support for climate devices with a temperature range, has been added to the
HomeKit controller integration.
Thanks, @thevoltagesource
! - The MQTT integration discovery feature, now has support for
device trackers, which has been added by @PeteBa
. - Sending animations using the Telegram Bot is now
possible with the new animation service added by @tofuSCHNITZEL
. - If you have a Xiaomi Miio vacuum cleaner with a mop function, this release
added status for the water box and the mop itself. Thanks, @JJdeVries
! -
WeMo now supports the outdoor plug, thanks @mattbilodeau
! - The Music Player Daemon integration now shows album art in the
media player. Looks good @mweinelt
! -
Amazon Polly has a new voice: Olivia. A female,
Australian and neural voice. Thanks @aque0us
! -
Google Cloud TTS now has support for SSML
(Speech Synthesis Markup Language). Thanks, @lufton
!
New Integrations
This release has not introduced new integrations.
New Platforms
The following integration got support for a new platform:
-
Somfy added climate controls and battery sensors,
added by @tetienne
-
Home Connect added support for functional and ambient
lights, added by @Sjack-Sch
-
Gree added support for device light panels, added by @cmroche
Integrations now available to set up from the UI
The following integrations are now available via the Home Assistant UI:
-
BMW Connected Drive, done by @rikroe
Release 2021.1.1 - January 9
- Fix KNX cover state return open when unknown (@farmio
- #44926 ) (knx docs) - Fix wait_template incorrectly matching falsey values (@bdraco
- #44938 ) - Disambiguate Supervisor HTTPUnauthorized on user/password validation (@zeehio
- #44940 ) (hassio docs) - Fix parameters when toggling light (@emontnemery
- #44950 ) (light docs) - Bump pymyq to 2.0.13 (@ehendrix23
- #44961 ) (myq docs)
Release 2021.1.2 - January 14
- Update the Utility Meter sensor status on HA start (@dgomes
- #44765 ) (utility_meter docs) - Bump bimmer_connected to 0.7.14 (@rikroe
- #45086 ) (bmw_connected_drive docs) - Fix neato battery sensor not ready (@Santobert
- #44946 ) (neato docs) - Fallback to tag for any AfterShip tracking that have no checkpoints (@ludeeus
- #45053 ) (aftership docs) - Bump MyQ to 2.0.14 (@ehendrix23
- #45067 ) (myq docs) - Fix OpenWeatherMap forecast timestamp (@spacegaier
- #45124 ) (openweathermap docs) - Add filtering (@frenck
- commit )
Release 2021.1.3 - January 15
- Extend filter and filter tests (@frenck
- #45179 ) (http docs) - Bump aioHTTP 3.7.3 - YARL 1.6.3 (@pvizeli
- #45180 )
Release 2021.1.4 - January 16
- Fix Home Connect ambient color (@Sjack-Sch
- #45038 ) (home_connect docs) - Fix HomeKit climate integration for devices with a single set point in Heat_Cool mode. (@thevoltagesource
- #45065 ) (homekit_controller docs) - Fix all forecast datetime values in OpenWeatherMap (@spacegaier
- #45202 ) (openweathermap docs) - Bump up ZHA dependency (@Adminiuga
- #45230 ) (zha docs)
Release 2021.1.5 - January 23
- Update python-mpd2 to 3.0.3 (@mweinelt
- #45141 ) (mpd docs) - Bump pybotvac to 0.0.20 (@Santobert
- #45367 ) (neato docs) - Bump pyatmo to v4.2.2 (@cgtobi
- #45386 ) (netatmo docs) - Avoid misuse sanitize_path, clarify docs (@balloob
- #45469 )
If you need help…
…don’t hesitate to use our very active forums or join us for a little chat
Experiencing issues introduced by this release? Please report them in our issue tracker
2020.12: Automate with Blueprints!
Welcome to Home Assistant Core 2020.12!
You are looking at our new versioning schema. From now on, the Home Assistant Core will be using calendar versioning, consisting of the year, month and a patch number to indicate a bug-fix release. This also means our release schedule is changing. Home Assistant Core will now be released every first Wednesday of the month!
As most things are announced at the Home Assistant Conference; more things will be added/tweaked in these release notes the next couple of days.
For me, this has been an exciting year! And thanks everybody for contributing to this amazing project, no matter what and how you contributed. You are all amazing! ❤️
With the Holiday season coming, it is time to slow down a bit, enjoy time with our family. And in a couple of weeks, a new year will start; Let’s make it a good one!
Happy holidays, stay safe and for the last time this year: Enjoy the release!
../Frenck
- Blueprints
- New neural voices for Nabu Casa Cloud TTS
- Assign areas to entities and readable area IDs
- Temporarily disable devices
- Other noteworthy changes
- New Integrations
- New Platforms
- Integrations now available to set up from the UI
- Release 2020.12.1 - December 16
- Release 2020.12.2 - December 30
- If you need help…
- Backward-incompatible changes
- Farewell to the following
- All changes
Blueprints
Say hello; to the major new feature of Home Assistant 2020.12: Blueprints!
Screenshot of the blueprints configuration panel.
An automation blueprint is a pre-created automation with user-settable options. This allows for a separation of the logic and inputs of an automation. It sounds a bit complicated, but as a matter of fact, it will make things re-usable and easier.
Imagine a blueprint that controls a light based on motion, that allows you to configure the motion sensor to trigger on, and the light to control.
It is now possible to create two automations that each have their own configuration for this blueprint and act completely independently, yet are based on the same automation configuration.
Sharing blueprints
Blueprints are great for sharing your automations and ideas with the community.
We created a Blueprint Exchange forum category where you can post your created blueprints. For others to use!
We believe that the power of blueprint relies in sharing. You can now share complex automations that others can use, even if they are using the UI editors.
For example, a blueprint can be shared for a specific Zigbee remote control that maps all buttons to a light. A blueprint that sends a notification when it found empty batteries. A blueprint for muting music when you pick up your Android phone.
The sky is the limit in the ideas and automations blueprints we can share!
Using blueprints
Let’s cut a long story short, it sounds exciting, but what does it mean?
You can import blueprints by copying the URL of the forum topic or from GitHub into the UI. Then you can create automations from these blueprints by filling out the required inputs.
Screenshot of a blueprint.
It is really easy to deploy a blueprint, even multiple times! Blueprints are fully functional in both the UI and for YAML.
Creating blueprints
We created a really nice tutorial on how to make blueprints.
Essentially, a blueprint is just like an automation, with some added blueprint metadata. You can convert any existing automation into a blueprint!
As the last step, be sure to share your freshly created blueprint on the community on the Blueprint Exchange, helping and and inspiring others.
New neural voices for Nabu Casa Cloud TTS
If you have a Nabu Casa Home Assistant Cloud
This is a great alternative to, for example, the Google TTS integration. The resulting audio is absolutely stunning and the neural voices sound supernatural.
This service is automatically enabled when you are signed in to your
Nabu Casa cloud account and can be called using the tts.cloud_say
For example:
action:
service: tts.cloud_say
target:
entity_id: media_player.family_room_speaker
data:
message: These new voices sound absolutely stunning!
options:
gender: female
language: en-US
Assign areas to entities and readable area IDs
Areas have been around for a bit already. But, not everything supports areas yet. And using it in for example YAML-based automations, is not really an easy task to do.
Today that changes, as this release works towards making areas more useful by making them more accessible and more universal.
The first change: individual entities can now be assigned to areas.
Previously this was limited to devices only. This also works for entities without a device (for example, entities provided by Helpers). Devices provide entities, and thus it is now possible to override the area with a single entity for a device as well. For example, your in-wall mounted switch controls a light in another room.
Screenshot of assigning a entity to an area.
Second improvement: The ID of a newly created area will now be based on the name of the area instead of a random string.
This makes it easier to use areas in service calls, as you can now use area identifiers that actually make sense for a human! In a YAML automation or script it will look like this:
action:
- service: light.turn_on
target:
area_id: living_room
To find the area ID for the area you want to target, go to the Configuration Panel, and edit the area you want to target. In area edit dialog, the ID is shown.
Temporarily disable devices
Do you have your Christmas tree set up in Home Assistant? After the Holidays are over, you store all those decorations for the next season. But what about those devices in Home Assistant?
Thanks to @emontnemery
Screenshot of disabling a device.
Of course, besides seasonal things, it can also be helpful if you have a broken device or temporarily taking down any other device.
Other noteworthy changes
- The Apple TV integration now supports tvOS version 13 and
above and can be setup from the UI, thanks @postlund
! -
@thecode
has been busy with the Shelly integration and added support for inputs, so you can now use the Shelly i3 and Shelly’s in detached state. - Thanks to @adrum
, the HomeKit controller integration now has support for (de)humidifiers. -
deCONZ now supports tilt on covers, and preset and fan
for climate devices, thanks @Kane610
! -
@frenck
added support for setting the repeat mode to the Spotify integration. - The Nest integration now supports camera and doorbell events,
thanks @allenporter
! - Changes made to your KNX integration’s YAML configuration,
can now be reloaded without restarting Home Assistant. Thanks @spacegaier
! - The number formatting in the frontend is more consistent, thanks to @joshmcrty
! -
@dmulcahey
has been improving the user experience of ZHA. The feedback when pairing a new Zigbee device in the frontend is improved, discovered devices are shown earlier with their progress, and the ZHA configuration panel now has a Zigbee network visualization tab! This allows you to see your network and find connection issues. - The rest integration can now handle request parameters, nicely
done @boxcee
! - Learn new RF commands using a Broadlink remote! Thanks, @felipediel
! -
@mLupine
extended templated binary sensors and these now support templating the delay_on
anddelay_off
!
New Integrations
We welcome the following new integrations this release:
-
FireServiceRota, added by @cyberjunky
-
Kuler Sky, added by @emlove
-
Motion Blinds, added by @starkillerOG
-
SRP Energy, added by @briglx
-
Twinkly, added by @dr1rrb
New Platforms
The following integration got support for a new platform:
-
HomeKit Controller now has initial support for
cameras, added by @Jc2k
-
@emontnemery
has added support for fans and covers to the Tasmota integration - [MQTT][MQTT docs] added support for scenes, added by @kiall
Integrations now available to set up from the UI
The following integrations are now available via the Home Assistant UI:
-
Aurora, done by @djtimca
-
Recollect Waste, done by @bachya
Release 2020.12.1 - December 16
- Bump envoy_reader version to 0.17.3 (@gtdiehl
- #44205 ) (enphase_envoy docs) - Bump dsmr-parser to 0.25 (@RobBie1221
- #44223 ) (dsmr docs) - Fix unhandled KeyError in Recollect Waste (@bachya
- #44224 ) (recollect_waste docs) - Bump hatasmota to 0.1.6 (@emontnemery
- #44226 ) (tasmota docs) - Remove Home Assistant Cast user when removing entry (@emontnemery
- #44228 ) (cast docs) - Default smartenergy multiplier and divisor (@dmulcahey
- #44257 ) (zha docs) - Fix setting timestamp on input_datetime (@balloob
- #44274 ) (input_datetime docs) - Fix Shelly devices missing properties field (@thecode
- #44279 ) (shelly docs)
Release 2020.12.2 - December 30
- Bump HAP-python to 3.1.0 (@bdraco
- #44176 ) (homekit docs) - Update denonavr to 0.9.8 (@scarface-4711
- #44194 ) (denonavr docs) - Bump pyroon to 0.0.28 (@pavoni
- #44302 ) (roon docs) - Fix velux homekit covers not enumerated correctly (@Jc2k
- #44318 ) (homekit_controller docs) - Bump pyMyQ to version 2.0.12 (@ehendrix23
- #44328 ) (myq docs) - Update pytradfri to 7.0.5 (@rubenbe
- #44347 ) - Bump pyiqvia to 0.3.1 (@bachya
- #44358 ) (iqvia docs) - Fix bug in unloading RainMachine options listener (@bachya
- #44359 ) (rainmachine docs) - Fix Volumio pause with missing track type (@OnFreund
- #44447 ) (volumio docs) - Fix falsey comparisons in NWS weather (@MatthewFlamm
- #44486 ) (nws docs) - Bump pydeconz to version 77 (@Kane610
- #44514 ) (deconz docs) - Fix Tasmota device triggers (@emontnemery
- #44574 ) (tasmota docs) - Fix template triggers from time events (@bdraco
- #44603 ) (template docs) - Bump env_canada to 0.2.5 (@michaeldavie
- #44631 ) (environment_canada docs) - Bump pycarwings2 to 2.10 (@filcole
- #44634 ) (nissan_leaf docs)
If you need help…
…don’t hesitate to use our very active forums or join us for a little chat
Experiencing issues introduced by this release? Please report them in our issue tracker
Home Assistant OS Release 5
Today we also release Home Assistant OS 5.8, the first stable version of the 5.x release series.
Highlights:
-
Improved Multicast Name Resolution on OS level
-
External Data Disk Feature
-
Improved Reliability against Container corruption
-
New support: Raspberry Pi 4 – 8GB
-
New support: ASUS Tinker Board S
-
New support: ODROID-C4
-
Improved: OVA Virtual image includes more drivers
Table of contents
Operating System Changes
Multicast Name Resolution
Release 5 uses systemd-resolved to provide DNS services on the operating system
level and acts as a multicast name resolution responder. Besides, mDNS
systemd-resolved also supports the LLMNR hostname resolution protocol. In
practice, this makes discovering a new installation of Home Assistant OS working
in most situations, either using http://homeassistant.local:8123
or
http://homeassistant:8123
.
External Data Disk
In release 4 we introduced external data disk support. The command datactl
allows moving the main data partition to any disk connected to the system. The
boot partition and main operating system partitions stay on the boot medium
(typically the SD card). Using this approach is more reliable than booting the
system from USB. Booting from USB requires several parts of the software stack
to rediscover the external storage. In release 5 we made the external data disk
feature more robust and the initial moving process much faster. We plan to
improve that feature even more and are happy to get your feedback!
Improved Reliability
The main system service to start Home Assistant Supervisor is now more reliable. Home Assistant OS is now able to detect a corrupted supervisor container in most situations and automatically downloads a new version of it. File system checks have also been expanded to the boot partition, which makes sure that all file systems are being checked now.
Under the Hood
Under the hood, we updated to Buildroot 2020.11, which brings tons of new software versions along with bug and security fixes. Some key components which received an update were systemd 246 and AppArmor version 3.0.
Board Support
Raspberry Pi
All Raspberry Pi versions now use Linux Kernel 5.4, just like Raspberry Pi OS. With the move to U-Boot 2020.10, we are now also supporting Raspberry Pi with 8GB of memory. With the new kernel and U-Boot Home Assistant OS can now also run on the Compute Module 4 as well as the Pi 400 (the keyboard). A keyboard is probably not the ideal form factor for a headless system such as Home Assistant OS, but it comes with good cooling, which makes it not the worst choice :-). We recently tested the 64-bit variant of Home Assistant OS much more and feel comfortable to recommend the 64-bit version for Raspberry Pi 4.
ODROID
The ODROID platforms now use Linux 5.9, which brings improved support for all ODROID platforms such as the ODROID N2(+). For the N2(+) the Real-Time Clock is now supported as well.
Open Virtualization Appliance/Intel NUC
The x86 platforms (Intel NUC, OVA - Open Virtualization Appliance) now use Linux 5.9. The kernel for OVA images has new drivers enabled for Intel Network devices with Virtual Function, PCIe passthrough for Hyper-V, or support for Audio (HDA audio devices).
New Board Support
Besides the ASUS Tinker Board, we now also support the Tinker Board S, a variant with fast on-board eMMC storage. Thanks to [@ubergeek801] we now also have support for ODROID-C4, a cost-effective alternative to Raspberry Pi in a similar form factor.
Other Changes
The build pipeline is now using GitHub Actions and we compress the images using the xz compression algorithm instead of gz. The flashing process will stay the same: Etcher supports flashing from gz as well as xz.
This is all I can think of for now. The release 5.8 will be on the stable
channel today, so watch out for the update notification in the Supervisor
section. Images are available in the release section over on
GitHub
Community Highlights: 7th edition
The 7th edition of the Home Assistant Community Highlights! Some interesting things popped up around our community, we thought was worth sharing.
Troy Hunt has jumped into our wonderful world and shared his journey in a blog post series. Some nice examples on a DIY solution for mounting a wall tablet and how to arm your alarm with a toothbrush!
Troy Hunt is unraveling IoT using Home Assistant
If you have never heard of Troy Hunt before, he is a web security specialist
and mostly known for creating “Have I Been Pwned”
Troy has been diving into the world of IoT and started automating his home, using… Home Assistant!
I'm massively impressed with HA and nothing else I've seen along my IoT journey comes even close to comparing. If you're going to do IoT in any meaningful way, you start with HA.
Troy Hunt
In 5 blogs, he writes about his journey in the big world of IoT:
- Part 1: It’s a Mess… But Then There’s Home Assistant
- Part 2: IP Addresses, Network, Zigbee, Custom Firmware and Soldering
- Part 3: Security
- Part 4: Making it All Work for Humans
- Part 5: Practical Use Case Videos
The 5th part Troy made 11! short and quick videos, showing actual use cases in his home. Really cool and inspiring!
Framing a wall-mounted tablet
If you are a bit like me, you probably want to wall mount a tablet someday (or you already have it of course 🥴). Doing that in a nice, elegant and pretty way is often the hard part. Especially if you only have brick walls (like me), which makes it hard to hide cable or recess the tablet.
Next I came across 2 posts on on the Home Assistant subreddit
This one popped up, made by ialex87, which uses a
3D printed frame from Thingiverse
Nothing much, but my honest work!from r/homeassistant
Next, Invinciberry shared his version:
Now let's wall mount this thing.from r/homeassistant
Both look very slick! Thanks for sharing!
Arm your alarm by brushing your teeth…
Automatically arm your alarm, when Home Assistant detects you are using your toothbrush… Why? Because we can! 😎
Have you ever seen a house alarm system controlled by a toothbrush? Here our @VanderbiltInd
— Ian (@imduffy15) November 19, 2020alarm is integrated into @home_assistant . Our toothbrush is ble enabled, it’s state is read by an ESP32 chip and sent into @home_assistant pic.twitter.com/T9XGi1Zjmb
Home Assistant Conference
This isn’t a highlight yet, but without a doubt, it is definitely is going to become one of the highlights of this year: The Home Assistant Conference.
Sunday, 13 December, we’ll be looking back at last year; but more importantly, lots of great talks are planned by speakers from our community about all different kinds of subjects:
Above all, some new and exciting stuff is going to be announced as well! So, ensure you don’t miss it.
Or, check the Home Assistant Conference page for other ways on how to watch.
Got a tip for the next edition?
Have you seen (or made) something awesome, interesting, unique, amazing, inspirational, unusual or funny, using Home Assistant?
Click here to send us your Community Highlight suggestion.
Also, don’t forget to share your creations with us via Social Media:
- Twitter it! Be sure to mention @home_assistant
- Share it on our Facebook group
- Post it to our subreddit
- Tag @homeassistant
on Instagram - Or via chat, drop us a line in the #lounge at Discord
See you next edition!
[Better solution!] TP-Link offers way to add local API back
Update Nov 26: TP-Link has now announced that they are working on a new firmware that should solve it. DM them on Twitter for info.
We're sorry the recent firmware update has problems for the Kasa community. Since its release, we've been busy creating a Beta firmware that'll enable people to continue to use third-party smart home software & platforms using local APIs. Please DM if you'd like the Beta firmware
— TP-LINK UK (@TPLINKUK) November 26, 2020
Last week TP-Link released an update for their HS100 and HS110 plugs that removed the local API. This was done because of a “security concern”. I put this in quotes because it has not been verified and this reason has been given before when removing interoperability. TP-Link communicated this via Twitter in response to a user voicing their concern.
There were security vulnerabilities on the plug for the local management, the latest firmware version fixed these security issues. It is suggested to use the TP-Link official App KASA to manage the plug. If you have issues, pls feel free to let us know.
— TP-LINK UK (@TPLINKUK) November 17, 2020
Lots of users, rightfully so, got angry. They bought the plugs assuming the local API was a feature. Removing this feature and forcing users through the TP-Link cloud sucks. It removes the one feature why TP-Link stood out among many smart plugs.
After a week of angry users, it looks like TP-Link has listened… somewhat. They are offering a temporary solution to roll back the firmware. We haven’t found any public documentation, but there are forum posts by their employees here
Forum post
We are hoping for a better solution, but for now this is what you should do:
-
Submit a ticket to technical supportWe got an update from TP-Link that this step is no longer necessary.. Make sure to include the MAC address of your plug. - Go to the forums and send this user
a message with your TP-Link ID, model number, hardware version and MAC address.
TP-Link, if you’re reading along, please reach out to us at [email protected] so we can discuss a better long term solution for local control. Happy to talk!
0.118: Grid and logbook cards, quick navigation, native template types
Home Assistant Core 0.118!
The second last release of 2020, while the end of the year is slowly closing in.
This also means we have only one more release left this year… And we plan to finish the year with a big bang! Also announced: the Home Assistant Conference. I am really excited about that one! The last major release of this year will be during the conference on December 13.
Back to 0.118! Some nice additions this release: Navigating around with the Quick bar (oh, I just love that feature), some new Lovelace cards, native types in templates is now the default and the Nest thermostat is back! 🎉
All in all, a fine release, with an exciting one ahead of us.
../Frenck
Table of contents
- Table of contents
- Home Assistant Conference
- Grid Card
- Quick Bar navigation
- Native types support for templates
- Logbook Card
- Header & Footer Editor
- Supervisor Network Configuration
- Home Assistant OS
- Other noteworthy changes
- New Integrations
- New Platforms
- Integrations now available to set up from the UI
- Release 0.118.1 - November 19
- Release 0.118.2 - November 20
- Release 0.118.3 - November 23
- Release 0.118.4 - November 26
- Release 0.118.5 - December 5
- If you need help…
- Backward-incompatible changes
- Farewell to the following
- All changes
Home Assistant Conference
Exciting news! Home Assistant is hosting an online conference this year!
An event to celebrate our community, share ideas, history, creations and celebrate major milestones! The event will take place on Sunday, December 13.
Paulus Schoutsen
Check out the conference schedule
The Home Assistant Conference will be hosted on Hopin
The conference will also be available as a free YouTube live stream. The live stream will be limited to the keynotes and the “everyone” track. You won’t have access to the chat and have that online conference feeling, so we recommend getting a ticket!
For the latest information, check our dedicated Home Assistant Conference page.
Edit: We all hate ads! But we do like to show off our users!
For those who don’t keep up with the release notes, we added an announcement about the conference in the Configuration panel. It was always set to disappear automatically when the conference is over, but when you are ready to be rid of it, just press the x!
We realize it is invoking concern of future ads and that it could have had a better execution. In fact, within some of the (yes, sometimes heated) discussions about it during the beta, there were some good thoughts and examples shared for working toward a truer “community news” integration. Such an integration could pull in future and ongoing community events, news, and project highlights, which could be enabled or disabled like any other integration. For now, it is this banner which will be removed on the next release.
Grid Card
Ever since the start of Lovelace, users have been making grids. However, this was not easy as it involved fiddling by combining horizontal and vertical stacks — a confusing and frustrating experience.
@balloob
The Grid Card offers straight forward options to mimic these setups and adds an option to force each card to be square to boot.
Screenshot of Grid Card.
*Note that the square option won’t work with all cards.
Quick Bar navigation
The Quickbar, which was introduced in Home Assistant 0.117, really took off! We are happy to see you like it.
If you haven’t tried the new Quick Bar yet… you should! It is a quick and
easy way to get to entities or run commands. From anywhere in Home
Assistant; press e
for entities or c
for commands.
This release, support for navigating Home Assistant via the Quick Bar was added.
You can now jump to any place, from any place. Amazing job @donkawechico
Screenshot of navigating around using the Quick Bar.
Native types support for templates
Announced in 0.117, but now by default enabled. Native template types allow templates to result in not just strings (text), but also other types.
Ever tried to make a list of entities or set an RGB color via a template? If so, you probably would have learned, that it is not that simple. In Home Assistant, the result of a template always has been a piece of text (a string), even if you made a list.
script:
my_script:
alias: "Example"
description: Example script with native lists in templates
variables:
entities:
- light.living_room_window
- light.living_room_table
color: [255, 0, 0]
sequence:
service: light.turn_on
target:
entity_id: "{{ entities }}"
data:
rgb_color: "{{ color }}"
This is an extremely powerful change to our template engine, that allows for more advanced future additions and can significantly reduce the complexity of existing templates in your set up.
It should be mostly compatible with your existing templates; However, be sure to check the backward-incompatible changes section for known possible breaking scenarios.
Logbook Card
Another new Lovelace card this release. @zsarnett
This card allows you to show the logs of one (or more) entities on a Lovelace Dashboard. This can be really helpful if you want to monitor, for example, the motion events of a sensor or a camera.
Screenshot of the new Logbook Card.
Header & Footer Editor
Entity cards in Lovelace have support for customizing the header and footer of that card. This is really useful for adding a nice image, a couple of buttons or a graph to the card.
Up until now, you needed some YAML magic to achieve that. Thanks to
@zsarnett
Screenshot of the new Header/Footer editor.
Supervisor Network Configuration
Expected to be available soon, a new Supervisor version which includes a new network layer with added support for wireless networks, multiple network interfaces and even VLANs.
This should cover most of the feature requests we had around networking.
New Supervisor Network configuration UI
The next step is that we use all the information from our new network backend to simplify some add-ons. Also, updates for Snapshot/Restore of these network settings are planned.
Home Assistant OS
The last few days, two new Home Assistant OS releases have been published.
While 4.17 continues to make small improvements in the 4.x release series, the latest pre-release 5.5 comes closer to our goals to declare 5.x release series stable. In particular, this pre-release includes the Linux 5.4 kernel for all Raspberry Pis! We also intend to declare 64-bit the recommended installation method for Raspberry Pi 4.
Release 5.5 is also the first release to support Hardkernel’s ODROID-C4, a very cost-effective single board computer featuring the Amlogic S905X3 SoC and 4GB of DDR4 memory (thanks @ubergeek801). Testers welcome!
Other noteworthy changes
- The new Nest SDM integration now supports thermostats! Thanks, @allenporter
! - Entity pickers in the UI will now show the full name of the entities.
Thanks, @spacegaier
! - The Roon media player now supports media browsing but also has support
for grouping and transferring between different players. Thanks @pavoni
-
@cnorick
added a button to duplicate Scripts from the UI. - The Shelly integration now has real-time status updates, which has been
implemented by @thecode
! -
@apop880
prepared the WLED integration for Christmas by adding a service for loading WLED presets. - Date pickers in entity cards have been replaced with a modern, good looking
version. Thanks, @thomasloven
! -
@joshmcrty
Made numbers shown in the frontend formatted in a way that matches your language settings. -
@spacegaier
has been busy improving the frontend, making it more accessible to people with disabilities. In this case, ARIA (Accessible Rich Internet Applications) labels have been added, so screen readers can use our +
buttons. Thanks!
New Integrations
We welcome the following new integration this release:
-
Color Extractor, added by @GenericStudent
New Platforms
The following integration got support for a new platform:
Integrations now available to set up from the UI
The following integrations are now available via the Home Assistant UI:
Release 0.118.1 - November 19
- Bump wolf_smartset to 0.1.8 and handle server fetch error (@adamkrol93
- #43351 ) (wolflink docs) - Bump hatasmota to 0.0.32 (@emontnemery
- #43360 ) (tasmota docs) - Fix homekit bridges when no name was provided (@bdraco
- #43364 ) (homekit docs) - Bump pyvizio to 0.1.57 (@raman325
- #43374 ) (vizio docs) - Add back system_health_info to the base of lovelace (@ludeeus
- #43382 ) (lovelace docs)
Release 0.118.2 - November 20
- Increase Advantage Air retry limit for older systems (@Bre77
- #43417 ) (advantage_air docs) - Fix time trigger based on entities ignoring entities if initially in the past (@balloob
- #43431 ) (homeassistant docs)
Release 0.118.3 - November 23
- Fix bug related to possibly missing task ID in Notion API data (@bachya
- #43330 ) (notion docs) - Fix unhandled exception when IQVIA API fails to return data (@bachya
- #43359 ) (iqvia docs) - Ensure Plex content_id in play_on_sonos service is a string (@frenck
- #43483 ) (plex docs) - Gracefully handle no uuid in kodi discovery (@OnFreund
- #43494 ) (kodi docs) - Bump sleepyq to 0.8.1 (@ahertz
- #43505 ) (sleepiq docs) - Upgrade Docker base image to 2020.11.1 (@frenck
- #43538 ) - Upgrade Docker base image to 2020.11.2 (@frenck
- #43560 )
Release 0.118.4 - November 26
- Make MQTT climate return PRESET_NONE when no preset is set (@emontnemery
- #43257 ) (mqtt docs) - Update zigpy-zigate to 0.7.3 (@doudz
- #43427 ) (zha docs) - Fix duplicate check on onewire config flow (@epenet
- #43590 ) (onewire docs) - Bump avea to 1.5.1 (@pattyland
- #43618 ) (avea docs) - Disable parsing scientific/complex number notation in template type (@balloob
- #43170 ) - Tweak template digit detection (@balloob
- #43621 ) - Fix deadlock if an integration from stage_1 fails (@pvizeli
- #43657 )
Release 0.118.5 - December 5
- Bump pyatmo to v4.2.1 (@cgtobi
- #43713 ) (netatmo docs) - Increase timeout for snapshot upload (@ludeeus
- #43851 ) (hassio docs) - Implement new Google TTS API via dedicated library (@marvin-w
- #43863 ) (google_translate docs) - Pin pip < 20.3 (@MartinHjelmare
- #43771 )
If you need help…
…don’t hesitate to use our very active forums or join us for a little chat
Experiencing issues introduced by this release? Please report them in our issue tracker