From 39c0f4abc90740a095e7e683ef20b4d917395dcc Mon Sep 17 00:00:00 2001 From: Robin Date: Sun, 25 Nov 2018 20:58:58 +0000 Subject: [PATCH 01/17] Update climate.nest.markdown (#7632) --- source/_components/climate.nest.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/climate.nest.markdown b/source/_components/climate.nest.markdown index 80ba8505f33..4881390d88e 100644 --- a/source/_components/climate.nest.markdown +++ b/source/_components/climate.nest.markdown @@ -13,7 +13,7 @@ ha_iot_class: "Cloud Push" --- -The `nest` climate platform let you control a thermostat from [Nest](https://nest.com). +The `nest` climate platform lets you control a thermostat from [Nest](https://nest.com).

You must have the [Nest component](/components/nest/) configured to use these sensors. The `nest` climate component will automatically be setup when you do. From 3ff8de96bf266bd9415a76d6fb1bc36deb96d6f0 Mon Sep 17 00:00:00 2001 From: Robin Date: Sun, 25 Nov 2018 21:00:01 +0000 Subject: [PATCH 02/17] Update camera.nest.markdown (#7633) --- source/_components/camera.nest.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/camera.nest.markdown b/source/_components/camera.nest.markdown index 20c616e9c19..9a9cd737f4c 100644 --- a/source/_components/camera.nest.markdown +++ b/source/_components/camera.nest.markdown @@ -19,4 +19,4 @@ The `nest` platform allows you to watch still frames from a video stream (not li You must have the [Nest component](/components/nest/) configured to use this camera. The `nest` camera will automatically be setup when you do.

-Nest Camera supports `camera.turn_on` and `camera.turn_off` service since 0.75 release. +Nest Camera supports the `camera.turn_on` and `camera.turn_off` services since the 0.75 release. From 458bc268d4ae4680b7ee5db3a47d9524619f1beb Mon Sep 17 00:00:00 2001 From: Robin Date: Sun, 25 Nov 2018 21:40:51 +0000 Subject: [PATCH 03/17] Update database.markdown (#7637) --- source/_docs/ecosystem/notebooks/database.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_docs/ecosystem/notebooks/database.markdown b/source/_docs/ecosystem/notebooks/database.markdown index afb900c56e8..58117385269 100644 --- a/source/_docs/ecosystem/notebooks/database.markdown +++ b/source/_docs/ecosystem/notebooks/database.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Database" -description: "Basic example how to work with stored Home Assistant information in a Jupyter notebook." +description: "Accessing the Home-Assistant database from a Jupyter notebook." date: 2016-07-23 09:00 sidebar: true comments: false @@ -10,4 +10,4 @@ footer: true redirect_from: /ecosystem/notebooks/database/ --- -The [Database example](http://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/blob/master/database-examples.ipynb) shows you the details about how you can work with stored values. +You can directly access the Home-Assistant database from Jupyter notebooks. The [Database example](http://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/blob/master/database-examples.ipynb) shows you how you can work with stored database values. From c35d33c9b2b0fb87eb7143168cb7e052df3674ae Mon Sep 17 00:00:00 2001 From: Robin Date: Sun, 25 Nov 2018 21:49:19 +0000 Subject: [PATCH 04/17] Update api.markdown (#7636) * Update api.markdown * :ambulance: Fixes spelling of Home Assistant --- source/_docs/ecosystem/notebooks/api.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_docs/ecosystem/notebooks/api.markdown b/source/_docs/ecosystem/notebooks/api.markdown index 11d01248a29..5473031a8ad 100644 --- a/source/_docs/ecosystem/notebooks/api.markdown +++ b/source/_docs/ecosystem/notebooks/api.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Home Assistant Python API" -description: "Basic example how to work with the Home Assistant Python API in a Jupyter notebook." +description: "Basic example of interacting with Home Assistant live from a Jupyter notebook using the Python API." date: 2016-07-23 09:00 sidebar: true comments: false @@ -10,4 +10,4 @@ footer: true redirect_from: /ecosystem/notebooks/api/ --- -The [Python API](/developers/python_api/) allows one to create [interactive notebooks](http://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/blob/master/home-assistant-python-api.ipynb). +You can interact with Home Assistant live from Jupyter notebooks buy using the Home Assistant [Python API](/developers/python_api/). [See this example notebook](http://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/blob/master/home-assistant-python-api.ipynb). From 6ae54cbf9a65361169e714cb8820b9d5adc8ae5c Mon Sep 17 00:00:00 2001 From: Robin Date: Sun, 25 Nov 2018 22:10:36 +0000 Subject: [PATCH 05/17] Update stats.markdown (#7638) * Update stats.markdown * :ambulance: Fixes spelling of Home Assistant --- source/_docs/ecosystem/notebooks/stats.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/ecosystem/notebooks/stats.markdown b/source/_docs/ecosystem/notebooks/stats.markdown index c94ccb583b8..105134ecf70 100644 --- a/source/_docs/ecosystem/notebooks/stats.markdown +++ b/source/_docs/ecosystem/notebooks/stats.markdown @@ -10,4 +10,4 @@ footer: true redirect_from: /ecosystem/notebooks/stats/ --- -The [Statistics notebook](http://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/blob/master/database-statistics.ipynb) gets you started if you want to create statistical analysis of your data. +The [Statistics notebook](http://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/blob/master/database-statistics.ipynb) shows some basic statistical analysis on data in the Home Assistant database. From b5d178be48acd57791b05dced1a4fb17b9d429c1 Mon Sep 17 00:00:00 2001 From: Robin Date: Mon, 26 Nov 2018 08:40:17 +0000 Subject: [PATCH 06/17] Update database.markdown (#7640) --- source/_docs/backend/database.markdown | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/source/_docs/backend/database.markdown b/source/_docs/backend/database.markdown index 199466b4c43..81a5226b41b 100644 --- a/source/_docs/backend/database.markdown +++ b/source/_docs/backend/database.markdown @@ -10,9 +10,9 @@ footer: true redirect_from: /details/database/ --- -The default database used by Home Assistant is [SQLite](https://www.sqlite.org/) and is stored in your [configuration directory](/getting-started/configuration/) (e.g., `/.homeassistant/home-assistant_v2.db`). To change the database, use the [`recorder` component](/components/recorder/). +The default database used by Home Assistant is [SQLite](https://www.sqlite.org/), and the database file is stored in your [configuration directory](/getting-started/configuration/) (e.g., `/.homeassistant/home-assistant_v2.db`). If you prefer to run a database server (e.g. PostgreSQL), use the [`recorder` component](/components/recorder/). -To work with the SQLite database manually, you will need an installation of `sqlite3`, the command-line for SQLite database, or [DB Browser for SQLite](http://sqlitebrowser.org/), which provides an editor for executing SQL commands. +To work with the SQLite database manually from the command-line, you will need an [installation](http://www.sqlitetutorial.net/download-install-sqlite/) of `sqlite3`. Alternatively [DB Browser for SQLite](http://sqlitebrowser.org/) provides a viewer for exploring the database data and an editor for executing SQL commands. First load your database with `sqlite3`: ```bash @@ -124,4 +124,4 @@ The `VACUUM` command cleans your database. sqlite> VACUUM; ``` -For a more interactive way to work with the database or the create statistics, checkout our [Jupyter notebooks](http://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/tree/master/). +For a more interactive way of working with the database, checkout our [Jupyter notebooks](http://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/tree/master/). From 394585980ed288a491cc18bf4cdda944b99efbd8 Mon Sep 17 00:00:00 2001 From: Robin Date: Mon, 26 Nov 2018 08:40:52 +0000 Subject: [PATCH 07/17] Update installation.markdown (#7635) --- source/_docs/ecosystem/notebooks/installation.markdown | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/source/_docs/ecosystem/notebooks/installation.markdown b/source/_docs/ecosystem/notebooks/installation.markdown index 4d3fc06b608..eb0b16a7982 100644 --- a/source/_docs/ecosystem/notebooks/installation.markdown +++ b/source/_docs/ecosystem/notebooks/installation.markdown @@ -20,7 +20,7 @@ $ pip3 install jupyter matplotlib Certain notebooks hosted in the [Home Assistant notebooks repository](https://github.com/home-assistant/home-assistant-notebooks) require access to a running Home Assistant instance or parts of a Home Assistant installation. If you want to run those notebooks, install Home Assistant with `$ pip3 install homeassistant` as well.

-Now you are able to start the application. +Run Jupyter from the command line. ```bash $ jupyter notebook @@ -37,7 +37,7 @@ Open [http://localhost:8888/](http://localhost:8888/) in your browser. Press "Ne

-You will get an empty notebook with one cell. Cells can contain code or text. To get the output of a cell you need to execute them with "Cell" -> "Run Cells" from the menu or by pressing the icon. +You will get an empty notebook with one cell. Cells can contain code or text. To get the output of a cell you need to execute them with "Cell" -> "Run Cells" from the menu or by pressing the Play icon.

@@ -46,6 +46,6 @@ You will get an empty notebook with one cell. Cells can contain code or text. To The downloadable version of this notebook is available in the [Home Assistant notebooks repository](https://github.com/home-assistant/home-assistant-notebooks/blob/master/first-notebook.ipynb). -As you can see is the workflow very similar to working directly with a Python shell. One advantage is that you can go back and forth as you please and save your work. +As you can see is the Jupyter notebook workflow is very similar to working directly with a Python shell. One advantage of notebooks is that you can go back and forth between cells as you please and save your work. From 9cb54def9a4e9cbc1398499f886fc5bf69ac291b Mon Sep 17 00:00:00 2001 From: Robin Date: Mon, 26 Nov 2018 09:06:49 +0000 Subject: [PATCH 08/17] Update notebooks.markdown (#7634) * Update notebooks.markdown * Fix typo --- source/_docs/ecosystem/notebooks.markdown | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/source/_docs/ecosystem/notebooks.markdown b/source/_docs/ecosystem/notebooks.markdown index 9cde967703a..b7fb97f2bac 100644 --- a/source/_docs/ecosystem/notebooks.markdown +++ b/source/_docs/ecosystem/notebooks.markdown @@ -10,12 +10,10 @@ footer: true redirect_from: /ecosystem/notebooks/ --- -The [Jupyter Notebooks](http://jupyter.org/) allows you to create and share documents that contain live code, equations, visualizations, and explanatory text directly in your browser. The web application what is formerly known as the IPython Notebook supports over 40 programming languages. - -Visit [https://try.jupyter.org/](https://try.jupyter.org/) to get a preview before you install it locally. +[Jupyter Notebooks](http://jupyter.org/) allow you to create and share documents that contain live code, equations, visualizations, and explanatory text directly in your browser. Over 40 programming languages are supported including Python, R and Julia. Visit [https://try.jupyter.org/](https://try.jupyter.org/) to try out Jupyter notebooks without installing anything.

-[nbviewer](http://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/tree/master/) is rendering our notebooks online. GitHub is creating a preview as well. +[nbviewer](http://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/tree/master/) is used to render the Home Assistant notebooks online. GitHub will also display a preview of Jupyter notebooks. From 99c0b304272702cf8dc5bf85c739eab730706f73 Mon Sep 17 00:00:00 2001 From: Antoni K Date: Mon, 26 Nov 2018 17:18:09 +0800 Subject: [PATCH 09/17] Improved formatting and fixed grammar mistake (#7643) --- source/_docs/configuration/remote.markdown | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/source/_docs/configuration/remote.markdown b/source/_docs/configuration/remote.markdown index f0135393685..13637d41147 100644 --- a/source/_docs/configuration/remote.markdown +++ b/source/_docs/configuration/remote.markdown @@ -16,7 +16,7 @@ Remember to follow the [securing checklist](/docs/configuration/securing/) befor

-Home Assistant no longer support remote access via IP address since release 0.77, you have to use domain name. +Home Assistant no longer support remote access via IP address since release 0.77, you have to use a domain name.

The most common approach is to set up port forwarding (for any port) from your router to port 8123 on the computer that is hosting Home Assistant. General instructions on how to do this can be found by searching ` port forwarding instructions`. You can use any free port on your router and forward that to port 8123. @@ -25,7 +25,9 @@ A problem with making a port accessible is that some Internet Service Providers If you cannot access your Home Assistant installation remotely, remember to check if your ISP provides you with a dedicated IP, instead of one shared with other users via a [CG-NAT](https://en.wikipedia.org/wiki/Carrier-grade_NAT). This is becoming fairly common nowadays due to the shortage of IPv4 addresses. Some, if not most ISPs will require you to pay an extra fee to be assigned a dedicated IPv4 address. -Remember: Just putting a port up is not secure. You should definitely consider encrypting your traffic if you are accessing your Home Assistant installation remotely. For details please check the [set up encryption using Let's Encrypt](/blog/2017/09/27/effortless-encryption-with-lets-encrypt-and-duckdns/) blog post or this [detailed guide](/docs/ecosystem/certificates/lets_encrypt/) to using Let's Encrypt with Home Assistant. +

+Just putting a port up is not secure. You should definitely consider encrypting your traffic if you are accessing your Home Assistant installation remotely. For details please check the [set up encryption using Let's Encrypt](/blog/2017/09/27/effortless-encryption-with-lets-encrypt-and-duckdns/) blog post or this [detailed guide](/docs/ecosystem/certificates/lets_encrypt/) to using Let's Encrypt with Home Assistant. +

Protect your communication with a [self-signed certificate](/docs/ecosystem/certificates/tls_self_signed_certificate/) between your client and the Home Assistant instance. From aa3aba59bea7e177b981beca6ce91499908c7622 Mon Sep 17 00:00:00 2001 From: wogri Date: Mon, 26 Nov 2018 12:08:49 +0100 Subject: [PATCH 10/17] Add more documentation to modbus services (#7505) * Add more documentation to modbus services Useful for people not so familiar with modbus terminology. I had to use Wikipedia to understand the paramters, this should clarify things. * Update modbus.markdown * :pencil2: Tweaks --- source/_components/modbus.markdown | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/source/_components/modbus.markdown b/source/_components/modbus.markdown index 75581a49746..e08cd84e03a 100644 --- a/source/_components/modbus.markdown +++ b/source/_components/modbus.markdown @@ -112,6 +112,13 @@ timeout: | ------- | ----------- | | write_register | Write register. Requires `unit`, `address` and `value` fields. `value` can be either single value or an array | +#### {% linkable_title Service Data Attributes %} + +| Attribute | Description | +| --------- | ----------- | +| unit | Slave address (set to 255 you talk to Modbus via TCP) | +| address | Address of the Register (e.g., 138) | +| value | An array of 16-bit values. Might need reverse ordering. E.g., to set 0x0004 you might need to set `[4,0]` | ## {% linkable_title Building on top of Modbus %} From 3227ff188447eecf8f1321d306ea7a18134407bf Mon Sep 17 00:00:00 2001 From: dimitripb <31191267+dimitripb@users.noreply.github.com> Date: Mon, 26 Nov 2018 12:26:57 +0100 Subject: [PATCH 11/17] The current text assumes your user is always "homeassistant" (#7642) * The current text assumes your user is always "homeassistant" If you follow the advanced guide to setup a virtual environment a user named "homeassistant" or whatever you want will be created. See: https://www.home-assistant.io/docs/installation/raspberry-pi/ If you follow this guide the "homeassistant" user won't be created: https://www.home-assistant.io/docs/installation/virtualenv This page actually refers to the Autostart page on which is assumed that you created a user named "homeassistant". It's better to refer to the user which runs HA in general. * All occurences of [your user] replaced by YOUR_USER * Update systemd.markdown --- source/_docs/autostart/systemd.markdown | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/source/_docs/autostart/systemd.markdown b/source/_docs/autostart/systemd.markdown index 6b43b19c2e1..937f7ae63e1 100644 --- a/source/_docs/autostart/systemd.markdown +++ b/source/_docs/autostart/systemd.markdown @@ -21,8 +21,8 @@ If the preceding command returns the string `systemd`, continue with the instruc A service file is needed to control Home Assistant with `systemd`. The template below should be created using a text editor. Note, root permissions via `sudo` will likely be needed. The following should be noted to modify the template: - `ExecStart` contains the path to `hass` and this may vary. Check with `whereis hass` for the location. -- For most systems, the file is `/etc/systemd/system/home-assistant@[your user].service` with [your user] replaced by the user account that Home Assistant will run as (normally `homeassistant`). In particular, this is the case for Ubuntu 16.04. -- If unfamiliar with command-line text editors, `sudo nano -w [filename]` can be used with `[filename]` replaced with the full path to the file. Ex. `sudo nano -w /etc/systemd/system/home-assistant@[your user].service`. After text entered, press CTRL-X then press Y to save and exit. +- For most systems, the file is `/etc/systemd/system/home-assistant@YOUR_USER.service` with YOUR_USER replaced by the user account that Home Assistant will run as (normally `homeassistant`). In particular, this is the case for Ubuntu 16.04. +- If unfamiliar with command-line text editors, `sudo nano -w [filename]` can be used with `[filename]` replaced with the full path to the file. Ex. `sudo nano -w /etc/systemd/system/home-assistant@YOUR_USER.service`. After text entered, press CTRL-X then press Y to save and exit. - If you're running Home Assistant in a Python virtual environment or a Docker container, please skip to the appropriate template listed below. ``` @@ -41,7 +41,7 @@ WantedBy=multi-user.target ### {% linkable_title Python virtual environment %} -If you've setup Home Assistant in `virtualenv` following our [Python installation guide](/getting-started/installation-virtualenv/) or [manual installation guide for Raspberry Pi](/getting-started/installation-raspberry-pi/), the following template should work for you. If Home Assistant install is not located at `/srv/homeassistant`, please modify the `ExecStart=` line appropriately. +If you've setup Home Assistant in `virtualenv` following our [Python installation guide](/getting-started/installation-virtualenv/) or [manual installation guide for Raspberry Pi](/getting-started/installation-raspberry-pi/), the following template should work for you. If Home Assistant install is not located at `/srv/homeassistant`, please modify the `ExecStart=` line appropriately. `YOUR_USER` should be replaced by the user account that Home Assistant will run as (e.g `homeassistant`). ``` [Unit] @@ -51,7 +51,7 @@ After=network-online.target [Service] Type=simple User=%i -ExecStart=/srv/homeassistant/bin/hass -c "/home/homeassistant/.homeassistant" +ExecStart=/srv/homeassistant/bin/hass -c "/home/YOUR_USER/.homeassistant" [Install] WantedBy=multi-user.target From 1d0ec122eb02d657c77c17882042e91ead45a416 Mon Sep 17 00:00:00 2001 From: Rene Nulsch <33263735+ReneNulschDE@users.noreply.github.com> Date: Mon, 26 Nov 2018 21:50:41 +0100 Subject: [PATCH 12/17] Add note for FB6490Cable with FritzOS6.87 (#7631) See [#18609](https://github.com/home-assistant/home-assistant/issues/18609) for details --- source/_components/sensor.fritzbox_netmonitor.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/source/_components/sensor.fritzbox_netmonitor.markdown b/source/_components/sensor.fritzbox_netmonitor.markdown index 9fcaa72084a..d00beddd060 100644 --- a/source/_components/sensor.fritzbox_netmonitor.markdown +++ b/source/_components/sensor.fritzbox_netmonitor.markdown @@ -58,3 +58,7 @@ The following statistics will be exposed as attributes. |max_byte_rate_down |Maximum downstream-rate in bytes/s | The sensor's state corresponds to the `is_linked` attribute and is either `online`, `offline`, or `unavailable` (in case connection to the router is lost). + +

+This component does not support "Fritz!Box 6490 Cable" with FritzOS 6.87 installed. +

From c4ef0394c227975dd2482bcede3f044e6f9426a2 Mon Sep 17 00:00:00 2001 From: Mark Leenaerts Date: Mon, 26 Nov 2018 21:52:08 +0100 Subject: [PATCH 13/17] Updated http base_url sample (#7639) * Updated http base_url sample The base_url example incorrectly referenced a duck dns link with https instead of http which may be confusing for some users. * Corrected base_url example. --- source/_addons/duckdns.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_addons/duckdns.markdown b/source/_addons/duckdns.markdown index d1726880996..4626bd7617e 100644 --- a/source/_addons/duckdns.markdown +++ b/source/_addons/duckdns.markdown @@ -55,7 +55,7 @@ Use the following configuration in Home Assistant to use the generated certifica ```yaml http: - base_url: https://my-domain.duckdns.org:8123 + base_url: my-domain.duckdns.org:8123 ssl_certificate: /ssl/fullchain.pem ssl_key: /ssl/privkey.pem ``` From b97911444cdcc7e6ed504a33e9ccc29b502b2411 Mon Sep 17 00:00:00 2001 From: sam-wright Date: Tue, 27 Nov 2018 00:58:36 -0700 Subject: [PATCH 14/17] Update sensor.pi_hole.markdown (#7652) Updating sensor.pi_hole.markdown to read more clearly. Not (intentionally) changing any content. --- source/_components/sensor.pi_hole.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_components/sensor.pi_hole.markdown b/source/_components/sensor.pi_hole.markdown index 071f5ca0314..884cc1cf8a8 100644 --- a/source/_components/sensor.pi_hole.markdown +++ b/source/_components/sensor.pi_hole.markdown @@ -14,7 +14,7 @@ ha_release: 0.28 --- -The `pi_hole` sensor platform is displaying the statistical summary of a [Pi-hole](https://pi-hole.net/) system. +The `pi_hole` sensor platform displays the statistical summary of a [Pi-hole](https://pi-hole.net/) system. ## {% linkable_title Configuration %} @@ -73,4 +73,4 @@ monitored_conditions: description: Total number of seen clients. {% endconfiguration %} -This sensor platform was not made by Pi-hole LLC or the Pi-hole community. They didn't provide support, feedback, testing or helped in any way while it was created. This is third party, may not work if Pi-hole is breaking their API with the latest release, not official, not developed, not supported and not endorsed Pi-hole LLC or the Pi-hole community. The trademark `Pi-hole` and the logo is used here to describe the platform and only to describe. `Pi-hole` is a registered trademark of Pi-hole LLC. +This sensor platform was not made by Pi-hole LLC or the Pi-hole community. They did not provide support, feedback, testing, or any other help during its creation. This is a third party platform which may break if Pi-hole changes their API in a later release. It is not official, not developed, not supported, and not endorsed Pi-hole LLC or the Pi-hole community. The trademark `Pi-hole` and the logo is used here to describe the platform. `Pi-hole` is a registered trademark of Pi-hole LLC. From 58da2a7bb13e3db91b7a110eab36b1aac2cdd50d Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Tue, 27 Nov 2018 10:47:13 +0100 Subject: [PATCH 15/17] Minor changes --- source/_components/homekit.markdown | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/source/_components/homekit.markdown b/source/_components/homekit.markdown index 66de0951e95..15513369952 100644 --- a/source/_components/homekit.markdown +++ b/source/_components/homekit.markdown @@ -12,7 +12,7 @@ ha_release: 0.64 logo: apple-homekit.png --- -The `HomeKit` component allows you to forward entities from Home Assistant to Apple `HomeKit`, so they can be controlled from Apple's `Home` app and `Siri`. Please make sure that you have read the [considerations](#considerations) listed below to save you some trouble later. However if you do encounter issues, check out the [troubleshooting](#troubleshooting) section. +The `homekit` component allows you to forward entities from Home Assistant to Apple HomeKit, so they can be controlled from Apple's Home app and Siri. Please make sure that you have read the [considerations](#considerations) listed below to save you some trouble later. However if you do encounter issues, check out the [troubleshooting](#troubleshooting) section.

If you want to control `HomeKit` only devices with Home Assistant, check out the [HomeKit controller](/components/homekit_controller/) component. @@ -132,14 +132,15 @@ homekit: ## {% linkable_title Setup %} -To enable the `HomeKit` component in Home Assistant, add the following to your configuration file: +To enable the HomeKit component in Home Assistant, add the following to your configuration file: ```yaml # Example for HomeKit setup homekit: ``` -After Home Assistant has started, the entities specified by the filter are exposed to `HomeKit` if they are [supported](#supported-components). To add them: +After Home Assistant has started, the entities specified by the filter are exposed to HomeKit if they are [supported](#supported-components). To add them: + 1. Open the Home Assistant frontend. A new card will display the `pin code`. 1. Open the `Home` app. 2. Click `Add Accessory`, then select `Don't Have a Code or Can't Scan?` and choose the `Home Assistant Bridge`. @@ -148,7 +149,7 @@ After Home Assistant has started, the entities specified by the filter are expos 6. Follow the setup by clicking on `Next` and lastly `Done` in the top right-hand corner. 7. The `Home Assistant` Bridge and the Accessories should now be listed in the `Home` app. -After the setup is completed, you should be able to control your Home Assistant components through `Home` and `Siri`. +After the setup is completed, you should be able to control your Home Assistant components through Apple's Home and Siri. ## {% linkable_title Move Home Assistant install %} @@ -288,13 +289,15 @@ The following components are currently supported: ### {% linkable_title Deleting the `.homekit.state` file %} The `.homekit.state` file can be found in the configurations directory. You might need to enable `view hidden files` to see it. + 1. **Stop** Home Assistant 2. Delete the `.homekit.state` file 3. **Start** Home Assistant ### {% linkable_title Errors during pairing %} -If you encounter any issues during pairing, make sure to +If you encounter any issues during pairing, make sure to: + 1. **Stop** Home Assistant 2. Delete the `.homekit.state` file 3. Edit your configuration (see below) From 9af8baf030652e6e165603fb681e927e646ce339 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Tue, 27 Nov 2018 10:54:27 +0100 Subject: [PATCH 16/17] Align Alexa intro with Google Assistant --- source/_components/alexa.markdown | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/source/_components/alexa.markdown b/source/_components/alexa.markdown index 23c8bc9c86d..e75b372e96c 100644 --- a/source/_components/alexa.markdown +++ b/source/_components/alexa.markdown @@ -13,9 +13,13 @@ featured: true ha_release: '0.10' --- -

- Use [Home Assistant Cloud](/components/cloud/) to integrate with Alexa without any effort. -

+## {% linkable_title Automatic setup via Home Assistant Cloud %} + +With [Home Assistant Cloud](/cloud/), you can connect your Home Assistant instance in a few simple clicks to Amazon Alexa. With Home Assistant Cloud you don't have to deal with dynamic DNS, SSL certificates or opening ports on your router. Just log in via the user interface and a secure connection with the cloud will be established. Home Assistant Cloud requires a paid subscription after a 30-day free trial. + +For Home Assistant Cloud Users, documentation can be found [here](https://www.nabucasa.com/config/amazon_alexa/). + +## {% linkable_title Manual setup %} There are a few ways that you can use Amazon Echo and Home Assistant together. From c8bef0b57d294820fa9987a00f742584dd09eb8e Mon Sep 17 00:00:00 2001 From: VDRainer <26381449+VDRainer@users.noreply.github.com> Date: Tue, 27 Nov 2018 18:26:56 +0100 Subject: [PATCH 17/17] Added theme to gauge card documentation (#7657) * Added theme to documentation * Update gauge.markdown --- source/_lovelace/gauge.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/source/_lovelace/gauge.markdown b/source/_lovelace/gauge.markdown index 605b4b18489..c8dbe85d806 100644 --- a/source/_lovelace/gauge.markdown +++ b/source/_lovelace/gauge.markdown @@ -40,6 +40,10 @@ unit_of_measurement: description: Unit of Measurement given to data type: string default: "Unit Of Measurement given by entity" +theme: + required: false + description: Set to any theme within `themes.yaml` + type: string min: required: false description: Minimum value for graph