Markdown fixes
This commit is contained in:
Paulus Schoutsen
parent
08d65ba714
commit
47eae9077e
52 changed files with 247 additions and 406 deletions
|
|
@ -25,7 +25,7 @@ Read on to learn how to enable the notify component and integrate it with other
|
|||
|
||||
To enable the new notify component, add the following to your `home-assistant.conf`:
|
||||
|
||||
```
|
||||
```conf
|
||||
[notify]
|
||||
platform=pushbullet
|
||||
api_key=ABCDEFGHJKLMNOPQRSTUVXYZ
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ Most devices still require some sort of interaction from the user after being di
|
|||
|
||||
To enable the discovery component, add the following to your `home-assistant.conf`:
|
||||
|
||||
```
|
||||
```conf
|
||||
[discovery]
|
||||
```
|
||||
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ The new integration exists out of two parts: a generic thermostat component and
|
|||
|
||||
If you own a Nest thermostat, add the following lines to your `home-assistant.conf`:
|
||||
|
||||
```
|
||||
```conf
|
||||
[thermostat]
|
||||
platform=nest
|
||||
username=YOUR_USERNAME
|
||||
|
|
|
|||
|
|
@ -9,8 +9,7 @@ comments: true
|
|||
categories: core
|
||||
---
|
||||
|
||||
Home Assistant is now using [YAML](http://yaml.org/) for it's configuration file.
|
||||
YAML allows the use of lists, which should make the configuration file a bit more flexible and useful. The new configuration file format is backwards compatible with existing components. Because of this, there is no need for component developers to update their components.
|
||||
Home Assistant is now using [YAML](http://yaml.org/) for it's configuration file. YAML allows the use of lists, which should make the configuration file a bit more flexible and useful. The new configuration file format is backwards compatible with existing components. Because of this, there is no need for component developers to update their components.
|
||||
|
||||
The new file is named configuration.yaml and if it can't be found in your config directory, Home Assistant will instead try to find the old configuration file, home-assistant.conf.
|
||||
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ categories: release-notes
|
|||
---
|
||||
A new version of Home Assistant has just been pushed out. It contains bugfixes contributed by [jamespcole](https://github.com/jamespcole), [andythigpen](https://github.com/andythigpen), [trainman419](https://github.com/trainman419) and [me](https://github.com/balloob). It also adds a bunch of great new features:
|
||||
|
||||
__Script__<br>
|
||||
__Script__
|
||||
Andythigpen has contributed a script component. This allows users to create a sequence of service calls and delays. Scripts can be started using the service `script/turn_on` and interrupted using the service `script/turn_off`. A separate page has been added to the frontend to see the status of your scripts.
|
||||
|
||||
```yaml
|
||||
|
|
@ -34,7 +34,7 @@ script:
|
|||
|
||||
<!--more-->
|
||||
|
||||
__Scene__<br>
|
||||
__Scene__
|
||||
I (Paulus) have contributed a scene component. A user can create scenes that capture the states you want certain entities to be. For example a scene can contain that light A should be turned on and light B should be bright red. Deactivating a scene will restore the previous state from before the scene was activated. Just like scripts, scenes have their own separate page to see which scenes are on.
|
||||
|
||||
```yaml
|
||||
|
|
@ -50,9 +50,8 @@ scene:
|
|||
```
|
||||
|
||||
<a name='sabnzbd'></a>
|
||||
__SABnzbd__<br>
|
||||
<img src='/images/supported_brands/sabnzbd.png' style='border:none; box-shadow: none; float: right;' height='50' />
|
||||
James Cole has contributed support to integrate SABnzbd. This will allow you to monitor your downloads from within Home Assistant and setup automation based on the information.
|
||||
__SABnzbd__
|
||||
<img src='/images/supported_brands/sabnzbd.png' style='border:none; box-shadow: none; float: right;' height='50' /> James Cole has contributed support to integrate SABnzbd. This will allow you to monitor your downloads from within Home Assistant and setup automation based on the information.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
|
@ -72,9 +71,8 @@ sensor:
|
|||
```
|
||||
|
||||
<a name='pushover'></a>
|
||||
__PushOver__<br>
|
||||
<img src='/images/supported_brands/pushover.png' style='border:none; box-shadow: none; float: right;' height='50' />
|
||||
James Cole has also contributed support for <a href='https://pushover.net/'>the PushOver service</a> as a platform for the notify component. This allows components to send messages to the user using PushOver.
|
||||
__PushOver__
|
||||
<img src='/images/supported_brands/pushover.png' style='border:none; box-shadow: none; float: right;' height='50' /> James Cole has also contributed support for <a href='https://pushover.net/'>the PushOver service</a> as a platform for the notify component. This allows components to send messages to the user using PushOver.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
|
|
|||
|
|
@ -10,16 +10,15 @@ categories: release-notes
|
|||
|
||||
It's been a month since the latest update and a lot has happened again. Here a quick overview of the new things.
|
||||
|
||||
__Line Charts__<br>
|
||||
__Line Charts__
|
||||
[James](https://github.com/jamespcole) has upgraded the history in the frontend to support line graphs. Line graphs will be shown for any entity that has a unit of measurement. The line graphs will also be shown in the more info card of an entity. [See the demo for a live example.](/demo/)
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/screenshots/history-line-graphs.png'>
|
||||
</p>
|
||||
|
||||
__ISY994 hub support__<br>
|
||||
<img src='/images/supported_brands/universal_devices.png' style='border:none; box-shadow: none; float: right;' height='50' />
|
||||
[Ryan](https://github.com/rmkraus) has contributed support to integrate the ISY994 hub by Universal Devices. This allows you to integrate your X10/Insteon sensors, switches and lights.
|
||||
__ISY994 hub support__
|
||||
<img src='/images/supported_brands/universal_devices.png' style='border:none; box-shadow: none; float: right;' height='50' /> [Ryan](https://github.com/rmkraus) has contributed support to integrate the ISY994 hub by Universal Devices. This allows you to integrate your X10/Insteon sensors, switches and lights.
|
||||
|
||||
He has created an extensive getting started guide which can be found on [the ISY994 component page](/components/isy994/).
|
||||
|
||||
|
|
@ -28,9 +27,8 @@ He has created an extensive getting started guide which can be found on [the ISY
|
|||
isy994:
|
||||
```
|
||||
|
||||
__Logbook__<br>
|
||||
<img src='/images/screenshots/logbook.png' style='margin-left:10px; float: right;' height="100" />
|
||||
I (Paulus) have added a logbook component. The logbook component provides a different perspective on the history of your house by showing all the changes that happened to your house in chronological order. [See the demo for a live example.](/demo/)
|
||||
__Logbook__
|
||||
<img src='/images/screenshots/logbook.png' style='margin-left:10px; float: right;' height="100" /> I (Paulus) have added a logbook component. The logbook component provides a different perspective on the history of your house by showing all the changes that happened to your house in chronological order. [See the demo for a live example.](/demo/)
|
||||
<span class='clearfix'></span>
|
||||
|
||||
```yaml
|
||||
|
|
@ -40,9 +38,8 @@ logbook:
|
|||
|
||||
<!--more-->
|
||||
|
||||
__Transmission support__<br>
|
||||
<img src='/images/supported_brands/transmission.png' style='border:none; box-shadow: none; float: right;' height='50' />
|
||||
James has also contributed support for integrating Transmission into Home Assistant.
|
||||
__Transmission support__
|
||||
<img src='/images/supported_brands/transmission.png' style='border:none; box-shadow: none; float: right;' height='50' /> James has also contributed support for integrating Transmission into Home Assistant.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
|
@ -59,7 +56,7 @@ sensor:
|
|||
- type: 'upload_speed'
|
||||
```
|
||||
|
||||
__Modbus support__<br>
|
||||
__Modbus support__
|
||||
[Kixam](https://github.com/kixam) has contributed support for modbus, a serial communication protocol to control PLCs. It currently supports sensors and switches which can be controlled over serial, TCP and UDP connections.
|
||||
|
||||
```yaml
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ To update to the latest version, run <code>scripts/update</code>. Please report
|
|||
|
||||
<!--more-->
|
||||
|
||||
__Overwriting Entity Attributes__<br>
|
||||
__Overwriting Entity Attributes__
|
||||
Before diving into the newly supported devices and services, I want to highlight an awesome configuration enhancement by [rmkraus](https://github.com/rmkraus): overwriting entity attributes.
|
||||
|
||||
These new configuration settings allow you to overwrite entity state attributes. The main usage for this is being able to overwrite attributes that influence how an entity is shown in the interface.
|
||||
|
|
@ -37,9 +37,8 @@ homeassistant:
|
|||
entity_picture: http://graph.facebook.com/schoutsen/picture
|
||||
```
|
||||
|
||||
__MySensors__<br>
|
||||
<img src='/images/supported_brands/mysensors.png' style='border:none; box-shadow: none; float: right;' height='50' />
|
||||
[Andythigpen](https://github.com/andythigpen) and [Theolind](https://github.com/theolind) have added support for the [MySensors platform](http://www.mysensors.org) to Home Assistant.
|
||||
__MySensors__
|
||||
<img src='/images/supported_brands/mysensors.png' style='border:none; box-shadow: none; float: right;' height='50' /> [Andythigpen](https://github.com/andythigpen) and [Theolind](https://github.com/theolind) have added support for the [MySensors platform](http://www.mysensors.org) to Home Assistant.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
|
@ -48,9 +47,8 @@ sensor:
|
|||
port: /dev/ttyACM0
|
||||
```
|
||||
|
||||
__OpenWeatherMap__<br>
|
||||
<img src='/images/supported_brands/openweathermap.png' style='border:none; box-shadow: none; float: right;' height='50' />
|
||||
[Fabaff](https://github.com/fabaff) has contributed support for [OpenWeatherMap](http://openweathermap.org). This will allow you to integrate local meteorological data into Home Assistant.
|
||||
__OpenWeatherMap__
|
||||
<img src='/images/supported_brands/openweathermap.png' style='border:none; box-shadow: none; float: right;' height='50' /> [Fabaff](https://github.com/fabaff) has contributed support for [OpenWeatherMap](http://openweathermap.org). This will allow you to integrate local meteorological data into Home Assistant.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
|
@ -68,9 +66,8 @@ sensor:
|
|||
- type: 'snow'
|
||||
```
|
||||
|
||||
__InstaPush__<br>
|
||||
<img src='/images/supported_brands/instapush.png' style='border:none; box-shadow: none; float: right;' height='50' />
|
||||
[Fabaff](https://github.com/fabaff) has contributed support for [InstaPush](https://instapush.im). This will allow you send messages from Home Assistant to your iOS and Android devices.
|
||||
__InstaPush__
|
||||
<img src='/images/supported_brands/instapush.png' style='border:none; box-shadow: none; float: right;' height='50' /> [Fabaff](https://github.com/fabaff) has contributed support for [InstaPush](https://instapush.im). This will allow you send messages from Home Assistant to your iOS and Android devices.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
|
@ -83,9 +80,8 @@ notify:
|
|||
tracker: ABCDEFGHJKLMNOPQRSTUVXYZ
|
||||
```
|
||||
|
||||
__XMPP__<br>
|
||||
<img src='/images/supported_brands/xmpp.png' style='border:none; box-shadow: none; float: right;' height='50' />
|
||||
[Fabaff](https://github.com/fabaff) has contributed support for Jabber/XMPP. This will allow you send messages from Home Assistant to anyone on Jabber/XMPP.
|
||||
__XMPP__
|
||||
<img src='/images/supported_brands/xmpp.png' style='border:none; box-shadow: none; float: right;' height='50' /> [Fabaff](https://github.com/fabaff) has contributed support for Jabber/XMPP. This will allow you send messages from Home Assistant to anyone on Jabber/XMPP.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
|
@ -96,9 +92,8 @@ notify:
|
|||
recipient: YOUR_RECIPIENT
|
||||
```
|
||||
|
||||
__Notify My Android__<br>
|
||||
<img src='/images/supported_brands/nma.png' style='border:none; box-shadow: none; float: right;' height='50' />
|
||||
[Fabaff](https://github.com/fabaff) has contributed support for [Notify My Android](http://www.notifymyandroid.com/). This will allow you to send messages from Home Assistant to your Android device.
|
||||
__Notify My Android__
|
||||
<img src='/images/supported_brands/nma.png' style='border:none; box-shadow: none; float: right;' height='50' /> [Fabaff](https://github.com/fabaff) has contributed support for [Notify My Android](http://www.notifymyandroid.com/). This will allow you to send messages from Home Assistant to your Android device.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
|
@ -108,7 +103,7 @@ notify:
|
|||
api_key: ABCDEFGHJKLMNOPQRSTUVXYZ
|
||||
```
|
||||
|
||||
__Time & Date sensor__<br>
|
||||
__Time & Date sensor__
|
||||
[Fabaff](https://github.com/fabaff) has contributed a time & date sensor. This will allow you to show the current time/date on the dashboard.
|
||||
|
||||
```yaml
|
||||
|
|
|
|||
|
|
@ -15,8 +15,7 @@ This release sets a record for the amount of people involved: 8! [Andythigpen](h
|
|||
A big improvement has been brought this release by wind-rider. He took the time to revive the Chromecast support and started improving the media player integration. This triggered other people to join in resulting in a revamped media player experience and support for the Music Player Daemon.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/screenshots/media_player-card.png' />
|
||||
Example of the new media player cards
|
||||
<img src='/images/screenshots/media_player-card.png' /> Example of the new media player cards
|
||||
</p>
|
||||
|
||||
<p class='note'>
|
||||
|
|
@ -39,9 +38,8 @@ Before jumping into the newly supported platforms, here are the other improvemen
|
|||
* Fix the device tracker getting in a deadlock by @balloob
|
||||
* Update documentation by @fabaff
|
||||
|
||||
__Music Player Daemon__<br>
|
||||
<img src='/images/supported_brands/mpd.png' style='border:none; box-shadow: none; float: right;' height='50' />
|
||||
Fabaff has contributed MusicPlayerDaemon support. The mpd platform allows you to control a [Music Player Daemon](http://www.musicpd.org/) from Home Assistant. Right now, only playback is supported and not playlist manipulation.
|
||||
__Music Player Daemon__
|
||||
<img src='/images/supported_brands/mpd.png' style='border:none; box-shadow: none; float: right;' height='50' /> Fabaff has contributed MusicPlayerDaemon support. The mpd platform allows you to control a [Music Player Daemon](http://www.musicpd.org/) from Home Assistant. Right now, only playback is supported and not playlist manipulation.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
|
@ -52,7 +50,7 @@ media_player:
|
|||
location: bedroom
|
||||
```
|
||||
|
||||
__Command line switch__<br>
|
||||
__Command line switch__
|
||||
A switch platform that issues specific commands when it is turned on and off. This might very well become our most popular platform as it allows anyone to integrate any type of switch into Home Assistant that can be controlled from the command line, including calling other scripts!
|
||||
|
||||
```yaml
|
||||
|
|
@ -65,7 +63,7 @@ switch:
|
|||
offcmd: switch_command off kitchen
|
||||
```
|
||||
|
||||
__LimitlessLED__<br>
|
||||
__LimitlessLED__
|
||||
This new platform can control your LimitlessLED lights from within Home Assistant. The lights are also known as EasyBulb, AppLight, AppLamp, MiLight, LEDme, dekolight or iLight.
|
||||
|
||||
```yaml
|
||||
|
|
@ -80,9 +78,8 @@ light:
|
|||
```
|
||||
|
||||
|
||||
__Bitcoin sensor__<br>
|
||||
<img src='/images/supported_brands/bitcoin.png' style='border:none; box-shadow: none; float: right;' height='50' />
|
||||
The bitcoin platform displays various details about the [Bitcoin](https://bitcoin.org) network. If you have an online wallet from [Blockchain.info](https://blockchain.info/) the sensor is capable to show your current balance.
|
||||
__Bitcoin sensor__
|
||||
<img src='/images/supported_brands/bitcoin.png' style='border:none; box-shadow: none; float: right;' height='50' /> The bitcoin platform displays various details about the [Bitcoin](https://bitcoin.org) network. If you have an online wallet from [Blockchain.info](https://blockchain.info/) the sensor is capable to show your current balance.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
|
@ -116,9 +113,8 @@ sensor:
|
|||
```
|
||||
|
||||
|
||||
__SMTP notificatoin platform__<br>
|
||||
<img src='/images/supported_brands/smtp.png' style='border:none; box-shadow: none; float: right;' height='50' />
|
||||
The smtp platform allows you to deliver notifications from Home Assistant to an e-mail recipient.
|
||||
__SMTP notificatoin platform__
|
||||
<img src='/images/supported_brands/smtp.png' style='border:none; box-shadow: none; float: right;' height='50' /> The smtp platform allows you to deliver notifications from Home Assistant to an e-mail recipient.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
|
@ -134,7 +130,7 @@ notify:
|
|||
```
|
||||
|
||||
|
||||
__Syslog notification platform__<br>
|
||||
__Syslog notification platform__
|
||||
The syslog platform allows you to deliver notifications from Home Assistant to the local syslog.
|
||||
|
||||
```yaml
|
||||
|
|
@ -144,13 +140,12 @@ notify:
|
|||
```
|
||||
|
||||
|
||||
__Swiss Public transport sensor__<br>
|
||||
__Swiss Public transport sensor__
|
||||
The swiss public transport sensor will give you the next two departure times from a given location to another one in Switzerland. See the [component page](/components/sensor.swiss_public_transport/) for more information how to set it up.
|
||||
|
||||
|
||||
__Transmission turtle mode switch__<br>
|
||||
<img src='/images/supported_brands/transmission.png' style='border:none; box-shadow: none; float: right;' height='50' />
|
||||
The transmission platform allows you to control your [Transmission](http://www.transmissionbt.com/) client from within Home Assistant. The platform enables you switch to your 'Alternative Speed Limits' (aka 'Turtle mode') setting.
|
||||
__Transmission turtle mode switch__
|
||||
<img src='/images/supported_brands/transmission.png' style='border:none; box-shadow: none; float: right;' height='50' /> The transmission platform allows you to control your [Transmission](http://www.transmissionbt.com/) client from within Home Assistant. The platform enables you switch to your 'Alternative Speed Limits' (aka 'Turtle mode') setting.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
|
@ -164,7 +159,7 @@ switch:
|
|||
```
|
||||
|
||||
|
||||
__Hikvision camera motion detection support__<br>
|
||||
__Hikvision camera motion detection support__
|
||||
This switch platform allows you to control your motion detection setting on your Hikvision camera.
|
||||
|
||||
```yaml
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ Another month has passed and some great new features have landed in Home Assista
|
|||
|
||||
This release includes some architectural changes by me. The first is that the frontend is now based on a [NuclearJS](http://optimizely.github.io/nuclear-js/) JavaScript backend. This has greatly helped to organize and optimize the frontend code. Another change is that Home Assistant will now install dependencies on-demand instead of installing dependencies for all supported devices.
|
||||
|
||||
__IP Camera Support__<br>
|
||||
__IP Camera Support__
|
||||
James has worked very hard to add support for IP cameras to Home Assistant which is included in this release. The initial release focusses on providing generic IP camera support. This means that any webcam that can exposes a JPEG image via a url can be integrated.
|
||||
|
||||
Home Assistant will route the requests to your camera via the server allowing you to expose IP camera's inside your network via the Home Assistant app.
|
||||
|
|
@ -33,9 +33,8 @@ To update to the latest version, run <code>scripts/update</code>. Please report
|
|||
|
||||
<!--more-->
|
||||
|
||||
__Arduino__<br>
|
||||
<img src='/images/supported_brands/arduino.png' style='border:none; box-shadow: none; float: right;' height='50' />
|
||||
Fabian has contributed support for interfacing with Arduinos. This makes it possible to connect your Arduino via USB and expose pins as sensor data and write to pins via switches. Have a look at [the docs](/components/arduino/) for an extensive guide to get started.
|
||||
__Arduino__
|
||||
<img src='/images/supported_brands/arduino.png' style='border:none; box-shadow: none; float: right;' height='50' /> Fabian has contributed support for interfacing with Arduinos. This makes it possible to connect your Arduino via USB and expose pins as sensor data and write to pins via switches. Have a look at [the docs](/components/arduino/) for an extensive guide to get started.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
|
@ -60,9 +59,8 @@ sensor:
|
|||
type: analog
|
||||
```
|
||||
|
||||
__Kodi (XBMC)__<br>
|
||||
<img src='/images/supported_brands/kodi.png' style='border:none; box-shadow: none; float: right;' height='50' />
|
||||
Ettisan has contributed a Kodi (XBMC) platform for the media player component. This allows you to track all the media that you are playing and allow you to control it.
|
||||
__Kodi (XBMC)__
|
||||
<img src='/images/supported_brands/kodi.png' style='border:none; box-shadow: none; float: right;' height='50' /> Ettisan has contributed a Kodi (XBMC) platform for the media player component. This allows you to track all the media that you are playing and allow you to control it.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
|
@ -74,9 +72,8 @@ media_player:
|
|||
password: my_secure_password
|
||||
```
|
||||
|
||||
__TP-Link__<br>
|
||||
<img src='/images/supported_brands/tp-link.png' style='border:none; box-shadow: none; float: right;' width='150' />
|
||||
Michael has added TP-Link support to the device tracker. This allows you to now detect presence if you have a TP-Link router.
|
||||
__TP-Link__
|
||||
<img src='/images/supported_brands/tp-link.png' style='border:none; box-shadow: none; float: right;' width='150' /> Michael has added TP-Link support to the device tracker. This allows you to now detect presence if you have a TP-Link router.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
|
@ -87,9 +84,8 @@ device_tracker:
|
|||
password: YOUR_ADMIN_PASSWORD
|
||||
```
|
||||
|
||||
__Efergy energy monitor__<br>
|
||||
<img src='/images/supported_brands/efergy.png' style='border:none; box-shadow: none; float: right;' height='50' />
|
||||
Miniconfig has contributed support for the [Efergy energy meters](https://efergy.com). To get an app token, log in to your efergy account, go to the Settings page, click on App tokens, and click "Add token".
|
||||
__Efergy energy monitor__
|
||||
<img src='/images/supported_brands/efergy.png' style='border:none; box-shadow: none; float: right;' height='50' /> Miniconfig has contributed support for the [Efergy energy meters](https://efergy.com). To get an app token, log in to your efergy account, go to the Settings page, click on App tokens, and click "Add token".
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
|
@ -105,7 +101,7 @@ sensor:
|
|||
currency: $
|
||||
```
|
||||
|
||||
__Forecast.io__<br>
|
||||
__Forecast.io__
|
||||
Fabian has added support for [Forecast.io](https://forecast.io/) to get weather forecasts for Home Assistant. You need an API key which is free but requires a [registration](https://developer.forecast.io/register). To add Forecast.io to your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
|
|
|
|||
|
|
@ -10,9 +10,8 @@ categories: release-notes
|
|||
|
||||
It's time for the August release and there is some serious good stuff this time. The core of Home Assistant has gone some serious clean up and a bump in test coverage thanks to [@balloob](https://github.com/balloob). If you're a developer, make sure you read up on [the deprecation notices](https://github.com/balloob/home-assistant/pull/251). [@fabaff](https://github.com/fabaff) did another great round of documentating all the various components.
|
||||
|
||||
__MQTT Support__<br>
|
||||
<img src='/images/supported_brands/mqtt.png' style='border:none; box-shadow: none; float: right;' height='50' />
|
||||
The big new addition in this release is the support for the MQTT protocol by [@fabaff](https://github.com/fabaff) with some help from [@balloob](https://github.com/balloob). It will now be possible to integrate any IoT device that talks via MQTT. For the initial release we support connecting Home Assistant to a broker (no TLS yet). Components can now subscribe and publish to MQTT topics ([see the example][mqtt-example]) and also support for the automation component [has been added][mqtt-automation]. For more information, see [the MQTT component page][mqtt-component].
|
||||
__MQTT Support__
|
||||
<img src='/images/supported_brands/mqtt.png' style='border:none; box-shadow: none; float: right;' height='50' /> The big new addition in this release is the support for the MQTT protocol by [@fabaff](https://github.com/fabaff) with some help from [@balloob](https://github.com/balloob). It will now be possible to integrate any IoT device that talks via MQTT. For the initial release we support connecting Home Assistant to a broker (no TLS yet). Components can now subscribe and publish to MQTT topics ([see the example][mqtt-example]) and also support for the automation component [has been added][mqtt-automation]. For more information, see [the MQTT component page][mqtt-component].
|
||||
|
||||
[mqtt-example]: https://github.com/balloob/home-assistant/blob/dev/config/custom_components/mqtt_example.py
|
||||
[mqtt-automation]: /components/automation/#mqtt-based-automation
|
||||
|
|
@ -32,9 +31,8 @@ mqtt:
|
|||
|
||||
<!--more-->
|
||||
|
||||
__Raspberry PI GPIO Support__<br>
|
||||
<img src='/images/supported_brands/raspberry-pi.png' style='border:none; box-shadow: none; float: right;' height='50' />
|
||||
[@gbarba](https://github.com/gbarba) has contributed support to use the general purpose input and output pins on a Raspberry PI as switches inside Home Assistant.
|
||||
__Raspberry PI GPIO Support__
|
||||
<img src='/images/supported_brands/raspberry-pi.png' style='border:none; box-shadow: none; float: right;' height='50' /> [@gbarba](https://github.com/gbarba) has contributed support to use the general purpose input and output pins on a Raspberry PI as switches inside Home Assistant.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
|
@ -45,9 +43,8 @@ switch:
|
|||
12: Light Desk
|
||||
```
|
||||
|
||||
__ASUSWRT based routers__<br>
|
||||
<img src='/images/supported_brands/asus.png' style='border:none; box-shadow: none; float: right;' height='50' />
|
||||
[@persandstrom](https://github.com/persandstrom) has contributed support to do prescence detection using ASUSWRT based routers.
|
||||
__ASUSWRT based routers__
|
||||
<img src='/images/supported_brands/asus.png' style='border:none; box-shadow: none; float: right;' height='50' /> [@persandstrom](https://github.com/persandstrom) has contributed support to do prescence detection using ASUSWRT based routers.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
|
@ -58,9 +55,8 @@ device_tracker:
|
|||
password: YOUR_ADMIN_PASSWORD
|
||||
```
|
||||
|
||||
__Logitech Squeezebox media player support__<br>
|
||||
<img src='/images/supported_brands/logitech.png' style='border:none; box-shadow: none; float: right;' height='50' />
|
||||
[@persandstrom](https://github.com/persandstrom) also contributed support for the Logitech Squeezebox media player. This allows you to control your Logitech Squeezebox from Home Assistant.
|
||||
__Logitech Squeezebox media player support__
|
||||
<img src='/images/supported_brands/logitech.png' style='border:none; box-shadow: none; float: right;' height='50' /> [@persandstrom](https://github.com/persandstrom) also contributed support for the Logitech Squeezebox media player. This allows you to control your Logitech Squeezebox from Home Assistant.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
|
@ -72,9 +68,8 @@ media_player:
|
|||
password: password
|
||||
```
|
||||
|
||||
__Slack notification support__<br>
|
||||
<img src='/images/supported_brands/slack.png' style='border:none; box-shadow: none; float: right;' height='50' />
|
||||
[@jamespcole](https://github.com/jamespcole) has contributed a Slack platform for the notification platform. This allows you to deliver messages to any channel.
|
||||
__Slack notification support__
|
||||
<img src='/images/supported_brands/slack.png' style='border:none; box-shadow: none; float: right;' height='50' /> [@jamespcole](https://github.com/jamespcole) has contributed a Slack platform for the notification platform. This allows you to deliver messages to any channel.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
|
@ -84,9 +79,8 @@ notify:
|
|||
default_channel: '#general'
|
||||
```
|
||||
|
||||
__Edimax Smart Switches support__<br>
|
||||
<img src='/images/supported_brands/edimax.png' style='border:none; box-shadow: none; float: right;' height='50' />
|
||||
[@rkabadi](https://github.com/rkabadi) has contributed support for integrating Edimax Smart Switches into Home Assistant.
|
||||
__Edimax Smart Switches support__
|
||||
<img src='/images/supported_brands/edimax.png' style='border:none; box-shadow: none; float: right;' height='50' /> [@rkabadi](https://github.com/rkabadi) has contributed support for integrating Edimax Smart Switches into Home Assistant.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
|
@ -98,7 +92,7 @@ switch:
|
|||
name: Edimax Smart Plug
|
||||
```
|
||||
|
||||
__RFXtrx sensor support__<br>
|
||||
__RFXtrx sensor support__
|
||||
[@danielhiversen](https://github.com/danielhiversen) has contributed support for RFXtrx sensors. It supports sensors that communicate in the frequency range of 433.92 MHz.
|
||||
|
||||
```yaml
|
||||
|
|
@ -110,7 +104,7 @@ sensor:
|
|||
|
||||
The path to your device, e.g. `/dev/serial/by-id/usb-RFXCOM_RFXtrx433_A1Y0NJGR-if00-port0`
|
||||
|
||||
__TEMPer temperature sensor support__<br>
|
||||
__TEMPer temperature sensor support__
|
||||
Support for Temper temperature sensors has been contributed by [@rkabadi](https://github.com/rkabadi).
|
||||
|
||||
```yaml
|
||||
|
|
|
|||
|
|
@ -17,9 +17,8 @@ As we didn't want to just push out bug fixes, this release includes a few additi
|
|||
- Support for modern TP-Link routers like the ArcherC9 line has been contributed by [@chrisvis](https://github.com/chrisvis).
|
||||
- Improved support for MQTT topic subscriptions has been contributed by [@qrtn](https://github.com/qrtn)
|
||||
|
||||
__Verisure Support__<br>
|
||||
<img src='/images/supported_brands/verisure.png' style='border:none; box-shadow: none; float: right;' height='50' />
|
||||
Home Assistant support to integrate your [Verisure](https://www.verisure.com/) alarms, hygrometers, sensors and thermometers has been contributed by [@persandstrom](https://github.com/persandstrom).
|
||||
__Verisure Support__
|
||||
<img src='/images/supported_brands/verisure.png' style='border:none; box-shadow: none; float: right;' height='50' /> Home Assistant support to integrate your [Verisure](https://www.verisure.com/) alarms, hygrometers, sensors and thermometers has been contributed by [@persandstrom](https://github.com/persandstrom).
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
|
|
|||
|
|
@ -54,7 +54,7 @@ Materials used:
|
|||
|
||||
Home Assistant Configuration:
|
||||
|
||||
```
|
||||
```yaml
|
||||
mqtt:
|
||||
broker: 192.168.1.100
|
||||
port: 1883
|
||||
|
|
|
|||
|
|
@ -9,31 +9,19 @@ categories: user-stories
|
|||
og_image: /images/screenshots/ui2015.png
|
||||
---
|
||||
|
||||
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:
|
||||
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 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`.
|
||||
- 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](https://github.com/rmkraus) for making this all possible. Please
|
||||
make sure you read [the full blog post][self] for details on how to migrate your existing setup.
|
||||
A huge shout out to [Ryan Kraus](https://github.com/rmkraus) for making this all possible. Please make sure you read [the full blog post][self] for details on how to migrate your existing setup.
|
||||
|
||||
[self]: /blog/2015/08/31/version-7-revamped-ui-and-improved-distribution/#read-more
|
||||
|
||||
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](/demo/) has been updated so give it a spin.
|
||||
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](/demo/) has been updated so give it a spin.
|
||||
|
||||
<p class='img'>
|
||||
<a href='/demo/'>
|
||||
|
|
@ -46,32 +34,26 @@ devices. The new UI moves away from a card per entity and has cards per group an
|
|||
|
||||
### {% linkable_title Migration to version 0.7 %}
|
||||
|
||||
For this example, let's say we have an old Home Assistant installation in
|
||||
`/home/paulus/home-assistant`.
|
||||
For this example, let's say we have an old Home Assistant installation in `/home/paulus/home-assistant`.
|
||||
|
||||
If you want to migrate your existing configuration to be used as the default configuration:
|
||||
|
||||
```bash
|
||||
cp -r /home/paulus/home-assistant ~/.homeassistant
|
||||
$ cp -r /home/paulus/home-assistant ~/.homeassistant
|
||||
```
|
||||
|
||||
It If you want to have the configuration in a different location, for example
|
||||
`/home/paulus/home-assistant-config`, you will have to point Home Assistant at this configuration
|
||||
folder when launching:
|
||||
It If you want to have the configuration in a different location, for example `/home/paulus/home-assistant-config`, you will have to point Home Assistant at this configuration folder when launching:
|
||||
|
||||
```bash
|
||||
hass --config /home/paulus/home-assistant-config
|
||||
$ hass --config /home/paulus/home-assistant-config
|
||||
```
|
||||
|
||||
### {% linkable_title New platforms %}
|
||||
|
||||
And last, but not least: new platforms!
|
||||
|
||||
__MQTT Sensors and Switches__<br>
|
||||
<img src='/images/supported_brands/mqtt.png' style='border:none; box-shadow: none; float: right;' height='50' />
|
||||
[@sfam](https://github.com/sfam) has blessed us with two more MQTT platforms to extend our
|
||||
integration with MQTTT: [sensor][mqtt-sensor] and [switch][mqtt-switch]. Both platforms require the
|
||||
MQTT component to be connected to a broker.
|
||||
__MQTT Sensors and Switches__
|
||||
<img src='/images/supported_brands/mqtt.png' style='border:none; box-shadow: none; float: right;' height='50' /> [@sfam](https://github.com/sfam) has blessed us with two more MQTT platforms to extend our integration with MQTTT: [sensor][mqtt-sensor] and [switch][mqtt-switch]. Both platforms require the MQTT component to be connected to a broker.
|
||||
|
||||
[mqtt-sensor]: /components/sensor.mqtt/
|
||||
[mqtt-switch]: /components/switch.mqtt/
|
||||
|
|
@ -94,9 +76,8 @@ switch:
|
|||
optimistic: false
|
||||
```
|
||||
|
||||
__Actiontec MI424WR Verizon FIOS Wireless router__<br>
|
||||
<img src='/images/supported_brands/actiontec.png' style='border:none; box-shadow: none; float: right;' height='50' />
|
||||
[Nolan](https://github.com/nkgilley) has contributed support for Actiontec wireless routers.
|
||||
__Actiontec MI424WR Verizon FIOS Wireless router__
|
||||
<img src='/images/supported_brands/actiontec.png' style='border:none; box-shadow: none; float: right;' height='50' /> [Nolan](https://github.com/nkgilley) has contributed support for Actiontec wireless routers.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
|
@ -107,10 +88,8 @@ device_tracker:
|
|||
password: YOUR_ADMIN_PASSWORD
|
||||
```
|
||||
|
||||
__DHT temperature and humidty sensors__<br>
|
||||
[@MakeMeASandwich](https://github.com/makemeasandwich) has contributed support for DHT temperature
|
||||
and humidity sensors. It allows you to get the current temperature and humidity from a DHT11, DHT22,
|
||||
or AM2302 device.
|
||||
__DHT temperature and humidty sensors__
|
||||
[@MakeMeASandwich](https://github.com/makemeasandwich) has contributed support for DHT temperature and humidity sensors. It allows you to get the current temperature and humidity from a DHT11, DHT22, or AM2302 device.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
|
@ -123,7 +102,7 @@ sensor:
|
|||
- humidity
|
||||
```
|
||||
|
||||
__Aruba device tracker__<br>
|
||||
__Aruba device tracker__
|
||||
[Michael Arnauts](https://github.com/michaelarnauts) has contributed support for Aruba wireless routers for presence detection.
|
||||
|
||||
```yaml
|
||||
|
|
|
|||
|
|
@ -10,14 +10,16 @@ categories: how-to mqtt
|
|||
og_image: /images/blog/2015-09-mqtt/arduino.png
|
||||
---
|
||||
|
||||
<img src='/images/supported_brands/mqtt.png' style='border:none; box-shadow: none; float: right;' height='80' />
|
||||
The [MQTT](https://en.wikipedia.org/wiki/MQTT) support was added to Home Assistant recently. The [MQTT component](https://home-assistant.io/components/mqtt/) 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.
|
||||
{::options coderay_line_numbers="table" /}
|
||||
|
||||
<img src='/images/supported_brands/mqtt.png' style='border:none; box-shadow: none; float: right;' height='80' /> [MQTT](https://en.wikipedia.org/wiki/MQTT) support was added to Home Assistant recently. The [MQTT component](https://home-assistant.io/components/mqtt/) 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](https://home-assistant.io/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/) post in this blog.
|
||||
|
||||
This post will give you a small overview of some other possibilities on how to use MQTT with Home Assistant.
|
||||
|
||||
<!--more-->
|
||||
|
||||
### {% linkable_title Manual usage %}
|
||||
|
||||
The simplest but not the coolest way as a human to interact with a Home Assistant sensor is launching a command manually. Let's create a "Mood" sensor. For simplicity Home Assistant and the MQTT broker are both running on the same host. The needed configuration snipplets to add to the `configuration.yaml` file consists of two parts: one for the broker and one for the sensor.
|
||||
|
|
@ -37,7 +39,7 @@ After a restart of Home Assistant the "Mood" sensor will show up in the frontend
|
|||
Now we can set the mood. The commandline tool (`mosquitto_pub`) which is shipped with `mosquitto` is used to send an MQTT message.
|
||||
|
||||
```bash
|
||||
mosquitto_pub -h 127.0.0.1 -t "home-assistant/fabian/mood" -m "bad"
|
||||
$ mosquitto_pub -h 127.0.0.1 -t "home-assistant/fabian/mood" -m "bad"
|
||||
```
|
||||
|
||||
<p class='img'>
|
||||
|
|
@ -45,7 +47,7 @@ mosquitto_pub -h 127.0.0.1 -t "home-assistant/fabian/mood" -m "bad"
|
|||
The Mood sensor
|
||||
</p>
|
||||
|
||||
This is a really bad example. Don't do this in the real world because you won't be able to create diagrams of historical data. Better use a numerical value.
|
||||
This is a really bad example. Don't do this in the real world because you won't be able to create diagrams of historical data. Better use a numerical value.
|
||||
|
||||
### {% linkable_title Python MQTT bindings %}
|
||||
|
||||
|
|
|
|||
|
|
@ -10,13 +10,9 @@ categories: how-to release-notes
|
|||
og_image: /images/blog/2015-09-ifttt/og_facebook.png
|
||||
---
|
||||
|
||||
Today we announce the release of Home Assistant v0.7.2 which includes brand new support by
|
||||
[@sfam][github-sfam] to integrate with [IFTTT][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.
|
||||
Today we announce the release of Home Assistant v0.7.2 which includes brand new support by [@sfam][github-sfam] to integrate with [IFTTT][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.
|
||||
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.
|
||||
|
||||
[github-sfam]: https://github.com/sfam
|
||||
[ifttt]: https://ifttt.com
|
||||
|
|
@ -25,13 +21,11 @@ if your smoke alarm goes off.
|
|||
<img src='/images/blog/2015-09-ifttt/splash.png'>
|
||||
</p>
|
||||
|
||||
Head over to the [setup instructions](/components/ifttt/) to get started with IFTTT. Click the
|
||||
read more button for some example recipes.
|
||||
Head over to the [setup instructions](/components/ifttt/) to get started with IFTTT. Click the read more button for some example recipes.
|
||||
|
||||
<!--more-->
|
||||
|
||||
In each of the following examples, make sure to replace the XXX in the url with your correct
|
||||
host address and api password.
|
||||
In each of the following examples, make sure to replace the XXX in the url with your correct host address and api password.
|
||||
|
||||
## {% linkable_title Turn off irregation system when not needed %}
|
||||
|
||||
|
|
@ -54,9 +48,7 @@ Maker channel setup:
|
|||
<img src='/images/blog/2015-09-ifttt/recipe-twitter.png' />
|
||||
</p>
|
||||
|
||||
This will tweet a message when an MQTT message is received that the smoke alarm has been triggered.
|
||||
Setup Maker channel with event name `HA_FIRE_ALARM` and Twitter channel to tweet the message in
|
||||
`value1`.
|
||||
This will tweet a message when an MQTT message is received that the smoke alarm has been triggered. Setup Maker channel with event name `HA_FIRE_ALARM` and Twitter channel to tweet the message in `value1`.
|
||||
|
||||
```yaml
|
||||
# Configuration.yaml entry
|
||||
|
|
|
|||
|
|
@ -23,21 +23,21 @@ In this post a default Fedora 22 Workstation installation is used on the host th
|
|||
|
||||
First some extra packages are needed beside Glances, especially the [bottle](http://bottlepy.org/docs/dev/index.html) webserver. I guess that Glances is available for your distribution as well. Otherwise follow those [instructions](https://github.com/nicolargo/glances#installation).
|
||||
|
||||
```
|
||||
sudo dnf -y install glances python-bottle
|
||||
```bash
|
||||
$ sudo dnf -y install glances python-bottle
|
||||
```
|
||||
|
||||
On Fedora the Firewall settings are strict. Let's open port 61208 to allow other hosts to connect to that port. This is not needed if you just want to observe your local machine.
|
||||
|
||||
```bash
|
||||
sudo firewall-cmd --permanent --add-port=61208/tcp
|
||||
sudo firewall-cmd --reload
|
||||
$ sudo firewall-cmd --permanent --add-port=61208/tcp
|
||||
$ sudo firewall-cmd --reload
|
||||
```
|
||||
|
||||
Launch `glances` and keep an eye on the output.
|
||||
|
||||
```bash
|
||||
glances -w
|
||||
$ glances -w
|
||||
Glances web server started on http://0.0.0.0:61208/
|
||||
```
|
||||
|
||||
|
|
@ -51,7 +51,7 @@ Now browse to http://IP_ADRRESS:61208/. You should see the webified view of Glan
|
|||
Another check is to access the API located at http://IP_ADRRESS:61208/api/2/mem/used and to confirm that a detail about your memory usage is provided as a JSON response. If so, you are good to proceed.
|
||||
|
||||
```bash
|
||||
curl -X GET http://IP_ADDRESS:61208/api/2/mem/used
|
||||
$ curl -X GET http://IP_ADDRESS:61208/api/2/mem/used
|
||||
{"used": 203943936}
|
||||
```
|
||||
|
||||
|
|
|
|||
|
|
@ -9,24 +9,17 @@ comments: true
|
|||
categories: release-notes
|
||||
---
|
||||
|
||||
It's like someone opened a can of rock solid developers and emptied it above our
|
||||
[chat channel](https://gitter.im/balloob/home-assistant) because it exploded with
|
||||
great conversations and solid contributions. Featured in release 0.7.3: Sonos, iTunes, Alarm component and Automation upgrade.
|
||||
It's like someone opened a can of rock solid developers and emptied it above our [chat channel](https://gitter.im/balloob/home-assistant) because it exploded with great conversations and solid contributions. Featured in release 0.7.3: Sonos, iTunes, Alarm component and Automation upgrade.
|
||||
|
||||
See [GitHub](https://github.com/balloob/home-assistant/releases/tag/0.7.3) for more detailed release notes.
|
||||
|
||||
_Migration note: the `scheduler` component has been removed in favor of the `automation` component._
|
||||
|
||||
__Sonos__<br>
|
||||
<img src='/images/supported_brands/sonos.png' style='border:none; box-shadow: none; float: right;' height='50' />
|
||||
Sonos support has been added by [@rhooper](https://github.com/rhooper) and [@SEJeff](https://github.com/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.
|
||||
__Sonos__
|
||||
<img src='/images/supported_brands/sonos.png' style='border:none; box-shadow: none; float: right;' height='50' /> Sonos support has been added by [@rhooper](https://github.com/rhooper) and [@SEJeff](https://github.com/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__<br>
|
||||
<img src='/images/supported_brands/itunes.png' style='border:none; box-shadow: none; float: right;' height='50' />
|
||||
[@maddox](https://github.com/maddox) has contributed support for controlling iTunes and airplay speakers. For this to work you will
|
||||
have to run [itunes-api](https://github.com/maddox/itunes-api) on your Mac as middleware.
|
||||
__iTunes and airplay speakers__
|
||||
<img src='/images/supported_brands/itunes.png' style='border:none; box-shadow: none; float: right;' height='50' /> [@maddox](https://github.com/maddox) has contributed support for controlling iTunes and airplay speakers. For this to work you will have to run [itunes-api](https://github.com/maddox/itunes-api) on your Mac as middleware.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
|
@ -39,10 +32,8 @@ media_player:
|
|||
|
||||
<!--more-->
|
||||
|
||||
__Automation__<br>
|
||||
Automation has gotten a lot of love. It now supports conditions, multiple triggers and new types of
|
||||
triggers. The best to get started with it is to head over to the new
|
||||
[getting started with automation](/getting-started/automation/) page.
|
||||
__Automation__
|
||||
Automation has gotten a lot of love. It now supports conditions, multiple triggers and new types of triggers. The best to get started with it is to head over to the new [getting started with automation](/getting-started/automation/) page.
|
||||
|
||||
```yaml
|
||||
# Example of entry in configuration.yaml
|
||||
|
|
@ -67,7 +58,5 @@ automation:
|
|||
entity_id: group.living_room
|
||||
```
|
||||
|
||||
__Verisure Alarms__<br>
|
||||
<img src='/images/supported_brands/verisure.png' style='border:none; box-shadow: none; float: right;' height='50' />
|
||||
We now support arming and disarming your verisure alarm from within Home Assistant thanks to added
|
||||
support by [@persandstrom](https://github.com/persandstrom).
|
||||
__Verisure Alarms__
|
||||
<img src='/images/supported_brands/verisure.png' style='border:none; box-shadow: none; float: right;' height='50' /> We now support arming and disarming your verisure alarm from within Home Assistant thanks to added support by [@persandstrom](https://github.com/persandstrom).
|
||||
|
|
|
|||
|
|
@ -10,9 +10,7 @@ categories: release-notes
|
|||
og_image: /images/screenshots/map.png
|
||||
---
|
||||
|
||||
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:
|
||||
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:
|
||||
|
||||
- [OwnTracks platform for the device tracker][platform-owntracks] to get locations for devices
|
||||
- Brand new [zone component][component-zone] to define zones to identify locations and [trigger automation][zone-automation]
|
||||
|
|
@ -30,8 +28,7 @@ We have added a new [getting started section][start-presence] to get up and runn
|
|||
Map in Home Assistant showing two people and three zones (home, school, work)
|
||||
</p>
|
||||
|
||||
Ofcourse more things happened in the last three weeks. I'm moving away from my usual long post to a
|
||||
short summary of highlights:
|
||||
Ofcourse more things happened in the last three weeks. I'm moving away from my usual long post to a short summary of highlights:
|
||||
|
||||
<a href='/components/media_player.plex/'>
|
||||
<img src='/images/supported_brands/plex.png' style='border:none; box-shadow: none; float: right;' height='50' />
|
||||
|
|
|
|||
|
|
@ -16,9 +16,7 @@ We discovered two issues annoying enough to warrent the release of 0.7.5:
|
|||
|
||||
This release also includes some new platforms (because they keep coming!):
|
||||
|
||||
<img src='/images/supported_brands/blinkstick.png' style='border:none; box-shadow: none; float: right;' height='50' />
|
||||
<img src='/images/supported_brands/rfxtrx.png' style='border:none; box-shadow: none; float: right; clear: right;' height='50' />
|
||||
<img src='/images/supported_brands/telegram.png' style='border:none; box-shadow: none; float: right; clear: right;' height='50' />
|
||||
<img src='/images/supported_brands/blinkstick.png' style='border:none; box-shadow: none; float: right;' height='50' /><img src='/images/supported_brands/rfxtrx.png' style='border:none; box-shadow: none; float: right; clear: right;' height='50' /><img src='/images/supported_brands/telegram.png' style='border:none; box-shadow: none; float: right; clear: right;' height='50' />
|
||||
|
||||
- Light: [blinkstick platform](/components/light.blinksticklight/) added ([@alanbowman](https://github.com/alanbowman))
|
||||
- Device Tracker: [SNMP platform](/components/device_tracker.snmp/) added ([@tomduijf](https://github.com/tomduijf))
|
||||
|
|
@ -26,5 +24,4 @@ This release also includes some new platforms (because they keep coming!):
|
|||
- Switch: [rfxtrx platform](/components/switch.rfxtrx/) added ([@badele](https://github.com/badele))
|
||||
- Notify: [telegram platform](/components/notify.telegram/) added ([@fabaff](https://github.com/fabaff))
|
||||
|
||||
Also, the media player was extended by [@maddox](https://github.com/maddox) to support the play media command.
|
||||
This has been implemented for the [iTunes platform](/components/media_player.itunes/).
|
||||
Also, the media player was extended by [@maddox](https://github.com/maddox) to support the play media command. This has been implemented for the [iTunes platform](/components/media_player.itunes/).
|
||||
|
|
|
|||
|
|
@ -9,17 +9,11 @@ comments: true
|
|||
categories: release-notes
|
||||
---
|
||||
|
||||
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%](https://coveralls.io/builds/3946399) and thanks to the hard work by
|
||||
[@fabaff](https://github.com/fabaff) and myself the [component section](/components/) on the website has gotten a
|
||||
complete revamp.
|
||||
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%](https://coveralls.io/builds/3946399) and thanks to the hard work by [@fabaff](https://github.com/fabaff) and myself the [component section](/components/) on the website has gotten a complete revamp.
|
||||
|
||||
#### Changes
|
||||
|
||||
<img src='/images/supported_brands/radiotherm.png' style='border:none; box-shadow: none; float: right; margin-bottom: 16px;' height='50' />
|
||||
<img src='/images/supported_brands/firetv.png' style='border:none; box-shadow: none; float: right; margin-bottom: 16px; clear: right;' height='50' />
|
||||
<img src='/images/supported_brands/geofancy.png' style='border:none; box-shadow: none; float: right; margin-bottom: 16px; clear: right;' height='50' />
|
||||
<img src='/images/supported_brands/radiotherm.png' style='border:none; box-shadow: none; float: right; margin-bottom: 16px;' height='50' /><img src='/images/supported_brands/firetv.png' style='border:none; box-shadow: none; float: right; margin-bottom: 16px; clear: right;' height='50' /><img src='/images/supported_brands/geofancy.png' style='border:none; box-shadow: none; float: right; margin-bottom: 16px; clear: right;' height='50' />
|
||||
|
||||
- Device tracker: Newer [TP-Link routers](/components/device_tracker.tplink/) now supported ([@mKeRix](https://github.com/mKeRix))
|
||||
- Alarm Control Panel: [Manual alarm](/components/alarm_control_panel.manual/) added ([@sfam](https://github.com/sfam))
|
||||
|
|
@ -44,17 +38,14 @@ complete revamp.
|
|||
|
||||
As part of this release we did some cleanup which introduced backwards incompatible changes:
|
||||
|
||||
**Heat Control thermostat no longer includes scheduling features.**<br>
|
||||
This feature has been removed completely. Use the [automation component](/components/automation/)
|
||||
instead to control target temperature.
|
||||
**Heat Control thermostat no longer includes scheduling features.**
|
||||
This feature has been removed completely. Use the [automation component](/components/automation/) instead to control target temperature.
|
||||
|
||||
**Config changed for calling a service from a script.**<br>
|
||||
`execute_service:` has been replaced with `service:`. See [component page](/components/script/)
|
||||
for example. The old method will continue working for some time.
|
||||
**Config changed for calling a service from a script.**
|
||||
`execute_service:` has been replaced with `service:`. See [component page](/components/script/) for example. The old method will continue working for some time.
|
||||
|
||||
**Scenes can no longer be turned off.**<br>
|
||||
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.
|
||||
**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.**<br>
|
||||
**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
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue