<![CDATA[Category: Release-Notes | Home Assistant]]> 2016-01-18T01:55:16+00:00 https://home-assistant.io/ Octopress <![CDATA[0.11: Extended support for DIY solutions]]> 2016-01-17T23:20:00+00:00 https://home-assistant.io/blog/2016/01/17/extended-support-for-diy-solutions First release of 2016 and we are on 🔥! The main repository has passed 2500 ⭐ on GitHub (2596 ⭐ as of now). This release also has a record number of 20 contributors all working on improving and extending Home Assistant. With the continued growth, I am very excited to see what 2016 will bring us 🤘.

Deprecations

]]> <![CDATA[0.10: Amazon Echo, iCloud, Dweet.io, Twitch and templating support!]]> 2015-12-22T09:30:00+00:00 https://home-assistant.io/blog/2015/12/22/amazon-echo-icloud-and-templates Alrighty, it’s time for Home Assistant 0.10. A lot amazing things have changed and sadly we also had to introduce a bunch of backwards incompatible changes. I would like to give a big shoutout to Philip Lundrigan (@philipbl) who put a lot in effort in helping the migration to move towards using templates for a wide variety of platforms.

Templates

This release introduces templates. This will allow you to parse data before it gets processed or create messages for notifications on the fly based on data within Home Assistant. The notification component and the new Alexa/Amazon Echo component are both using the new template functionality to render responses. A template editor has been added to the developer tool section in the app so you can get instant feedback if your templates are working or not.

The temperature at home is {{ states('sensor.temperature') }}.

More information and examples can be found in the template documentation.

Breaking changes

Templates will now be the only way to extract data from ‘raw’ sources like REST, CommandSensor or MQTT. This will replace any specific option that used to do this before. This means that precision, factor, attribute or json_path etc will no longer work.

Affected components and platforms:

]]> <![CDATA[0.9: Rollershutters, locks, binary sensors and InfluxDB]]> 2015-12-06T19:29:00+00:00 https://home-assistant.io/blog/2015/12/06/locks-rollershutters-binary-sensors-and-influxdb-support It’s been a few weeks but we managed to polish a nice new release of Home Assistant for y’all!

To update, run pip3 install --upgrade homeassistant.

]]> <![CDATA[0.8: Honeywell Thermostats, Orvibo switches and Z-Wave switches and lights ]]> 2015-11-16T21:27:00+00:00 https://home-assistant.io/blog/2015/11/16/zwave-switches-lights-and-honeywell-thermostats-now-supported 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

]]> <![CDATA[0.7.6: Amazon FireTV, Radiotherm thermostats]]> 2015-10-26T18:10:00+00:00 https://home-assistant.io/blog/2015/10/26/firetv-and-radiotherm-now-supported 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

Breaking changes

As part of this release we did some cleanup which introduced backwards incompatible changes:

Heat Control thermostat no longer includes scheduling features.
This feature has been removed completely. Use the automation component instead to control target temperature.

Config changed for calling a service from a script.
execute_service: has been replaced with service:. See component page for example. The old method will continue working for some time.

Scenes can no longer be turned off.
It is no longer possible to turn a scene off after it has been activated. The way it worked was unpredictable and causes a lot of confusion.

Downloader treats relative paths now relative to the config dir instead of the current working dir.
This makes more sense as most people run Home Assistant as a daemon

]]>