I am super excited about this release as it brings some great examples of how we are refining the system to become more customizable and, at the same time, user friendly. The first thing that I am really excited about is a new experimental user interface that we call Lovelace. Check this awesome rundown of all the features by @ciotlosm. The TL;DR: a faster, more customizable and more extensible UI with the same look and feel as the old one.

Be aware, this is experimental, so things will change. However, we felt like we didn’t want to keep this away from you any longer. Check the Lovelace UI docs on how to get started. Make sure to share your creations!

Thanks to all the people that have been hanging out in the #beta channel on Discord helping development, finding and squashing bugs and making suggestions. Especially thanks to @c727 for all his development work and @arsaboo for being the first guinea pig.

Example user interface created using Lovelace ([source](https://gist.github.com/ciotlosm/9508388876edf92c4c1f3579e740fbd5#file-ui-lovelace-yaml))

Another change is that Nest, Sonos and Cast will now have to be configured using a config entry. Config entries can be created via the integrations page in the config panel. This is a concept that we have been developing for a couple of months now and it’s our goal to eventually use this as the way to configure all components.

Screenshot of the Nest config entry.

And as if this releases even needs more cool stuff, the Insteon integration now supports X10 thanks to @teharris1. It was a frequent requested feature from the Insteon community.

And finally, we’ll be extending the open beta for Home Assistant Cloud until the first of September.

Enjoy this release and have a good weekend all!

New Platforms

• Weather Platform - IPMA (@dgomes - #14716) (weather.ipma docs) (new-platform)
• Add Freebox device tracker (@stilllman - #12727) (device_tracker.freebox docs) (new-platform)
• Add IBM Watson IoT Platform component (@mtreinish - #13664) (watson_iot docs) (new-platform)
• Wireless tags platform (@sergeymaysak - #13495) (wirelesstag docs) (binary_sensor.wirelesstag docs) (sensor.wirelesstag docs) (switch.wirelesstag docs) (new-platform)
• Add netgear_lte component (@amelchio - #14687) (netgear_lte docs) (notify docs) (sensor.netgear_lte docs) (new-platform)
• Add Uptime Robot sensor (@ludeeus - #14631) (binary_sensor.uptimerobot docs) (new-platform)
• Add support for the Unitymedia Horizon HD Recorder (@benleb - #14275) (media_player.horizon docs) (new-platform)
• Add support for KIWI Door Locks (@c7h - #14485) (lock.kiwi docs) (new-platform)
• Epson projector support (@pszafer - #14841) (media_player.epson docs) (new-platform)
• Add sensor.nsw_fuel_station component (@nickw444 - #14757) (sensor.nsw_fuel_station docs) (new-platform)
• Add support for ZhongHong HVAC Controllers (@crhan - #14552) (climate.zhong_hong docs) (new-platform)
• Xiaomi Cameras - multiple models (@vaidyasr - #14244) (camera.xiaomi docs) (new-platform)

Release 0.72.1 - June 25

• Prevent Nest component setup crash due insufficient permission. (@awarecan - #14966) (nest docs)
• Fix socket bug with Yi in 0.72 (@bachya - #15109) (camera.yi docs)
• Skip nest security state sensor if no Nest Cam exists (@awarecan - #15112) (sensor.nest docs)
• Fix cast config (@balloob - #15143) (media_player.cast docs)
• Bump python-nest to 4.0.3 (@awarecan - #15098) (nest docs) (sensor.nest docs)

If you need help…

…don’t hesitate to use our very active forums or join us for a little chat. The release notes have comments enabled but it’s preferred if you use the former communication channels. Thanks.

Reporting Issues

Experiencing issues introduced by this release? Please report them in our issue tracker. Make sure to fill in all fields of the issue template.

0.71 has arrived. My favorite feature in this release is the conversion of the Nest component from cloud poll to cloud push. Sure, it’s still through the cloud but changes are now made available in Home Assistant as soon as they happen. Thanks @awarecan!

We’ve continued the frontend tweaks after the major overhaul in the last release. We’ve had some issues with the Hass.io panel on both Firefox and Safari. They have been addressed and all browsers should hopefully work again.

On the frontend side, custom panels have gotten some new tricks, including support for building panels using React. So if you’re a developer, check it out. And thanks to @c727 a lot more strings can now be translated. More info on how to help with translating the frontend can be found here.

HomeKit support also keeps growing. This release includes support for media players, automations and outlets thanks to @schmittx.

And in case you missed it, @OttoWinter has created esphomeyaml, which allows you to program and deploy ESP chips throughout your house by using a Home Assistant inspired configuration.yaml. Check it out.

Have a good weekend everyone!

New Platforms

• Lagute LW-12 Wifi LED control (@jaypikay - #13307) (light.lw12wifi docs) (new-platform)
• Add Xiaomi Aqara Lock support (@SchumyHao - #14419) (xiaomi_aqara docs) (lock.xiaomi_aqara docs) (new-platform)
• Add Iperf3 client sensor (@tchellomello - #14213) (sensor.iperf3 docs) (new-platform)
• Add homematicip cloud climate platform (@mxworm - #14388) (homematicip_cloud docs) (climate.homematicip_cloud docs) (new-platform)
• Add Hydrawise component (@ptcryan - #14055) (hydrawise docs) (binary_sensor.hydrawise docs) (sensor.hydrawise docs) (switch.hydrawise docs) (new-platform)
• Adding ryobi garage door opener (@guillaume1410 - #14618) (cover.ryobi_gdo docs) (new-platform)
• Add sensors and services to RainMachine (@bachya - #14326) (rainmachine docs) (binary_sensor.rainmachine docs) (sensor.rainmachine docs) (switch.rainmachine docs) (new-platform)
• Add Flock notification platform (@fabaff - #14533) (notify docs) (new-platform)

New Features

• Add HomeKit support for media players (@schmittx - #14446) (homekit docs) (new-feature)
• Add HomeKit support for automations (@schmittx - #14595) (homekit docs) (new-feature)
• Extend package support (@cdce8p - #14611) (new-feature)
• Change nest to cloud push (@awarecan - #14656) (nest docs) (binary_sensor.nest docs) (climate.nest docs) (sensor.nest docs) (new-feature)
• Add support for outlets in HomeKit (@schmittx - #14628) (homekit docs) (new-feature)

If you need help…

…don’t hesitate to use our very active forums or join us for a little chat. The release notes have comments enabled but it’s preferred if you use the former communication channels. Thanks.

Reporting Issues

Experiencing issues introduced by this release? Please report them in our issue tracker. Make sure to fill in all fields of the issue template.

The ESP8266 and ESP32 are dirt cheap WiFi-enabled microcontrollers that have established themselves as the base for many DIY home automation projects. Even quite a few manufacturers like iTead with their Sonoff devices have chosen these controllers because of their competitive price.

Setting up these microcontrollers for some basic functionality has also gotten really easy over the years with popular projects like ESPEasy or Sonoff-Tasmota: You just download their firmware and flash it onto your chip. But if you’ve ever tried to go a bit beyond the basic set of functions of those frameworks and tried to do some customization, you will have probably noticed that it’s not that easy. Often times you’ll end up having to download some Arduino code project from the internet and customizing it to your needs.

This is where esphomelib comes in: The esphomelib suite is a set of tools that are designed with the goal of achieving the best possible user experience. esphomelib a) allows for lots of customization without touching a single line of code and b) has complete Home Assistant integration. Inside the esphomelib ecosystem, you essentially just have to write a simple YAML configuration file. The rest like compiling, flashing, uploading etc. will then be taken care of automatically.

It’s time for release 0.70. It’s a little later than expected because of a major overhaul of how our frontend is build. It should not have any impact on how the frontend looks or behaves. Thanks to all the people running the beta who helped test this. Right now it looks like Firefox is still having some issues running the Hass.io panel. We’re working on releasing a fix for that soon.

If you’re using custom UI or Panels, some changes have been made. Make sure you run the latest version. More info on our developer blog.

Talking about our developer blog, this is a new blog with accompanying Twitter account. This is part of our ongoing effort of splitting content and interaction for users and developers of Home Assistant.

One cool new component in this release is Konnected (product page). It allows you to connect your existing wired alarm systen and plug it … straigt into Home Assistant!

Another cool one this release is Facebox. It will allow you to do local face detection on your camera feeds. Can’t wait to hear the cool things people will do with this.

New Platforms

• Converted SABnzbd to a component (@jeradM - #12915) (sabnzbd docs) (sensor.sabnzbd docs) (breaking change) (new-platform)
• Add more homematicip cloud components (@mxworm - #14084) (homematicip_cloud docs) (binary_sensor.homematicip_cloud docs) (light.homematicip_cloud docs) (switch.homematicip_cloud docs) (new-platform)
• Adds facebox (@robmarkcole - #14356) (image_processing.facebox docs) (new-platform)
• Add SpaceAPI support (@fabaff - #14204) (spaceapi docs) (new-platform)
• Samsung Family hub camera component (@Klathmon - #14458) (camera.familyhub docs) (new-platform)
• Add Konnected component with support for discovery, binary sensor and switch (@heythisisnate - #13670) (konnected docs) (binary_sensor.konnected docs) (switch.konnected docs) (new-platform)
• New Sensor FinTS (@ChristianKuehnel - #14334) (sensor.fints docs) (new-platform)

New Features

• Allow HomeKit name to be customized (@schmittx - #14159) (homekit docs) (new-feature)
• Add HomeKit support for fans (@schmittx - #14351) (homekit docs) (new-feature)

Release 0.70.1 - May 31

• Update Hue platform to aiohue 1.5.0, and re-implement logic for duplicate scene names. (@MizterB - #14653) (hue docs)
• Ignore unsupported Sonos favorite lists (@amelchio - #14665) (media_player.sonos docs)
• MQTT Cover Fix Assumed State (@OttoWinter - #14672) (cover.mqtt docs)
• Fix Eco mode display on Nest (@ciotlosm - #14706) (climate.nest docs)
• Frontend: bug fixes for date time more info, cover icons, slider overflow issue (@c727, @cdce8p, @balloob)
• Add Simplepush back (#14728)

If you need help…

…don’t hesitate to use our very active forums or join us for a little chat. The release notes have comments enabled but it’s preferred if you use the former communication channels. Thanks.

Reporting Issues

Experiencing issues introduced by this release? Please report them in our issue tracker. Make sure to fill in all fields of the issue template.

Not much time to write a great intro this time as we’re hanging out at PyCon! Some fixes for the Hue and Wink colors thanks to @amelchio. Initial foundation for users has landed, it’s not anywhere near usable. We’ll keep hacking on it. Google Assistant for Home Assistant Cloud now supports room hints. This will cause Google Assistant put the devices in the right groups when you link your account.

New Platforms

• Support Xiaomi Mijia Bluetooth Wireless Temperature and Humidity Sensor (@ratcashdev - #13955) (sensor.mitemp_bt docs) (new-platform)
• Move RainMachine to component/hub model (@bachya - #14085) (rainmachine docs) (switch.rainmachine docs) (breaking change) (new-platform)
• Add Social Blade Sensor (@meauxt - #14060) (sensor.socialblade docs) (sensor.uscis docs) (new-platform)
• Add PostNL sensor (Dutch Postal Services) (@iMicknl - #12366) (new-platform)
• Issue/add template fans (@giangvo - #12027) (fan.template docs) (new-platform)
• Matrix Chatbot (@tinloaf - #13355) (matrix docs) (notify docs) (breaking change) (new-platform)

Release 0.69.1 - May 12

• Fix loading of Matrix chatbot (@tinloaf - [#14346]) (matrix docs)

If you need help…

…don’t hesitate to use our very active forums or join us for a little chat. The release notes have comments enabled but it’s preferred if you use the former communication channels. Thanks.

Reporting Issues

Experiencing issues introduced by this release? Please report them in our issue tracker. Make sure to fill in all fields of the issue template.

Weekend is around the corner and that means that it’s time for the next release of Home Assistant. 0.68 brings a ton of great goodies and bug fixes.

One of the coolest features this release is by @mjg59: you are now able to control HomeKit devices. Previously, it was possible to control Home Assistant from iOS devices using the HomeKit protocol. With this release, Home Assistant is able to become the controller and use HomeKit to control lights and switches directly. Since HomeKit is vendor agnostic, it means that any HomeKit light or switch will now be compatible with Home Assistant. Very cool.

Another cool new platform, also by @mjg59, is support for Eufy devices. Eufy is the Home Automation brand of Anker and they have been producing reasonably priced devices which can now be controlled by Home Assistant too. Thanks for all your contributions @mjg59 ❤️.

New Platforms

• Add support for Eufy bulbs and switches (@mjg59 - #13773) (eufy docs) (light.eufy docs) (switch.eufy docs) (new-platform)
• Add support for controlling homekit lights and switches (@mjg59 - #13346) (homekit_controller docs) (light.homekit_controller docs) (new-platform)
• Adding USCIS component (@meauxt - #13764) (sensor.uscis docs) (new-platform)
• Add support for new platform: climate.modbus (@Kirchoff - #12224) (climate.modbus docs) (new-platform)
• Add AVM fritzbox smarthome component (@hthiery - #10688) (fritzbox docs) (climate.fritzbox docs) (switch.fritzbox docs) (new-platform)
• Adds SigFox sensor (@robmarkcole - #13731) (sensor.sigfox docs) (new-platform)
• Add blackbird media player component (@koolsb - #13549) (media_player.blackbird docs) (new-platform)
• Add support for Sensirion SHT31 temperature/humidity sensor (@viorels - #12952) (sensor.sht31 docs) (new-platform)
• Qwikswitch binary sensors (@kellerza - #14008) (qwikswitch docs) (binary_sensor.qwikswitch docs) (sensor.qwikswitch docs) (beta fix) (new-platform)

New Features

• Support binary_sensor and device_tracker in HomeKit (@Yonsm - #13735) (homekit docs) (new-feature)
• Add Homekit locks support (@philk - #13625) (homekit docs) (new-feature)
• Support CO2/PM2.5/Light sensors in HomeKit (@Yonsm - #13804) (homekit docs) (new-feature)
• Support Garage Doors in HomeKit (@marthoc - #13796) (homekit docs) (new-feature)
• Support basic covers with open/close/stop services HomeKit (@nickw444 - #13819) (homekit docs) (new-feature)

Release 0.68.1 - April 30

• Fix color setting of tplink lights (@amelchio - #14108) (light.tplink docs)
• Improve precision of Hue color state (@amelchio - #14113) (light.hue docs)
• Revert Hue color state to be xy-based (@amelchio - #14154)
• Fix Python 3.6 compatibility for HomeKit controller (@mjg59 - #14160) (homekit_controller docs)
• Added CONF_IP_ADDRESS to HomeKit (@cdce8p - #14163) (homekit docs)
• Do not sync entities with an empty name (@balloob - #14181) (google_assistant docs)
• Improve chromecast disconnection logic (@OttoWinter - #14190) (media_player.cast docs)
• Fix poorly formatted automations (@balloob - #14196)
• Disable eliqonline requirement (@balloob - #14156)

If you need help…

…don’t hesitate to use our very active forums or join us for a little chat. The release notes have comments enabled but it’s preferred if you use the former communication channels. Thanks.

Reporting Issues

Experiencing issues introduced by this release? Please report them in our issue tracker. Make sure to fill in all fields of the issue template.

When we launched the website in December 2014, we’ve only had a handful of components and usage instructions. Since then the website has grown to over a 1000 pages touching a wide range of topics. The growth, while great, also has put a lot of strain on how the docs are organised. One of the places that was especially suffering under the growth was the developer section. It was living under a single top menu item and had to contain everything in a single sidebar.

To fix this, we’re releasing a new website: developers.home-assistant.io. The website is aimed at people that are developing Home Assistant. It will contain resources how to setup your development environment, how to fix bugs, help with translations or improve the frontend. The main website will now solely be focused on Home Assistant users.

Go check it out and let us know what you think: developers.home-assistant.io.

Guess what? Yep, our Google Assistant Smart Home skill is live! It’s a mouthful but it means that you can now control your Home Assistant devices via any Google Assistant enabled device by simply saying things like “Ok Google, turn on the lights”.

To get started:

• Enable Home Assistant Cloud
• Install our skill for Google Assistant. As of this writing, the link is not live yet: you can find it by opening the Google Home app -> Home Control, tap on the blue + at the bottom right and find Hass.io in the list.
• Optional: Tweak the devices that are getting exposed to Google Assistant.

Things to note:

• The skill is called Hass.io, but will work with normal Home Assistant too. The name was necessary to avoid confusion between Home Assistant, Google Assistant and Google Home.
• Works with Home Assistant 0.65.6 or later.
• All message handling is done local and is open source.
• If you have an Android device with Google Assistant, you can control your devices too.
• Home Assistant 0.68 will introduce a button to the Cloud config panel to trigger a sync of available devices.

Home Assistant Cloud is still in open beta and free to use. Open beta period has been extended to June 1. Many thanks to Quadflight for providing the Raspberry Pis that Google used for physical testing and thanks to Arsaboo for helping with testing.

We noticed that there is some confusion in the community about how Hass.io relates to Home Assistant and what impact the upcoming Hass.io changes will have. We will try to clarify it all in this blog post.

What is Hass.io

Hass.io is a complete solution to run Home Assistant, by the authors of Home Assistant. The goal of Hass.io is to provide an easy to use and secure system, entirely managed from within the Home Assistant user interface.

Hass.io is a complete solution, which means that it comes with its own highly secure and optimized operating system, a supervisor application to maintain and configure that system, and of course Home Assistant itself.

When using Hass.io, you’ll see a new Hass.io panel inside the Home Assistant UI. From here users can configure the system and install Home Assistant updates with a simple click of a button. Users are also able to make snapshots of their system, making it easy to migrate all their configuration to a new system or restore their system to a previous state.

We wanted to be able to provide the convenience of seamless updates and configuration via the UI to other applications too, and so we introduced Hass.io add-ons. Any application can be packaged up as a Hass.io add-on, allowing any user to install and manage it easily. Since the introduction, we’ve seen an amazing growth in users sharing their add-ons with the community. It’s now possible to install an adblocker for your network, an MQTT broker or Tor with a single click.

Upcoming changes to Hass.io

We’ve introduced Hass.io last July. Since then, we’ve noticed some room for improvements in making Hass.io easier to use, lighter to maintain and easier to integrate with other host systems.

Note that the descriptions of upcoming improvements can get quite technical. Feel free to jump to the conclusion.

Automatic add-on configuration

Home Assistant has recently introduced configuration entries. We’re going to hook into this new functionality and allow add-ons to configure their related integration in Home Assistant automatically. For example, if a user installs the MQTT broker add-on, we will automatically set up Home Assistant to connect to it.

Host management

To control the host system, we currently use a custom service called HostControl. This allows the user to manage here host and restart/shutdown the computer from within Home Assistant. Instead of relying on our own system, we’re going to change to use D-Bus. D-Bus is a standardized mechanism for services and applications to communicate. Using a defined standard means that all parts of the host can now be remotely configured: sound, network, etc, etc. We will be extending the Hass.io panel in Home Assistant with controls to configure various parts of the host.

Hass.io OS

Hass.io is currently using a forked version of ResinOS as our operating system. ResinOS has been designed to run a minimal environment for Docker, simple over the air updates and connect to the ResinIO cloud. Our fork removed the ResinIO logic. Over time, ResinOS has been evolving but not in a direction that is aligned with our goals, resulting in the maintenance of our fork to take up a lot of time.

The ResinOS build system is based on the Yocto Project. This is a very powerful system, but also requires specific support for each hardware platform need to be specifically added and maintained (like each version of Raspberry Pi), which caused long build and development times for Hass.io.

All these factors made us decide to build our own, custom, operating system. We’re obviously not starting from scratch, but instead, are basing it off Buildroot as the foundation and use RAUC for over the air updates.

Some things that the new operating system will be able to do:

• Easier to add support for new hardware.
• Updating will be atomic and has a Fail-safe. If a system fails to boot after an OS upgrade, it will fallback, by booting the previous working version.
• Updates are required to be securely signed by the Home Assistant team, adding a whole new level of security.
• Compressing the root file system, making it faster on SD cards and slow IO-Interfaces.
• Compressing parts of the memory so that we can store more information.

What Hass.io users should do to prepare for these updates

At this moment: Nothing.

The new Hass.io supervisor still supports the old ResinOS builds (our official downloads for Raspberry Pi and Intel NUC) and generic Linux installations. If you’re using a generic Linux installation on SUSE Linux or Ubuntu, you have to update your local AppArmor profile if you want to use the new functionality (instructions will be provided upon release).

Once our new installation images with HassioOS are released, you have to reflash your device once. You can do this without losing any configuration by using our Snapshot feature:

• Create a snapshot of your current installation and download it to your PC.
• Flash the SD card with the new Hass.io OS image.
• Restore your snapshot.
• Enjoy a new and improved Hass.io

Release 0.67 is here! In case you missed the announcement from yesterday, Ubiquiti is paying me to write these release notes. Ooooooh yeah. With more time on my hands I’m going to be focusing on major improvements that we have been postponing for a while, first up will be a user system.

This release includes a security fix. The error log was accessible via the API without requiring authentication in previous releases. Although not a leak on its own, combined with a faulty component that would log sensitive information to the error log could lead to that being exposed (we don’t know of any component that does this). Thanks to Matt Hamilton for disclosing this issue to us.

New Platforms

• Adds folder_watcher component (@robmarkcole - #12918) (folder_watcher docs) (new-platform)
• Add FreeDNS component (@bdurrer - #13526) (freedns docs) (new-platform)
• Google Maps location sharing device tracker (@michaelarnauts - #12301) (device_tracker.google_maps docs) (new-platform)
• Added Waze travel time sensor (@Myrddyn1 - #12387) (sensor.waze_travel_time docs) (new-platform)
• Added switch component to Amcrest IP Camera. (@adpriebe - #12992) (amcrest docs) (switch.amcrest docs) (new-platform)
• Add mastodon (@fabaff - #13441) (notify docs) (new-platform)
• Tahoma switches (@ikucuze - #13636) (tahoma docs) (switch.tahoma docs) (new-platform)
• Add support for Nanoleaf Aurora Light Panels (@Oro - #13456) (light.nanoleaf_aurora docs) (new-platform)

Release 0.67.1 - April 17

• Fix Gogogate2 ‘available’ attribute (@dlbroadfoot - #13728)
• Fix so it is possible to ignore discovered config entry handlers (@Kane610 - #13741)
• Prevent vesync doing I/O in event loop (@balloob - #13862) (switch.vesync docs)
• Fix #13846 Double underscore in bluetooth address (@aav7fl - #13884) (device_tracker docs)
• Fix race condition for component loaded before listening (@balloob - #13887) (config docs)
• Missing property decorator added (@syssi - #13889) (fan.xiaomi_miio docs)
• Fix call to parent broadlink switch (@Danielhiversen - #13906) (switch.broadlink docs)
• Import operation modes from air humidifier (@syssi - #13908) (fan.xiaomi_miio docs)
• Upgrade pyqwikswitch to 0.71 (@kellerza - #13920) (qwikswitch docs)
• Upgrade somecomfort to 0.5.2 (@balloob - #13940) (climate.honeywell docs)
• Update pyhydroquebec to 2.2.2 (@titilambert - #13946)
• Update pyfido to 2.1.1 (@titilambert - #13947) (sensor.fido docs)
• Bumped pypollencom to 1.1.2 (@bachya - #13959) (sensor.pollen docs)
• Revert “Upgrade pyqwikswitch to 0.71 (@balloob - #13920) (qwikswitch docs)

If you need help…

…don’t hesitate to use our very active forums or join us for a little chat. The release notes have comments enabled but it’s preferred if you use the former communication channels. Thanks.

Reporting Issues

Experiencing issues introduced by this release? Please report them in our issue tracker. Make sure to fill in all fields of the issue template.