The images for the Raspberry Pi family and the Intel NUC are an easy way to get started with Hass.io. For a test or if you have a system which is already hosting virtual machines then the Hass.io installer is an option to use Hass.io in a virtualized environment. In this guide the host is a Fedora 27 system with libvirt support and the guest will be running Debian 9. Hass.io will be installed on the guest.

Translation update

Translations are up and running in full speed. Shortly after the last release we got our translation pipeline figured out. @armills and @c727 are doing an amazing job managing this project. We’ve doubled the number of supported languages to 42 and the amount of keys to translate went from 8 to 130. Our translators are on top of their game and 79% is already translated.

Talking about our translators, we now have 445 people with an account to help with translations. Not bad for 3 weeks!

And because more translations is more better, @robbiet480 has added the iOS app to Lokalise, our translation management platform. The iOS app is currently supported in 7 different languages.

Learn more about how to help with translations

Frontend improvements continue

Thanks to @Andrey-git we now are able to serve the frontend in modern JavaScript. Leveraging modern JavaScript makes the frontend faster to load and run. For now it’s opt-in but we’re looking into making it opt-out in the future. The ES5 version of the frontend will remain available for older devices.

To try it once, add ?latest to your Home Assistant bookmark. To make it the default on your installation, update your config to look like this:

frontend:
  javascript_version: latest

System log enhanced

Our about screen that shows the error logs has gained a nice upgrade by @postlund. Now the 50 latest exceptions will be displayed with the option to get more information.

Screenshot of the about screen showing the system log.

New Platforms

• pyLoad download sensor (@iMarkus - #10089) (sensor.pyload docs) (new-platform)
• Add LaCrosse sensor platform (@hthiery - #10195) (sensor.lacrosse docs) (new-platform)
• Refactor Neato botvac components as a vacuum (@jabesq - #9946) (neato docs) (sensor.neato docs) (switch.neato docs) (vacuum.neato docs) (breaking change) (new-platform)
• Add platform and sensors for Vultr VPS (@GenericStudent - #9928) (vultr docs) (binary_sensor.vultr docs) (sensor.vultr docs) (new-platform)
• Adds support for Tile® Bluetooth trackers (@bachya - #10478) (device_tracker.tile docs) (new-platform)
• Support presence detection using Hitron Coda router (@arilotter - #9682) (device_tracker.hitron_coda docs) (new-platform)
• Add basic backend support for a system log (@postlund - #10492) (system_log docs) (new-platform)
• New sensor viaggiatreno. (@fabfurnari - #10522) (sensor.viaggiatreno docs) (new-platform)

Release 0.58.1 - November 21

• Fix yweather (@tinloaf - #10661)
• Properly initialize Harmony remote (@amelchio - #10665) (remote.harmony docs)
• Handle the new version of HydroQuebec website (@titilambert - #10682)
• Fix for time_date sensor (@etsinko - #10694) (sensor.time_date docs)
• Frontend fixes (@andrey-git @armills @balloob)

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.

Routers and gateways provided by broadband internet providers are very often limited regarding features and configuration possibilities. Most of these limitations affect the opportunities that allow users to set up port-forwarding, DMZ, and DHCP reservations since the suppliers figured that average user does not want (or should not) deal with these. Making your Home Assistant instance available remotely (and securely), in this case, becomes more difficult. Are you one of those unlucky ones?

There are a couple of options available to achieve a remote (and secure) accessible Home Assistant instance. However, almost all of them require you to: open one or more ports on your router, expose a public IP address, and require you to reserve a fixed IP in your DHCP server (or set up a static IP address). Examples of these are:

• Combination of DuckDNS (or similar), Let’s Encrypt (SSL), DHCP reservation, and forwarding a port to your device running Home Assistant.
• Setup a VPN, which often requires more hardware and software. Additionally, it also requires port-forwarding, DHCP reservation and most likely DuckDNS (or similar).
• SSH tunnel-ing. Which still requires port-forwarding, DHCP reservation and most likely (yeah, you’ve guessed it) DuckDNS (or similar).

There is, however, another option available that most people do not realize: Tor. Tor offers a capability that they refer to as Tor’s Hidden Services, which allows you to securely access your Home Assistant installation without the need for all these things. No need to forward and open ports, no need to expose your public IP, no DNS entry, no need for SSL certificates, and you do not have to assign a fixed IP to the device running your Home Assistant.

The most amazing part? It is super easy to set up!

The Home Assistant integration for The Things Network (TTN) uses their Storage feature to get the sensor data. The easiest way to observe TTN sensors would be MQTT as it doesn’t requires any additional configuration.

At the moment Home Assistant only supports one MQTT broker. This means that you can’t subscribe to topics which are located on different brokers.

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.