The first release of the new decade! Happy New Year!
We are starting this new year with a packed release! So let us dive in!
- Improved entity handling on startup
- Ignore discovered devices & services
- Reload all the input things & bye generated groups
- Add a device to Lovelace
- Multi-select entity management
- ZHA configuration panel improvements
- Removing your Lovelace configuration
- In other news
- New Integrations
- New Platforms
- Breaking Changes
- Beta Fixes
- All changes
We are now restoring all entities, stored in the registry, on Home Assistant startup.
During the startup of Home Assistant, all your configured integrations are loaded. Each of those integrations results in one or more devices and entities. However, there was a catch!
The loading of some integrations could take a while, which caused some entities not to be available immediately. Sometimes, this affected multiple things, like missing devices in HomeKit/Google/Alexa or those big red boxes in our Lovelace UI. We are sure, at some point, we’ve all experienced that.
As of this release, all these entities, if registered in our entity registry, will be restored as “unavailable”. That allows other parts of our system to use them immediately, solving a lot of common issues during startup.
These restored entities can be differentiated from normal “unavailable” entities by an additional state attribute added to those entities: “restored”.
Screenshot of a removing an unavailable entity.
As a result, entities will no longer “disappear”, so restored and unavailable entities are removable, as shown in the screenshot above. Please note that, if an integration provides an unavailable entity, the providing integration needs to be removed first, or else, those entities can not be deleted.
Got that one device that gets discovered over and over again?
It is now possible to ignore a specific discovered device with a single click!
Screenshot of a discovered Hue bridge.
It requires the integration to be updated to support this. For this release, the Hue, Axis, deCONZ, WLED and HomeKit integrations are updated to support this new feature.
input_* integrations now have a
reload service to reload your YAML configuration for these integrations, without the need to restart Home Assistant.
Furthermore, time to say bye-bye, to all generated entity groups (
group.all_*). Chances are, you have never heard of those because they were hidden. However, if you rely on those groups for your automations, you need to adjust those automations. Check out the breaking changes section for more information.
We added a button to the device page to add all entities of a device to Lovelace in a blip! Home Assistant suggests cards based on the type of entities the device provides so that you can add them to a view of your choice instantly.
If you are using Lovelace in YAML mode, you still can use this new feature. The generated YAML can be copied and pasted into your configuration file.
Screenshot of a card suggestion for a light device.
This same functionality is also added to the unused entities page of Lovelace.
Entity management has never been easier; It now allows for changing multiple entities at once. Select multiple entities and remove, enable or disable them with one click.
Screenshot of the entities configuration page with multi selection.
@dmulcahey did a lot of work on the ZHA config panel this release.
The navigation for the ZHA configuration panel has been redesigned to provide a better user experience on mobile and desktop.
As part of the redesign, full Zigbee group management has been added, allowing you to create and manage Zigbee groups right from the UI.
Screenshot of the ZHA configuration panel.
In a future releases, the ability to bind devices directly to groups, will be added as well.
Want to start your Lovelace configuration from scratch? Or go back to the automatically generated Lovelace interface?
Now you can by clearing the Lovelace configuration in the raw configuration editor and saving it.
Screenshot of the remove Lovelace confirmation dialog.
HassOS Release-3 build 8 (Stable) released today. Changelog: https://github.com/home-assistant/hassos/releases/tag/3.8 … – Next we start the first 4.0 Beta builds include the N2 support and Linux LT 5.4
:beginner: Home Assistant Operating System. Contribute to home-assistant/operating-system development by creating an account on GitHub.
Besides the release of HassOS 3.8, the first beta version of HassOS 4.0 is now available as well. This beta release adds support for Hardkernel’s ODROID-N2!
The ODROID-N2 is a great and powerful alternative for the Raspberry Pi.
Brad Crc made this impressive demo of setting up a custom now playing poster card in Lovelace floor plans. This allows you to show currently playing media in your floor plan!
Bas Nijholt kept seeing his own theme popping up on Reddit, so he decided it was time for him to show off his Lovelace dashboard, featuring this lovely theme.
- Add Elgato Key Light integration (@frenck – #29592) (elgato docs) (new-integration)
- Add IntesisHome Climate Platform (@jnimmo – #25364) (intesishome docs) (new-integration)
- Add Signal Messenger integration (@bbernhard – #28537) (signalmessenger docs) (new-integration)
- Revert Tahoma removal (@balloob – #29840) (tahoma docs) (new-integration)
- Add GIOS integration (@bieniu – #28719) (gios docs) (new-integration)
- Add local_ip component (@issacg – #29973) (localip docs) (new-integration)
- Add KEF speakers integration (@basnijholt – #28959) (kef docs) (new-integration)
- Add Sentry component (@dcramer – #30422) (sentry docs) (new-integration)
- Add surepetcare component (@benleb – #24426) (surepetcare docs) (new-integration)
- Add Brother Printer integration (@bieniu – #30359) (brother docs) (new-integration)
- Add TMB sensor (@alemuro – #27964) (tmb docs) (new-integration)
- Add Stookalert integration (@fwestenberg – #30306) (stookalert docs) (new-integration)
- Add battery sensor to iCloud (@Quentame – #29818) (icloud docs) (new-platform)
- Add light support to Velbus integration (@brefra – #30323) (velbus docs) (new-platform)
- Add support for v1 and v2 HomeKit fans. (@Jc2k – #30503) (homekit_controller docs) (new-platform)
- Add support for homekit air quality sensors (@Jc2k – #30510) (homekit_controller docs) (new-platform)
- Add pilight dimmer as light component (@Trekky12 – #30107) (pilight docs) (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, that is helping us a lot!
It’s been a busy week with a lot of announcements around IoT standards, so I thought I would do a quick round up of them, and how it might impact Home Assistant users.
As it’s been a while, the industry has announced yet a new effort to create a new IoT standard called Project Connected Home over IP. I think that there are a few interesting bits to this standard:
The standard will be royalty-free. This is big, as it means that it will be easy for companies to build products. Take, for example, Homekit, which is a great IP-based local standard. Homekit has strict licensing and royalties, which prevented it from widespread adoption.
The new standard specification will be written in conjunction with building an open source implementation of the standard. Once it’s all finished, we’ll be able to integrate this implementation into Home Assistant.
Finally, Apple, Google and Amazon are seriously involved, even contributing their own IoT standards to help bootstrap this specification. This significantly increases the odds of them also integrating it into their products. Since their products are everywhere, it means that more companies might incorporate the standard and it can get widespread adoption.
But don’t hold your breath. Developing a standard takes time. They aim for a draft to be released at the end of 2020. And that’s just the specification. Not any of the devices built with it. If (and that’s a big IF) everything works out, expect this standard to get into your home in 2022.
A bit behind the original timeline, but we happy to announce, we’ve released version 3 of Hass.io Operating System: HassOS. Just in time for Christmas!
TL;DR; A quick summary of the changes:
- Official RPi4 support
- Linux LT 4.19
- Buildroot LT 2019
- USB-boot capabilities for the RPi3
- SMS integrations with USB/GSM modem
- Qemu Agent support
- Optimized kernel for virtual appliances
- Improved automatic disk expansion
- Initial foundation for offloading the data partition
We now officially support the Raspberry Pi 4 on this stable version of HassOS! The Raspberry Pi 4 is a great and powerful device to get you started on Hass.io and Home Assistant.
@rbray89 worked hard on this release to add the very often requested USB boot support! Please note, this is currently limited to RPi3 devices. Carefully read how the USB boot works and be aware of the limited supported hardware.
The HassOS image for virtual appliances did get some useful updates as well. We have optimized the Linux kernel to support more virtual hardware.
We have now included the QEMU Agent in HassOS. So if you are running on a Hypervisor that is QEMU based (e.g., Proxmox or Libvirt), you now have a lot more information in your Hypervisor control panel, proper shutdown support and improved support for backing up/snapshotting your virtual machine.
Finally, the automated disk expansion got some updates. So if you need more disk space in your virtual appliance, add it in your Hypervisor and HassOS automatically pick it up at the next boot.
We want to emphasize that running Hass.io as a virtual machine is the only supported method to run Hass.io on a virtualized system. We’ve lately seen some funky tutorials on how to run Hass.io inside a container like Docker or LXC, which we DO NOT recommend, you will end up having issues.
If you are already running HassOS, you have the full flavor of Hass.io, and thus, all the comfort it has to offer, making this upgrade a breeze!
To update via the user interface, go to the Home Assistant frontend, click on Hass.io in the sidebar to go into the Hass.io panel. Next, click on the System tab and press the UPDATE button in the “Host system” panel. In case the update isn’t showing up yet, push the RELOAD button on the “Hass.io supervisor” box first, which makes your system look for updates instantly.
Another option is to use our powerful CLI, that is shipped with the SSH add-on. Run the following command to trigger the upgrade:
hassio os update --version 3.7.
After some confusion about the statement of supporting virtual environments and running Hass.io on top of a custom Linux; so let’s clarify it.
The supported ways to run Hass.io are documented here: https://www.home-assistant.io/hassio/installation/
This also includes running Hass.io on Linux using the Generic Linux installer, which is a supported method.
Hass.io runs partly on your local machine, but for most parts inside multiple containers. All installation types we list, respect this.
If you run VMWare, ProxMox or other virtualization environments, you can use the HassOS OVA/VMDK to run a virtual machine with. Or, if you like to use a Ubuntu VM, that will work with the supported generic Linux installer.
We DO NOT support any kind of LXC hacks like listed here: https://github.com/whiskerz007/proxmox_hassio_lxc. These setups try to put everything inside a single container, which will cause you issues. Hass.io is not designed to run fully inside a containerized system, like LXC.
We hope this clarifies our earlier statement.