From 973cefc4277014f09b7bbe456f8ba4e16b8084fb Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sun, 3 Dec 2017 16:12:43 +0100 Subject: [PATCH 01/15] Remove blank lines --- source/_components/input_number.markdown | 74 ++++++++++-------------- 1 file changed, 30 insertions(+), 44 deletions(-) diff --git a/source/_components/input_number.markdown b/source/_components/input_number.markdown index 9c041e1b7f3..ccec8bc39bd 100644 --- a/source/_components/input_number.markdown +++ b/source/_components/input_number.markdown @@ -55,11 +55,9 @@ Configuration variables: Here's an example of `input_number` being used as a trigger in an automation. -```yaml {% raw %} +```yaml # Example configuration.yaml entry using 'input_number' as a trigger in an automation - -# Define input_number input_number: bedroom_brightness: name: Brightness @@ -67,8 +65,6 @@ input_number: min: 0 max: 254 step: 1 - -# Automation. automation: - alias: Bedroom Light - Adjust Brightness trigger: @@ -76,20 +72,19 @@ automation: entity_id: input_number.bedroom_brightness action: - service: light.turn_on -# Note the use of 'data_template:' below rather than the normal 'data:' if you weren't using an input variable + # Note the use of 'data_template:' below rather than the normal 'data:' if you weren't using an input variable data_template: entity_id: light.bedroom brightness: '{{ trigger.to_state.state | int }}' -{% endraw %} + ``` +{% endraw %} Another code example using `input_number`, this time being used in an action in an automation. -```yaml {% raw %} +```yaml # Example configuration.yaml entry using 'input_number' in an action in an automation - -# Define 'input_select' input_select: scene_bedroom: name: Scene @@ -101,8 +96,6 @@ input_select: - Relax - 'OFF' initial: 'Select' - -# Define input_number input_number: bedroom_brightness: name: Brightness @@ -110,8 +103,6 @@ input_number: min: 0 max: 254 step: 1 - -# Automation. automation: - alias: Bedroom Light - Custom trigger: @@ -120,21 +111,18 @@ automation: to: CUSTOM action: - service: light.turn_on -# Again, note the use of 'data_template:' rather than the normal 'data:' if you weren't using an input variable. + # Again, note the use of 'data_template:' rather than the normal 'data:' if you weren't using an input variable. data_template: entity_id: light.bedroom brightness: '{{ states.input_number.bedroom_brightness.state | int }}' -{% endraw %} ``` - +{% endraw %} Example of `input_number` being used in a bidirectional manner, both being set by and controlled by an MQTT action in an automation. -```yaml {% raw %} +```yaml # Example configuration.yaml entry using 'input_number' in an action in an automation - -# Define input_number input_number: target_temp: name: Target Heater Temperature Slider @@ -143,31 +131,29 @@ input_number: step: 1 unit_of_measurement: step icon: mdi:target - -# Automation. # This automation script runs when a value is received via MQTT on retained topic: setTemperature # It sets the value slider on the GUI. This slides also had its own automation when the value is changed. -- alias: Set temp slider - trigger: - platform: mqtt - topic: "setTemperature" - action: - service: input_number.set_value - data_template: - entity_id: input_number.target_temp - value: '{{ trigger.payload}}' - - # This automation script runs when the target temperature slider is moved. - # It publishes its value to the same MQTT topic it is also subscribed to. -- alias: Temp slider moved - trigger: - platform: state - entity_id: input_number.target_temp - action: - service: mqtt.publish - data_template: +automation: + - alias: Set temp slider + trigger: + platform: mqtt topic: "setTemperature" - retain: true - payload: '{{ states.input_number.target_temp.state | int }}' -{% endraw %} + action: + service: input_number.set_value + data_template: + entity_id: input_number.target_temp + value: '{{ trigger.payload}}' +# This automation script runs when the target temperature slider is moved. +# It publishes its value to the same MQTT topic it is also subscribed to. + - alias: Temp slider moved + trigger: + platform: state + entity_id: input_number.target_temp + action: + service: mqtt.publish + data_template: + topic: "setTemperature" + retain: true + payload: '{{ states.input_number.target_temp.state | int }}' ``` +{% endraw %} From 785dc3c27b9035122ffcc9b39bc7d762607467fa Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sun, 3 Dec 2017 16:15:31 +0100 Subject: [PATCH 02/15] Fix link --- source/_components/skybell.markdown | 18 ++++++++++++------ 1 file changed, 12 insertions(+), 6 deletions(-) diff --git a/source/_components/skybell.markdown b/source/_components/skybell.markdown index b160a879231..4a7a2cfdac6 100644 --- a/source/_components/skybell.markdown +++ b/source/_components/skybell.markdown @@ -13,11 +13,11 @@ ha_release: 0.56 ha_iot_class: "Cloud Polling" --- -The `skybell` implementation allows you to integrate your [Skybell.com](https://skybell.com) doorbells in Home Assistant. +The `skybell` implementation allows you to integrate your [Skybell.com](http://www.skybell.com/) doorbells in Home Assistant. Currently only the Skybell HD is supported by this platform. -To enable devices set up with your [Skybell.com](https://skybell.com/) account, add the following to your `configuration.yaml` file: +To enable devices set up with your [Skybell.com](http://www.skybell.com/) account, add the following to your `configuration.yaml` file: ```yaml # Example configuration.yaml entry @@ -26,9 +26,15 @@ skybell: password: secret ``` -Configuration variables: - -- **username** (*Required*): The username for accessing your Skybell account. -- **password** (*Required*): The password for accessing your Skybell account. +{% configuration %} +username: + description: The username for accessing your Skybell account. + required: true + type: string +password: + description: The password for accessing your Skybell account. + required: true + type: string +{% endconfiguration %} Finish your configuration by visiting the [Skybell binary sensor](/components/binary_sensor.skybell/), [Skybell camera](/components/camera.skybell/), [Skybell light](/components/light.skybell/), [Skybell sensor](/components/sensor.skybell/), or [Skybell switch](/components/switch.skybell/) documentation. From 0891fe66471a9c0f1284cc6aeae20986320e48d6 Mon Sep 17 00:00:00 2001 From: Erik Eriksson Date: Sun, 3 Dec 2017 16:48:49 +0100 Subject: [PATCH 03/15] Update sensor.eliqonline.markdown (#4128) --- source/_components/sensor.eliqonline.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/sensor.eliqonline.markdown b/source/_components/sensor.eliqonline.markdown index cfa071e3079..7d8452595fc 100644 --- a/source/_components/sensor.eliqonline.markdown +++ b/source/_components/sensor.eliqonline.markdown @@ -28,7 +28,7 @@ sensor: Configuration variables: - **access_token** (*Required*): The Access Token for your account. -- **channel_id** (*Optional*): Channel ID (as integer) of your device. Needed if you have more than one device. +- **channel_id** (*Required*): Channel ID (as integer) of your device. - **name** (*Optional*): The name of the sensor, eg. the city. For details please check the [API documentation](https://my.eliq.se/knowledge/sv-SE/49-eliq-online/299-eliq-online-api). From 786fc1cf350dfa7fbf233563c4ce0a815ae832ef Mon Sep 17 00:00:00 2001 From: Michael Wei Date: Sun, 3 Dec 2017 08:06:12 -0800 Subject: [PATCH 04/15] Update Xiaomi Air Filter support (#4124) --- source/_components/fan.xiaomi_miio.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/fan.xiaomi_miio.markdown b/source/_components/fan.xiaomi_miio.markdown index 7acf1291e45..218a7c0da40 100644 --- a/source/_components/fan.xiaomi_miio.markdown +++ b/source/_components/fan.xiaomi_miio.markdown @@ -13,7 +13,7 @@ ha_version: 0.57 ha_iot_class: "Local Polling" --- -The `xiaomi_miio` fan platform allows you to control the Xiaomi Air Purifier 2. The Air Purifier Pro isn't supported right now. +The `xiaomi_miio` fan platform allows you to control the Xiaomi Air Purifier 2, Air Purifier 2S andd Air Purifier Pro. Currently, the supported features are From 5332b437dd81b280e36b898014e928d0984e521c Mon Sep 17 00:00:00 2001 From: Travis Carr Date: Mon, 27 Nov 2017 16:01:45 -0800 Subject: [PATCH 05/15] Clarify advanced install instructions I just added a direct command to run for an advanced install. The docs at https://github.com/home-assistant/hassio-build/tree/master/install#install-hassio need some cleanup too, but that is clearly a separate change. I'm not a huge fan of adding code here that might change, but otherwise the linked document is confusing out of context, and I suspect that set of commands isn't actually that likely to change. --- source/hassio/installation.markdown | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/source/hassio/installation.markdown b/source/hassio/installation.markdown index 2211ba4381f..ecb1e0a0520 100644 --- a/source/hassio/installation.markdown +++ b/source/hassio/installation.markdown @@ -35,10 +35,14 @@ If you copy over your existing Home Assistant configuration, make sure to enable ## {% linkable_title Alternative: install on generic Linux server %} -For advanced users, it is also possible to try Hass.io on your Linux server or inside a VM. To do so, [follow these instructions][linux]. +For advanced users, it is also possible to try Hass.io on your Linux server or inside a VM. To do so, run the following command as root: + +```curl -sL https://raw.githubusercontent.com/home-assistant/hassio-build/master/install/hassio_install | bash -s```

When you use this installation method, some add-ons will not be available and the documentation might not work for your installation.

+More information about this kind of install [is located here][linux]. + [Etcher]: https://etcher.io/ [resinos-network]: https://docs.resin.io/deployment/network/2.0.0/ [pi1]: https://github.com/home-assistant/hassio-build/releases/download/1.1/resinos-hassio-1.1-raspberrypi.img.bz2 From c6b442c96b1d335c716ff2c3ac8efe6a90655ac6 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sun, 3 Dec 2017 17:14:11 +0100 Subject: [PATCH 06/15] Add link to blog post --- source/hassio/installation.markdown | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/source/hassio/installation.markdown b/source/hassio/installation.markdown index ecb1e0a0520..cb752fe2a4b 100644 --- a/source/hassio/installation.markdown +++ b/source/hassio/installation.markdown @@ -35,13 +35,17 @@ If you copy over your existing Home Assistant configuration, make sure to enable ## {% linkable_title Alternative: install on generic Linux server %} -For advanced users, it is also possible to try Hass.io on your Linux server or inside a VM. To do so, run the following command as root: +For advanced users, it is also possible to try Hass.io on your [Linux server or inside a virtual machine][linux]. To do so, run the following command as root: -```curl -sL https://raw.githubusercontent.com/home-assistant/hassio-build/master/install/hassio_install | bash -s``` +```bash +curl -sL https://raw.githubusercontent.com/home-assistant/hassio-build/master/install/hassio_install | bash -s +``` -

When you use this installation method, some add-ons will not be available and the documentation might not work for your installation.

+

+When you use this installation method, some add-ons will not be available and the documentation might not work for your installation. +

-More information about this kind of install [is located here][linux]. +A detailed guide about running Hass.io as a virtual machine is available in the [blog](/blog/2017/11/29/hassio-virtual-machine/). [Etcher]: https://etcher.io/ [resinos-network]: https://docs.resin.io/deployment/network/2.0.0/ From bb8b434cb61b21f198e61c3b61a1294c785b2609 Mon Sep 17 00:00:00 2001 From: Moos Date: Sun, 3 Dec 2017 09:04:20 -0800 Subject: [PATCH 07/15] Added netdisco note for Synology users. (#4125) * Added netdisco note for Synology users. The suggested steps for netdisco issue don't work for Synology users. I've added a link to forum post with confirmed steps. * Minor changes --- source/_components/discovery.markdown | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/source/_components/discovery.markdown b/source/_components/discovery.markdown index 1b96320acf9..18ac58261ce 100644 --- a/source/_components/discovery.markdown +++ b/source/_components/discovery.markdown @@ -96,7 +96,9 @@ If you are on Windows and you're using Python 3.5, download the [Netifaces](http

-If you see `Not initializing discovery because could not install dependency netdisco==0.6.1` in the logs, you will need to install the `python3-dev` or `python3-devel` package on your system manually (eg. `sudo apt-get install python3-dev` or `sudo dnf -y install python3-devel`). On the next restart of home-assistant, discovery should work. If you still get an error, check if you have a compiler (`gcc`) available on your system. +If you see `Not initializing discovery because could not install dependency netdisco==0.6.1` in the logs, you will need to install the `python3-dev` or `python3-devel` package on your system manually (eg. `sudo apt-get install python3-dev` or `sudo dnf -y install python3-devel`). On the next restart of Home Assistant, the discovery should work. If you still get an error, check if you have a compiler (`gcc`) available on your system. + +For DSM/Synology, install via debian-chroot [see this forum post](https://community.home-assistant.io/t/error-starting-home-assistant-on-synology-for-first-time/917/15).

If you are developing a new platform, please read [how to make your platform discoverable](/developers/component_discovery/) for further details. From e3a54014bfc5624838fbcd68dfe0d2469586b2dd Mon Sep 17 00:00:00 2001 From: DubhAd Date: Sun, 3 Dec 2017 17:12:25 +0000 Subject: [PATCH 08/15] Added note about disabling Z-Way (#4027) * Added note about disabling Z-Way A few people have had problems where they've installed the Razberry software, and it's then caused problems (locking the card, and/or over-writing the `zwcfg*.xml` file). Adding a note to ensure that if installed it is disabled. * Minor changes --- source/_docs/z-wave/device-specific.markdown | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/source/_docs/z-wave/device-specific.markdown b/source/_docs/z-wave/device-specific.markdown index 419d8a8c850..0aba503a710 100644 --- a/source/_docs/z-wave/device-specific.markdown +++ b/source/_docs/z-wave/device-specific.markdown @@ -61,6 +61,10 @@ $ sudo systemctl disable hciuart Finally, reboot to make those changes active. It's been reported that this is also required on the Pi2. +

+ If you've installed the Z-Way software, you'll need to ensure you disable it before you install Home Assistant or you won't be able to access the board. Do this with `sudo /etc/init.d/z-way-server stop; sudo update-rc.d z-way-server disable`. +

+ ### {% linkable_title Aeon Minimote %} Here's a handy configuration for the Aeon Labs Minimote that defines all possible button presses. Put it into `automation.yaml`. @@ -74,7 +78,6 @@ Here's a handy configuration for the Aeon Labs Minimote that defines all possibl event_data: entity_id: zwave.aeon_labs_minimote_1 scene_id: 1 - - id: mini_1_held alias: 'Minimote Button 1 Held' trigger: @@ -83,7 +86,6 @@ Here's a handy configuration for the Aeon Labs Minimote that defines all possibl event_data: entity_id: zwave.aeon_labs_minimote_1 scene_id: 2 - - id: mini_2_pressed alias: 'Minimote Button 2 Pressed' trigger: @@ -92,7 +94,6 @@ Here's a handy configuration for the Aeon Labs Minimote that defines all possibl event_data: entity_id: zwave.aeon_labs_minimote_1 scene_id: 3 - - id: mini_2_held alias: 'Minimote Button 2 Held' trigger: @@ -101,7 +102,6 @@ Here's a handy configuration for the Aeon Labs Minimote that defines all possibl event_data: entity_id: zwave.aeon_labs_minimote_1 scene_id: 4 - - id: mini_3_pressed alias: 'Minimote Button 3 Pressed' trigger: @@ -110,7 +110,6 @@ Here's a handy configuration for the Aeon Labs Minimote that defines all possibl event_data: entity_id: zwave.aeon_labs_minimote_1 scene_id: 5 - - id: mini_3_held alias: 'Minimote Button 3 Held' trigger: @@ -119,7 +118,6 @@ Here's a handy configuration for the Aeon Labs Minimote that defines all possibl event_data: entity_id: zwave.aeon_labs_minimote_1 scene_id: 6 - - id: mini_4_pressed alias: 'Minimote Button 4 Pressed' trigger: @@ -128,7 +126,6 @@ Here's a handy configuration for the Aeon Labs Minimote that defines all possibl event_data: entity_id: zwave.aeon_labs_minimote_1 scene_id: 7 - - id: mini_4_held alias: 'Minimote Button 4 Held' trigger: From 4efe527fe75bf9376c263c335cf5130fdbe08952 Mon Sep 17 00:00:00 2001 From: Carlo Costanzo Date: Sun, 3 Dec 2017 14:27:18 -0500 Subject: [PATCH 09/15] fix 404 (#4131) --- source/_components/device_tracker.unifi_direct.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/device_tracker.unifi_direct.markdown b/source/_components/device_tracker.unifi_direct.markdown index 24124d3cbc2..d00d2259646 100644 --- a/source/_components/device_tracker.unifi_direct.markdown +++ b/source/_components/device_tracker.unifi_direct.markdown @@ -13,7 +13,7 @@ ha_release: 0.59 --- -This platform allows you to detect presence by looking at devices connected to a [UniFi AP](http://ubnt.com/unifi-ap/). This device tracker differs form [Ubiquiti Unifi WAP](https://home-assistant.io/components/device_tracker.unifi/) because it doesn't require the Unifi controller software. +This platform allows you to detect presence by looking at devices connected to a [UniFi AP](https://www.ubnt.com/products/#unifi). This device tracker differs form [Ubiquiti Unifi WAP](https://home-assistant.io/components/device_tracker.unifi/) because it doesn't require the Unifi controller software. To use this device tracker in your installation, add the following to your `configuration.yaml` file: From b7f83e64fc635da2cc9d4e6e28dc9323f52f9888 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Sun, 3 Dec 2017 11:38:24 -0800 Subject: [PATCH 10/15] Update sensor.tahoma.markdown --- source/_components/sensor.tahoma.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_components/sensor.tahoma.markdown b/source/_components/sensor.tahoma.markdown index 1b373ac81ce..80cf6bc4ebb 100644 --- a/source/_components/sensor.tahoma.markdown +++ b/source/_components/sensor.tahoma.markdown @@ -14,8 +14,8 @@ ha_release: 0.59 To use your tahoma sensors in your installation, add the following to your `configuration.yaml` file: -``yaml +```yaml # Example configuration.yml entry sensor: platform: tahoma -``` \ No newline at end of file +``` From 493a7603972cf248215d49196d2b4654fa093399 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Sun, 3 Dec 2017 12:05:48 -0800 Subject: [PATCH 11/15] Update 2017-12-03-release-59.markdown --- source/_posts/2017-12-03-release-59.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_posts/2017-12-03-release-59.markdown b/source/_posts/2017-12-03-release-59.markdown index 6e49724439b..766577d9792 100644 --- a/source/_posts/2017-12-03-release-59.markdown +++ b/source/_posts/2017-12-03-release-59.markdown @@ -27,7 +27,7 @@ With the Dominos Pizza integration made by [@wardcraigj] your home is now taking

## {% linkable_title Shopping list tweaks %} -New items for the [`shopping_list`][shopping_list docs] can now be created with HTTP requests. [@balloob] extented the component with this feature. +[@balloob] has refreshed the shopping list UI to make it more usable. It's now possible to add items by typing, instead of just voice. Also editting has been made easier. ## {% linkable_title Entity picker %} [@balloob] improved the way if you want to pick an entity. In the automation editor, the script editor and the service section of the Developer Tools it's much easier to identify the right one! The automation editor will only suggest relevant entities. From 3e406f47ea67a0ede33cd17ca51e512217c1a0e7 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sun, 3 Dec 2017 20:58:30 +0100 Subject: [PATCH 12/15] Fix link --- source/_posts/2017-12-03-release-59.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_posts/2017-12-03-release-59.markdown b/source/_posts/2017-12-03-release-59.markdown index 766577d9792..cfbf749b0b6 100644 --- a/source/_posts/2017-12-03-release-59.markdown +++ b/source/_posts/2017-12-03-release-59.markdown @@ -16,7 +16,7 @@ og_image: /images/blog/2017-12-0.59/components.png We are proud to announce the availability of Home Assistant 0.59. To keep you in the loop: This is the second last release in 2017. We have stuck to our bi-weekly release cycle for another year but we decided that we will take a little break between Christmas and New Year. ## {% linkable_title Dominos Pizza platform %} -With the Dominos Pizza integration made by [@wardcraigj] your home is now taking care that you don't starve. In combination with a [Skybell](/components/skybell/) or a [DoorBird](/components/skybell/) you will know exactly when the pizza is in front of your door. +With the Dominos Pizza integration made by [@wardcraigj] your home is now taking care that you don't starve. In combination with a [Skybell](/components/skybell/) or a [DoorBird](/components/doorbird/) you will know exactly when the pizza is in front of your door. ## {% linkable_title Color picker %} @NovapaX created a new color picker. While dragging the color badge with your finger, a badge will appear above your finger so you can see the current color. From 1f65b9bf3b1c19f2ea6c265b83a7669ae118ad87 Mon Sep 17 00:00:00 2001 From: Nicko van Someren Date: Sun, 3 Dec 2017 15:30:57 -0700 Subject: [PATCH 13/15] Added documentation for the json_attributes configuration. (#4046) * Added documentation for the json_attributes configuration. * Updated to reflect change to make json_attributes a list rather than a boolean. * Fixed json_attributes examples to mark templates in documentation as {% raw %}. Also corrected typos in entity_id entries for examples. * Add additional example --- source/_components/sensor.rest.markdown | 67 +++++++++++++++++++++++-- 1 file changed, 62 insertions(+), 5 deletions(-) diff --git a/source/_components/sensor.rest.markdown b/source/_components/sensor.rest.markdown index 9f3da04c7ca..aa34b219058 100644 --- a/source/_components/sensor.rest.markdown +++ b/source/_components/sensor.rest.markdown @@ -49,6 +49,7 @@ Configuration variables: - **username** (*Optional*): The username for accessing the REST endpoint. - **password** (*Optional*): The password for accessing the REST endpoint. - **headers** (*Optional*): The headers for the requests. +- **json_attributes** (*Optional*): A list of keys to extract values from a JSON dictionary result and then set as sensor attributes. Default is an empty list.

Make sure that the URL exactly matches your endpoint or resource. @@ -67,9 +68,7 @@ In this section you find some real life examples of how to use this sensor. ### {% linkable_title External IP address %} -You can find your external IP address using the service [JSON Test](http://www.jsontest.com) at their http://ip.jsontest.com/ endpoint. - -To display the IP address, the entry for a sensor in the `configuration.yaml` file will look like this. +You can find your external IP address using the service [JSON Test](http://www.jsontest.com) at their [http://ip.jsontest.com/](http://ip.jsontest.com/) URL. ```yaml sensor: @@ -83,8 +82,6 @@ sensor: The [glances](/components/sensor.glances/) sensor is doing the exact same thing for all exposed values. -Add something similar to the entry below to your `configuration.yaml` file: - ```yaml sensor: - platform: rest @@ -154,3 +151,63 @@ sensor: User-Agent: Home Assistant REST sensor ``` +### {% linkable_title Fetch multiple JSON values and present them as attibutes %} + +[JSON Test](http://www.jsontest.com) returns the current time, date and milliseconds since epoch from [http://date.jsontest.com/](http://date.jsontest.com/). + +{% raw %} +```yaml +sensor: + - platform: rest + name: JSON time + json_attributes: + - date + - milliseconds_since_epoch + resource: http://date.jsontest.com/ + value_template: '{{ value_json.time }}' + - platform: template + sensors: + date: + friendly_name: 'Date' + value_template: '{{ states.sensor.json_time.attributes["date"] }}' + milliseconds: + friendly_name: 'milliseconds' + value_template: '{{ states.sensor.json_time.attributes["milliseconds_since_epoch"] }}' +``` +{% endraw %} + +This sample fetches a weather report from [OpenWeatherMap](http://openweathermap.org/), maps the resulting data into attributes of the RESTful sensor and then creates a set of [template](/components/sensor.template/) sensors that monitor the attributes and present the values in a usable form. + +{% raw %} +```yaml +sensor: + - platform: rest + name: OWM_report + json_attributes: + - main + - weather + value_template: '{{ value_json["weather"][0]["description"].title() }}' + resource: http://api.openweathermap.org/data/2.5/weather?zip=80302,us&APPID=VERYSECRETAPIKEY + - platform: template + sensors: + owm_weather: + value_template: '{{ states.sensor.owm_report.attributes.weather[0]["description"].title() }}' + icon_template: '{{ "http://openweathermap.org/img/w/"+states.sensor.owm_report.attributes.weather[0]["icon"]+".png" }}' + entity_id: sensor.owm_report + owm_temp: + friendly_name: 'Outside temp' + value_template: '{{ states.sensor.owm_report.attributes.main["temp"]-273.15 }}' + unit_of_measurement: "°C" + entity_id: sensor.owm_report + owm_pressure: + friendly_name: 'Outside pressure' + value_template: '{{ states.sensor.owm_report.attributes.main["pressure"] }}' + unit_of_measurement: "hP" + entity_id: sensor.owm_report + owm_humidity: + friendly_name: 'Outside humidity' + value_template: '{{ states.sensor.owm_report.attributes.main["humidity"] }}' + unit_of_measurement: "%" + entity_id: sensor.owm_report +``` +{% endraw %} From 9af39648c365af631813ed960ef8aed0741a724f Mon Sep 17 00:00:00 2001 From: austinmroczek Date: Sun, 3 Dec 2017 15:21:46 -0800 Subject: [PATCH 14/15] Add example network_key line (#4133) Added an example network_key line for configuration.yaml file. I was having a hard time making it work because I was re-using an existing key from Razberry which was in a slightly different format. It wasn't until I "created" a new key to see the format. --- source/_docs/z-wave/installation.markdown | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/source/_docs/z-wave/installation.markdown b/source/_docs/z-wave/installation.markdown index 4765ecb07be..513028a96f0 100644 --- a/source/_docs/z-wave/installation.markdown +++ b/source/_docs/z-wave/installation.markdown @@ -188,6 +188,12 @@ An easy script to generate a random key: cat /dev/urandom | tr -dc '0-9A-F' | fold -w 32 | head -n 1 | sed -e 's/\(..\)/0x\1, /g' -e 's/, $//' ``` +```yaml +# Example configuration.yaml entry for network_key +zwave: + network_key: "0x2e, 0xcc, 0xab, 0x1c, 0xa3, 0x7f, 0x0e, 0xb5, 0x70, 0x71, 0x2d, 0x98, 0x25, 0x43, 0xee, 0x0c" +``` + Ensure you keep a backup of this key. If you have to rebuild your system and don't have a backup of this key, you won't be able to reconnect to any security devices. This may mean you have to do a factory reset on those devices, and your controller, before rebuilding your Z-Wave network. ## {% linkable_title First Run %} From a120cee6cc547568c42c5bd50e24a97a9627e17d Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Sun, 3 Dec 2017 20:19:02 -0800 Subject: [PATCH 15/15] Release 0.59.1 --- _config.yml | 6 +++--- source/_posts/2017-12-03-release-59.markdown | 16 +++++++++++++++- 2 files changed, 18 insertions(+), 4 deletions(-) diff --git a/_config.yml b/_config.yml index f52d2b10a96..de05f2cbf1c 100644 --- a/_config.yml +++ b/_config.yml @@ -140,11 +140,11 @@ social: # Home Assistant release details current_major_version: 0 current_minor_version: 59 -current_patch_version: 0 -date_released: 2017-12-03 +current_patch_version: 1 +date_released: 2017-12-04 # Either # or the anchor link to latest release notes in the blog post. # Must be prefixed with a # and have double quotes around it. # Major release: -patch_version_notes: "#" +patch_version_notes: "#release-0591---december-4" # Minor release (Example #release-0431---april-25): diff --git a/source/_posts/2017-12-03-release-59.markdown b/source/_posts/2017-12-03-release-59.markdown index cfbf749b0b6..38f1f744860 100644 --- a/source/_posts/2017-12-03-release-59.markdown +++ b/source/_posts/2017-12-03-release-59.markdown @@ -19,7 +19,7 @@ We are proud to announce the availability of Home Assistant 0.59. To keep you in With the Dominos Pizza integration made by [@wardcraigj] your home is now taking care that you don't starve. In combination with a [Skybell](/components/skybell/) or a [DoorBird](/components/doorbird/) you will know exactly when the pizza is in front of your door. ## {% linkable_title Color picker %} -@NovapaX created a new color picker. While dragging the color badge with your finger, a badge will appear above your finger so you can see the current color. +[@NovapaX] created a new color picker. While dragging the color badge with your finger, a badge will appear above your finger so you can see the current color.

Screenshot of the color wheel. @@ -53,6 +53,13 @@ If you follow our [twitter feed](https://twitter.com/home_assistant) then you ma - Add tts.baidu platform ([@zhujisheng] - [#10724]) ([tts.baidu docs]) (new-platform) - Create ecobee weather platform ([@PhracturedBlue] - [#10869]) ([ecobee docs]) ([weather.ecobee docs]) (new-platform) +## {% linkable_title Release 0.59.1 - December 4 %} + +- Fix Notifications for Android TV ([@danielperna84] - [#10798]) ([notify.nfandroidtv docs]) +- fix iOS component config generation ([@wrboyce] - [#10923]) +- Fix color wheel in group more info dialogs ([@NovapaX] - [#10934]) +- Dominos no order fix ([@wardcraigj] - [#10935]) ([dominos docs]) + ## {% linkable_title If you need help... %} ...don't hesitate to use our very active [forums](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e). The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks. @@ -389,3 +396,10 @@ Experiencing issues introduced by this release? Please report them in our [issue [vacuum.xiaomi_miio docs]: https://home-assistant.io/components/vacuum.xiaomi_miio/ [weather.ecobee docs]: https://home-assistant.io/components/weather.ecobee/ [zwave docs]: https://home-assistant.io/components/zwave/ +[#10798]: https://github.com/home-assistant/home-assistant/pull/10798 +[#10923]: https://github.com/home-assistant/home-assistant/pull/10923 +[#10934]: https://github.com/home-assistant/home-assistant/pull/10934 +[#10935]: https://github.com/home-assistant/home-assistant/pull/10935 +[@NovapaX]: https://github.com/NovapaX +[@wrboyce]: https://github.com/wrboyce +[notify.nfandroidtv docs]: https://home-assistant.io/components/notify.nfandroidtv/