2021.11: Icon picker, device links and entity categories

Point eleven (.11), which means it is November! 🥶 (or 🏖 depending on where you are in this world, of course.)

It also means: This is the second last release of the year…

Hacktoberfest is over! In the month October, people contribute to projects (like Home Assistant) to celebrate open source. I’ve seen lots of new faces and new contributors this month. To those I want to say: Welcome! Thanks for contributing your free spare time; Thanks for being a hero! ❤️

And, there is more! Something that isn’t really visible. In the background, an army of contributors are improving a tremendous amount of Home Assistant code, which improves stability, readability, and maintainability of our project’s codebase. As a matter of fact, because of this incredible work, counted by the number of contributions, this release might just as well be one of the biggest ever. Work, you generally don’t notice, but is still done. Weird huh? Another group of heroes! ❤️

For me personally, this has been a crazy month. After the last release, I was sad to read about issues people had with the new Tuya integration. I went to different stores, bought many Tuya devices, and spent a lot of time improving the experience by extending device support. Hopefully, I’ve been able to do enough to make the Tuya integration acceptable.

This release… a long-time wishlist item of mine is in: The icon picker! 😍 So cool to see this happening, it is amazing, beautiful, super helpful, and it also supports third-party icon sets! 🤩

Oh, to spoil some inside information, you might want to block your agenda for the Home Assistant State of the Union 2021 on Saturday 11 December, 8 pm (CET)!

Enjoy the release!

../Frenck

Daylight saving time bug

If you have already transitioned daylight saving time (DST), you might have experienced it already. If you have not switched yet, this message is extra important for you.

Last weekend we experienced a bug with daylight saving time transitioning, causing Home Assistant to crash or have higher CPU loads than usual. If you experience this, restarting Home Assistant will resolve this issue.

This release has a more permanent fix for the issue, preventing it from happening. If you can’t upgrade to 2021.11 right now, we have also published Home Assistant 2021.10.7, which has the same bugfix included.

So if you still have to transition to a new summer/winter time, be sure to upgrade!

Visit devices and services

Your device has a web interface, but you don’t remember the (IP) address it has on your network… So you start guessing a couple of addresses; And end up checking your router, looking it up in an app, or scanning the network… Sounds familiar? Annoying, right?

Well, as of today, integrations can provide the URLs to devices or services where the device can be managed or configured.

Screenshot of WLED that now has a button that links to the WLED web interface of the device directly Screenshot of WLED that now has a button that links to the WLED web interface of the device directly.

If an integration provides a single web interface to configure multiple devices, it can even deep-link to the specific device page for that device.

Over 50! integrations have already added support for this feature, which is fantastic! Just to name a few integrations: MQTT, Tasmota, WLED, Synology, Plex, Netatmo, Pi-hole, RainMachine, Plugwise, Sure Petcare, Axis, UniFi Controller, FRITZ!Box, and many more!

If you are a custom integration developer, you can add support for this feature too; Read all about it on our developer blog.

Entity categorization

Since we introduced the concept of devices, we have been seeing more and more entities being created, which is great! It means we can automate on a lot more device features. However, this does impose other issues, like: clutter on a generated dashboard, unused entities exposed to voice assistants, or turn on/off things in areas as a side-effect. Let me try to explain the latter issue with an example.

Let’s consider a wall plug. It can be turned on/off using a switch entity, however, my wall plug also has a switch to enable a child lock that controls its physical button. Now, if I had this device in my living room area and turned off all switches in my living room, it would turn off the switch and the child lock! This is not what we want, right?

To resolve issues like these (and more), we introduce: Entity categories.

Entities without a category are now considered primary entities: The entities we daily use and expect from a device, i.e., the power on/off switch. Furthermore, entities can be categorized as configuration or diagnostic entities. A configuration entity provides a setting/configuration option for the device, while a diagnostic entity provides information about the device.

Take a light bulb as an example. The light entity itself is a primary entity. However, the select entity that provides the power on behavior configuration of the bulb is a setting of the device and thus a configuration entity. While the sensor providing the signal strength of the light bulb is a diagnostic entity.

Another, more visual example, from the device page of a Sonos Move speaker:

Screenshot of the Sonos device page that now has entities categorized Screenshot of the Sonos device page that now has entities categorized.

In the above screen, you can see the Sonos speaker itself is a primary control entity, while the entities that provide device configuration options and entities that provide diagnostic information about the device itself are now separated nicely.

With entities that are non-primary (so are either configuration or diagnostic entities), we now do the following:

  • Non-primary entities are hidden from generated Lovelace dashboards. This reduces the clutter and makes the generated dashboards more useful for daily use.
  • Non-primary entities are, by default, not exposed to Amazon Alexa or Google Assistant. You, of course, still can expose them, but by default, we don’t send them to these voice assistants.
  • Non-primary entities are not called by service calls that target the device or area the device is in. They are only called if explicitly called by their entity ID.

Please note, the above-listed points are breaking changes, also listed in the breaking changes section of these release notes.

Like the previous visit device or service feature, this new organization capability has been adopted by many of our maintainers: 60+ integrations! To name a few: Sonos, Z-Wave JS, Shelly, SwitchBot, deCONZ, Neato, Netatmo, August, MQTT, Hue, Roomba, Tibber, AirVisual, KNX, motionEye, and many more. Oh, and soon, we can add ESPHome to that list!

If you are a custom integration developer, you can add support for this feature too; Read all about it on our developer blog.

The icon picker

Adding nice and matching icons to your entities, makes all the difference for how your Home Assistant interface looks and feels.

Finding those icons was somewhat clumsy. You’d go to the Material Design Icons website to find one, remember its code and add the mdi:<code> to your entity. Not a great experience, especially with the number of icons available your browser doesn’t always like that website.

Thanks to the great work of @piitaya, we now have a beautiful, super easy, smart and fast icon picker! Yes, you can now search and choose icons, straight from the Home Assistant interface.

Screen capture showing the new icon picker in action Screen capture showing the new icon picker in action.

When you start typing, it not only looks for icons that match the MDI code, it also looks for aliases and categories of the icons. That way, you’ll always find the icon you’re looking for.

Third-party custom icon sets can also utilize this feature; however, the author of that set needs to add compatibility for it. For example, the Hue icons by arallsopp added support for this feature already.

Tuya update

Our previous release included an update to the Tuya integration, making it use the official API instead of a soon-to-be-removed API. Sadly, this update did not live up to our standards, for which we want to apologize.

Tuya had initially planned to deprecate the old API in December, giving users 2 months to migrate. That’s not a lot of time, so we decided to move forward with releasing the updated integration. Tuya pushed back the timeline for sunsetting the old API with 6 months; but it was too late for us to change course and ship the old integration.

The updated Tuya integration had some bugs and also was missing some features compared to the previous integration and various available custom components. This caused some users to have a poor experience. To make up for this, @frenck spent a good chunk of time on bringing the Tuya integration up to the latest standards and adding a ton of new features and bug fixes.

Almost all Home Assistant entity platforms are supported now, including (binary) sensors, covers, vacuums, and even cameras! However, be aware that Tuya has a lot of devices and variations, so there is still work left to be done; We have done everything we can to provide a solid base this release.

As a final note: Some people complained about that this integration relies on the cloud. We have always supported integrations with both local and cloud APIs. Integrations with cloud APIs allow people to adopt Home Assistant without having to replace all devices in their house. Although we recommend local, using devices that require the cloud, or are fully local, is a choice everyone should make for themselves.

Some nice new template filters

For some of our more advanced users, this release has some helpful template improvements included as well!

Let’s start with the new today_at filter/function that @Petro31 added. It allows you to quickly get a DateTime at a certain time of today. This can be really helpful if you need to compare against another DateTime. For example:

# Is the current time past 10:15?
{{ now() > today_at("10:15") }}

Next up is @raman325, who added the area_entities and area_devices filters and functions which allow you to get all devices or entities that are in an area. The methods return a list, which you can loop on.

{{ area_entities('Living Room') }}  # ['light.ceiling', 'media_player.tv', ...]

Lastly, @Petro31 added another one: the average filter and function. It does what you think it does… It calculates the average of a list of items you pass to it.

{{ [1, 2, 3, 4, 5] | average }} # Result: 3

Other noteworthy changes

There is much more juice in this release; here are some of the other noteworthy changes this release:

  • Debug traces of automations and scripts are now stored! So you no longer lose them when you restart Home Assistant. Thanks @emontnemery
  • @frenck adjusted the number entity and it can now be displayed as a slider instead of an input box. Home Assistant will automatically figure out which is the best to use.
  • Add support for fan groups! Thanks @bdraco!
  • Thanks to @ludeeus, the Supervisor integration now has binary sensors that can tell you which add-on is running or not.
  • @allenporter blew our minds this release by adding initial support for WebRTC streams and cameras to Home Assistant.
  • But had a good reason, he added support for Nest Battery Cameras and Nest battery Doorbell Cameras to Home Assistant! Thanks @allenporter!
  • When you log in to Home Assistant, there is now a “Keep me logged in” checkbox! Awesome @MartinTuroci
  • @goyney updated the Material Design Icon to version v6.4.95 ensuring we have all the latest icons available in our new beautiful icon picker.
  • Sure PetCare now supports the Felaqua devices, thanks @benleb!
  • The MQTT number platform now has support for providing a unit of measurement and resetting the number field (by @frenck and @emontnemery).
  • The Broadlink integration added sensors for voltage, current, overload, and total consumption. Thanks @felipediel!
  • WLED now has the much requested sliders for speed & intensity controls. Thanks, @rytilahti!
  • OpenGarage has seen lots of updates and love from @Danielhiversen, adding lots of sensors in the process.
  • With the recent improvements made to the VLC media player integration and add-on, there is now a way to get TTS working by connecting some speakers to your Blue, ODROID or Raspberry Pi. Thanks, @mib1185 & @MartinHjelmare!

Adding support for long-term statistics is a much requested feature; This release adds support for long-term statistics to the following integrations:

New Integrations

We welcome the following new integration this release:

Integrations now available to set up from the UI

The following integrations are now available via the Home Assistant UI:

Release 2021.11.1 - November 5

Release 2021.11.2 - November 9

Release 2021.11.3 - November 11

Release 2021.11.4 - November 15

Release 2021.11.5 - November 19

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. Make sure to fill in all fields of the issue template.

Read on →

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 and the many comments we received on design ideas I’ve shared on Twitter.

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 shared in his fantastic keynote, UX offers perspective. Who are the users? What are their tasks? And what is their pain? What do they want to achieve?

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. This allows anyone to experiment with the Home Assistant interface and quickly try out different concepts. Try it yourself and feel free to share your designs.

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! If you make 4 contributions to any open-source project (Home Assistant, for example 😘), you’ll receive a free t-shirt!

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 @ 21:00 CEST.

Enjoy the release!

../Frenck

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.

Screenshot of Z-Wave JS pairing a new device with S2 security 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 have been updated to v6!

This new version of MDI is packed with nearly 400 new icons (and over 75+ icons have been specifically marked for Home Assistant) ❤️

Sample image showing some of the new Material Design Icons available 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 breaking 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 has been working hard to add this layer of encryption to the ESPHome API, which utilizes the noise protocol.

Besides this version of Home Assistant, you’ll need at least ESPHome 2021.9.0, and configure your ESPHome device to enable encrypted communications.

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 and input_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:

Integrations now available to set up from the UI

The following integrations are now available via the Home Assistant 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…

…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. Make sure to fill in all fields of the issue template.

Read on →

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 later today (9:00 PM CET) to learn more about this release!

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 and Twitter, which is really awesome. Share a screenshot of your dashboard and your story too!

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 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 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 to obtain your gas usage.

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 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 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, Home Assistant can now discover USB devices and the integrations that work with that device. This makes setting up things like Z-Wave or Zigbee with Home Assistant an actual breeze now!

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 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 a select entity.
  • We’ve made zwave_js.* services more flexible: They now support area IDs and group entities as inputs!
  • We’ve made basic CC values directly controllable by moving them from using sensor entities to become number entities instead.

New template entities: Number and Select

Yes! We have new platforms you can utilize using the template integration!

Thanks to @raman325 you can now template your own select 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. The value 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. The value 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:

Integrations now available to set up from the UI

The following integrations are now available via the Home Assistant 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…

…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. Make sure to fill in all fields of the issue template.

Read on →

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, typically hassio_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. OS Agent allows for better communication between the host OS and the Supervisor which will enable new features. You can find the installation instructions for OS Agent in its GitHub repository.

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 for P1 ports & Home Assistant Glow for activity LEDs. Upgraded most of the existing energy integrations to be compatible.

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.

Diagram how both home automation and energy management use the same data. 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 or its collected data and build anything with it. We already see this happening: the European federation of citizen energy cooperatives is using Home Assistant to build energy management software tailored for communities. We are part of a rich ecosystem with many different approaches, all connected with Home Assistant.

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 later today (9:00 PM CET).

../Frenck

Matthias de Baat joins Nabu Casa

Let start by announcing that Matthias de Baat is joining the team at Nabu Casa to work on Home Assistant as a UX-designer.

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 that Matthias has prepared.

Welcome Matthias! Excited to have you on board!

But wait! There is more!

[Otto Winter][@ottowinter], the founder of ESPHome, will be joining Nabu Casa during his summer break as well! Welcome Otto! This summer is going to be fantastic!

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 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 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 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 for adding this noisemaker to the family! He also implemented the first integration to add support for Sirens: the Z-Wave JS integration. So, if you have a Z-Wave enabled Siren, you can now control it.

Locking, Unlocking and Jammed

Locks in Home Assistant can be a little bit smarter as of today, thanks to @bdraco. Besides the locked & unlocked states, support for locking, unlocking and jammed has been added.

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 added some new template functions that can be helpful when working with devices.

  • 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 of attr_name for the given device ID or entity ID.
  • is_device_attr(device_or_entity_id, attr_name, attr_value) returns whether the value of attr_name for the given device ID or entity ID matches attr_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:

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 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…

…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. Make sure to fill in all fields of the issue template.

Read on →

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! He has been an intern with Nabu Casa for the last months. Besides doing the community highlights, he has been working on some awesome stuff that will land in upcoming Home Assistant releases.

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

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 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 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 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, as of this release, we also provide a series version tag that always points to the latest patch version of that release, in addition to all existing tags we already provide.

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!
  • 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:

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 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…

…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. Make sure to fill in all fields of the issue template.

Read on →

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 made by CyrisXD. With this, you can create a card that is locked and you can unlock it with, for example, a pin code or a simple click on the card.

Lovelace Dashboard


This week again we have a new Lovelace dashboard for the necessary portion of inspiration 😄 This time the one from swake88 who is improving his dashboard for use on a mobile device. If you want to know more about it, check out the comment part on Reddit.

Would you also like your dashboard to be in the community highlight? Drop it on Reddit and maybe I’ll pick it out for the next edition.

Statistic Tools


Home Assistant has a number of tools for working with statistics, but the question is how can you best approach this. Carlos has written a very good guide on how to get started and how to make cards that use this data.

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:

See you next edition!