Blog
User Experiences and Designers
About two months ago my phone kept buzzing with notifications. I got the kindest tweets after it was announced that I was joining Home Assistant as the first full-time UX designer. That enthusiasm is also reflected in the more than 500 registrations for our user research group
User Experiences
Home Assistant has a large group of users with a common goal: home automation that puts local control and privacy first. From our analytics we have over 85,000 users who opted in to share their data anonymously, but we know that there are a lot more. None of these houses and users are alike and may have different, perhaps conflicting interests. Here lies the power of UX. As Scott Jenson
In the coming period, I will investigate what type of smart home users there are, what their needs are and what stands in the way of achieving this.
Designers
Last year alone, there were over 8,000 GitHub contributors to Home Assistant. That’s really fantastic! With a Designer-to-Developer ratio of 1 per 8,000, it’s easy to get lost in the backend of design and forget the users. This can result in inconsistent user interfaces or designs that could be more user-friendly. For now we’re working on three areas.
UX contributors
We want to make it as easy for designers to contribute as it is for developers. There’s a lot a designer can contribute to. For example, making it easier to work with light groups or getting started with automating your house. If you have a design you really think we should look at? Would you like to help build our own Design System? Do you have experience with user testing? Do you have strategic design ideas? Want to organize an online design workshop? Or just want to meet fellow designers? Meet us at devs_ux Discord channel or join us on GitHub discussions
Tooling
We want it to be easy to start creating and iterating on design mockups for Home Assistant. We want anyone that is interested to be able to jump in. To achieve this we’ve been hard at work at re-creating the components that make up the Home Assistant interface as a DesignKit for Figma
Documentation
With clear guidelines, you can ensure speed and quality. That’s why we’re working on design documentation that will be available soon. Its goal is to help designers and developers make better choices. Got suggestions or want to help with our guidelines? Meet us at devs_ux Discord channel.
2021.10.0: Z-Wave S2 support, Tuya, secure ESPHome and 400 new icons
October! I love this month!
For most of you (just like me), it means winter is coming. We all go back inside. An excellent excuse to spent a bit more time on our smart homes, right? 😃
It is also the month of celebrating open source by joining
Hacktoberfest
For the Home Assistant project, this means a busy month. However, that doesn’t matter. It is always great to see new people contributing!
Meanwhile, Home Assistant turned 8 years old already! Wild! And the birthday announcement was even wilder (more about that below).
Anyways, about this release: Z-Wave JS is stepping up its game! If you have a Z-Wave network and are not using Z-Wave JS yet… well… it might be time to bite the bullet and go for it. You won’t regret it.
This release also brings the new much-talked-about, Tuya integration supported by Tuya themselves! I’m looking forward to how that evolves!
Oh, and of course, we will be live streaming the 2021.10 release party later today!
Join us at https://youtu.be/QWy4jWzKUEw
Enjoy the release!
../Frenck
- Home Assistant Yellow
- Z-Wave JS updates!
- New Tuya integration
- Updated Material Design Icons
- Encrypted communications support for ESPHome
- Other noteworthy changes
- New Integrations
- Integrations now available to set up from the UI
- Release 2021.10.1 - October 7
- Release 2021.10.2 - October 8
- Release 2021.10.3 - October 10
- Release 2021.10.4 - October 11
- Release 2021.10.5 - October 15
- Release 2021.10.6 - October 18
- Release 2021.10.7 - November 1
- If you need help…
- Backward-incompatible changes
- Farewell to the following
- All changes
Home Assistant Yellow
In case you’ve missed it: Home Assistant turned 8 years old! 🥳 And to celebrate that, we’ve revealed the Home Assistant Yellow!
Home Assistant Yellow was launched using a crowdfunding campaign, which already reached its funding goal! This is absolutely fantastic!
And… You can still back the campaign to get your own Home Assistant Yellow!
Go to campaign on CrowdSupply »
Z-Wave JS updates!
We have two awesome Z-Wave JS updates to share with you this release.
S2 is now supported
Security is something we all care about; We don’t want devices to be tampered with, when using things like door locks or motion sensors that trip the alarm system. For our Z-Wave devices, this is no different!
As of this release, Home Assistant’s Z-Wave JS integration supports S2!
S2 is short for Security 2, a new security standard for Z-Wave devices, providing different keys for each device in the network. It is the more secure upgrade of the previous S0 version.
Besides improved security, S2 capable devices (in general) are more reliable, provide greater battery life and have less latency compared to S0.
The Z-Wave JS integration will automatically pick the best and most optimal security method available.
Automatically uses the best possible security method when adding a new Z-Wave device.
If you have existing Z-Wave devices capable of using S2 already paired with Home Assistant before this update, you will need to repair those to let them use the new S2 feature.
Migration wizard from the old Z-Wave integration
Are you still using the old (and deprecated) zwave
integration? If so, it
might be that you have been holding back on the Z-Wave JS upgrade because of
the work involved in migrating. Time to reconsider…
Home Assistant now provides a migration wizard for users of the old Z-Wave integration to migrate more easily to the new Z-Wave JS integration.
To avoid surprises, the wizard will exactly show what it will do, what it can and cannot migrate.
The old and deprecated Z-Wave integration will continue to work as long as technically possible, but will no longer receive updates.
New Tuya integration
Oh yeah! The Tuya integration has been updated to the latest greatest version: developed and maintained by a team of developers at Tuya themselves!
Right now, we have support for lights, switches, scenes, fans and climate devices. Compared to the old integration, support for covers is currently missing, which we hope to add in a future release. Additionally, the new integration now pushes updates to Home Assistant!
If you ran the Tuya integration previously, you need to set it up from scratch, as the integration has been entirely re-written and uses a different API.
For more information, please see the Tuya integration documentation.
Updated Material Design Icons
The Material Design Icons
This new version of MDI is packed with nearly 400 new icons (and over 75+ icons have been specifically marked for Home Assistant) ❤️
Some really useful new MDI icons have been added in this release!
Several icons have been removed or renamed in v6, but we have ensured they will keep working for the upcoming two releases. Home Assistant will write warnings in the logs in case you are using one of the affected icons. The backward-incompatible changes section has more information about this.
Encrypted communications support for ESPHome
ESPHome and the ESPHome integration now have support for communicating
encrypted with each other. @OttoWinter
Besides this version of Home Assistant, you’ll need at least
ESPHome 2021.9.0
Awesome job @OttoWinter
For more information on how to do that, check out the
ESPHome documentation
Other noteworthy changes
There is much more juice in this release; here are some of the other noteworthy changes this release:
- The energy dashboard now supports gas sensors that use kWh as the unit of measurement.
- We have a new dev tool available for long-term statistics. This tool can be helpful when you need to resolve issues or warnings with the statistics.
- The Shelly team has been busy and added support for the new, next-generation, Shelly devices. Also known as Gen2 or Plus devices (which are WebSocket RPC based).
- The TP-Link Kasa Smart integration had a lot of love and improvements: support
for new devices, configurable via the UI and device discovery. It fixes the
famous and disliked “unavailable” bug! Thanks @rytilahti
! -
@Aohzan
adjusted the Logitech Harmony integration to have a select entity to change the activity. Very handy! - HomeKit now supports the
select
andinput_select
entities, thanks to @ha0y! -
@Kane610
added support to deCONZ for the Siren entity. - The manual alarm control panel now supports vacation mode, thanks @mbo18
! -
@koying
added a new template method: regex_findall
, that can return a list of all matches of a regular expression. -
@emontnemery
added more template goodness by adding the is_number
function and filter that can be used to quickly determine if a value is a number or not. - The Lovelace entity card now supports setting the icon to change color when
the entity is active (
state_color
). Thanks, @spacegaier - The SwitchBot integration is receiving a lot of love from @RenierM26
! A bunch of new platforms, configuration via the UI, nice work!
New Integrations
We welcome the following new integrations this release:
-
Airthings, added by @Danielhiversen
-
Amberelectric, added by @madpilot
-
Crownstone, added by @RicArch97
-
WattTime, added by @bachya
-
Whirlpool Sixth Sense, added by @abmantis
Integrations now available to set up from the UI
The following integrations are now available via the Home Assistant UI:
-
DLNA-DMR, done by @chishm
-
Modem Caller ID, done by @tkdrob
-
Netgear, done by @starkillerOG
-
OpenGarage, done by @Danielhiversen
-
Sure Petcare, done by @Danielhiversen
-
SwitchBot, done by @RenierM26
Release 2021.10.1 - October 7
- Recreate the powerwall session/object when attempting relogin (@bdraco
- #56935 ) (powerwall docs) - Update led brightness select state only if valid data is available, Xiaomi Miio integration (@bieniu
- #57197 ) (xiaomi_miio docs) - Convert val to str when needed while calling zwave_js.set_value (@raman325
- #57216 ) (zwave_js docs) - Discover tplink devices periodically (@bdraco
- #57221 ) (tplink docs) - Correct SQL query generated by get_metadata_with_session (@emontnemery
- #57225 ) (recorder docs) - Fix netgear config flow import (@MartinHjelmare
- #57253 ) (netgear docs) - Validate initial value for input_datetime (@emontnemery
- #57256 ) (input_datetime docs) - Bump Mill library to 0.6.1 (@Danielhiversen
- #57261 ) (mill docs) - Fix RGB only (no color temp) devices with tplink (@bdraco
- #57267 ) (tplink docs) - Update frontend to 20211007.0 (@bramkragten
- #57268 ) (frontend docs) - Fix transition handling for tplink lights (@rytilahti
- #57272 ) (tplink docs) - Bump HAP-python to 4.30 (@bdraco
- #57284 ) (homekit docs) - Stopgap fix for inconsistent upstream API of tplink dimmers (@rytilahti
- #57285 ) (tplink docs) - Bump yeelight to 0.7.7 (@bdraco
- #57290 ) (yeelight docs)
Release 2021.10.2 - October 8
- Netgear fix port and device model beeing overwritten (@starkillerOG
- #57277 ) (netgear docs) - Fix Nanoleaf light turn_off transition (@milanmeu
- #57305 ) (nanoleaf docs) - Migrate tplink hosts that were previously imported from yaml (@bdraco
- #57308 ) (tplink docs) - Upgrade aionanoleaf to 0.0.3 to fix deadlock (@milanmeu
- #57312 ) (nanoleaf docs) - Improve state of cover groups (@emontnemery
- #57313 ) (group docs) - Fix multiple upnp/ssdp issues (@StevenLooman
- #57314 ) (upnp docs) (yeelight docs) (dlna_dmr docs) (ssdp docs) - Guard for bad last reset (@balloob
- #57344 ) (sensor docs)
Release 2021.10.3 - October 10
- Catch errors for efergy (@tkdrob
- #57326 ) (efergy docs) - Use switch format unique ids for tplink dimmers (@bdraco
- #57346 ) (tplink docs) - Fix Shelly RGB/W supported color mode detection (@thecode
- #57359 ) (shelly docs) - Bump pynws to 1.3.2 (@MatthewFlamm
- #57361 ) (nws docs) - Bump Switchbot library (@RenierM26
- #57367 ) (switchbot docs) - Bump pyhaversion to 21.10.0 (@ludeeus
- #57377 ) (version docs) - Update frontend to 20211007.1 (@bramkragten
- #57385 ) (frontend docs) - Do all of dhcp scapy startup in the executor (@bdraco
- #57392 ) (dhcp docs) - Remove executor calls in isy994 as its fully async (@bdraco
- #57394 ) (isy994 docs) - Fix default parameter values for service opentherm_gw.set_clock (@mvn23
- #57397 ) (opentherm_gw docs) - Fix
opentherm_gw.set_clock
time
parameter name (@mvn23- #57398 ) (opentherm_gw docs) - Restore yeelight workaround for failing to update state after on/off (@bdraco
- #57400 ) (yeelight docs) - Fix Shelly button filter empty event (@thecode
- #57427 ) (shelly docs) - Fix Shelly button type in roller mode (@thecode
- #57429 ) (shelly docs) - Bump zeroconf to 0.36.8 (@bdraco
- #57451 ) (zeroconf docs) - Fix netgear renamed mdi icons (@thecode
- #57431 ) (netgear docs)
Release 2021.10.4 - October 11
- Upgrade youless library to fix missing sensor LS110 (@gjong
- #57366 ) (youless docs) - Fix Netgear orbi port in ssdp discovery (@starkillerOG
- #57432 ) (netgear docs) - Fix upnp creating derived sensors (@StevenLooman
- #57436 ) (upnp docs) - Fix referenced before assignment in modem_callerid (@tkdrob
- #57460 ) (modem_callerid docs) - Upgrade aiomusiccast to tolererate not decodable characters (@micha91
- #57461 ) (yamaha_musiccast docs) - Detect if mysql and sqlite support row_number (@emontnemery
- #57475 ) (recorder docs) (sensor docs) - Bump youtube-dl to 2021.06.06 (@chpego
- #57490 ) (media_extractor docs) - Simplify yeelight setup to improve reliability (@bdraco
- #57500 ) (yeelight docs)
Release 2021.10.5 - October 15
- Log reason for DLNA-DMR device becoming unavailable (@chishm
- #57516 ) (dlna_dmr docs) - Bump Mill library to 0.6.2 (@Danielhiversen
- #57533 ) (mill docs) - Fix Fast.com autoupdate (@Z1ni
- #57552 ) (fastdotcom docs) - Bump simplisafe-python to 11.0.7 (@bachya
- #57573 ) (simplisafe docs) - Correct detection of row_number support for MariaDB (@emontnemery
- #57663 ) (recorder docs) - Ensure Notion device name is stored as a string (@bachya
- #57670 ) (notion docs) - Bump spiderpy to 1.4.3 (@peternijssen
- #57675 ) (spider docs) - Fix Shelly humidity sensor available condition (@thecode
- #57721 ) (shelly docs) - Reconnect and retry yeelight commands after previous wifi drop out (@bdraco
- #57741 ) (yeelight docs) - Always send color/temp when switching from an effect in yeelight (@bdraco
- #57745 ) (yeelight docs) - Fix Youless state class for power total sensor (@gjong
- #57758 ) (youless docs) - Fix broken upnp derived sensors reporting b/s instead of kb/s (@StevenLooman
- #57681 ) (upnp docs)
Release 2021.10.6 - October 18
- Avoid setting up harmony websocket from discovery (@bdraco
- #57589 ) (harmony docs) - Fix device class for energy plugwise sensors (@squio
- #57803 ) (plugwise docs) - Prevent yeelight discovery from overloading the bulb (@bdraco
- #57820 ) (yeelight docs) - Bump bond-api to 0.1.14 (@bdraco
- #57874 ) (bond docs) - Revert “Fix bmw_conntected_drive check_control_message short description” (@cdce8p
- #57928 ) (bmw_connected_drive docs) - Fix bug that prevents multiple instances of Tile (@bachya
- #57942 ) (tile docs)
Release 2021.10.7 - November 1
- Fix Tuya documentation URL (@ludeeus
- #57889 ) - Fix netgear NoneType and discovery (@starkillerOG
- #57904 ) - Abort keenetic SSDP discovery if the unique id is already setup or ignored (@foxel
- #58009 ) - Fix Yamaha MusicCast media_stop (@micha91
- #58024 ) - Sleep between device requests to detect socket closes (@chishm
- #58087 ) - Fix template sensor when name template doesn’t render (@emontnemery
- #58088 ) - Bump pymazda to 0.2.2 (@bdr99
- #58113 ) - Abort Fritz config flow for configured hostnames (@chemelli74
- #58140 ) - Fix find_next_time_expression_time (@OttoWinter
- #58894 )
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 Yellow
This project was originally published under the name Home Assistant Amber.
To celebrate our 8th birthday we’re launching a crowdfunding campaign for Home Assistant Yellow. We designed Home Assistant Yellow from scratch for both beginners and home automation enthusiasts to be the easiest way to run Home Assistant.
Go to campaign on CrowdSupply »
We will be hosting a Home Assistant Yellow live stream today at 12.00 PDT / 21.00 CEST. We will talk about how Home Assistant Yellow came to be and answer any questions you might have!
2021.9.0: More energy, USB discovery, template ❤️
Last release we introduced Home Energy management, and we are so happy with all the reactions and response we have received ❤️! In this version we have added some much requested features to make it even more useful, also a lot more integrations now have support for it ⚡️.
Personally I also really like the new long term statistics and statistics card introduced last release, and I’m really happy that in this release we will be able to use it for a lot more sensors.
Enjoy another great release! Be sure to tune into the 2021.9 Release Party on YouTube
- Home Energy Management updates
- Long term statistics unlocked for all sensors
- USB Discovery
- Z-Wave JS Updates
- New template entities: Number and Select
- New template functions for areas
- Other noteworthy changes
- New Integrations
- Integrations now available to set up from the UI
- Release 2021.9.1 - September 2
- Release 2021.9.2 - September 3
- Release 2021.9.3 - September 4
- Release 2021.9.4 - September 6
- Release 2021.9.5 - September 8
- Release 2021.9.6 - September 11
- Release 2021.9.7 - September 18
- If you need help…
- Backward-incompatible changes
- All changes
Home Energy Management updates
Last release, we introduced the new Home Energy management features into Home Assistant and we are happy to see you like it!
We have seen quite a few people sharing their Energy dashboards on socials like
Facebook
In this release, the story continues! Here is what we have in store for you:
View energy usage over a period of time
The first iteration of the Energy Dashboard showed a single day at the time. Great! But what if you want to see how you did this week? Or month? Heck, a year even?!
Well, now you can! In the top right of the dashboard, you can now select the grouping period you want to see: Day, Week, Month or Year.
Screenshot of the new Energy Dashboard period selection.
The arrow buttons allow you to browse through those periods. For example, when selecting a period of a month to display, the arrow buttons will take you a whole month back/forward in the view.
Keeping track of your gas usage
In some countries, homes are connected to gas. The gas is being used to heat water, cook and for heating the house. If you have a home that is connected to gas, we have some great news for you!
Maybe you noticed it already in the previous screenshot, as of this release, we have added support for monitoring your gas usage.
Screenshot of the new Energy Dashboard monitoring gas usage.
In certain countries, the gas meters have a standardized way of reading
out the gas usage locally or provide this information via the electricity
meter. For example, in the Netherlands, Belgium and Luxembourg you could
use the SlimmeLezer
Support for home batteries
Having solar panels is a great way to generate electricity to power your home. However, where do you store energy generated by your solar panels that you don’t need right now?
Well, for many, the solution resides in a, high capacity, home battery to store electricity for use when the sun can’t provide it (e.g., during the night).
Numerous have requested this feature, and therefore we now have added support for home batteries to the Home Assistant energy management.
Animation of a home battery as part of the energy distribution.
Added support for many more integrations
When releasing a feature such as the Home Energy management, we understand you want to use and play with it right away. And while we had prepared and updated a lot of integrations to be ready when we first launched, there were still many in need of an update.
As a result, we have been flooded by requests to add support to virtually all integrations that didn’t had it yet… :) Many of those requests have been fulfilled in this release.
For example, the Kostal Plenticore Solar Inverter, PVOutput, Fronius, SolaX Power, Growatt, Solar-Log, YouLess, Emoncms, Modbus, and many more have added support for all the energy goodness.
If you are a custom integration developer who wants to add support, be sure to check out our developer blog to catch up with the latest changes.
Long term statistics unlocked for all sensors
In the previous release, we introduced long term statistics for sensors, including a beautiful Lovelace card that goes with it. However, in the previous release we had limited this feature to temperature, humidity, power and energy related sensors.
As of this release, we unleashed the long term statistics for all sensors!
Screenshot of a statistics graph showing the luminosity in the garden versus the front of my house.
Long term statistics applies to all integrations that indicate their sensors support those. Luckily a lot have already done so.
USB Discovery
Thanks to @bdraco
For example, if you plug in your new Nortek HubZ USB stick into the machine running Home Assistant, it will discover and notify you about it.
Screenshot of a discovered USB device compatible with Z-Wave JS.
Now it is just a single click on the “Configure” button to set up the Z-Wave JS integration and done! Super nice!
Support for USB discovery has currently been added to the Z-Wave JS and ZHA integrations.
Z-Wave JS Updates
If you are a Z-Wave siren/doorbell owner, you probably know how frustrating it was to wait for Home Assistant to add entity support for the Sound Switch CC (Command Class). This is caused by the blazing fast speed the upstream Z-Wave JS project is moving forward at; Often much faster than Home Assistant is able to keep up with.
It also might be that Home Assistant cannot (or is likely not to) support the specific command class you care about; Nevertheless, that shouldn’t stop you from being able to create automations for those devices!
In this release, we have introduced the new zwave_js.value_updated
automation
trigger type which will allow you to trigger an automation off of any
Command Class value that Z-Wave JS supports!
In order to leverage this trigger type in the UI, you will have to use device automations, but if you are writing your automations in YAML, you can use the trigger directly.
That’s not all for Z-Wave JS integration, we have more to share!
- Tired of your child flipping that switch that’s fully automated? Use the new
select
entity for the Protection Command Class to disable local access. - Don’t want to specify the tone and volume every time you activate your siren?
Now you have access to the default volume via a
number
entity and the default tone via aselect
entity. - We’ve made
zwave_js.*
services more flexible: They now support area IDs andgroup
entities as inputs! - We’ve made basic CC values directly controllable by moving them from using
sensor
entities to becomenumber
entities instead.
New template entities: Number and Select
Yes! We have new platforms you can utilize using the template integration!
Thanks to @raman325select
and number
entities! This unlocks quite the potential for creating some advanced
user interfaces :)
As an example says more than a thousand words, here are two examples that both are based on a WLED LED strip. It can be used to extract features from the WLED strip into their own entities.
# Example number entity that represents the effect speed on a WLED LED strip
# between 0 and 100%, translating it from an 0 to 255 scale.
template:
number:
- name: "Example number: WLED effect speed"
state: "{{ (( state_attr('light.wled', 'Speed') / 255) * 100) | round }}"
min: 0
max: 100
step: "{{ 1 }}"
set_value:
service: wled.effect
target:
entity_id: light.wled
data:
speed: "{{ (255 / 100) * value }}"
# Example select entity that extracts effects from a light.
# When you change the selected option, the effect of the light changes.
template:
select:
- name: "Example select: WLED effect"
state: "{{ state_attr('light.wled', 'effect') }}"
options: "{{ state_attr('light.wled', 'effect_list') }}"
select_option:
service: light.turn_on
target:
entity_id: light.wled
data:
effect: "{{ option }}"
Oh! And they can also be used with the new trigger templates! Check out the documentation for all options available.
New template functions for areas
Two new template functions have been added, making working with areas in YAML (when using templating) a little bit easier.
-
area_id("value")
returns the area ID for a given value. Thevalue
can be a device ID, entity ID, or area name. This function can also be used as a filter.example: "{{ area_id('light.living_room_tv') }}" example: "{{ area_id('Garden Shed') }}" example: "{{ trigger.entity_id | area_id }}"
-
area_name("value")
returns the area name for a given value. Thevalue
can be a device ID, entity ID, or area ID. This function can also be used as a filter.service: notify.frenck data: title: "Motion detected!" message: >- Motion has been detected in the {{ area_name(trigger.entity_id) }} area.
Thanks @raman325
Other noteworthy changes
There is much more juice in this release; here are some of the other noteworthy changes this release:
-
@balloob
added a lot more validations to the energy configuration UI and added more warning/error messages. @ludeeus made them look good by adding a beautiful new styling for these kind of messages. - Home Assistant offline and missed generating its energy/long statistics?
Not anymore! Home Assistant will now catch up on start, thanks @emontnemery
! - Thanks to @bdraco
, camera images can now be scaled to a resolution that fits the device/screen you are looking at; Additionally, they only update when visible. This makes cameras usable in any bandwidth situation. - The Shelly integration now supports transitions for lights! Thanks @bieniu
! - Yeelight now supports local push (instead of polling), awesome @starkillerOG
! -
@emontnemery
upgraded DSMR to support Swedish smart energy meters! Nice! - For Yamaha MusicCast, @micha91
has unlocked the Media Browser features! - The Rainforest Eagle will now provide pricing data if that is available,
thanks @balloob
! -
@giannello
added the ability to ask your Google Home where your vacuum cleaner is :) - If you use the shopping list feature of Home Assistant, you can now remove
all completed items at once using a service call. Thanks, @GrumpyMeow
! -
@bdraco
Added a new advanced feature for HomeKit, allowing to forward device events to HomeKit, unlocking the ability to trigger HomeKit automations or scenes. - Thanks to @ludeeus
, we can now use different brand images in the UI when it is in dark mode. - If you have a Sonos speaker, you can now modify the bass & treble level
using a service call, thanks @Tigger2014
! - Utility Meter cycles are now super flexible with the new cron patterns
option, nice @dgomes
! - Bond now provides new services to start/stop increasing/decreasing the
brightness of a light. Thanks @bdraco
!
New Integrations
We welcome the following new integrations this release:
-
AirTouch 4, added by @LonePurpleWolf
-
Fjäråskupan, added by @elupus
-
P1 Monitor, added by @klaasnicolaas
-
IoTaWatt, added by @gtdiehl
-
Tractive, added by @zhulik
-
USB Discovery, added by @bdraco
Integrations now available to set up from the UI
The following integrations are now available via the Home Assistant UI:
-
Nanoleaf, done by @milanmeu
-
Nmap Tracker, done by @bdraco
-
Rainforest EAGLE-200, done by @balloob
-
Uptime Robot, done by @ludeeus
Release 2021.9.1 - September 2
- Bump pyuptimerobot to 21.9.0 (@ludeeus
- #55546 ) (uptimerobot docs) - xiaomi_miio: bump python-miio dependency (@rytilahti
- #55549 ) (xiaomi_miio docs) - Pick right coordinator (@Adminiuga
- #55555 ) (zha docs) - Correct duplicate address. (@janiversen
- #55578 ) (modbus docs) - Downgrade sqlite-libs on docker image (@pvizeli
- #55591 )
Release 2021.9.2 - September 3
- Ignore missing devices when in ssdp unsee (@bdraco
- #55553 ) (ssdp docs) - Disable observer for USB on containers (@pvizeli
- #55570 ) (usb docs) - Fix CONFIG_SCHEMA validation in Speedtest.net (@mib1185
- #55612 ) (speedtestdotnet docs) - Narrow zwave_js USB discovery (@bdraco
- #55613 ) (zwave_js docs) - Fix template sensor availability (@balloob
- #55635 ) (template docs) - Better handle invalid trigger config (@balloob
- #55637 ) (hue docs) (device_automation docs) - Guard for unexpected exceptions in device automation (@balloob
- #55639 ) (device_automation docs) - Fix Starline sensor state AttributeError (@Anonym-tsk
- #55654 ) (starline docs) - Fix hdmi_cec switches (@ludeeus
- #55666 ) (hdmi_cec docs) - Guard for doRollover failing (@balloob
- #55669 )
Release 2021.9.3 - September 4
- better detect legacy eagly devices (@balloob
- #55706 ) (rainforest_eagle docs) - Handle negative numbers in sensor long term statistics (@emontnemery
- #55708 ) (sensor docs) - Handle Fritz InternalError (@chemelli74
- #55711 ) (fritz docs) - Fix LIFX firmware version information (@amelchio
- #55713 ) (lifx docs) - Fix SamsungTV sendkey when not connected (@chemelli74
- #55723 ) (samsungtv docs)
Release 2021.9.4 - September 6
- Fix switch name attribute for thinkingcleaner (@Joshi425
- #55730 ) (thinkingcleaner docs) - Fix logbook entity_matches_only query mode (@tathamoddie
- #55761 ) (logbook docs) - Allow same IP if ports are different on modbus (@janiversen
- #55766 ) (modbus docs) - Allow same address different register types in modbus (@janiversen
- #55767 ) (modbus docs) - Fix xiaomi miio Air Quality Monitor initialization (@bieniu
- #55773 ) (xiaomi_miio docs) - Fix incomfort min/max temperatures (@zxdavb
- #55806 ) (incomfort docs) - Upgrade pymazda to 0.2.1 (@bdr99
- #55820 ) (mazda docs) - Bump zwave-js-server-python to 0.30.0 (@MartinHjelmare
- #55831 ) (zwave_js docs) - Fix a lazy preset mode update for Xiaomi Miio fans (@bieniu
- #55837 ) (xiaomi_miio docs) - Fix typo in in rfxtrx Barometer sensor (@mrwhite31
- #55839 ) (rfxtrx docs) - Surepetcare, bug fix (@Danielhiversen
- #55842 ) (surepetcare docs) - Fix target humidity step for Xiaomi MJJSQ humidifiers (@bieniu
- #55858 ) (xiaomi_miio docs) - Fix exception during rediscovery of ignored zha config entries (@bdraco
- #55859 ) (zha docs) - Integration Sensor unit of measurement overwrite (@dgomes
- #55869 ) (integration docs)
Release 2021.9.5 - September 8
- Try to avoid rate limiting in honeywell (@rdfurman
- #55304 ) (honeywell docs) - Edit unit of measurement for gas/electricity supplier prices (@pascalwinters
- #55771 ) (dsmr_reader docs) - Integration Sensor Initial State (@dgomes
- #55875 ) (integration docs) - Fix available property for Xiaomi Miio fan platform (@bieniu
- #55889 ) (xiaomi_miio docs) - Allow multiple template.select platform entries (@raman325
- #55908 ) (template docs) - Bump aioswitcher to 2.0.5 (@thecode
- #55934 ) (switcher_kis docs) - Do not let one bad statistic spoil the bunch (@emontnemery
- #55942 ) (recorder docs) - Do not allow
inf
ornan
sensor states in statistics (@emontnemery- #55943 ) (sensor docs) - Fix handling of imperial units in long term statistics (@emontnemery
- #55959 ) (recorder docs) (sensor docs) - Fix gas validation (@balloob
- #55886 ) (energy docs) - Add support for state class measurement to energy cost sensor (@emontnemery
- #55962 ) (energy docs) - Add significant change support to AQI type sensors (@emontnemery
- #55833 ) (light docs) (google_assistant docs) (sensor docs)
Release 2021.9.6 - September 11
- Correct confusing log message in sensor statistics (@emontnemery
- #56016 ) (sensor docs) - Suppress last_reset deprecation warning for energy cost sensor (@emontnemery
- #56037 ) (sensor docs) - Fix UDP message handling by upgrading aiomusiccast to 0.9.2 (@micha91
- #56041 ) (yamaha_musiccast docs) - Bump amcrest version to 1.8.1 (@flacjacket
- #56058 ) (amcrest docs) - Fix singleton not working with falsey values (@balloob
- #56072 ) - Bump pymyq to 3.1.4 (@ehendrix23
- #56089 ) (myq docs)
Release 2021.9.7 - September 18
- Support incoming SMS messages via polling (@ocalvo
- #54237 ) (sms docs) - Fix generic thermostat switch state initialization (@brianegge
- #56073 ) (generic_thermostat docs) - Bump growattServer to 1.1.0 (@muppet3000
- #56084 ) (growatt_server docs) - Ensure rainmachine device name is a string (@bdraco
- #56121 ) (rainmachine docs) - Bump pykodi to 0.2.6 (@mxilievski
- #56148 ) (kodi docs) - Bump plexapi to 4.7.1 (@jjlawren
- #56163 ) (plex docs) - Update docker base image to 2021.09.0 (@ludeeus
- #56191 ) - Fix HomeKit requests with hvac mode and temperature in the same call (@bdraco
- #56239 ) (homekit docs) - Bump pyopenuv to 2.2.1 (@bachya
- #56270 ) (openuv docs) - Bump pychromecast to 9.2.1 (@emontnemery
- #56296 ) (cast docs) - Avoid sending Standby when already off (@elupus
- #56306 ) (philips_js docs) - Bump aioswitcher to 2.0.6 (@thecode
- #56358 ) (switcher_kis docs) - Fix yeelight nightlight mode (@bdraco
- #56363 ) (yeelight docs) - Fetch the data a second time when -9999 error occurs in Xiaomi Miio integration (@bieniu
- #56288 ) (xiaomi_miio 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
Supervisor update
Renaming snapshot to backup
“Snapshot” is a term that we have been using in the Supervisor since the beginning, but it’s not very descriptive for those that do not know what it is. Over the next few weeks, we will start using “backup” in all our software and documentation.
The functionality of it does not change, this is just a rename to make it more understandable.
Supervised installations
Having a supervisor does not make it a supervised installation, Home Assistant Operating System also has this, the information below does not apply to Home Assistant Operating System.
While we try not to break supervised installations, we do have a few things we need to change. These adjustments you have to manually apply to your installation. Without these adjustments you will start to see warnings in your logs, and your installation will eventually be marked as unsupported.
If you are interested to make changes required on supervised installations more maintainable, have a look at the blog on the developer site.
As an alternative to doing these adjustments, you can migrate your installation to Home Assistant Operating System.
Bullseye
Two weeks ago Debian 11 (Bullseye) was released. The upcoming version of the Supervisor will recognize that version as a supported Operating System. This means that if you are running Home Assistant Supervised, you can start upgrading that.
Support for the previous version (Debian 10 (Buster)) is now deprecated and will be removed in the first version of the Supervisor after the 4 months grace period. This means that within the next 4 months you need to update to Debian 11.
Environment variables
There are a few environment variables that you have to add in order to make the Supervisor work properly with newer versions of the Supervisor. These variables have to be added to the run command for the Supervisor container, on most installations this is a script called from a service file.
-
SUPERVISOR_SHARE
- The path to the directory for the Supervisor data files, typically/usr/share/hassio
. -
SUPERVISOR_NAME
- The name of the supervisor container, typicallyhassio_supervisor
-
SUPERVISOR_MACHINE
- The machine you are using. For a list of machine types, have a look here
OS Agent
Recently, we created an OS Agent
If you you are interested we have also just published a blog on the developer site.
Energy Management in Home Assistant
TL; DR: We’re adding energy management and it’s awesome. Created two products to read out electricity meters: SlimmeLezer
The world is in a climate crisis. Global warming is a reality and the weather is getting unpredictable. Our way of living needs to change, at all levels. I am worried that the climate crisis is something that the world is going to try to solve too late and after irreversible damages have already been done.
So with Home Assistant we want to do our part to help take on the climate crisis, and help you do the same. One part of fighting the climate crisis is making sure our homes are energy efficient and use low-carbon energy sources.
Starting today, Home Assistant is adding official support for home energy management. Our energy management will help users monitor the energy usage, transition to sustainable energy and save money.
Home automation and energy management are built on top of knowing what devices are doing
Energy management and Home Assistant in context
Bill Gates was recently interviewed by Marques Brownlee (MKBHD) and talked about how intelligent homes are needed to make smart cities. And how all of this starts with energy management in the home. The interview is 3 minutes and worth watching:
Home Assistant won’t have all the answers when it comes to energy management, at least not right away. But we have two key things going for us that makes us the perfect platform to choose for your energy management:
The first is that we’re completely open. This means that with Home Assistant, anyone can use the source
The second thing is that we have a passionate and global community that wants to make their homes the best it can be. A community that revolves around building and sharing their own hardware and software to be able to achieve their goals. Through experimentation and iteration we will be able to improve energy management over time to fit our needs – there are no investors to satisfy.
When it comes to your home, Home Assistant is the best platform to manage it and figure out what works and what doesn’t.
Read on →2021.8.0: Feel the energy ⚡️
Happy August! ☀️
Home Assistant Core 2021.8 is here, and this is the release I have been looking forward to for months! There is so much exciting new stuff in here: I don’t know where to start.
The most exciting part is the new main focus that is added to Home Assistant:
Home Energy management.
A massive deal for a lot of people, no matter if you are doing it for environmental reasons or simply to save a buck or two (or both 😬). Knowing that moving forward, it will be an additional focus, I think, is amazing.
But besides the Energy management stuff, I’m also excited about the side effects of it. A lot of things created for Energy, are also re-usable for other things! That is how we roll, right?
We get long-term statistics, new super nice and fast graphs, and a new layout option for Lovelace. All the building blocks are available for customization and re-use. I am looking forward to seeing how they are going to be put to use.
Anyways, enjoy the release! And don’t forget the drop by
the release party on YouTube
../Frenck
- Matthias de Baat joins Nabu Casa
- Home Energy Management!
- Long term statistics
- Sidebar view
- Gauge card now has needle mode
- Currency core setting
- Siren
- Locking, Unlocking and Jammed
- Scripts/Automations/Templates
- Other noteworthy changes
- New Integrations
- New Platforms
- Integrations now available to set up from the UI
- Release 2021.8.1 - August 4
- Release 2021.8.2 - August 5
- Release 2021.8.3 - August 6
- Release 2021.8.4 - August 8
- Release 2021.8.5 - August 9
- Release 2021.8.6 - August 10
- Release 2021.8.7 - August 15
- Release 2021.8.8 - August 18
- If you need help…
- Backward-incompatible changes
- Farewell to the following
- All changes
Matthias de Baat joins Nabu Casa
Let start by announcing that Matthias de Baat
UX stands for “User Experience”, which is Matthias’ area of expertise and what he will be working on improving. His goal is to make Home Assistant easier to use and accessible for everyone. He will be setting up design processes and tooling, doing user research and making designs.
If you are interested in joining the Home Assistant user research group, you
can show your interest by filling in this Google Form
Welcome Matthias! Excited to have you on board!
But wait! There is more!
[Otto Winter][@ottowinter], the founder of ESPHome
Home Energy Management!
This feature is a big thing; A start of something new. Home Assistant is going to provide you insight into your energy usage.
But this needs more than just a paragraph in the release notes, this needs its own blog! So, at this point, stop reading the release notes (momentarily) and read the blog Paulus has written about this:
Read the blog about the new Home Energy Management features of Home Assistant
Long term statistics
Storing sensor data for a more extended period using the recorder, can make your database grow pretty fast (especially if you have sensors that update a lot!).
In the previous releases, we’ve worked towards improving this situation and laid down the groundwork for tracking statistics in the database; We are making it widely available this release!
Integrations can now hint Home Assistant about the type of value the sensor represents, allowing us to process and store that data in a more efficient way. Every hour, we calculate things like mean, min/max values, or the difference created that hour and store just that result in our long-term statistics.
These statistics is what partly powers the new Energy dashboard, however, they can be used for anything else: Introducing the Lovelace statistics graph card.
Screenshot of the new Lovelace statistics graph card.
This card can make beautiful graphs, allowing you to make graphs for any of
your stored long-term statistical data. It can render as a line or bar chart.
Bars are suited for metered
entities that have a summed value. Lines are
perfect to display the mean
, min
and max
of the entity.
The support for long-term statistics is limited at this moment. We are expecting to open it up for more measurements in the upcoming releases while more integrations are adding support for these new measurement types.
Sidebar view
The default layout you see in Lovelace (which we generally all use), is called the “masonry” layout. We also have a panel view/layout that stretches a single card to the whole view. This release brings in a brand new view layout: Sidebar.
This new sidebar view has two columns, a wide one and a small one on the right. It is perfect for displaying larger cards like graphs (like that nice new statistics graph card), or maps. While having some additional smaller cards with information on the side.
The new Energy dashboard uses this new view layout, but of course, made available for use in other Lovelace dashboards as well.
Screenshot of new Lovelace sidebar view layout.
Gauge card now has needle mode
A nice little addition to the Lovelace gauge card: Needle mode!
Instead of showing a value and filling it partially, in needle mode, it will show the full gauge but point out the value with a needle. And, if you add severity to your gauge card configuration, it will always be shown.
Screenshot of the Gauge card in needle mode with severity configured.
These settings are available straight from the Lovelace UI editor; More information and examples can be found in the Gauge card documentation.
Currency core setting
To support the display of financial values, we’ve added a new setting to Home Assistant that allows you to define the currency Home Assistant should use in cases it relies on your input.
You can find this new currency setting in the general settings of Home Assistant.
This setting is used for the cost calculation of the new energy features.
Siren
The last release, we introduced the select
entity,
this release, we introduce the siren
entity! 🚨
Thanks to @raman325
Locking, Unlocking and Jammed
Locks in Home Assistant can be a little bit smarter as of today, thanks
to @bdraco
Support for these new states has been added to the August, HomeKit Controller and template integrations. Additionally, HomeKit, Alexa and Google Assistant have been made compatible and aware for these states as well.
Scripts/Automations/Templates
Some new features landed for script, automations and templates this release.
This
When an automation or script is triggered to run, a new variable is available:
this
. This variable contains the state object
of the automation or script running and allows you to access information about
the automation directly. Thanks, @r-t-s
Device template functions
If you like to write YAML automations manually, are using templates, and require device IDs or device information, than you know those IDs are hard to find and the device information is not available at all.
@raman325
-
device_entities(device_id)
returns a list of entities associated with a given device ID (can also be used as a filter). -
device_attr(device_or_entity_id, attr_name)
returns the value ofattr_name
for the given device ID or entity ID. -
is_device_attr(device_or_entity_id, attr_name, attr_value)
returns whether the value ofattr_name
for the given device ID or entity ID matchesattr_value
. -
device_id(entity_id)
returns the device ID for a given entity ID (can also be used as a filter).
Thanks for these powerful new features!
Other noteworthy changes
There is much more juice in this release; here are some of the other noteworthy changes this release:
- Thanks to @firstof9
, Z-Wave JS now has support for transitions with lights! - More Z-Wave JS improvements by @raman325
. He added support for device triggers and conditions. Thanks! - You can now assign a unique ID to light, cover and media player groups, allowing you to manage them from the Home Assistant frontend and assign them to an area!
- The motionEye integration now has support for motion detection, thanks @dermotduffy
- ZHA can now work with Formaldehyde and VOC level sensors, thanks @Adminiuga
-
@posixx
added a new feature for integration that provide alarm panels; those integrations can now update to support Vacation mode! - Rainbird now has a service to change the rain delay, thanks @Kr0llx
! - If you are using BMW Connected Drive, @EddyK69
added a lot of trip sensors. - Sonos snapshots now behave, are more robust and work as expected. Additionally,
support for controlling crossfade has been added, thanks @jjlawren
! - WLED now supports controlling the new playlists features introduced in WLED 0.13.
-
@farmio
added support for KNX lights that use HS-colors, thanks! - And @joncar
added support for transitions to LiteJet lights, awesome! - If you have MFA on your Tesla account, thanks to @BreakingBread0
, the integration now supports that. - When using the Netatmo integration, you can now control the schedule it
should be using with a select entity. Thanks, @cgtobi
! -
@janiversen
added more data types to modus and added array write to the turn on/off capabilities of Modbus switches, fans and lights. - Advantage Air now has temperature sensors for each zone, thanks @Bre77
! - Gree Climate now has switches to support more modes, thanks to @cmroche
! - You can now remove holidays from the workday sensor by name instead of
date. This is useful for holidays they don’t have a fixed date each year.
Thanks @matthewgottlieb
! - HomeKit will not auto-recreated TVs when sources are out of sync. One thinsg
less to worry about, thanks @bdraco
-
@jbouwh
has drastically reworked and extended the Humidifier support for the Xiaomi Miio integration. Amazing job!
New Integrations
We welcome the following new integrations this release:
-
Adax, added by @Danielhiversen
- Energy, added by the Home Assistant Core team
-
Flipr, added by @cnico
-
Generic Hygrostat, added by @Shulyaka
-
Prosegur, added by @dgomes
-
Siren, added by @raman325
-
YouLess, added by @gjong
-
Renault, added by @epenet
New Platforms
The following integration got support for a new platform:
-
Belkin WeMo added sensors for energy usage. Added by @esev
-
Freedompro now supports binary sensors, sensors, switches, locks, covers, climate and fans! Added by @stefano055415
-
GIOŚ now has sensors for replacing the air quality platform, added by @bieniu
-
Goal Zero Yeti, added sensors that provide a lot of information, added by @tkdrob
-
Itho Daalderop Spider, added sensors for energy usages. Added by @peternijssen
-
Mill, added support for sensors for its energy consumption, added by @Danielhiversen
-
motionEye now exposes switches, added by @dermotduffy
-
TP-Link Kasa Smart added sensors for energy usage. Added by @mib1185
-
Velux now supports lights, added by @bramstroker
-
Z-Wave JS now supports sirens, added by @raman325
Integrations now available to set up from the UI
The following integrations are now available via the Home Assistant UI:
-
CO2 Signal, done by @Danielhiversen
-
Honeywell Total Connect Comfort (US), done by @rdfurman
-
Notifications for Android TV / Fire TV, done by @tkdrob
-
Switcher, done by @thecode
-
Yale Smart Living, done by @gjohansson-ST
Release 2021.8.1 - August 4
- Fix Panasonic Viera TV going unavailable when turned off (@Hyralex
- #53788 ) (panasonic_viera docs) - Add temporary fix to modbus to solve upstream problem (@janiversen
- #53857 ) (modbus docs) - Fix attr_unit_of_measurement in update of apcupsd entity (@mib1185
- #53947 ) (apcupsd docs) - Fix coordinator not defined in yale_smart_alarm (@gjohansson-ST
- #53973 ) (yale_smart_alarm docs) - Fix divider for Fritz sensors (@chemelli74
- #53980 ) (fritz docs) - Fix empty sonos_group entity attribute on startup (@jjlawren
- #53985 ) (sonos docs) - Update frontend to 20210804.0 (@bramkragten
- #53997 ) (frontend docs)
Release 2021.8.2 - August 5
- Bump pylitterbot to 2021.8.0 (@natekspencer
- #54000 ) (litterrobot docs) - Add missing device class to SAJ energy sensors (@frenck
- #54048 ) (saj docs) - Handle empty software version when setting up HomeKit (@bdraco
- #54068 ) (homekit docs) - Bump up ZHA dependencies (@puddly
- #54079 ) (zha docs) - Packages to support config platforms (@balloob
- #54085 ) (automation docs) (script docs) (template docs) - Fix Shelly last_reset (@thecode
- #54101 ) (shelly docs) - Two fixes (@chemelli74
- #54102 ) (fritz docs) - Increase time before scene and script HomeKit entities are reset (@bdraco
- #54105 ) (homekit docs) - Bump zeroconf to 0.33.3 (@bdraco
- #54108 ) (zeroconf docs)
Release 2021.8.3 - August 6
- Gracefully handle additional GSM errors (@ocalvo
- #54114 ) (sms docs) - Handle software version being None when setting up HomeKit accessories (@nzapponi
- #54130 ) (homekit docs) - Fix sensor PLATFORM_SCHEMA for ebox and enphase_envoy (@mib1185
- #54142 ) (enphase_envoy docs) - Fetch interface index from network integration instead of socket.if_nametoindex in zeroconf (@bdraco
- #54152 ) (zeroconf docs) (network docs) - Bump zeroconf to 0.33.4 to ensure zeroconf can startup when ipv6 is disabled (@bdraco
- #54165 ) (zeroconf docs)
Release 2021.8.4 - August 8
- Add missing
motor_speed
sensor for Xiaomi Miio humidifier CA1 and CB1 (@bieniu- #54202 ) - Fix update entity prior to adding (@Trinnik
- #54015 ) (aladdin_connect docs) - Fix androidtv media_image_hash (@tkdrob
- #54188 ) (androidtv docs) - Solve missing automatic update of struct configuration in modbus (@janiversen
- #54193 ) (modbus docs) - Update const.py (@Mk4242
- #54195 ) (ebusd docs) - Add parameter to delay sending of requests in modbus (@janiversen
- #54203 ) (modbus docs) - Bugfix: Bring back unique IDs for ADS covers after #52488 (@carstenschroeder
- #54212 ) (ads docs) - Don’t block motionEye setup on NoURLAvailableError (@dermotduffy
- #54225 ) (motioneye docs) - Pin google-cloud-pubsub to an older version (@allenporter
- #54239 )
Release 2021.8.5 - August 9
- Fix camera state and attributes for agent_dvr (@tkdrob
- #54049 ) (agent_dvr docs) - Force an attempted subscribe on speaker reboot (@geuben
- #54100 ) (sonos docs) - Fix login to BMW services for rest_of_world and north_america (@rikroe
- #54261 ) (bmw_connected_drive docs) - Always set interfaces explicitly when IPv6 is present (@bdraco
- #54268 ) (zeroconf docs) - Fix atom integration for long term statistics (@ZeGuigui
- #54285 ) (atome docs) - Use correct state attribute for alarmdecoder binary sensor (@tkdrob
- #54286 ) (alarmdecoder docs) - Bump soco to 0.23.3 (@jjlawren
- #54288 ) (sonos docs) - Fix ondilo_ico name attribute (@cdce8p
- #54290 ) (ondilo_ico docs) - Bump zeroconf to 0.34.3 (@bdraco
- #54294 ) (zeroconf docs) - Ensure hunterdouglas_powerview model type is a string (@bdraco
- #54299 ) (hunterdouglas_powerview docs) - Remove zwave_js transition on individual color channels (@firstof9
- #54303 ) (zwave_js docs) - Restores unit_of_measurement (@dgomes
- #54335 ) (integration docs) - Fix xiaomi air fresh fan preset modes (@jbouwh
- #54342 ) (xiaomi_miio docs) - Update frontend to 20210809.0 (@bramkragten
- #54350 ) (frontend docs) - Fix Xiaomi-miio turn fan on with speed, percentage or preset (@jbouwh
- #54353 ) (xiaomi_miio docs) - Fix aqualogic state attribute update (@dailow
- #54354 ) (aqualogic docs) - Cast SimpliSafe version number as a string in device info (@bachya
- #54356 ) (simplisafe docs) - Do not process forwarded for headers for cloud requests (@balloob
- #54364 ) (http docs) (cloud docs) - Revert “Use entity class attributes for Bluesound (#53033)” (@balloob
- #54365 ) (bluesound docs) - Update Climacell rate limit (@raman325
- #54373 ) (climacell docs) - Fix race condition in Advantage Air (@Bre77
- #53439 ) (advantage_air docs)
Release 2021.8.6 - August 10
- Handle CO2Signal response value being None (@balloob
- #54377 ) (co2signal docs) - Fix Canary sensor state (@ludeeus
- #54380 ) (canary docs) - Re-add Tibber notify service name (@Danielhiversen
- #54401 ) (tibber docs) - Bump hass_nabucasa to 0.46.0 (@balloob
- #54421 ) (cloud docs) - Bump pyopenuv to 2.1.0 (@bachya
- #54436 ) (openuv docs)
Release 2021.8.7 - August 15
- Use pycarwings2 2.11 (@filcole
- #54424 ) (nissan_leaf docs) - Fix Huawei LTE entity state updating (@scop
- #54447 ) (huawei_lte docs) - Strip attributes whitespace in universal media_player (@0xFelix
- #54451 ) (universal docs) - Bump notifications-android-tv to 0.1.3 (@tkdrob
- #54462 ) (nfandroidtv docs) - Updates to bump MyQ to 3.1.2 (@ehendrix23
- #54488 ) (myq docs) - Add missing PRESSURE_BAR conversion (@Danielhiversen
- #54497 ) - Treat temporary errors as warnings for Tesla (@alandtse
- #54515 ) (tesla docs) - Fix attributes not showing after using entity class attributes (@gerard33
- #54558 ) (bmw_connected_drive docs) - Upgrade qnapstats library to 0.4.0 (@colinodell
- #54571 ) (qnap docs) - Fix bug in ambiclimate (@Danielhiversen
- #54579 ) (ambiclimate docs) - Fix Tibber last reset (@Danielhiversen
- #54582 ) (tibber docs) - Adax, update requirements (@Danielhiversen
- #54587 ) (adax docs) - Clamp color temperature to supported range in ESPHome light (@oxan
- #54595 ) (esphome docs) - Bump zeroconf to 0.35.0 (@bdraco
- #54604 ) (zeroconf docs) - Bump py-synologydsm-api to 1.0.4 (@mib1185
- #54610 ) (synology_dsm docs) - Guard partial upgrade (@balloob
- #54617 ) (http docs) - Solve switch/verify register type convert problem in modbus (@janiversen
- #54645 ) (modbus docs) - Send color_brightness to ESPHome devices on 1.20 (pre-color_mode) (@jesserockz
- #54670 ) (esphome docs)
Release 2021.8.8 - August 18
- Fix TPLink emeter reset not updating (@TomBrien
- #54848 ) (tplink docs) - Fix tplink doing I/O in event loop and optimize (@rytilahti
- #54570 ) (tplink docs) - Fix ‘in’ comparisons vesync light (@cdce8p
- #54614 ) (vesync docs) - Update PyMetEireann to 2021.8.0 (@DylanGore
- #54693 ) (met_eireann docs) - Fix BMW remote services in rest_of_world & north_america (@rikroe
- #54726 ) (bmw_connected_drive docs) - Fix HomeKit cover creation with tilt position, open/close, no set position (@bdraco
- #54727 ) (homekit 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
2021.7: A new entity, trigger IDs and script debugging
Happy July, which means Home Assistant Core 2021.7!
An interesting release, with a bunch of little goodies to make things easier in creating automations, scripts and doing templating. Those are things that in general, make me very happy. Mainly because, well, I use Home Assistant to automate 😁
Also, we are saying “hi!” 👋 to a new type of entity, which is really exciting and I can’t wait to see how that is being put to use in the future.
Lastly, I want to give a shout-out to @klaasnicolaas
His internship is now over, and he passed with a nice grade. Yet, he could not leave without a little present as it seems. He contributed the Forecast.Solar integration, bringing in energy production forecasting for your solar panels. Really cool!
Alright, that’s it! Enjoy the release!
../Frenck
- New entity: Select
- Trigger conditions and trigger IDs
- Script debugging
- Referencing other entities in triggers and conditions
- Working with dates in templates
- Series version tags for Docker containers
- Other noteworthy changes
- New Integrations
- New Platforms
- Integrations now available to set up from the UI
- Release 2021.7.1 - July 8
- Release 2021.7.2 - July 12
- Release 2021.7.3 - July 16
- Release 2021.7.4 - July 21
- If you need help…
- Backward-incompatible changes
- All changes
New entity: Select
In this release, we welcome the select
entity to the Home Assistant family. The
select entity is a close relative of the dropdown helper (also known as
input_select
).
The difference is that while the input select is configured and managed by you, the select entities are provided by integrations.
This means integrations can now provide entities that give a choice. Either in the Lovelace UI, but also via automations using services, and via the Google Assistant.
Screenshot of a select entity, providing a choice from a list of options.
Some integrations started implementing the first select entities as of this release. MQTT & KNX made it available for use, WLED uses it to provide controls on selecting and activating a user preset, and with Rituals Perfume Genie you can now change the room size for your diffuser.
Trigger conditions and trigger IDs
If you are creating some complex automations in YAML, you might be familiar with this. Consider a big automation, with a whole bunch of triggers. But how would you know which of those triggers actually triggered the automation?
You can now assign an id
to your triggers that is passed into automation when
triggered, allowing you to make decisions on it.
automation:
- alias: "Trigger IDs!"
trigger:
- platform: state
id: "normal"
entity_id: binary_sensor.gate
state: "on"
- platform: state
id: "forgotten"
entity_id: binary_sensor.gate
state: "on"
for:
minutes: 10
...
The above example triggers the same automation twice, when the gate opens and when the gate is left open for 10 minutes (probably forgotten). Each trigger has its own ID.
Now introducing the new trigger condition! So you can add a condition on which trigger fired the automation.
automation:
- alias: "Trigger IDs!"
...
action:
...
- condition: trigger
id: "forgotten"
- service: notify.frenck_iphone
data:
message: "Someone left the gate open..."
You can use the trigger condition in all places where all the other conditions work as well, including things like choose from a group of actions.
Rather use the UI to create and manage your automations? No problem! These new features have been added to the automation editor as well!
Screenshot of using a trigger condition in the automation editor.
Script debugging
In Home Assistant Core 2021.4, we added the ability to debug automations. In this release, we’ve made these same powerful tools available for scripts!
So, this helps for the next time you are wondering: Why didn’t that script work? Or why did it behave as it did? What the script is going on here?
Screenshot of using the new script debugger on my office announce script.
The above screenshot shows a previous run of a script, using an interactive graph for each step in this script; with the path it took highlighted. Each node in the graph can be clicked to view the details of what happened on each step in the script sequence.
Referencing other entities in triggers and conditions
A small, but possibly helpful, change to our script and automations. You can now reference other entities for the above/below values of numeric state triggers and conditions. Both sensors and number entities can be used.
For example, you can now trigger an automation if the outside temperature is higher than the temperature inside.
automation:
- alias: "Notify to close the window"
trigger:
- platform: numeric_state
entity_id: sensor.outside_temperature
above: sensor.inside_temperature
action:
- service: notify.frenck_iphone
data:
message: "Close all windows, it is warm outside!"
The numeric state conditions supports the same.
Additionally, the time conditions now support a similar thing using other sensors that provide a time in the before and after options. Time triggers added support for that already in a previous release.
Working with dates in templates
If you ever tried to work with dates in templates, you probably know that that is hard. And honestly, that will never go away, times, dates and timezones are complex little beasts.
However, we realized that the hardest part of using date & times with templates
is converting the state of a sensor or text to a datetime. This
release adds a small template method to help with that: as_datetime
.
It can be used as a filter or as a method. Here is an example of calculating the number of days until my drivers’ license expires:
{{ (states('sensor.drivers_license') | as_datetime - now()).days }} days
Series version tags for Docker containers
If you are using the Home Assistant Container installation method, we recommend using a specific version tag; however, that means you need to update the version tag each time we release a new patch version of Home Assistant.
Thanks to @kmdm
docker pull ghcr.io/home-assistant/home-assistant:2021.7
The 2021.7
, will contain the latest July release, even if that is
actually version 2021.7.2
.
Other noteworthy changes
There is much more juice in this release; here are some of the other noteworthy changes this release:
- Z-Wave JS got quite a few updates this release:
- A new
zwave_js.multicast_set_value
is available, allowing to issue a set value command via multicast. Thanks, @raman325! - Each node now has a status sensor available and can be pinged using the
new
zwave_js.ping
service. Added by @raman325. - The Z-Wave JS configuration panel now has a “Heal Network” button,
thanks @cgarwood
! - Z-Wave JS Server connection can now be re-configured from the Z-Wave JS
configuration panel, added by @MartinHjelmare
. - Z-Wave JS logs can now be downloaded, thanks @raman325
!
- A new
- The Google Assistant integration now has support for fan speed percentages and
preset modes. Thanks, @jbouwh
! -
@jbouwh
didn’t stop there and added fan preset mode support to Alexa too! - The Philips TV integration now supports Ambilights, added by @elupus
. - Yamaha MusicCast integration now supports grouping services, thanks @micha91
! -
@raman325
added a whole bunch of sensors to the ClimaCell integration! - WLED now supports local push. Updates are now instantly both ways. Also, the master light can be kept and added support for controlling user presets.
- Setting up Xiaomi devices has gotten way easier! There is no need to do
difficult things to get the tokens. Instead, Home Assistant can now extract
the tokens from a Xiaomi Cloud account. Thanks, @starkillerOG
! - More Xiaomi updates, @jbouwh
added support for fan percentage-based speeds and preset modes. -
@RenierM26
added a lot of new services to the Ezviz integration, thanks! - Tibber had quite a few improvements and now provides a power factor sensor,
added by @Danielhiversen
! - Google Translate TTS now supports the Bulgarian language,
thanks @hristo-atanasov
! - If you have a SmartTube, you can now reset your reminders, thanks @mdz
! - KNX had quite a lot of updates and added support for XY-color lights,
thanks @farmio
. -
@OttoWinter
added support for presets, custom presets and custom fan modes for climate controls in ESPHome. Awesome! - Nuki now has a service to enable/disable continuous mode, thanks @anaisbetts
! -
@cgomesu
added quantiles to Statistics integration, thanks! - The Home Assistant login page now better support password manager,
thanks, @rianadon
!
New Integrations
We welcome the following new integrations this release:
-
Ambee, added by @frenck
-
Forecast.Solar, added by @klaasnicolaas
-
Freedompro, added by @stefano055415
-
Modern Forms, added by @wonderslug
-
Select, added by @frenck
New Platforms
The following integration got support for a new platform:
-
AVM FRITZ!Box Tools now has switches available, added by @chemelli74
-
Bosch SHC has now several sensors for their devices, added by @tschamm
-
Groups now support creating Media Player groups, added by @definitio
-
Hyperion can now provide a camera feed with the live image, added by @dermotduffy
-
KNX added support for number and the new select entities, added by @farmio
-
Meteoclimatic now provides sensors with weather information, added by @adrianmo
-
MQTT got support for the new select entities, added by @emontnemery
-
Rituals Perfume Genie added a number and select entity to adjust your diffuser, added by @milanmeu
-
SIA Alarm Systems now provides various binary sensors, added by @eavanvalkenburg
-
Sony Bravia TV now offers a remote entity, added by @Drafteed
-
Switcher now provides sensors, added by @thecode
-
WLED now exposes color palettes and presets using select entities, added by @frenck
Integrations now available to set up from the UI
The following integrations are now available via the Home Assistant UI:
-
Coinbase, done by @TomBrien
-
DSMR Slimme Meter, done by @RobBie1221
-
Yamaha MusicCast, done by @vigonotion
Release 2021.7.1 - July 8
- Fix service registration typo in Nuki integration (@anaisbetts
- #52631 ) (nuki docs) - Fix Fritz default consider home value (@chemelli74
- #52648 ) (fritz docs) - Handle KeyError when accessing device information (@ludeeus
- #52650 ) (ecovacs docs) - Warn if
interface_addr
remains in Sonos configuration (@jjlawren- #52652 ) (sonos docs) - Ignore unused keys from Sonos device properties callback (@jjlawren
- #52660 ) (sonos docs) - Ensure Forecast.Solar returns an iso formatted timestamp (@frenck
- #52669 ) (forecast_solar docs) - Use iso-formatted times in MetOffice weather forecast (@avee87
- #52672 ) (metoffice docs) - Fix precipitation calculation for hourly forecast (@agners
- #52676 ) (openweathermap docs) - Move recorder.py import to runtime (@uvjustin
- #52682 ) (stream docs) - Bump simplisafe-python to 11.0.1 (@bachya
- #52684 ) (simplisafe docs) - pyWeMo version bump (0.6.5) (@esev
- #52701 ) (wemo docs) - Bump pylutron to 0.2.8 fixing python 3.9 incompatibility (@JonGilmore
- #52702 ) (lutron docs) - Add check for _client existence in modbus (@janiversen
- #52719 ) (modbus docs) - Fix KNX Fan features (@Tommatheussen
- #52732 ) (fan docs) - Esphome fix camera image (@jesserockz
- #52738 ) (esphome docs)
Release 2021.7.2 - July 12
- Ignore Sonos Boost devices during discovery (@jjlawren
- #52845 ) (sonos docs) - Add zeroconf discovery to Sonos (@bdraco
- #52655 ) (sonos docs) - Remove scale calculation for climacell cloud cover (@apaperclip
- #52752 ) (climacell docs) - Fix homebridge devices becoming unavailable frequently (@Jc2k
- #52753 ) (homekit_controller docs) - Fix nexia thermostats humidify without dehumidify support (@bdraco
- #52758 ) (nexia docs) - Support certain homekit devices that emit invalid JSON (@Jc2k
- #52759 ) (homekit_controller docs) - Send ssdp requests to ipv4 broadcast as well (@bdraco
- #52760 ) (ssdp docs) - Bump dependency to properly handle current and voltage not being reported on some zhapower endpoints (@Kane610
- #52764 ) (deconz docs) - Upgrade pymazda to 0.2.0 (@bdr99
- #52775 ) - Fix ESPHome Camera not merging image packets (@OttoWinter
- #52783 ) (esphome docs) - Fix Neato parameter for token refresh (@chemelli74
- #52785 ) (neato docs) - Add the Trane brand to nexia (@bdraco
- #52805 ) (nexia docs) - Bump python-fireservicerota to 0.0.42 (@cyberjunky
- #52807 ) (fireservicerota docs) - Bump up ZHA depdencies (@Adminiuga
- #52818 ) (zha docs) - Update arcam lib to 0.7.0 (@elupus
- #52829 ) (arcam_fmj docs) - Bump aiohomekit to 0.5.1 to solve performance regression (@bdraco
- #52878 ) (homekit_controller docs) - Bump pyhaversion to 21.7.0 (@ludeeus
- #52880 ) (version docs) - Prefer using xy over hs when supported by light (@Kane610
- #52883 ) (deconz docs) - Bump zwave-js-server-python to 0.27.1 (@raman325
- #52885 ) (zwave_js docs) - Surepetcare, fix set_lock_state (@Danielhiversen
- #52912 ) (surepetcare docs) - Bump pyinsteon to 1.0.11 (@teharris1
- #52927 ) (insteon docs) - Fix recorder purge with sqlite3 < 3.32.0 (@bdraco
- #52929 ) - Bump pysonos to 0.0.52 (@jjlawren
- #52934 ) (sonos docs)
Release 2021.7.3 - July 16
- Update ZHA to support zigpy 0.34.0 device initialization (@puddly
- #52610 ) (zha docs) - copy() –> deepcopy(). (@janiversen
- #52794 ) (modbus docs) - only allow one active call in each platform. (@janiversen
- #52823 ) (modbus docs) - Bump pyatv to 0.8.1 (@doug-hoffman
- #52849 ) (apple_tv docs) - Handle dhcp packets without a hostname (@bdraco
- #52882 ) (dhcp docs) - Add OUIs for legacy samsungtv (@bdraco
- #52928 ) (samsungtv docs) - Bump python-fireservicerota to 0.0.43 (@cyberjunky
- #52966 ) (fireservicerota docs) - More graceful exception handling in Plex library sensors (@jjlawren
- #52969 ) (plex docs) - Fix issue connecting to Insteon Hub v2 (@teharris1
- #52970 ) (insteon docs) - Bump pysma to 0.6.4 (@rklomp
- #52973 ) (sma docs) - Update pyrainbird to 0.4.3 (@peternijssen
- #52990 ) (rainbird docs) - Bump pypck to 0.7.10 (@alengwenus
- #53013 ) (lcn docs) - fix for timestamp not present in SIA (@eavanvalkenburg
- #53015 ) (sia docs) - Co2signal, set SCAN_INTERVAL (@Danielhiversen
- #53023 ) (co2signal docs) - Another SIA fix for timestamp not present. (@eavanvalkenburg
- #53045 ) - Fix knx expose feature not correctly falling back to default value (@da-anda
- #53046 ) (knx docs) - Expose Spotify as a service (@balloob
- #53063 ) - Increase polling interval to prevent reaching daily limit (@vlebourl
- #53066 ) (home_plus_control docs) - Add light white parameter to light/services.yaml (@emontnemery
- #53075 ) (light docs)
Release 2021.7.4 - July 21
- Allow pymodbus to reconnect in running system (not startup) (@janiversen
- #53020 ) (modbus docs) - Fix groups reporting incorrect supported color modes (@Kane610
- #53088 ) (deconz docs) - Handle all WeMo ensure_long_press_virtual_device exceptions (@esev
- #53094 ) (wemo docs) - Fix remote rpi gpio input type (@jgriff2
- #53108 ) (remote_rpi_gpio docs) - More restrictive state updates of UniFi uptime sensor (@Kane610
- #53111 ) (unifi docs) - Bump simplisafe-python to 11.0.2 (@bachya
- #53121 ) (simplisafe docs) - Bump nexia to 0.9.10 to fix asair login (@bdraco
- #53122 ) (nexia docs) - Bump surepy to 0.7.0 (@benleb
- #53123 ) (surepetcare docs) - Upgrade pysonos to 0.0.53 (@amelchio
- #53137 ) (sonos docs) - Correctly detect is not home (@balloob
- #53279 ) (device_tracker docs) - Upgrade to async-upnp-client==0.19.1 (@StevenLooman
- #53288 ) (dlna_dmr docs) (ssdp docs) (upnp docs) - Fix homekit locks not being created from when setup from the UI (@bdraco
- #53301 ) (homekit 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
Community Highlights: 27th edition
The 27th edition of the Home Assistant Community Highlights! Some interesting things popped up around our community, which we thought was worth sharing.
But first I have one more announcement. My internship is (almost) over and I’m happy to say that I passed and completed it with a good grade. That also means that this community highlight is the last one from me as an intern, time will tell when the next one will appear.
Do you want to share something for the next edition? Information on how to share.
./Klaas
Intern on Home Assistant Energy
Blueprint of the week
This week’s blueprint is that of bfranke1973, who has created a blueprint with which you can receive a notification when a device loses connection with the network. Try it out! Read more about it on the community forum or install this automation in your instance with a click on the My button!
Love Lock Card
Do you ever accidentally turn on a light or switch? Then try the
love lock card
Lovelace Dashboard
This week again we have a new Lovelace dashboard for the necessary portion
of inspiration 😄 This time the one from swake88
Would you also like your dashboard to be in the community highlight? Drop it
on Reddit
Statistic Tools
Home Assistant has a number of tools for working with statistics, but the
question is how can you best approach this. Carlos
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:
- Tweet 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!
Community Highlights: 26th edition
The 26th edition of the Home Assistant Community Highlights! Some interesting things popped up around our community, which we thought was worth sharing.
Do you want to share something for the next edition? Information on how to share.
./Klaas
Intern on Home Assistant Energy
Power-up your ESPHome Projects
Speaking of interesting stuff, have you seen what cool new stuff has come to
ESPHome
Blueprint of the week
This week’s blueprint is that of danielbook, who created a blueprint that turns on the lights of a room based on a motion and brightness sensor. You will no longer be in the dark when you get home 😉 Try it out! Read more about it on the community forum or install this automation in your instance with a click on the My button!
Floor3D Card
Last time we shared a dashboard with floorplan, this time the
floor3D card
Lovelace Dashboard
This week again we have a new Lovelace dashboard for the necessary portion
of inspiration 😄 This time the one from suckfail
Would you also like your dashboard to be in the community highlight? Drop it
on Reddit
Chore Tracker
Are you tired of doing those household chores all the time, or do the kids just don’t want to unload the dishwasher? Make it more fun with the chores tracker made by djbrooks022, where you can earn points for every chore you complete!
Do you want to get started? Then find all the information here.
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:
- Tweet 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!