From 8ddfd3d5ad33bca0670ea7de0149365bbf2ecfd1 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Sun, 17 Dec 2017 09:09:14 -0800 Subject: [PATCH 01/13] Update link to cloud intro --- source/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/index.html b/source/index.html index a847b2632b9..173bef72c13 100644 --- a/source/index.html +++ b/source/index.html @@ -38,7 +38,7 @@ description: Open-source home automation platform running on Python 3. Track and Use Alexa to control Home Assistant.
- LEARN MORE + LEARN MORE
From 79a8a157fbca25f858d7c4f181baf96a3cae749e Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Sun, 17 Dec 2017 09:19:01 -0800 Subject: [PATCH 02/13] Add link to cloud config at bottom of getting started --- .../_posts/2017-12-17-introducing-home-assistant-cloud.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/_posts/2017-12-17-introducing-home-assistant-cloud.markdown b/source/_posts/2017-12-17-introducing-home-assistant-cloud.markdown index 8a8aaa10fc1..ae5cc1d49ef 100644 --- a/source/_posts/2017-12-17-introducing-home-assistant-cloud.markdown +++ b/source/_posts/2017-12-17-introducing-home-assistant-cloud.markdown @@ -42,6 +42,8 @@ The next step is to configure Alexa. This can be done by enabling the Home Assis Once you’re done, ask Alexa to discover devices (“Alexa, discover devices”) and you are all set to control them: “Alexa, turn on <device name>”. +See the [Cloud component configuration](/components/cloud/) to learn how to filter which devices get exposed to Alexa. + ## {% linkable_title FAQ %} **Will Home Assistant and Hass.io remain open source?** From e4a1572318bcfa41b69b5abfbd7aee0e5bd56ffd Mon Sep 17 00:00:00 2001 From: cgtobi Date: Sun, 17 Dec 2017 19:05:24 +0100 Subject: [PATCH 03/13] Update bluetooth_le_tracker.markdown (#4217) Add missing configuration options, such as `scan_duration`. --- .../_components/device_tracker.bluetooth_le_tracker.markdown | 3 +++ 1 file changed, 3 insertions(+) diff --git a/source/_components/device_tracker.bluetooth_le_tracker.markdown b/source/_components/device_tracker.bluetooth_le_tracker.markdown index e0da81a826a..b812d2f5e0d 100644 --- a/source/_components/device_tracker.bluetooth_le_tracker.markdown +++ b/source/_components/device_tracker.bluetooth_le_tracker.markdown @@ -43,6 +43,9 @@ device_tracker: Configuration variables: - **device_id** (*Optional*): The device ID for the Bluetooth device to be used for tracking. Defaults to `hci0`. +- **track_new_devices** (*Optional*): If new discovered devices are tracked by default. Defaults to `True`. +- **scan_duration** (*Optional*): How long should the scanner be looking for BLE devices. Defaults to `10` seconds. +- **interval_seconds** (*Optional*): Seconds between each scan for new devices. Defaults to `12` seconds. As some BT LE devices change their MAC address regularly, a new device is only discovered when it has been seen 5 times. Some BTLE devices (e.g. fitness trackers) are only visible to the devices that they are paired with. In this case, the BTLE tracker won't see this device. From c8933e1536d16bd663a66ce26efab86e21caa535 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Sun, 17 Dec 2017 10:32:26 -0800 Subject: [PATCH 04/13] Add more FAQ --- .../2017-12-17-introducing-home-assistant-cloud.markdown | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/source/_posts/2017-12-17-introducing-home-assistant-cloud.markdown b/source/_posts/2017-12-17-introducing-home-assistant-cloud.markdown index ae5cc1d49ef..4a8b3d32ef4 100644 --- a/source/_posts/2017-12-17-introducing-home-assistant-cloud.markdown +++ b/source/_posts/2017-12-17-introducing-home-assistant-cloud.markdown @@ -61,3 +61,11 @@ We have a lot of ideas! We are not going to make any promises but here are some - Generic HTTP cloud endpoint for people to send messages to their local instance. This will allow people to build applications on - top of the Home Assistant cloud. - IFTTT integration - Alexa shopping list integration + +**What countries are supported?** + +Only US is currently supported. Expect more countries to be supported soon. + +**How is the connection made to the cloud?** + +The connection is made using a WebSocket connection over HTTPS. [See the source here](https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/cloud/iot.py). From 81fe3853338b2f20991dc710e97b01ed29514b65 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Sun, 17 Dec 2017 11:04:06 -0800 Subject: [PATCH 05/13] Update FAQ --- .../_posts/2017-12-17-introducing-home-assistant-cloud.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_posts/2017-12-17-introducing-home-assistant-cloud.markdown b/source/_posts/2017-12-17-introducing-home-assistant-cloud.markdown index 4a8b3d32ef4..222114e2111 100644 --- a/source/_posts/2017-12-17-introducing-home-assistant-cloud.markdown +++ b/source/_posts/2017-12-17-introducing-home-assistant-cloud.markdown @@ -64,7 +64,7 @@ We have a lot of ideas! We are not going to make any promises but here are some **What countries are supported?** -Only US is currently supported. Expect more countries to be supported soon. +Only US is currently supported. Expect more countries to be supported soon. The reason there is a country limitation is that we need to do extra steps and certifications for each country's Alexa skill. **How is the connection made to the cloud?** From 1fd30d5796812ce46d24c32c70a91f9f40f25cd4 Mon Sep 17 00:00:00 2001 From: Adam Mills Date: Mon, 18 Dec 2017 02:48:16 -0500 Subject: [PATCH 06/13] Explanation for translation placeholders (#4236) --- source/developers/frontend_translation.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/developers/frontend_translation.markdown b/source/developers/frontend_translation.markdown index ace77c6fe9b..1699e85da20 100644 --- a/source/developers/frontend_translation.markdown +++ b/source/developers/frontend_translation.markdown @@ -15,6 +15,8 @@ ha_release: 0.57 First time users may find it helpful to switch between multilanguage and single language view using the Multilanguage view button. For more information about the translation workflow, please see the [Lokalise translation workflow documents](https://docs.lokalise.co/category/iOzEuQPS53-for-team-leads-and-translators). +Some translation strings will contain special placeholders that will be replaced later. Placeholders shown in square brackets `[]` are [Lokalise key references](https://docs.lokalise.co/article/KO5SZWLLsy-key-referencing). These are primarily used to link translation strings that will be duplicated. Different languages may not have the same duplicates as English, and are welcome to link duplicate translations that are not linked in English. Placeholders shown in curly brackets `{}` are [translation arguments](https://formatjs.io/guides/message-syntax/) that will be replaced with a live value when Home Assistant is running. Any translation argument placeholders present in the original string must be included in the translated string. These may include special syntax for defining plurals or other replacement rules. The linked format.js guide explains the syntax for adding plural definitions and other rules. +

The translation of the Home Assistant frontend is still a work in progress. More phrases will be available for translation soon.

From f638ff27e55752131176b786e057729f0ffab3d3 Mon Sep 17 00:00:00 2001 From: Jordan Hotmann Date: Mon, 18 Dec 2017 00:48:57 -0700 Subject: [PATCH 07/13] calendar.caldav.markdown typo fix (#4234) Additional system packages had libxm2-dev which should be libxml2-dev --- source/_components/calendar.caldav.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/calendar.caldav.markdown b/source/_components/calendar.caldav.markdown index c8f4b973489..95e4b28a0ce 100644 --- a/source/_components/calendar.caldav.markdown +++ b/source/_components/calendar.caldav.markdown @@ -22,7 +22,7 @@ You need to have a CalDav server and eventually credentials for it. This compone You might need some additional system packages to compile the Python caldav library. On a Debian based system, install them by: ```bash -$ sudo apt-get install libxm2-dev libxslt1-dev zlib1g-dev +$ sudo apt-get install libxml2-dev libxslt1-dev zlib1g-dev ``` ### {% linkable_title Basic Setup %} From 2037605f6c02b7ce2c9674d2deb64be581aa7429 Mon Sep 17 00:00:00 2001 From: Brent Saltzman Date: Mon, 18 Dec 2017 01:49:38 -0600 Subject: [PATCH 08/13] Replaced refereneces to Yahoo Finance (#4233) Unless something weird is needed with using the `yahoo_finance`, replaced this with `alpha_vantage` --- source/_components/sensor.alpha_vantage.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_components/sensor.alpha_vantage.markdown b/source/_components/sensor.alpha_vantage.markdown index 9fb5b85a569..3e78232b24b 100644 --- a/source/_components/sensor.alpha_vantage.markdown +++ b/source/_components/sensor.alpha_vantage.markdown @@ -16,7 +16,7 @@ ha_release: "0.60" The `alpha_vantage` sensor platform uses [Alpha Vantage](https://www.alphavantage.co) to monitor the stock market. -To enable the `yahoo_finance` platform, add the following lines to your `configuration.yaml` file: +To enable the `alpha_vantage` platform, add the following lines to your `configuration.yaml` file: ```yaml # Example configuration.yaml entry @@ -45,7 +45,7 @@ In this section you find some real life examples of how to use this sensor. ```yaml sensor: - - platform: yahoo_finance + - platform: alpha_vantage symbols: - RHT - GOOGL From 764362e467dbd1f6aec64d4441ed09d3897583e4 Mon Sep 17 00:00:00 2001 From: NeLLyMerC Date: Mon, 18 Dec 2017 02:50:50 -0500 Subject: [PATCH 09/13] Update hue.markdown (#4231) - changed service name to align with breaking changes in .60 - removed link (no longer applies) --- source/_components/hue.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_components/hue.markdown b/source/_components/hue.markdown index 8fda3584311..474fe180f17 100644 --- a/source/_components/hue.markdown +++ b/source/_components/hue.markdown @@ -106,7 +106,7 @@ More information can be found on the [Philips Hue API documentation](https://www The Hue platform has it's own concept of scenes for setting the colors of a group of lights at once. Hue Scenes are very cheap, get created by all kinds of apps (as it is the only way to have 2 or more lights change at the same time), and are rarely deleted. A typical Hue hub might have hundreds of scenes stored in them, many that you've never used, almost all very poorly named. -To avoid user interface overload we don't expose scenes directly. Instead there is a [light.hue_activate_scene](/components/light/#service-lighthue_activate_scene) service which can be used by `automation` or `script` components. +To avoid user interface overload we don't expose scenes directly. Instead there is a hue.hue_activate_scene service which can be used by `automation` or `script` components. This will have all the bulbs transitioned at once, instead of one at a time using standard scenes in Home Assistant. For instance: @@ -115,7 +115,7 @@ For instance: script: porch_on: sequence: - - service: light.hue_activate_scene + - service: hue.hue_activate_scene data: group_name: "Porch" scene_name: "Porch Orange" From e6688b9759ac715aa55f7bd58dc8b74ace4ec3ff Mon Sep 17 00:00:00 2001 From: Matthew Treinish Date: Mon, 18 Dec 2017 03:51:36 -0800 Subject: [PATCH 10/13] Mochad light fixes (#4214) * Add brighness levels option to mochad In home-assistant/home-assistant#11146 a new configuration option, brighness_levels, is added to the mochad light component. This is used to tell home-assistant how many brightness levels the X10 light device supports because there is no way to actually discover this. This commit adds documentation for the new option. * Fix some leftover references to the switch component The documentation for the mochad light component was mostly copy and pasted from the mochad switch device. Since the configuration is more or less the same between devices. However in doing this several references to mochad switches was left in by mistake. This commit fixes these and replaces them with the correct name of the component. --- source/_components/light.mochad.markdown | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/source/_components/light.mochad.markdown b/source/_components/light.mochad.markdown index 0bf8b817fe6..2902cb71be0 100644 --- a/source/_components/light.mochad.markdown +++ b/source/_components/light.mochad.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Mochad Light" -description: "Instructions how to integrate X10 Mochad switches into Home Assistant." +description: "Instructions how to integrate X10 Mochad lights into Home Assistant." date: 2017-07-14 11:29 sidebar: true comments: false @@ -11,7 +11,7 @@ ha_category: Light ha_release: 0.51 --- -The `mochad` switch platform lets you control an X10 enabled dimmer/light +The `mochad` light platform lets you control an X10 enabled dimmer/light device. To enable this sensor, you first have to set up the [mochad component](/components/mochad/) and then add the following to your `configuration.yaml` file: @@ -28,5 +28,7 @@ light: Configuration variables: - **address** (*Required*): The X10 address of the light. -- **name** (*Optional*): The name of the switch. Default is: x10_light_dev_*address*. +- **name** (*Optional*): The name of the light. Default is: x10_light_dev_*address*. - **comm_type** (*Optional*): pl (powerline) or rf (radio frequency). Default is pl. +- **brightness_levels** (*Optional*): The number of brightness levels the X10 light device supports. This can either be 32, 64, or 256 (note that the max +value sent to the device will be n-1 because it starts at 0) From 69d8837ef98990020de91ad674e2995f4eab7bfa Mon Sep 17 00:00:00 2001 From: Erik Eriksson Date: Mon, 18 Dec 2017 16:42:21 +0100 Subject: [PATCH 11/13] Update volvooncall.markdown (#4237) * Update volvooncall.markdown * :pencil2: Small grammar change --- source/_components/volvooncall.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_components/volvooncall.markdown b/source/_components/volvooncall.markdown index acd511a037c..20b8fc51106 100644 --- a/source/_components/volvooncall.markdown +++ b/source/_components/volvooncall.markdown @@ -65,4 +65,5 @@ Configuration variables: - **service_url** (*Optional*): The service URL to use for Volvo On Call. Normally not neccessary to specify. - **name** (*Optional*): Make it possible to provide a name for the vehicles. - **resources** (*Optional*): A list of resources to display (defaults to all available). +- **scandinavian_miles** (*Optional*): If set to yes, Scandinavian miles ("mil") are used for distances and fuel range (defaults to no). From b6ce601803f566ea386520ba5fe8154ce56b4592 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Mon, 18 Dec 2017 19:48:30 +0100 Subject: [PATCH 12/13] Replace personal details (fixes #4235) (#4239) * Replace personal details (fixes #4235) * Update domain --- source/_components/dominos.markdown | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/source/_components/dominos.markdown b/source/_components/dominos.markdown index a7b70d7fafb..062c0fbfea8 100644 --- a/source/_components/dominos.markdown +++ b/source/_components/dominos.markdown @@ -25,11 +25,11 @@ Currently, there is no support in this component for toppings, coupons or order ```yaml dominos: country_code: ca - first_name: Justin - last_name: Trudeau - email: justin.trudeau@parl.gc.ca - phone: 6139950253 - address: 24 Sussex Dr, Ottawa, ON, K1M1M4 + first_name: John + last_name: Smith + email: john.smith@example.com + phone: 123456789 + address: 24 Housten Dr, Ottawa, ON, K2M2M2 orders: - name: Medium Pan codes: From 1a24650217b972e68a3cbdd960101260a290c9a8 Mon Sep 17 00:00:00 2001 From: Andrea Campi Date: Tue, 19 Dec 2017 00:41:17 +0000 Subject: [PATCH 13/13] Fix example (#4241) The current text seems to suggest `platform: hue` is still needed or supported. Not so. --- source/_components/hue.markdown | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/source/_components/hue.markdown b/source/_components/hue.markdown index 474fe180f17..76f4741c5f1 100644 --- a/source/_components/hue.markdown +++ b/source/_components/hue.markdown @@ -64,8 +64,7 @@ hue: bridges: - host: BRIDGE1_IP_ADDRESS filename: phue.conf - - platform: hue - host: BRIDGE2_IP_ADDRESS + - host: BRIDGE2_IP_ADDRESS filename: phue2.conf ```