<![CDATA[Category: Release-Notes | Home Assistant]]> 2016-03-26T08:09:04+00:00 https://home-assistant.io/ Octopress <![CDATA[0.16: Embedded MQTT broker, Uber, Yamaha receivers and Growl]]> 2016-03-26T07:10:00+00:00 https://home-assistant.io/blog/2016/03/26/embedded-mqtt-broker-uber-yamaha-growl Party people, 0.16 is here! The big thing with this release is that we have completely removed the barrier to get started by MQTT by being able to launch an embedded MQTT server: hbMQTT. Just add mqtt: to your config and a broker is launched and connected with Home Assistant. See the documentation for more info.

Further in this release a bunch of cool new stuff, bug fixes and rewrites for the Vera and Tellstick component (see breaking changes section at bottom for this!).

Rock on.

Breaking changes

  • Automation: support for old deprecated config has been removed

  • Tellstick configuration has changed

tellstick:
  signal_repetitions: X
  • Vera configuration has changed
vera:
  vera_controller_url: http://192.168.1.161:3480/
  # Optional to exclude devices - this is a list of vera device ids
  exclude: [ 13, 14, 16, 20, 23, 72, 73, 74, 75, 76, 77, 78, 88, 89, 99]
  # Optional to import switches as lights - this is a list of vera device ids
  lights: [15, 17, 19, 21, 22, 24, 26, 43, 64, 70, 87]
]]> <![CDATA[0.15: Unforked Open Z-Wave, templated service calls, extended scene support and PEP257 compliance.]]> 2016-03-12T18:55:00+00:00 https://home-assistant.io/blog/2016/03/12/z-wave-pep257-templated-service-calls Two weeks has past so here is 0.15! We have been focussing a lot on quality. Making sure the system is more stable and reliable. I usually try to highlight one cool thing in the release notes but this release has 4 exciting announcements!

  • @fabaff has upgraded the codebase to follow the PEP257 documentation standard.
  • @partofthething has migrated us to use the main Python Open Z-Wave library instead of our forked version.
  • To make our automations more powerful, @persandstrom added the option to use templates to dynamically create service calls. This works for automation, Alexa, universal media player, template switch. Learn more.
  • @MartinHjelmare has upgraded our scene support to now support all built-in services and components.

Besides bug fixes, this release also brings:

# Example using templates for service and data in service call.
# Works for automation, Alexa, universal media player, template switch.
automation:
  - trigger:
      - platform: state
        entity_id: switch.bathroom
    action:
      service_template: >
        {% if is_state('switch.bathroom', 'on') %}
          switch.turn_on
        {% else %}
          switch.turn_off
        {% endif %}
      data_template:
        entity_id: switch.{{ states('input_select.is') }}

Breaking Changes

  • Media Player: Attributes to call service play_media has been renamed to
    media_content_type and media_content_id, to match the corresponding media
    player state attributes. This change affects automations, scripts and scenes.
]]> <![CDATA[0.14: Steam, D-Link smart plugs and Neurio Energy Sensors]]> 2016-02-27T22:15:00+00:00 https://home-assistant.io/blog/2016/02/27/steam-d-link-smart-plugs-and-neurio-energy-sensors It’s been another two weeks which means it’s time for release: 0.14!

Camera feeds are now directly embedded in the frontend.

Backwards incompatible changes

  • Component: Simple Alarm has been removed. Still available in the cookbook.
  • Script: Turning on a script that is already on is now a no-op instead of skipping current delay.
  • Wemo switches now have to be set up via the main Wemo component
  • Command line platforms for switch, sensor and binary_sensor have been renamed to command_line.
  • The rfxtrx sensors entity ids will incur a one time change to move to a stable format. See the docs for more details.
]]> <![CDATA[0.13: Speedtest.net, Bloomsky, Splunk and Garage Doors]]> 2016-02-13T06:15:00+00:00 https://home-assistant.io/blog/2016/02/13/speedtest-bloomsky-splunk-and-garage-doors The focus of 0.13 was on test coverage, big cheers to @rmkraus for his hard work on this. I’m proud to announce that we’ve hit the 90% test coverage of the core + important components. A big milestone for the project.

Examples of the new input_select and weblink components.

Not only did we gain a lot of test coverage, we also attracted a lot of new developers that contributed a variety of components and platforms:

]]> <![CDATA[0.12: Insteon, LIFX, Twitter and ZigBee]]> 2016-01-30T08:22:00+00:00 https://home-assistant.io/blog/2016/01/30/insteon-lifx-twitter-and-zigbee Another sprint has come to an end and it seems that we have not slowed down a single bit 🚀. 0.12 is full of new components, platforms and organizational additions.

I would like to give a shout out to Greg Dowling (@pavoni) as every release includes new work from him. He is constantly adding support for new platforms or improving the reliablity of existing components and platforms. Keep up the good work!

This release includes a very frequent requested feature: the ability to organize entities in different tabs in the frontend. See the demo to see this in action and read more in the group documentation how to get started.

Example of the new views in the frontend. Learn more.

Backwards incompatible changes

  • Nest config has moved from thermostat to the Nest component.
  • Entity IDs for Z-Wave devices are now generated in a deterministic way causing all IDs to change starting this release. This is a one time change.
]]>