The Home Assistant sidebar in 12 different languages.

Translations

As mentioned in the 0.57 release notes, Home Assistant has launched a translated frontend. With the immediate influx of translations, we’ve made integration with a translation tool a top priority. @c727 took the initiative to evaluate several tools, and we’re happy to announce that Home Assistant will be partnering with Lokalise to manage our translations!

Lokalise allows us to open up translations for all of our multilingual users willing to contribute. Users can join the project using our public signup link, and start translating right away. We’ve created a translation startup guide with additional details about how to contribute. Instructions are provided there for how to request a new language.

Now that we have a system in place, expect a lot more of the interface to be translatable soon. We still have some technical hurdles to overcome, but the hardest work is behind us now. The community has already done an outstanding job of providing translations. The future is looking bright!

The Home Assistant sidebar in 12 different languages.

Whaaaaaats up everyone?! 😁 It’s been another crazy 2 weeks here at the virtual Home Assistant headquarters with a ton of great contributions from all over the world. New features, bug fixes, performance improvements. It’s a lot so let’s jump right in.

Translations

The first great feature, if you haven’t guessed it yet from the screenshot above: we are now able to translate the UI! Currently the translations are limited to the sidebar menu items. Even without a translation tool available, our contributors have jumped in and submitted translations for these menu items in over twenty languages! Home Assistant will automatically pick an available translation based on your browser settings, or a translation can be manually selected in the configuration panel.

We’re currently working on an integration with the web based translation tool lokalise.co, to make the translation process accessible to anyone who would like to contribute. Stay tuned for a blog post with more documentation soon.

Frontend improvements

As part of getting translations to work, we did a lot of cleanup work on the frontend side. The re-organization should allow us to iterate faster on the frontend. We’ve already seen a lot of clean up as part of this thanks to @armills and @andrey-git for keep raising the quality!

Hacktoberfest

Hacktoberfest 2017 is over! FINALLY. Each year we’re attracting more developers that want to contribute to Home Assistant. This is great but also very exhausting to our code reviewers. I want to give an enormous gigantic huge big shout out to our reviewers @pvizeli, @andrey-git, @armills, @MartinHjelmare, @fabaff. You have all done an amazing job and we couldn’t run Home Assistant without any of you! ❤

Hacktoberfest is obviously about the people contributing to open source. Big thanks to everyone that has taken the time to learn our code base and make contributions. We hope it was a pleasant experience and show how great open source can be. Hope to see many contributions in the future 👍

Here are our Hacktoberfest 2017 stats. It’s a miracle everyone is still alive:

• Main repo: 273 Pull requests were merged out of 307.
• Docs repo: 295 Pull requests merged out of 310.
• Frontend: 57 pull requests merged.

This means that we processed over 20 Pull requests per day. The result was already visible in 0.56. This release is almost the same. In those releases we were able to add over 40 new integrations.

IKEA TRÅDFRI

Good news and bad news on this front. The bad news is that IKEA changed the internal API for TRÅDFRI with a firmware update, breaking the Home Assistant integration. The good news is that they were nice enough to email us with instructions on the backward-incompatible changes.

Long time contributor @lwis jumped on the case and managed to migrate our integration in Home Assistant in time for this release. Great work!

@clhett01 made us a pumpkin ([via Twitter](https://twitter.com/clhett01/status/925481848612032512))

Timer

Okay, one more highlight before we’ll let you check out the changelog. Contributor @danielperna84 (famous for creating the HASS Configurator), had another great component up his sleeve: the Timer component. With the timer component you’ll be able to start countdown timers. A neat tool for your automation toolbox! More info in the timer docs.

New Platforms

• Introducing Ring Door Bell Camera (including StickUp cameras) and WiFi sensors (@tchellomello - #9962) (ring docs) (binary_sensor.ring docs) (camera.ring docs) (sensor.ring docs) (new-platform)
• add irish rail transport sensor (@ttroy50 - #9883) (sensor.irish_rail_transport docs) (new-platform)
• Add fail2ban sensor (@fronzbot - #9975) (sensor.fail2ban docs) (new-platform)
• add eph ember controls (@ttroy50 - #9721) (climate.ephember docs) (new-platform)
• whois domain lookup sensor (@GenericStudent - #10000) (sensor.whois docs) (new-platform)
• Add Deluge Switch Component (@HydrelioxGitHub - #9979) (switch.deluge docs) (new-platform)
• SNMP switch (@kirichkov - #9840) (switch.snmp docs) (new-platform)
• Microsoft tts (@jeroenterheerdt - #9973) (tts.microsoft docs) (new-platform)
• Telldus Live: Device without methods is a binary sensor (@rasmusbe - #10106) (tellduslive docs) (binary_sensor.tellduslive docs) (new-platform)
• Support for NO-IP (@fabaff - #10155) (no_ip docs) (new-platform)
• Linode (@ryanm101 - #9936) (linode docs) (binary_sensor.linode docs) (new-platform)
• Nederlandse spoorwegen (@b10m - #10136) (sensor.nederlandse_spoorwegen docs) (new-platform)
• added Yesss SMS platform (@flowolf - #10177) (new-platform)
• Add Sytadin Traffic component (@gautric - #9524) (new-platform)
• Added new Clickatell SMS messaging Notify Platform (@davlloyd - #9775) (notify.clickatell docs) (new-platform)
• Add Random binary sensor (@fabaff - #10164) (binary_sensor.random docs) (new-platform)
• Add gc100 platforms and component (@davegravy - #10159) (gc100 docs) (binary_sensor.gc100 docs) (switch.gc100 docs) (new-platform)
• Timer component (@danielperna84 - #9889) (timer docs) (new-platform)
• integration with Remember The Milk. (@ChristianKuehnel - #9803) (remember_the_milk docs) (new-platform)
• Luftdaten sensor (@lichtteil - #10274) (sensor.luftdaten docs) (new-platform)

release 0.57.1 - november 4

• Fix login screen not showing when no password stored (@balloob)

release 0.57.2 - november 5

• Update frontend with fixes for setting temperature on climate card (@balloob)
• Fix setting max brightness for TRADFRI (@ggravlingen - #10359)

release 0.57.3 - november 11

• Tellstick Duo acync callback fix (@stefan-jonasson - #10384) (tellstick docs)
• Fixed update() method and removed ding feature from stickupcams/floodlight (@tchellomello - #10428) (binary_sensor.ring docs) (camera.ring docs) (sensor.ring 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.

Most system engineers are very familiar with SSH (Secure shell). This tool which contains a server part and a client part is used to access a remote system in a secure way. It can also help you if your are running Home Assistant but don’t want to expose it to the public. On a Linux system SSH is often available by default. If you are using a Windows installation additional steps are required which are not covered here.

In this blog post we are going to use the tunneling option of SSH to create a secure connection and forward the Home Assistant frontend to a local system.

If you are planning to host a Home Assistant meetup or doing a talk, then you probably want to show Home Assistant to an audience. You could use a Wireless router, bulbs, switches, and a single board computer to do a realistic demo. For a workshop, this is what I usually do because I think that working with physical hardware is more fun for the participants. The issue is that you need time to set up, power and space. For a talk or in a location, where you only have a beamer and a table or a lectern, the physical hardware approach is not very convenient.

The simplest way to show Home Assistant to others is the online demo at /demo/

Home Assistant's online demo

This blog post is about building a super simple analog sensor for Home Assistant. The physical sensor will send the data over its virtual serial port as it will be connected over USB. The concept is similar to the TEMPer USB devices. The attatched sensor type to the microcontroller can be any kind of sensor which gives you an analog signal from brightness over soil moisture to temperature.

The microcontroller will only transfer the voltage of an analog input pin which will be between 0 and 1024. Home Assistant will use the new serial sensor platform to read the data and perform actions to convert the raw reading into a real measurement. This means that you don’t have to adjust the code of your microcontroller if you change the attached sensor type.

The assembled sensor

We reached another milestone aka number: 10000. GitHub is assigning numbers to pull requests and issues and the “10000” is a PR. Our ratio is around 1/3 issues and 2/3 pull requests. To be more precise: 64% pull requests and 36% issues.

If you haven’t noticed, there is now a glossary that collects some Home Assistant relevant terms. Talking about the documentation: @DubhAd rewrote large parts of the Z-Wave section. More structure to get started and to find details during the setup and the configuration.

Google Assistant / Google Home integration

This release includes a new component to integrate Home Assistant with Google Assistant by Phil Kates. We integrate via the Smart Home API, this means that you will be able to control your devices in Home Assistant via any device that has Google Assistant. Learn more in the documentation.

Hacktoberfest

Hacktoberfest is still on and so far we have received a lot improvements. We can’t make any promises to review everything by the end of October, but we are trying to make sure that you will get your t-shirt.

Map

The map is now its own component. Similar to configuration (config:), it will not show up without adding it to your configuration.yaml file.

map:

Travis CI

Why not observe your Travis CI jobs with Home Assistant? @tchellomello created a Travis CI sensor which allows one to check on the current state of Travis jobs. Now you can make sure that the coffee is ready when the build passed.

New Platforms

• Add Arlo alarm control panel component (@vickyg3 - #9711) (alarm_control_panel.arlo docs) (new-platform)
• Abode Temp, Humidity, and Light Sensor (@MisterWil - #9709) (abode docs) (sensor.abode docs) (new-platform)
• Introducing support to Travis-CI (@tchellomello - #9701) (sensor.travisci docs) (new-platform)
• Skybell (@MisterWil - #9681) (skybell docs) (binary_sensor.skybell docs) (camera.skybell docs) (light.skybell docs) (sensor.skybell docs) (switch.skybell docs) (new-platform)
• Xiaomi Smart WiFi Socket and Smart Power Strip integration (@syssi - #9138) (switch.xiaomi_miio docs) (new-platform)
• Add notification platform for Rocket.Chat (@webworxshop - #9553) (notify.rocketchat docs) (new-platform)
• Tesla bug fixes. (@zabuldon - #9774) (tesla docs) (binary_sensor.tesla docs) (climate.tesla docs) (lock.tesla docs) (sensor.tesla docs) (switch.tesla docs) (new-platform)
• Split map panel out into its own component (@cgarwood - #9814) (map docs) (breaking change) (new-platform)
• Support for Yi cameras (@bachya - #9787) (camera.yi docs) (new-platform)
• Add namecheap DNS component (@Munsio - #9821) (namecheapdns docs) (new-platform)
• Uptime sensor (@fronzbot - #9856) (sensor.uptime docs) (new-platform)
• Cloud connection via aiohttp (@balloob - #9860) (new-platform)
• Google Actions for Assistant (@philk - #9632) (google_assistant docs) (http docs) (new-platform)
• A new platform for controlling Monoprice 6-Zone amplifier (@etsinko - #9662) (media_player.monoprice docs) (new-platform)
• Add serial sensor (@fabaff - #9861) (sensor.serial docs) (new-platform)
• Add Toon support (@Boltgolt - #9483) (toon docs) (climate.toon docs) (sensor.toon docs) (switch.toon docs) (new-platform)

0.56.1 - October 22

• Fix device update / entity_id with names (@pvizeli - #10029)
• fix temperature/humidity sensors valid values (@bieniu - #10024) (sensor.xiaomi_aqara docs)

0.56.2 - October 23

• Fix gateway illumination sensor value (@bieniu - #10045) (sensor.xiaomi_aqara docs)
• Fix device update/entity_id with names (@rytilahti - #10053) (switch.tplink docs)
• Remove warning component / Update event trigger for UI created (@pvizeli - #10060)

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.

Show notes available on the Home Assistant Podcast Website

Listen online

This Pull Request shows in a clear way what happens if the documentation is not as good as it should be. In short, it’s about Templating and how people start to think about creative ways to solve it if it’s not documented. Let’s assume that we want the current year. There are a couple of options available to do that:

• Query JSON Test with a rest sensor and a value_template:.
• Use a time_date sensor and a template {{ strptime(states('sensor.date'), '%Y-%m-%d').year }}.
• Write a script in language X and use it with the command sensor or use date +"%Y" as a command:.

Beside the improved Wink support which was contributed by @w1ll1am23, ships this release a wide variety of new components and platforms. The input_slider components has received a makeover by @BioSehnsucht and is now input_number. @tinloaf added a feature that allows you to enter dates: input_datetime. Both will help you to improve your automation rules.

DuckDNS

Using Home Assistant with DuckDNS for Dynamic DNS (DDNS or DynDNS) is an old story. DuckDNS is also integrated in Hass.io. 0.55 ships a component for non Hass.io users to get a similar feature.

Recorder

The purging of data was improved. With purge_interval you can schedule regular purges of older events and states. In combination you can specify with purge_keep_days the amount of days you want to keep. The new service recorder.purge allows you to handle this task when needed.

Owntracks

Owntracks is an easy way to track your devices. For some times we have the device tracker which depends on MQTT but thanks to a new feature in Owntracks we can now offer support for HTTP. The new platform doesn’t require a MQTT broker but sends messages directly as HTTP requests to Home Assistant.

Tibber

This release introduces a new sensor: Tibber. The sensor provides the current electricity price if you are a Tibber customer. This will allow you to make automation for turning off the heater when the electricity price is high or only charge your electric car when the prices are low. We further plan to add support for showing future electricity prices and historic electricity consumption data. Tibber is currently only available in Norway and Sweden

The Things Network

The Things Network (TTN) is a LoRaWAN based network especially designed for IoT devices. With this integration one can observe the state of devices which are out of range of the local WiFi network as long as they are connected to a TTN gateway.

New Platforms

• GeoRSS sensor (@exxamalte - #9331) (sensor.geo_rss_events docs) (new-platform)
• Add DuckDNS component (@balloob - #9556) (duckdns docs) (new-platform)
• Add OwnTracks over HTTP (@balloob - #9582) (http docs) (device_tracker.owntracks docs) (device_tracker.owntracks_http docs) (new-platform)
• Add an input_datetime (@tinloaf - #9313) (input_datetime docs) (new-platform)
• Cover component for RFlink (@passie - #9432) (rflink docs) (cover.rflink docs) (new-platform)
• Introducing support to Melnor RainCloud sprinkler systems (@tchellomello - #9287) (raincloud docs) (binary_sensor.raincloud docs) (sensor.raincloud docs) (switch.raincloud docs) (new-platform)
• MQTT climate platform [continuation of #8750] (@tinloaf - #9589) (climate.mqtt docs) (new-platform)
• Add Tibber sensor (@danielhiversen - #9661) (sensor.tibber docs) (new-platform)
• Updating clicksendaudio component based on feedback (@jeroenterheerdt - #9692) (notify.clicksendaudio docs) (new-platform)
• Support for The Things Network (@fabaff - #9627) (thethingsnetwork docs) (sensor.thethingsnetwork docs) (new-platform)

0.55.1 - October 15

• Fix for TypeError in synology camera (@snjoetw - #9754) (camera.synology docs)
• missing is_closed ( rflink cover fix ) (@passie - #9776) (cover.rflink docs)
• [light.tradfri] Fix transition time (@lwis - #9785) (light.tradfri docs)
• OwnTracks: Fix handler is None checking (@balloob - #9794) (device_tracker.owntracks docs)
• Changed yaml.load into yaml.safe_load (@GenericStudent - #9841) (google docs)
• Bugfix/9811 jinja autoescape (@GenericStudent - #9842)
• Livebox Play TV bug: fix #9839 (@pschmitt - #9880)

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.

Update February 16, 2018: Home Assistant 0.64 will be the last release to support Python 3.4. Starting with release 0.65, Home Assistant will require a minimum version of Python 3.5.3.

Starting with our next release, 0.55, we will deprecate Python 3.4 support. The current plan is to remove support for Python 3.4 at the beginning of 2018.

Python 3.5 was released on September 13th, 2015. It has since then become the default Python installation on the stable releases of Debian, Ubuntu, Raspbian and Hassbian. Our other own operating system, Hass.io, is more advanced and is already running the greatly improved Python 3.6.

The jump to Python 3.5 as a minimum version is driven by the Home Assistant core, which is based on asyncio. Starting with Python 3.5, asyncio got improved support in the language with dedicated keywords async and await. As this is the proper way of doing async in Python, we’re seeing a move by async libraries to either only support the new syntax from the beginning or dropping support for the Python 3.4 approach. Not moving along means an increased maintenance burden as we cannot use the latest releases of our libraries. Next to that it will prevent our users from being able to leverage the bug fixes and performance improvements that come with Python 3.5.

Hass.io

If you’re running Hass.io, you don’t have to do anything. Your system will always stay up to date.

Hassbian

If you’re running Hassbian it’s recommended that you make a backup of your configuration files and restore them on a fresh install. Upgrading an existing installation isn’t recommended.

Windows

If you’re on Windows, you’re fine as our minimum version for Windows has been 3.5 for a while now.

Other Debian based systems

If you’re running a Debian based system, follow these instructions to upgrade.