0.8: Honeywell Thermostats, Orvibo switches and Z-Wave switches and lights

1 minute reading time
  • Release-Notes
Comments

We have all been hard at work to get this latest release ready. One of the big highlights in this release is the introduction of an extended iconset to be used in the frontend (credits to @happyleavesaoc for idea and prototype). To get started with customizing, pick any icon from MaterialDesignIcons.com, prefix the name with mdi: and stick it into your customize section in configuration.yaml:

homeassistant:
  customize:
    switch.ac:
      icon: 'mdi:air-conditioner'

Breaking changes

  • Any existing zone icon will have to be replaced with one from MaterialDesignIcons.com.
  • LimitlessLED light services require colors to be specified in RGB instead of XY.

Changes


0.7.6: Amazon FireTV, Radiotherm thermostats

two minutes reading time
  • Release-Notes
Comments

After two weeks of hard work I’m proud to announce the release of Home Assistant v0.7.6. For this release the main focus was bugs, test coverage and documentation. And we exceeded expectations on all three fronts. Bugs have been squashed, test coverage increased to 85% and thanks to the hard work by @fabaff and myself the component section on the website has gotten a complete revamp.

Changes

Read on →

Report the temperature with ESP8266 to MQTT

seven minutes reading time
  • How-To
  • MQTT
  • ESP8266
Comments

I recently learned about the ESP8266, a $5 chip that includes WiFi and is Arduino compatible. This means that all your DIY projects can now be done for a fraction of the price.

For this tutorial, I’ll walk through how to get going with ESP8266, get the temperature and humidity and report it to MQTT where Home Assistant can pick it up.

Picture of the final setup (+ 2 LED for decoration)

Home Assistant will keep track of historical values and allow you to integrate it into automation.

Read on →

0.7.5: Blinkstick, SNMP, Telegram

Less than one minute reading time
  • Release-Notes
Comments

We discovered two issues annoying enough to warrant the release of 0.7.5:

  • Home Assistant package did not include the CloudMQTT certificate.
  • A bug in the core caused issues when some platforms are loaded twice.

This release also includes some new platforms (because they keep coming!):

Also, the media player was extended by @maddox to support the play media command. This has been implemented for the iTunes platform.


Home Assistant goes geo with OwnTracks

1 minute reading time
  • Release-Notes
Comments

A few weeks have past and it is time again for another release: version 0.7.4. This time we’re very glad to be able to introduce brand new integration with OwnTracks to allow tracking of people on a map. The geo support consists of three different parts:

We have added a new getting started section to get up and running.

Map in Home Assistant showing two people and three zones (home, school, work)

Ofcourse more things happened in the last three weeks. I’m moving away from my usual long post to a short summary of highlights:


Alarms, Sonos and iTunes now supported

two minutes reading time
  • Release-Notes
Comments

It’s like someone opened a can of rock solid developers and emptied it above our chat channel because it exploded with great conversations and solid contributions. Featured in release 0.7.3: Sonos, iTunes, Alarm component and Automation upgrade.

See GitHub for more detailed release notes.

Migration note: the scheduler component has been removed in favor of the automation component.

Sonos Sonos support has been added by @rhooper and @SEJeff. Home Assistant is now able to automatically detect Sonos devices in your network and set them up for you. It will allow you to control music playing on your Sonos and change the volume.

iTunes and airplay speakers @maddox has contributed support for controlling iTunes and airplay speakers. For this to work you will have to run itunes-api on your Mac as middleware.

# Example configuration.yaml entry
media_player:
  platform: itunes
  name: iTunes
  host: http://192.168.1.50
  port: 8181
Read on →

Remote Monitoring with Glances

two minutes reading time
  • How-To
Comments

Inspired by a feature requests I started looking into the available options to do monitoring of remote hosts. The feature request is about displaying system information in a similar way than the systemmonitor sensor does it for the local system. After a while I started to think that it would be a nice addition for a small home network where no full-blown system monitoring setup is present.

Read on →

Home Assistant meets IFTTT

two minutes reading time
  • How-To
  • Release-Notes
Comments

Today we announce the release of Home Assistant v0.7.2 which includes brand new support by @sfam to integrate with IFTTT. IFTTT stands for If This, Then That and is a webservice that integrates with almost every possible webservice out there. Adding Home Assistant to this mix means Home Assistant can connect with all via IFTTT.

It is now possible to disable your irregation system if it is going to be cloudy tomorrow or tweet if your smoke alarm goes off.

Head over to the setup instructions to get started with IFTTT. Click the read more button for some example recipes.

Read on →

Using MQTT with Home Assistant

eight minutes reading time
  • How-To
  • MQTT
Comments

MQTT support was added to Home Assistant recently. The MQTT component will enable you to do all sort of things. Most likely you will use it to communicate with your devices. But Home Assistant doesn’t care where the data is coming from or is limited to real hardware as long as there is MQTT support. This means that it doesn’t matter if the data is coming from a human, a web service, or a device.

A great example is shown in a Laundry Automation post in this blog.

This post will give you a small overview of some other possibilities on how to use MQTT with Home Assistant.

Read on →

0.7: Better UI and improved distribution

three minutes reading time
  • Release-Notes
Comments

As Home Assistant is gaining more and more users we started to feel the pain from not having a proper release mechanism. We had no version numbering and required users to checkout the source using Git to get started. On top of that, as the number of devices that we support keeps raising, so did the number of dependencies that are used. That’s why we decided to change the way we roll. From now on:

  • Each release will have a version number, starting with version 0.7. This was chosen because it shows that we have been around for some time but are not considering ourselves to be fully stable.
  • Each release will be pushed to PyPi. This will be the only supported method of distribution.
  • Home Assistant is available after installation as a command-line utility hass.
  • The default configuration location has been moved from config in the current working directory to ~/.homeassistant (%APPDATA%/.homeassistant on Windows).
  • Requirements for components and platforms are no longer installed into the current Python environment (being virtual or not) but will be installed in <config-dir>/lib.

A huge shout out to Ryan Kraus for making this all possible. Please make sure you read the full blog post for details on how to migrate your existing setup.

And while Ryan was fixing distribution, I have been hard at work in giving Home Assistant a face lift. We already looked pretty good but lacked proper form of organization for users with many devices. The new UI moves away from a card per entity and has cards per group and domain instead. The demo has been updated so give it a spin.

Screenshots of the new UI

Read on →