Well, hello!, Home Assistant Core 0.106! We are happy to see you 😃
A great release that improves stability, reliability and a lot of helpful additions to make everything much more friendly and easier to use. So let’s dive in!
In Home Assistant 0.105, we introduced Safe Mode. Our goal is to make sure Home Assistant always starts and provide you an interface to work with. No matter what.
@balloob has been busy this release to improve on this feature even more, and Home Assistant is now able to overcome issues when things in the core system get into trouble and even when the Lovelace configuration isn’t readable. Besides that, the way Safe Mode is presented has changed, so you instantly know you are in Safe Mode:
Screenshot of Home Assistant running in Safe Mode.
Ever tried to make an automation to brighten or dim your lights? Or tried to hook up a remote to control the brightness of a light? If you have, you probably know that doing that was pretty painful and involved some additional templating to get that going.
This release just made that a lot easier. An example device automation:
Screenshot of a device automation with dimming lights.
We have also added this functionality to the
light.turn_on service. You can now change the brightness, based on the current brightness, using the
brightness_step (-255, 255) and
brightness_step_pct (-100, 100) parameters.
Good to know, when the brightness hits 0, it will turn off the light. If the light is already off, and you step the brightness up, it will turn on. This is awesome, because if you have a rotating dimmer button (for example, an IKEA SYMFONISK), you can rotate it to change the brightness, but also turn the light on/off by just rotating it.
Persons have a new more info dialog. They now show the location of the person on the map and if the person is not in a zone, you can create a zone with the current location of that person with one click.
Screenshot of the new more info for a person.
The entities configuration panel previously only contained entities that were uniquely identifiable by Home Assistant (they have a so-called: unique ID). However, those are not provided by all integrations of Home Assistant, confusing since the entities panel did not show all of your entities.
In this version, we now include all entities in the panel, giving you a nice complete overview of all available entities in your system. You can’t edit all entities, since that requires an entity to be uniquely identifiable. If an entity doesn’t have a unique ID, the pencil icon will be striked through.
Screenshot of uneditable entities in the configuration panel.
Since all entities are now available in this panel, it does not only provide you a clear overview of all the available entities; you can also make use of the “related items” feature introduced in release 0.105 to see where they are being used!
The developer tools panel also got some nice little touches. In the “Info” tab you can now find a list of all integrations you are using and the logs are now aware of the integrations as well.
Both now include links to the documentation and our GitHub issue tracker. This allows you to dive in quickly when you run into troubles with an integration.
Screenshot of the integrations list and an example log message.
Our sensor card has had a style update. We initially got the design from the Lovelace Mini Graph Card and now updated to match the improved new look of that card.
Screenshot of the updated sensor card.
But wait… there is more! Some other smaller noteworthy changes in this release:
- In the zone editor that was introduced in the previous release, you can now change the location of your home zone. The radius of the home zone cannot be changed yet (we will work on that!), but you can drag the home zone on the map.
- Also an improvement on a feature introduced in the previous release, the
state_coloroption is now also available for other cards, so you can override the defaults of the cards.
- New automations now default to device automations instead of state triggers and service calls. Device automations are so much easier and clearer to create from the UI. You can, of course, still use the old triggers and actions like you are used to.
- In the generated Lovelace we no longer include automations and battery entities. You can find these in the automation configuration panel and the battery in the device configuration page. If you want to have your automations and/or battery in your Lovelace UI, you can always take control and add them.
- Scripts and scenes now have the ability to set a custom icon. Previously, you would have to create a customization to do this, now, you can just set them in your configuration.
12345678<span class="token key atrule">scene</span><span class="token punctuation">:</span><span class="token punctuation">-</span> <span class="token key atrule">name</span><span class="token punctuation">:</span> Movies<span class="token key atrule">icon</span><span class="token punctuation">:</span> mdi<span class="token punctuation">:</span>movie<span class="token punctuation">-</span>open<span class="token key atrule">entities</span><span class="token punctuation">:</span><span class="token key atrule">light.tv_back_light</span><span class="token punctuation">:</span><span class="token key atrule">state</span><span class="token punctuation">:</span> on<span class="token key atrule">brightness</span><span class="token punctuation">:</span> <span class="token number">125</span><span class="token key atrule">light.ceiling</span><span class="token punctuation">:</span> offYAML
Are you the creator of an awesome custom card for Lovelace?
We have made some changes to Lovelace that might impact your custom card, so be sure to read the blog post on the developers site about this.
- Add Salt Fiber Box device tracker (@bjornorri – #30986) (salt docs) (new-integration)
- Add GDACS feed integration (@exxamalte – #31235) (gdacs docs) (new-integration)
- Add Minecraft Server Integration (@elmurato – #30992) (minecraft_server docs) (new-integration)
- Add MELCloud integration (@vilppuvuorinen – #30712) (melcloud docs) (new-integration)
- Dynalite Integration (@ziv1234 – #27841) (dynalite docs) (new-integration)
- Add initial version of Vilfo Router integration (@ManneW – #31177) (vilfo docs) (new-integration)
- Add totalconnect zones as binary sensors (@austinmroczek – #28712) (totalconnect docs) (new-platform)
- Add Tahoma lock support (@vlebourl – #31311) (tahoma docs) (new-platform)
- Clean up Tahoma smartlock (@vlebourl – #31430) (tahoma docs) (new-platform)
- Add Tado water_heater (@michaelarnauts – #30095) (tado docs) (breaking change) (new-platform)
Experiencing issues introduced by this release? Please report them in our issue tracker. Make sure to fill in all fields of the issue template.
It’s time for the third installment of our revamped community highlights. We got some really great stuff again.
This time I (Paulus) am in charge of writing the community highlights. The reason for this is that the main item involves Frenck’s own work, and he felt weird promoting his own awesome, great, wonderful, enlighting and fabulous work on the revamped Visual Studio Code add-on.
Visual Studio Code is a free text editor by Microsoft that works inside your browser. It makes it very easy to manage your configuration.
The add-on used to be only available for x64 devices like intel NUC. With this update, it is now also available for ARM64 devices, including the Raspberry Pi 3 and 4 (the 64-bit version).
It comes installed with all the extensions necessary for editing Home Assistant related files:
If this is the first time you hear about the Home Assistant Config Helper, it is genius. It will set-up a realtime connection from VS Code directly to your Home Assistant installation so it can offer auto-complete suggestions when editing your configuration. This is pre-configured and works out of the box with the VS Code add-on.
To install the add-on, search for Visual Studio Code in the add-on store.
But there is more in the add-on! Home Assistant contains an add-on service registry where add-ons can make their services available for other add-ons without requiring any configuration. The VS Code add-on uses this feature to offer a built-in terminal that has pre-configured tools to connect to the MariaDB add-on and the MQTT add-on.
To try it out, open VS Code, click on the menu button top left -> view -> terminal.
This requires the Mosquitto add-on to be installed and an MQTT sensor (instructions).
To publish a message to an MQTT topic:
mosquitto_pub -t home/bedroom/temperature -m <span class="token number">23</span>
Or watch all messages that go through your MQTT broker:
mosquitto_sub -t <span class="token punctuation">\</span>#
This requires the MariaDB add-on to be installed and the recorder configured to use it (instructions).
To query the available tables:
mysql -D homeassistant -e <span class="token string">"SELECT entity_id, state, last_updated FROM states LIMIT 0, 10"</span>
Today we are releasing the first beta of Home Assistant Core 0.106. It is packed with awesome features. For a sneak peek of what is coming, check the beta release notes.
I’m personally most excited about the extended safe mode. It will guarantee that the frontend will always load, no matter how broken your configuration is.
On Reddit user /u/Jenova70 showed a super slick navigation arrow that indicates the traffic on his daily commute. Very slick! Instructions can be found in the comments.
Thanks, Jean-Loïc Pouffier & cogneato for sending in this item! 👍
Have you seen (or made) something awesome, interesting, unique, amazing, inspirational, unusual or funny, using Home Assistant?
Also, don’t forget to share your creations with us via Social Media:
- Twitter it! Be sure to mention @home_assistant
- Share it on our Facebook group
- Post it to our subreddit
- Tag @homeasssistant on Instagram
- Or via chat, drop us a line in the #lounge at Discord
See you next edition!