From 34a39c7865b234cb5880b12ab82794adf0d7bb3c Mon Sep 17 00:00:00 2001 From: Dan Jackson Date: Fri, 27 Dec 2019 01:28:02 -0800 Subject: [PATCH 01/35] Update homekit.markdown: URL encode space char (#11542) I'm not sure this addition to the URL works for everyone - it looks like unprivileged users can't label new issues, but this *does* fix the formatting of the link. --- source/_integrations/homekit.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/homekit.markdown b/source/_integrations/homekit.markdown index 20acf947f03..dc0e98fdddf 100644 --- a/source/_integrations/homekit.markdown +++ b/source/_integrations/homekit.markdown @@ -459,7 +459,7 @@ To use the HomeKit integration with to different Home Assistant instances on the #### Specific entity doesn't work -Although we try our best, some entities don't work with the HomeKit integration yet. The result will be that either pairing fails completely or all Home Assistant accessories will stop working. Use the filter to identify which entity is causing the issue. It's best to try pairing and step by step including more entities. If it works unpair and repeat until you find the one that is causing the issues. To help others and the developers, please open a new issue here: [home-assistant/issues/new](https://github.com/home-assistant/home-assistant/issues/new?labels=component: homekit) +Although we try our best, some entities don't work with the HomeKit integration yet. The result will be that either pairing fails completely or all Home Assistant accessories will stop working. Use the filter to identify which entity is causing the issue. It's best to try pairing and step by step including more entities. If it works unpair and repeat until you find the one that is causing the issues. To help others and the developers, please open a new issue here: [home-assistant/issues/new](https://github.com/home-assistant/home-assistant/issues/new?labels=component:%20homekit) #### Accessories are all listed as not responding From a0c74463603fa74b59ca0df719e0db04a08d9b15 Mon Sep 17 00:00:00 2001 From: Frankster-NL Date: Fri, 27 Dec 2019 10:58:26 +0100 Subject: [PATCH 02/35] Added warning on method for spikey appliances (#11539) --- source/_integrations/integration.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/integration.markdown b/source/_integrations/integration.markdown index f2bd8fbf086..c40b9290208 100644 --- a/source/_integrations/integration.markdown +++ b/source/_integrations/integration.markdown @@ -59,7 +59,7 @@ method: default: trapezoidal {% endconfiguration %} -If 'unit' is set then 'unit_prefix' and 'unit_time' are ignored. +In case you have an appliance which produces 'spikey' consumption (like an on/off electrical boiler) you should opt for the left method I order to get accurate readings. 'unit' is set then 'unit_prefix' and 'unit_time' are ignored. ## Energy From d3eb43dde3191b435191c09e3f5e2c0764c21151 Mon Sep 17 00:00:00 2001 From: Kyle McNally Date: Fri, 27 Dec 2019 10:04:17 -0500 Subject: [PATCH 03/35] Update discovery.markdown (#11544) Spelling Error --- source/_integrations/discovery.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/discovery.markdown b/source/_integrations/discovery.markdown index 933320e1a5b..3b08c0c1d9c 100644 --- a/source/_integrations/discovery.markdown +++ b/source/_integrations/discovery.markdown @@ -47,7 +47,7 @@ Zeroconf discoverable integrations [Axis](/integrations/axis/)/[ESPHome](/integr -`discovery` is included in the defalult configuration. To load this component manually, add the following lines to your `configuration.yaml` file: +`discovery` is included in the default configuration. To load this component manually, add the following lines to your `configuration.yaml` file: ```yaml # Example configuration.yaml entry From 22cc5201601839f09e93a95164297152350063f8 Mon Sep 17 00:00:00 2001 From: Kyle McNally Date: Fri, 27 Dec 2019 12:34:05 -0500 Subject: [PATCH 04/35] Update wwlln.markdown (#11545) * Update wwlln.markdown * :pencil2: Tweak Co-authored-by: Klaas Schoute --- source/_integrations/wwlln.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/wwlln.markdown b/source/_integrations/wwlln.markdown index e9ef0048341..c5720cf57a7 100644 --- a/source/_integrations/wwlln.markdown +++ b/source/_integrations/wwlln.markdown @@ -65,7 +65,7 @@ the standard ones: | latitude | Latitude of the lightning strike. | | longitude | Longitude of the lightning strike. | | source | `wwlln` to be used in conjunction with the `geo_location` automation trigger. | -| external_id | The external ID used in the feed to identify the earthquake in the feed. | +| external_id | The external ID used in the feed to identify the lightning strike in the feed. | | publication_date | Date and time when this event occurred. | ## Full Configuration From 8054e564a980c5a2f7cf13c7a15d03b37fe88c6f Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Fri, 27 Dec 2019 22:39:01 +0100 Subject: [PATCH 05/35] Update style (#11546) --- source/_integrations/integration.markdown | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/source/_integrations/integration.markdown b/source/_integrations/integration.markdown index c40b9290208..34d2859b897 100644 --- a/source/_integrations/integration.markdown +++ b/source/_integrations/integration.markdown @@ -10,7 +10,7 @@ logo: integral.png ha_qa_scale: internal --- -The `integration` platform provides the [Riemann sum](https://en.wikipedia.org/wiki/Riemann_sum) of the values provided by a source sensor. The Riemann sum is an approximation of an **integral** by a finite sum. The integration sensors is updated upon changes of the the **source**. Fast sampling source sensors provide better results. In this implementation, the default is the Trapezoidal method, but Left and Right methods can optionally be used. +The `integration` platform provides the [Riemann sum](https://en.wikipedia.org/wiki/Riemann_sum) of the values provided by a source sensor. The Riemann sum is an approximation of an **integral** by a finite sum. The integration sensors is updated upon changes of the **source**. Fast sampling source sensors provide better results. In this implementation, the default is the Trapezoidal method, but Left and Right methods can optionally be used. ## Configuration @@ -25,7 +25,7 @@ sensor: {% configuration %} source: - description: The entity ID of the sensor providing numeric readings + description: The entity ID of the sensor providing numeric readings. required: true type: string name: @@ -39,27 +39,27 @@ round: default: 3 type: integer unit_prefix: - description: Metric unit to prefix the integration result. Available units are k, M, G, T. + description: "Metric unit to prefix the integration result. Available units are `k`, `M`, `G` and `T`." required: false default: None type: string unit_time: - description: SI unit of time to integrate over. Available units are s, min, h, d. + description: "SI unit of time to integrate over. Available units are `s`, `min`, `h` and `d`." required: false default: h type: string unit: - description: Unit of Measurement to be used for the integration. + description: Unit of measurement to be used for the integration. required: false type: string method: - description: Riemann sum method to be used. Available methods are trapezoidal, left, right. + description: Riemann sum method to be used. Available methods are `trapezoidal`, `left` and `right`." required: false type: string default: trapezoidal {% endconfiguration %} -In case you have an appliance which produces 'spikey' consumption (like an on/off electrical boiler) you should opt for the left method I order to get accurate readings. 'unit' is set then 'unit_prefix' and 'unit_time' are ignored. +In case you have an appliance which produces spikey consumption (like an on/off electrical boiler) you should opt for the `left` method to get accurate readings. If `unit` is set then `unit_prefix` and `unit_time` are ignored. ## Energy From 68c0c82f24d7e68ce3526e85f851e348b35345ad Mon Sep 17 00:00:00 2001 From: Kevin Haffner Date: Sat, 28 Dec 2019 10:07:46 +0100 Subject: [PATCH 06/35] Specify Raspberry Pi version (#11548) Raspberry Pi 4 has gigabit ethernet --- source/_integrations/fastdotcom.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/fastdotcom.markdown b/source/_integrations/fastdotcom.markdown index ba875c36483..079ab1dc0d4 100644 --- a/source/_integrations/fastdotcom.markdown +++ b/source/_integrations/fastdotcom.markdown @@ -75,6 +75,6 @@ action: ## Notes -- When running on Raspberry Pi, the maximum speed is limited by its 100 Mbit/s LAN adapter. +- When running on Raspberry Pi 3 or older, the maximum speed is limited by its 100 Mbit/s LAN adapter. - The sensor will return the maximum measured speed during a 15-second test. - Speed tests consume data depending on your internet speed, make sure to consider this if your internet connection has limited bandwidth. From b5a2b12f3beaeb398ed17d4f5732912506ccfdba Mon Sep 17 00:00:00 2001 From: bkcberry Date: Sat, 28 Dec 2019 03:08:17 -0600 Subject: [PATCH 07/35] added build-essential to the ubuntu prerequisites (#11547) --- source/_docs/z-wave/installation.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/z-wave/installation.markdown b/source/_docs/z-wave/installation.markdown index d8c0842ea06..095956822ae 100644 --- a/source/_docs/z-wave/installation.markdown +++ b/source/_docs/z-wave/installation.markdown @@ -153,7 +153,7 @@ On the Raspberry Pi you will need to enable the serial interface in the `raspi-c On Debian Linux platforms there are dependencies you will need to have installed ahead of time (included in `systemd-devel` on Fedora/RHEL systems): ```bash -$ sudo apt-get install libudev-dev +$ sudo apt-get install libudev-dev build-essential ``` You may also have to install the Python development libraries for your version of Python. For example `libpython3.6-dev`, and possibly `python3.6-dev` if you're using Python 3.6. From 0cb2421c2d92352905855b987cc1d49882bcafb2 Mon Sep 17 00:00:00 2001 From: Mark Lopez Date: Sat, 28 Dec 2019 05:05:27 -0600 Subject: [PATCH 08/35] Html5 push docs (#11549) * Improved html5 docs around domain verification. * Minor change Co-authored-by: Fabian Affolter --- source/_integrations/html5.markdown | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/source/_integrations/html5.markdown b/source/_integrations/html5.markdown index 97ab7cdb13d..bbd852874d9 100644 --- a/source/_integrations/html5.markdown +++ b/source/_integrations/html5.markdown @@ -54,15 +54,15 @@ name: type: string default: notify vapid_pub_key: - description: The VAPID public key generated by Google (this is the key that is immediately visible under "webpush certificates"). + description: The VAPID public key generated by Google (this is the key that is immediately visible under "webpush certificates"), [see configuring the platform](#configuring_the_platform). required: true type: string vapid_prv_key: - description: The VAPID private key generated by Google. + description: The VAPID private key generated by Google, [see configuring the platform](#configuring_the_platform). required: true type: string vapid_email: - description: The e-mail account associated with your Firebase project. + description: The e-mail account associated with your Firebase project, [see configuring the platform](#configuring_the_platform). required: true type: string gcm_api_key: @@ -80,7 +80,7 @@ gcm_sender_id: The `html5` platform can only function if all of the following requirements are met: * You are using Chrome and/or Firefox on any desktop platform, ChromeOS or Android. -* Your Home Assistant instance is accessible from outside your network over HTTPS. +* Your Home Assistant instance is accessible from outside your network over HTTPS or can perform an alternative [Domain Name Verification Method](https://support.google.com/webmasters/answer/9008080#domain_name_verification) on the domain used by Home Assistant. * If using a proxy, HTTP basic authentication must be off for registering or unregistering for push notifications. It can be re-enabled afterwards. * If you don't run Hass.io: `pywebpush` must be installed. `libffi-dev`, `libpython-dev` and `libssl-dev` must be installed prior to `pywebpush` (i.e. `pywebpush` probably won't automatically install). * You have configured SSL/TLS for your Home Assistant. It doesn't need to be configured in Home Assistant though, e.g., you can be running [NGINX](/ecosystem/nginx/) in front of Home Assistant and this will still work. The certificate must be trustworthy (i.e. not self signed). @@ -88,13 +88,13 @@ The `html5` platform can only function if all of the following requirements are ### Configuring the platform -1. Make sure you can access your Home Assistant installation from outside your network over HTTPS ([see docs](/docs/configuration/remote/)). -2. Create a new project at [https://console.cloud.google.com/home/dashboard](https://console.cloud.google.com/home/dashboard). +1. Make sure you can access your Home Assistant installation from outside your network over HTTPS ([see docs](/docs/configuration/remote/)) or can perform an alternative [Domain Name Verification Method](https://support.google.com/webmasters/answer/9008080#domain_name_verification) on the domain used by Home Assistant. +2. Create a new project at [https://console.cloud.google.com/home/dashboard](https://console.cloud.google.com/home/dashboard), this project will be imported into Firebase later (alternatively, the project can also be created during step 4). 3. Go to [https://console.cloud.google.com/apis/credentials/domainverification](https://console.cloud.google.com/apis/credentials/domainverification) and verify your domain via Google Webmaster Central / Search Console - [see below](#verify-your-domain). 4. With the domain verified, go to [https://console.firebase.google.com](https://console.firebase.google.com), select import Google project and select the project you created. 5. Then, click the cogwheel on top left and select "Project settings". 6. Select 'Cloud Messaging' tab. -7. Generate a new key pair under the Web configuration listing at the bottom of the page. To view the private key click the three dots to the right and 'Show private key'. +7. Generate a new key pair under the Web configuration listing at the bottom of the page. To view the private key click the three dots to the right and 'Show private key'. ### Setting up your browser From 95b2141bd7d8dca565172763af478220e4157b35 Mon Sep 17 00:00:00 2001 From: Chris Hasenpflug <35075+chrishas35@users.noreply.github.com> Date: Sat, 28 Dec 2019 09:47:19 -0600 Subject: [PATCH 09/35] Correct typo in MQTT Certificate docs (#11552) --- source/_docs/mqtt/certificate.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/mqtt/certificate.markdown b/source/_docs/mqtt/certificate.markdown index 86225053aca..a1dc43c41a6 100644 --- a/source/_docs/mqtt/certificate.markdown +++ b/source/_docs/mqtt/certificate.markdown @@ -16,7 +16,7 @@ mqtt: {% configuration %} certificate: - description: "'auto' or the certificate authority certificate file that is to be treated as trusted by this client. To enable a secure (TLS) connection to your server you must define the 'certitificate' configuration parameter. 'auto' uses the certifite CAs bundled certificates. If a file is specified the file should contain the root certificate of the certificate authority that signed your broker's certificate, but may contain multiple certificates. Example: `/home/user/identrust-root.pem`." + description: "'auto' or the certificate authority certificate file that is to be treated as trusted by this client. To enable a secure (TLS) connection to your server you must define the 'certificate' configuration parameter. 'auto' uses the certifite CAs bundled certificates. If a file is specified the file should contain the root certificate of the certificate authority that signed your broker's certificate, but may contain multiple certificates. Example: `/home/user/identrust-root.pem`." required: false type: string client_key: From be1a66b43c0a59e68412bd1a27afdead1060276e Mon Sep 17 00:00:00 2001 From: Pascal Vizeli Date: Sat, 28 Dec 2019 22:18:01 +0100 Subject: [PATCH 10/35] Release 0.103.5 (#11556) --- _config.yml | 4 ++-- source/_posts/2019-12-11-release-103.markdown | 8 ++++++++ 2 files changed, 10 insertions(+), 2 deletions(-) diff --git a/_config.yml b/_config.yml index d4725650dfe..89d27b569a1 100644 --- a/_config.yml +++ b/_config.yml @@ -101,8 +101,8 @@ social: # Home Assistant release details current_major_version: 0 current_minor_version: 103 -current_patch_version: 4 -date_released: 2019-12-22 +current_patch_version: 5 +date_released: 2019-12-28 # Either # or the anchor link to latest release notes in the blog post. # Must be prefixed with a # and have double quotes around it. diff --git a/source/_posts/2019-12-11-release-103.markdown b/source/_posts/2019-12-11-release-103.markdown index 0df2480bf89..8db433707b2 100644 --- a/source/_posts/2019-12-11-release-103.markdown +++ b/source/_posts/2019-12-11-release-103.markdown @@ -334,6 +334,14 @@ All services for use in Home Assistant are moved to their integration naming spa [seven_segments docs]: /integrations/seven_segments/ [tensorflow docs]: /integrations/tensorflow/ +## Release 0.103.5 - December 28 + +- Bump ring to 0.2.8 to fix Oauth issues ([@tchellomello] - [#30245]) ([ring docs]) + +[#30245]: https://github.com/home-assistant/home-assistant/pull/30245 +[@tchellomello]: https://github.com/tchellomello +[ring docs]: /components/ring/ + ## 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). From a4871be308f6205178a43bdc1929dddf13361a85 Mon Sep 17 00:00:00 2001 From: Andrew Jackson Date: Mon, 30 Dec 2019 08:56:54 +0000 Subject: [PATCH 11/35] Update transmission.markdown (#11561) Corrected Sensors & Switches sections. All are prefixed with transmission_ and on_off has changed to transmission_switch. --- source/_integrations/transmission.markdown | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/source/_integrations/transmission.markdown b/source/_integrations/transmission.markdown index dd8455037c5..8f0640beb9a 100644 --- a/source/_integrations/transmission.markdown +++ b/source/_integrations/transmission.markdown @@ -70,18 +70,18 @@ scan_interval: The Transmission Integration will add the following sensors and switches. Sensors: -- current_status: The status of your Transmission daemon. -- download_speed: The current download speed [MB/s]. -- upload_speed: The current upload speed [MB/s]. -- active_torrents: The current number of active torrents. -- paused_torrents: The current number of paused torrents. -- total_torrents: The total number of torrents present in the client. -- started_torrents: The current number of started torrents (downloading). -- completed_torrents: The current number of completed torrents (seeding) +- transmission_current_status: The status of your Transmission daemon. +- transmission_download_speed: The current download speed [MB/s]. +- transmission_upload_speed: The current upload speed [MB/s]. +- transmission_active_torrents: The current number of active torrents. +- transmission_paused_torrents: The current number of paused torrents. +- transmission_total_torrents: The total number of torrents present in the client. +- transmission_started_torrents: The current number of started torrents (downloading). +- transmission_completed_torrents: The current number of completed torrents (seeding) Switches: -- on_off: A switch to start/stop all torrents -- turtle_mode: A switch to enable turtle mode. +- transmission_switch: A switch to start/stop all torrents +- transmission_turtle_mode: A switch to enable turtle mode. ## Event Automation From 9d0fef4eb6bcba0dd66536e874e48af962f2e870 Mon Sep 17 00:00:00 2001 From: Luke Pomfrey Date: Mon, 30 Dec 2019 08:58:44 +0000 Subject: [PATCH 12/35] =?UTF-8?q?Clarification=20on=20external=20access=20?= =?UTF-8?q?for=20Alexa=20intents=20and=20smart=20h=E2=80=A6=20(#11555)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Clarifies that your Home Assistant instance must be accessible from the internet via HTTPS on port 443, using a valid certificate to use account linking. --- source/_integrations/alexa.intent.markdown | 7 ++++--- source/_integrations/alexa.smart_home.markdown | 6 +++--- 2 files changed, 7 insertions(+), 6 deletions(-) diff --git a/source/_integrations/alexa.intent.markdown b/source/_integrations/alexa.intent.markdown index c5f34e5bd08..f67737a01f9 100644 --- a/source/_integrations/alexa.intent.markdown +++ b/source/_integrations/alexa.intent.markdown @@ -19,7 +19,7 @@ The built-in Alexa integration allows you to integrate Home Assistant into Alexa - Amazon Developer Account. You can sign on [here](https://developer.amazon.com). - An [AWS account](https://aws.amazon.com/free/) is need if you want to use Alexa Custom Skill API. Part of your Alexa Custom Skill will be hosted on [AWS Lambda](https://aws.amazon.com/lambda/pricing/). However you don't need worry the cost, AWS Lambda allow free to use up to 1 millions requests and 1GB outbound data transfer per month. -- The Alexa Custom Skill API also needs your Home Assistant instance can be accessed from Internet. We strongly suggest you host HTTPS server and use validation certificate. Read more on [our blog](/blog/2015/12/13/setup-encryption-using-lets-encrypt/) about how to set up encryption for Home Assistant. When running Hass.io using the [Duck DNS](/addons/duckdns/) add-on is the easiest method. +- The Alexa Custom Skill API also needs your Home Assistant instance to be accessible from the internet via HTTPS on port 443 using a certificate signed by [an Amazon approved certificate authority](https://ccadb-public.secure.force.com/mozilla/IncludedCACertificateReport), this is so account linking can take place. Read more on [our blog](/blog/2015/12/13/setup-encryption-using-lets-encrypt/) about how to set up encryption for Home Assistant. When running Hass.io using the [Duck DNS](/addons/duckdns/) add-on is the easiest method. ### Create Your Amazon Alexa Custom Skill @@ -94,8 +94,9 @@ Alexa can link your Amazon account to your Home Assistant account. Therefore Hom - Find the skill you just created and click `Edit` in the `Actions` column. - Click `ACCOUNT LINKING` in the left navigation bar of build page - Input all information required. Assuming your Home Assistant can be accessed by https://[YOUR HOME ASSISTANT URL:PORT] - * `Authorization URI`: https://[YOUR HOME ASSISTANT URL:PORT]/auth/authorize - * `Access Token URI`: https://[YOUR HOME ASSISTANT URL:PORT]/auth/token + * `Authorization URI`: https://[YOUR HOME ASSISTANT URL]/auth/authorize + * `Access Token URI`: https://[YOUR HOME ASSISTANT URL]/auth/token + - Note: you must use a valid/trusted SSL Certificate and port 443 for account linking to work * `Client ID`: - https://pitangui.amazon.com/ if you are in US - https://layla.amazon.com/ if you are in EU diff --git a/source/_integrations/alexa.smart_home.markdown b/source/_integrations/alexa.smart_home.markdown index e68f75e19cd..0d016189628 100644 --- a/source/_integrations/alexa.smart_home.markdown +++ b/source/_integrations/alexa.smart_home.markdown @@ -37,7 +37,7 @@ For Home Assistant Cloud Users, documentation can be found [here](https://www.na - Amazon Developer Account. You can sign on [here](https://developer.amazon.com). - An [AWS account](https://aws.amazon.com/free/) is need if you want to use Smart Home Skill API. Part of your Smart Home Skill will be hosted on [AWS Lambda](https://aws.amazon.com/lambda/pricing/). However you don't need worry the cost, AWS Lambda allow free to use up to 1 millions requests and 1GB outbound data transfer per month. -- Smart Home API also needs your Home Assistant instance can be accessed from Internet. We strongly suggest you host HTTPS server and use validation certificate. Read more on [our blog](/blog/2015/12/13/setup-encryption-using-lets-encrypt/) about how to set up encryption for Home Assistant. When running Hass.io using the [Duck DNS](/addons/duckdns/) add-on is the easiest method. +- The Smart Home API also needs your Home Assistant instance to be accessible from the internet via HTTPS on port 443 using a certificate signed by [an Amazon approved certificate authority](https://ccadb-public.secure.force.com/mozilla/IncludedCACertificateReport), this is so account linking can take place. Read more on [our blog](/blog/2015/12/13/setup-encryption-using-lets-encrypt/) about how to set up encryption for Home Assistant. When running Hass.io using the [Duck DNS](/addons/duckdns/) add-on is the easiest method. ### Create Your Amazon Alexa Smart Home Skill @@ -171,8 +171,8 @@ Alexa can link your Amazon account to your Home Assistant account. Therefore Hom - Find the skill you just created, click `Edit` link in the `Actions` column. - Click `ACCOUNT LINKING` in the left navigation bar of build page - Input all information required. Assuming your Home Assistant can be accessed by https://[YOUR HOME ASSISTANT URL:PORT] - * `Authorization URI`: https://[YOUR HOME ASSISTANT URL:PORT]/auth/authorize - * `Access Token URI`: https://[YOUR HOME ASSISTANT URL:PORT]/auth/token + * `Authorization URI`: https://[YOUR HOME ASSISTANT URL]/auth/authorize + * `Access Token URI`: https://[YOUR HOME ASSISTANT URL]/auth/token - Note: you must use a valid/trusted SSL Certificate and port 443 for account linking to work * `Client ID`: - https://pitangui.amazon.com/ if you are in US From 4e4245df33ef78438d8d69f07fa757d42878787c Mon Sep 17 00:00:00 2001 From: Geoff Pursell Date: Mon, 30 Dec 2019 03:00:35 -0600 Subject: [PATCH 13/35] Cleanup, doc hierarchy, and ordering (#11562) * Cleanup, doc hierarchy, and ordering Hierarchical headings for TV support, working, not working lists, put naming info first to assist with finding your TV on the list * :pencil2: Tweak Co-authored-by: Klaas Schoute --- source/_integrations/samsungtv.markdown | 24 +++++++++++++++++------- 1 file changed, 17 insertions(+), 7 deletions(-) diff --git a/source/_integrations/samsungtv.markdown b/source/_integrations/samsungtv.markdown index 9ffd7b3e2ea..26fd4920b91 100644 --- a/source/_integrations/samsungtv.markdown +++ b/source/_integrations/samsungtv.markdown @@ -55,7 +55,17 @@ broadcast_address: type: string {% endconfiguration %} -Currently known supported models: +### Supported models + +If your model is not on the list then give it a test, if everything works correctly then add it to the list on [GitHub](https://github.com/home-assistant/home-assistant.io/tree/current/source/_integrations/samsungtv.markdown). + +#### Naming + +The first letter (U, P, L, H & K) represent the screen type, e.g., LED or Plasma. The second letter represents the region, E is Europe, N is North America and A is Asia & Australia. The two numbers following that represent the screen size. If you add your model remember to remove these first 4 characters before adding to the list. + +For example: for model `UN55NU7100`, the `UN55` would mean it's an LED, North American, 55 inch TV, and the model number listed below would be the remainder: `NU7100`. + +#### Models tested and working - C7700 - D5500 @@ -103,7 +113,7 @@ Currently known supported models: - UE49KU6470 (port must be set to 8001, On/Off, Forward/Backward, Volume are OK, but no Play button) - UE46ES5500 (partially supported, turn on doesn't works) -Currently tested but not working models: +#### Models tested but not yet working - J5200 - Unable to see state and unable to control - J5500 - State is always "on" and unable to control (but port 8001 *is* open) @@ -125,10 +135,9 @@ Currently tested but not working models: None of the 2014 (H) and 2015 (J) model series (e.g., J5200) will work, since Samsung have used a different (encrypted) type of interface for these. -If your model is not on the list then give it a test, if everything works correctly then add it to the list on -[GitHub](https://github.com/home-assistant/home-assistant.io/tree/current/source/_integrations/samsungtv.markdown). -The first letter (U, P, L, H & K) represent the screen type, e.g., LED or Plasma. The second letter represents the region, E is Europe, N is North America and A is Asia & Australia. The two numbers following that represent the screen size. -If you add your model remember to remove these first 4 characters before adding to the list. +### Usage + +#### Changing channels Changing channels can be done by calling the `media_player.play_media` service with the following payload: @@ -140,8 +149,9 @@ with the following payload: "media_content_type": "channel" } ``` +#### Selecting a source -Currently the ability to select a source is not implemented. +Source selection is not yet implemented. ### Hass.io From 412455943597a3c8710aed90601f139dbee81805 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Emil=20H=C3=B8rlyck?= Date: Mon, 30 Dec 2019 10:01:00 +0100 Subject: [PATCH 14/35] Linked to SimpliSafe website (#11563) Added inline link to SimpliSafe website to show their lock. --- source/_integrations/simplisafe.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/simplisafe.markdown b/source/_integrations/simplisafe.markdown index f3fd0b49cd1..f8070448b9b 100644 --- a/source/_integrations/simplisafe.markdown +++ b/source/_integrations/simplisafe.markdown @@ -8,7 +8,7 @@ ha_category: - Lock --- -The `simplisafe` integration integrates SimpliSafe home security (V2 and V3) systems into Home Assistant. Multiple SimpliSafe accounts can be accommodated. +The `simplisafe` integration integrates [SimpliSafe home security](https://simplisafe.com/smart-lock) (V2 and V3) systems into Home Assistant. Multiple SimpliSafe accounts can be accommodated. There is currently support for the following device types within Home Assistant: From 4f88bf1ef5561fc2a2c323884b7610ce697ce329 Mon Sep 17 00:00:00 2001 From: Rudertier <19547127+Rudertier@users.noreply.github.com> Date: Mon, 30 Dec 2019 12:55:42 +0100 Subject: [PATCH 15/35] Update rmvtransport.markdown (#11568) --- source/_integrations/rmvtransport.markdown | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/source/_integrations/rmvtransport.markdown b/source/_integrations/rmvtransport.markdown index c8d8b33db3b..dfe20a02f96 100644 --- a/source/_integrations/rmvtransport.markdown +++ b/source/_integrations/rmvtransport.markdown @@ -59,9 +59,9 @@ next_departure: required: false type: [string, integer] products: - description: "One or more modes of transport `['U-Bahn', 'Tram', 'Bus', 'S-Bahn', 'RB', 'RE', 'EC', 'IC', 'ICE']`." + description: "One or more modes of transport `['U-Bahn', 'Tram', 'Bus', 'S', 'RB', 'RE', 'EC', 'IC', 'ICE']`." required: false - default: ['U-Bahn', 'Tram', 'Bus', 'S-Bahn', 'RB', 'RE', 'EC', 'IC', 'ICE'] + default: ['U-Bahn', 'Tram', 'Bus', 'S', 'RB', 'RE', 'EC', 'IC', 'ICE'] type: [string] time_offset: description: Do not display departures leaving sooner than this number of minutes. Useful if you are a couple of minutes away from the stop. @@ -97,7 +97,7 @@ sensor: - 'RB' - 'RE' - 'Bus' - - 'S-Bahn' + - 'S' - station: 3006907 products: 'Bus' destinations: ['Wiesbaden Dernsches Gelände', 'Mainz Hauptbahnhof'] @@ -105,7 +105,7 @@ sensor: - station: 3006904 lines: 'S8' max_journeys: 5 - products: 'S-Bahn' + products: 'S' ``` The first sensor will return S-Bahn, bus, RB and RE trains departures from Frankfurt Hauptbahnhof to Frankfurt Airport or Stadium that are at least 5 minutes away. From 25d9e68286e30cbb14774656f2da43c410b0312a Mon Sep 17 00:00:00 2001 From: Dan Jackson Date: Mon, 30 Dec 2019 12:35:19 -0800 Subject: [PATCH 16/35] =?UTF-8?q?Update=20trigger.markdown=20for=20consist?= =?UTF-8?q?ency=20with=20automation=5Fsun.ma=E2=80=A6=20(#11573)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Looks like a similar change was made to `automation_sun.markdown` in #10532, attributed to #10315. As someone trying to add an automation for the sun's elevation, the inconsistency was confusing. I don't know if other parts of this page should be updated in a similar way. --- source/_docs/automation/trigger.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/automation/trigger.markdown b/source/_docs/automation/trigger.markdown index 2be3ee4b435..448da488c73 100644 --- a/source/_docs/automation/trigger.markdown +++ b/source/_docs/automation/trigger.markdown @@ -216,7 +216,7 @@ automation: trigger: platform: numeric_state entity_id: sun.sun - value_template: "{{ state.attributes.elevation }}" + value_template: "{{ state_attr('sun.sun', 'elevation') }}" # Can be a positive or negative number below: -4.0 action: From 1a50ee649a4d499079b2241298aba867394a0493 Mon Sep 17 00:00:00 2001 From: Aaron Bach Date: Mon, 30 Dec 2019 14:27:36 -0700 Subject: [PATCH 17/35] Correct SimpliSafe website link (#11574) * Revert "Linked to SimpliSafe website (#11563)" This reverts commit 412455943597a3c8710aed90601f139dbee81805. * Revert "Revert "Linked to SimpliSafe website (#11563)"" This reverts commit a0543d47d71ce9cd961317dfb1337553ac8d6535. * Corrected link --- source/_integrations/simplisafe.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/simplisafe.markdown b/source/_integrations/simplisafe.markdown index f8070448b9b..40e6e089501 100644 --- a/source/_integrations/simplisafe.markdown +++ b/source/_integrations/simplisafe.markdown @@ -8,7 +8,7 @@ ha_category: - Lock --- -The `simplisafe` integration integrates [SimpliSafe home security](https://simplisafe.com/smart-lock) (V2 and V3) systems into Home Assistant. Multiple SimpliSafe accounts can be accommodated. +The `simplisafe` integration integrates [SimpliSafe home security](https://simplisafe.com) (V2 and V3) systems into Home Assistant. Multiple SimpliSafe accounts can be accommodated. There is currently support for the following device types within Home Assistant: From 7adb9d0b27437209ecd0fc9511d71f8d9ea369c1 Mon Sep 17 00:00:00 2001 From: Patrick Smits Date: Mon, 30 Dec 2019 23:45:24 +0100 Subject: [PATCH 18/35] Update proxmoxve.markdown (#11576) Machine was misspelled --- source/_integrations/proxmoxve.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/proxmoxve.markdown b/source/_integrations/proxmoxve.markdown index 5cec938598b..dd997c31386 100644 --- a/source/_integrations/proxmoxve.markdown +++ b/source/_integrations/proxmoxve.markdown @@ -97,6 +97,6 @@ proxmoxve: ## Binary Sensor -The integration will automatically create a binary sensor for each tracked virtual machone or container. The binary sensor will either be on if the VM's state is running or off if the VM's state is different. +The integration will automatically create a binary sensor for each tracked virtual machine or container. The binary sensor will either be on if the VM's state is running or off if the VM's state is different. The created sensor will be called `binary_sensor.NODE_NAME_VMNAME_running`. From e2b183091072ab5d8aeb7e44f2f4fedc5aa1a57a Mon Sep 17 00:00:00 2001 From: Ronald Dehuysser Date: Tue, 31 Dec 2019 10:17:07 +0100 Subject: [PATCH 19/35] Update climate.markdown (#11575) --- source/_integrations/climate.markdown | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/source/_integrations/climate.markdown b/source/_integrations/climate.markdown index de691fce92c..4a999999b29 100644 --- a/source/_integrations/climate.markdown +++ b/source/_integrations/climate.markdown @@ -28,7 +28,7 @@ Turn auxiliary heater on/off for climate device | Service data attribute | Optional | Description | | ---------------------- | -------- | ----------- | -| `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. Targets all when omitted. +| `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. To target all climate devices, use `all`. | `aux_heat` | no | New value of auxiliary heater. #### Automation example @@ -53,7 +53,7 @@ reflecting a situation where the climate device is set to save energy. For examp | Service data attribute | Optional | Description | | ---------------------- | -------- | ----------- | -| `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. Targets all when omitted. +| `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. To target all climate devices, use `all`. | `preset_mode` | no | New value of preset mode. #### Automation example @@ -76,7 +76,7 @@ Set target temperature of climate device | Service data attribute | Optional | Description | | ---------------------- | -------- | ----------- | -| `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. Targets all when omitted. +| `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. To target all climate devices, use `all`. | `temperature` | no | New target temperature for climate device (commonly referred to as a *setpoint*). Do not use if `hvac_mode` is `heat_cool`. | `target_temp_high` | yes | The highest temperature that the climate device will allow. Required if `hvac_mode` is `heat_cool`. | `target_temp_low` | yes | The lowest temperature that the climate device will allow. Required if `hvac_mode` is `heat_cool`. @@ -119,7 +119,7 @@ Set target humidity of climate device | Service data attribute | Optional | Description | | ---------------------- | -------- | ----------- | -| `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. Targets all when omitted. +| `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. To target all climate devices, use `all`. | `humidity` | no | New target humidity for climate device #### Automation example @@ -142,7 +142,7 @@ Set fan operation for climate device | Service data attribute | Optional | Description | | ---------------------- | -------- | ----------- | -| `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. Targets all when omitted. +| `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. To target all climate devices, use `all`. | `fan_mode` | no | New value of fan mode #### Automation example @@ -165,7 +165,7 @@ Set climate device's HVAC mode | Service data attribute | Optional | Description | | ---------------------- | -------- | ----------- | -| `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. Targets all when omitted. +| `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. To target all climate devices, use `all`. | `hvac_mode` | no | New value of HVAC mode #### Automation example @@ -188,7 +188,7 @@ Set swing operation mode for climate device | Service data attribute | Optional | Description | | ---------------------- | -------- | ----------- | -| `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. Targets all when omitted. +| `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. To target all climate devices, use `all`. | `swing_mode` | no | New value of swing mode #### Automation example @@ -211,7 +211,7 @@ Turn climate device on. This is only supported if the climate device supports be | Service data attribute | Optional | Description | | ---------------------- | -------- | ----------- | -| `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. Targets all when omitted. +| `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. To target all climate devices, use `all`. ### Service `climate.turn_off` @@ -219,4 +219,4 @@ Turn climate device off. This is only supported if the climate device has the hv | Service data attribute | Optional | Description | | ---------------------- | -------- | ----------- | -| `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. Targets all when omitted. +| `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. To target all climate devices, use `all`. From 4edb0f7b84517f8effc0f42596ec41fffccc1e41 Mon Sep 17 00:00:00 2001 From: Panagiotis Panagiotopoulos Date: Tue, 31 Dec 2019 11:33:15 +0200 Subject: [PATCH 20/35] Entity_id isn't optional anymore at light.{turn_off/turn_on} (#11578) After #29178 entity_id isn't optional anymore. You have to use group.all_lights as entity_id. --- source/_integrations/light.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_integrations/light.markdown b/source/_integrations/light.markdown index 0e623c64b0a..a72f02ed95b 100644 --- a/source/_integrations/light.markdown +++ b/source/_integrations/light.markdown @@ -24,7 +24,7 @@ Most lights do not support all attributes. You can check the integration documen | Service data attribute | Optional | Description | | ---------------------- | -------- | ----------- | -| `entity_id` | yes | String or list of strings that point at `entity_id`s of lights. Else targets all. +| `entity_id` | no | String or list of strings that point at `entity_id`s of lights. To target all the lights use all as `entity_id`. | `transition` | yes | Number that represents the time (in seconds) the light should take to transition to the new state. | `profile` | yes | String with the name of one of the [built-in profiles](https://github.com/home-assistant/home-assistant/blob/master/homeassistant/components/light/light_profiles.csv) (relax, energize, concentrate, reading) or one of the custom profiles defined in `light_profiles.csv` in the current working directory. Light profiles define an xy color and a brightness. If a profile is given and a brightness then the profile brightness will be overwritten. | `hs_color` | yes | A list containing two floats representing the hue and saturation of the color you want the light to be. Hue is scaled 0-360, and saturation is scaled 0-100. @@ -82,7 +82,7 @@ Turns one or multiple lights off. | Service data attribute | Optional | Description | | ---------------------- | -------- | ----------- | -| `entity_id` | yes | String or list of strings that point at `entity_id`s of lights. Else targets all. +| `entity_id` | no | String or list of strings that point at `entity_id`s of lights. To target all the lights use all as `entity_id`. | `transition` | yes | Integer that represents the time the light should take to transition to the new state in seconds. ### Service `light.toggle` From cc2cf98fc829aa07259efe4058f7e420d5369261 Mon Sep 17 00:00:00 2001 From: Keith Bentrup Date: Wed, 1 Jan 2020 06:18:33 -0500 Subject: [PATCH 21/35] Remove bash prompt from shell commands to copy (#11588) By including the prompts in the shell commands, it breaks the copy/paste functionality provided on the webpage https://www.home-assistant.io/docs/installation/raspberry-pi/. I understand it was to indicate a change for the user but that should be in the surrounding text. --- source/_docs/installation/raspberry-pi.markdown | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/source/_docs/installation/raspberry-pi.markdown b/source/_docs/installation/raspberry-pi.markdown index c1799b53744..89b92ca9428 100644 --- a/source/_docs/installation/raspberry-pi.markdown +++ b/source/_docs/installation/raspberry-pi.markdown @@ -67,22 +67,22 @@ cd /srv/homeassistant python3 -m venv . source bin/activate ``` -Once you have activated the virtual environment (notice the prompt change) you will need to run the following command to install a required python package. +Once you have activated the virtual environment (notice the prompt change to `(homeassistant) homeassistant@raspberrypi:/srv/homeassistant $`) you will need to run the following command to install a required python package. ```bash -(homeassistant) homeassistant@raspberrypi:/srv/homeassistant $ python3 -m pip install wheel +python3 -m pip install wheel ``` Once you have installed the required python package it is now time to install Home Assistant! ```bash -(homeassistant) homeassistant@raspberrypi:/srv/homeassistant $ pip3 install homeassistant +pip3 install homeassistant ``` Start Home Assistant for the first time. This will complete the installation for you, automatically creating the `.homeassistant` configuration directory in the `/home/homeassistant` directory, and installing any basic dependencies. ```bash -(homeassistant) $ hass +hass ``` You can now reach your installation on your Raspberry Pi over the web interface on `http://ipaddress:8123`. From dde32d1d858d5aa91580bcb354a593d13c052681 Mon Sep 17 00:00:00 2001 From: "dependabot-preview[bot]" <27856297+dependabot-preview[bot]@users.noreply.github.com> Date: Wed, 1 Jan 2020 14:03:17 +0100 Subject: [PATCH 22/35] Bump sinatra from 2.0.7 to 2.0.8 (#11590) Bumps [sinatra](https://github.com/sinatra/sinatra) from 2.0.7 to 2.0.8. - [Release notes](https://github.com/sinatra/sinatra/releases) - [Changelog](https://github.com/sinatra/sinatra/blob/master/CHANGELOG.md) - [Commits](https://github.com/sinatra/sinatra/compare/v2.0.7...v2.0.8) Signed-off-by: dependabot-preview[bot] Co-authored-by: null <27856297+dependabot-preview[bot]@users.noreply.github.com> --- Gemfile | 2 +- Gemfile.lock | 12 +++++++----- 2 files changed, 8 insertions(+), 6 deletions(-) diff --git a/Gemfile b/Gemfile index e6f7c14f627..21a95182769 100644 --- a/Gemfile +++ b/Gemfile @@ -18,7 +18,7 @@ group :jekyll_plugins do gem 'jekyll-commonmark', '1.3.1' end -gem 'sinatra', '2.0.7' +gem 'sinatra', '2.0.8' gem 'nokogiri', '1.10.7' # Windows and JRuby does not include zoneinfo files, so bundle the tzinfo-data gem diff --git a/Gemfile.lock b/Gemfile.lock index cb651a8c54d..fb8e7fa3903 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -70,7 +70,8 @@ GEM mercenary (0.3.6) mini_portile2 (2.4.0) multi_json (1.14.1) - mustermann (1.0.3) + mustermann (1.1.0) + ruby2_keywords (~> 0.0.1) nokogiri (1.10.7) mini_portile2 (~> 2.4.0) nokogiri (1.10.7-x64-mingw32) @@ -79,7 +80,7 @@ GEM forwardable-extended (~> 2.6) public_suffix (4.0.1) rack (2.0.8) - rack-protection (2.0.7) + rack-protection (2.0.8) rack rake (13.0.1) rb-fsevent (0.10.3) @@ -88,6 +89,7 @@ GEM rouge (3.13.0) ruby-enum (0.7.2) i18n + ruby2_keywords (0.0.1) safe_yaml (1.0.5) sass (3.4.25) sass-globbing (1.1.5) @@ -96,10 +98,10 @@ GEM ffi (~> 1.9) sassc (2.2.1-x64-mingw32) ffi (~> 1.9) - sinatra (2.0.7) + sinatra (2.0.8) mustermann (~> 1.0) rack (~> 2.0) - rack-protection (= 2.0.7) + rack-protection (= 2.0.8) tilt (~> 2.0) stringex (2.8.5) terminal-table (1.8.0) @@ -126,7 +128,7 @@ DEPENDENCIES nokogiri (= 1.10.7) rake (= 13.0.1) sass-globbing (= 1.1.5) - sinatra (= 2.0.7) + sinatra (= 2.0.8) stringex (= 2.8.5) tzinfo (~> 2.0) tzinfo-data From 0a7b70a189fcd536547e7276f79097dd8593f004 Mon Sep 17 00:00:00 2001 From: John Hollowell Date: Wed, 1 Jan 2020 08:38:52 -0500 Subject: [PATCH 23/35] Update ha-vs-hassio.markdown (#11586) --- source/_faq/ha-vs-hassio.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_faq/ha-vs-hassio.markdown b/source/_faq/ha-vs-hassio.markdown index 6b6a8988c33..f83a3beb903 100644 --- a/source/_faq/ha-vs-hassio.markdown +++ b/source/_faq/ha-vs-hassio.markdown @@ -4,7 +4,7 @@ description: "Home Assistant vs. Hass.io" ha_category: Installation --- -Home Assistant is a Python program, in simple words. It can be run various operating system and provide the ability to track, control and automate your devices. When people talking about Home Assistant they usually refer to a standalone [installation method](/docs/installation/). +Home Assistant is a Python program, in simple words. It can be run on various operating systems and provide the ability to track, control and automate your devices. When people talking about Home Assistant they usually refer to a standalone [installation method](/docs/installation/). [Hass.io](/hassio/) is a combination of Home Assistant and tools which allows one to run it easily on a Raspberry Pi and other platforms without setting up an operating system first. Hass.io is an all-in one-solution and has a management user interface that can be used from the Home Assistant frontend. This interface is not present in a standalone setup of Home Assistant. From f20728ef001763d2f09f148bfb60c753b9e2df8a Mon Sep 17 00:00:00 2001 From: Thiago Oliveira Date: Wed, 1 Jan 2020 10:52:26 -0800 Subject: [PATCH 24/35] Fix zwave control panel wiki (#11583) The **Entity Attrributes** button is actually named **Entity Information**. Also fixing the description on polling intensity to be a little clearer. --- source/_docs/z-wave/control-panel.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_docs/z-wave/control-panel.markdown b/source/_docs/z-wave/control-panel.markdown index 5a516eaf494..d6ea9944505 100644 --- a/source/_docs/z-wave/control-panel.markdown +++ b/source/_docs/z-wave/control-panel.markdown @@ -78,11 +78,11 @@ Battery powered devices need to be awake before you can use the Z-Wave control p This is a dropdown where you can select all the entities of this node. Once selected you can then use: * **Refresh Entity** to refresh just that entity's values -* **Entity Attributes** to display the attributes of that entity (e.g., its friendly name, the ID of the node, etc) +* **Entity Information** to display the attributes of that entity (e.g., its friendly name, the ID of the node, etc) Here you can mark a device as requiring polling so the controller is aware of changes because the device doesn't send updates itself. Do see the information on [polling here](/docs/z-wave/devices/#polling), since excessive polling can break your Z-Wave network. -The **Polling intensity** says how many poll intervals does is this device polled on. For example, if you set 2 then it's polled on every second interval. +The **Polling intensity** says how many poll intervals this device is polled on. For example, if you set 2 then it's polled on every second interval. You can also exclude a Z-Wave devices from Home Assistant. You can do that if you have a device that you need to have on the Z-Wave network, but you don't want it to appear in Home Assistant, or if you've got a device that's failed and you're unable to exclude it. From 01f101ddbbf025c6be6837309e6b533e870c342b Mon Sep 17 00:00:00 2001 From: Roelof Schuiling Date: Thu, 2 Jan 2020 09:22:51 +0100 Subject: [PATCH 25/35] Improved wording for ModemManager troubleshooting (#11599) Users experiencing issues / interference by ModemManager are still commonly popping up in the forum. I changed the wording, so hopefully users will more easily recognize this applies to them. --- source/_docs/z-wave/installation.markdown | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/source/_docs/z-wave/installation.markdown b/source/_docs/z-wave/installation.markdown index 095956822ae..0c7a2228ce7 100644 --- a/source/_docs/z-wave/installation.markdown +++ b/source/_docs/z-wave/installation.markdown @@ -122,7 +122,7 @@ You can also check what hardware has been found using the [hassio command](/hass $ hassio hardware info ``` -If you did an alternative install on Linux then the `modemmanager` package will interfere with any Z-Wave (or Zigbee) stick and should be removed or disabled. Failure to do so will result in random failures of those components. For example you can disable with `sudo systemctl disable ModemManager` and remove with `sudo apt-get purge modemmanager`. +If you did an alternative install of Hass.io on Linux (e.g. installing Ubuntu, then Docker, then Hass.io) then the `modemmanager` package will interfere with any Z-Wave (or Zigbee) stick and should be removed or disabled in the host OS. Failure to do so will result in random failures of those components, e.g. dead or unreachable Z-Wave nodes, most notably right after HomeAssistant restarts. Connect to your host OS via SSH, then you can disable with `sudo systemctl disable ModemManager` and remove with `sudo apt-get purge modemmanager` (commands are for Debian/Ubuntu). ### Docker @@ -215,13 +215,16 @@ ls /dev/cu.usbmodem* If your device path changes when you restart, see [this guide](http://hintshop.ludvig.co.nz/show/persistent-names-usb-serial-devices/) on fixing it. -## Ubuntu and Debian based host system +## Random unreachable Z-Wave nodes: ModemManager interference -If your instance is running on a Debian based system, e.g., Ubuntu, the ModemManager may cause unexpected issues. +If this applies to your situation: +- Some or all Z-Wave nodes are unreachable after restarting Home Assistant; not necessarily after every restart but seemingly random. +- The Z-Wave stick stops responding, needs to be re-plugged or Home Assistant needs a restart to get Z-Wave back. +- Your host OS is Debian-based/Ubuntu (for example: you installed Ubuntu, then Docker, then Hass.io). -The ModemManager might be claiming or interfering with a USB Z-Wave stick, like the much used Aeotec ones. If you experience issues where the stick stops responding, needs to be re-plugged or Home Assistant needs a restart to get Z-Wave back, chances are high that the ModemManager is causing the issue. +Then chances are high that the ModemManager in the host OS is causing the issue, claiming or interfering with the USB Z-Wave stick like the much used Aeotec ones. In this case you need to disable ModemManager. - Execute the following command on your host system to disable the ModemManager: +Connect to your host OS (e.g. Ubuntu) through SSH, then execute the following command on your host system to disable the ModemManager: ```bash systemctl disable ModemManager.service From b86b20e695bfb954fe8975efcb1212775313571e Mon Sep 17 00:00:00 2001 From: stappel Date: Thu, 2 Jan 2020 09:29:39 +0100 Subject: [PATCH 26/35] Added information to clarify options (#11580) * Added information to clarify options Added information to clarify options * Minor changes Co-authored-by: Fabian Affolter --- source/_integrations/synologydsm.markdown | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/source/_integrations/synologydsm.markdown b/source/_integrations/synologydsm.markdown index 29c40eb41df..cad8a19a30d 100644 --- a/source/_integrations/synologydsm.markdown +++ b/source/_integrations/synologydsm.markdown @@ -29,7 +29,7 @@ sensor: {% configuration %} name: - description: The name of your device + description: The name to use in the frontend for your Synology device. required: false default: Synology DSM type: string @@ -56,11 +56,11 @@ ssl: default: true type: boolean volumes: - description: Array of volumes to monitor. Defaults to all volumes. + description: "Array of volumes to monitor. Defaults to all volumes. Replace any spaces in the volume name with underscores, e.g., `volume 1` with `volume_1`." required: false type: list disks: - description: Array of disks to monitor. Defaults to all disks. + description: "Array of disks to monitor. Defaults to all disks. Use only disk names like `sda`, `sdb`, etc." required: false type: list monitored_conditions: From 03dcf265635b9f80bb13f64c5fc0a81b22e8acec Mon Sep 17 00:00:00 2001 From: Jon Gilmore <7232986+JonGilmore@users.noreply.github.com> Date: Thu, 2 Jan 2020 02:30:54 -0600 Subject: [PATCH 27/35] example automation for hunter douglas scenes (#11592) --- .../_integrations/hunterdouglas_powerview.markdown | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/source/_integrations/hunterdouglas_powerview.markdown b/source/_integrations/hunterdouglas_powerview.markdown index 6a231a79af5..319742d7c76 100644 --- a/source/_integrations/hunterdouglas_powerview.markdown +++ b/source/_integrations/hunterdouglas_powerview.markdown @@ -24,3 +24,15 @@ address: required: true type: string {% endconfiguration %} + +## Example Automations + +``` yaml +- alias: "blinds closed at night" + trigger: + platform: time + at: "18:00:00" + action: + - service: scene.turn_on + entity_id: scene.10877 +``` From 14a6b3a10e607a733b90d4416cb9d99c1bc7214a Mon Sep 17 00:00:00 2001 From: omegacore Date: Thu, 2 Jan 2020 00:54:01 -0800 Subject: [PATCH 28/35] Alert users pymysql is not required for external MariaDB (#11527) * Update recorder.markdown * :pencil2: Tweak Co-authored-by: Franck Nijhof --- source/_integrations/recorder.markdown | 37 +++++++++++++++----------- 1 file changed, 22 insertions(+), 15 deletions(-) diff --git a/source/_integrations/recorder.markdown b/source/_integrations/recorder.markdown index 875d26c90e0..6fe93a8a3f4 100644 --- a/source/_integrations/recorder.markdown +++ b/source/_integrations/recorder.markdown @@ -121,24 +121,25 @@ If you only want to hide events from your history, take a look at the [`history` Call the service `recorder.purge` to start a purge task which deletes events and states older than x days, according to `keep_days` service data. -| Service data attribute | Optional | Description | -| ---------------------- | -------- | ----------- | -| `keep_days` | yes | The number of history days to keep in recorder database (defaults to the integration `purge_keep_days` configuration) -| `repack` | yes | Rewrite the entire database, possibly saving some disk space. Only supported for SQLite and requires at least as much disk space free as the database currently uses. +| Service data attribute | Optional | Description | +| ---------------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `keep_days` | yes | The number of history days to keep in recorder database (defaults to the integration `purge_keep_days` configuration) | +| `repack` | yes | Rewrite the entire database, possibly saving some disk space. Only supported for SQLite and requires at least as much disk space free as the database currently uses. | ## Custom database engines -| Database engine | `db_url` | -| :---------------|:---------------------------------------------------------| -| SQLite | `sqlite:////PATH/TO/DB_NAME` | -| MariaDB | `mysql+pymysql://SERVER_IP/DB_NAME?charset=utf8` | -| MariaDB         | `mysql+pymysql://user:password@SERVER_IP/DB_NAME?charset=utf8` | -| MySQL | `mysql://SERVER_IP/DB_NAME?charset=utf8` | -| MySQL | `mysql://user:password@SERVER_IP/DB_NAME?charset=utf8` | -| PostgreSQL | `postgresql://SERVER_IP/DB_NAME` | -| PostgreSQL | `postgresql://user:password@SERVER_IP/DB_NAME` | -| PostgreSQL (Socket) | `postgresql://@/DB_NAME` | -| MS SQL Server | `mssql+pyodbc://username:password@SERVER_IP/DB_NAME?charset=utf8;DRIVER={DRIVER};Port=1433;` | +| Database engine | `db_url` | +| :--------------------- | :------------------------------------------------------------------------------------------- | +| SQLite | `sqlite:////PATH/TO/DB_NAME` | +| MariaDB | `mysql+pymysql://SERVER_IP/DB_NAME?charset=utf8` | +| MariaDB | `mysql+pymysql://user:password@SERVER_IP/DB_NAME?charset=utf8` | +| MariaDB (omit pymysql) | `mysql://user:password@SERVER_IP/DB_NAME?charset=utf8` | +| MySQL | `mysql://SERVER_IP/DB_NAME?charset=utf8` | +| MySQL | `mysql://user:password@SERVER_IP/DB_NAME?charset=utf8` | +| PostgreSQL | `postgresql://SERVER_IP/DB_NAME` | +| PostgreSQL | `postgresql://user:password@SERVER_IP/DB_NAME` | +| PostgreSQL (Socket) | `postgresql://@/DB_NAME` | +| MS SQL Server | `mssql+pyodbc://username:password@SERVER_IP/DB_NAME?charset=utf8;DRIVER={DRIVER};Port=1433;` |
@@ -148,6 +149,12 @@ Some installations of MariaDB/MySQL may require an ALTERNATE_PORT (3rd-party hos
+If using an external MariaDB backend (e.g., running on a separate NAS) with Home Assistant, you should omit `pymysql` from the URL. `pymysql` is not included in the base docker image, and is not necessary for this to work. + +
+ +
+ Unix Socket connections always bring performance advantages over TCP, if the database is on the same host as the `recorder` instance (i.e. `localhost`).
From 15914931fc83072c5826d6b6336b2f362cb66764 Mon Sep 17 00:00:00 2001 From: "dependabot-preview[bot]" <27856297+dependabot-preview[bot]@users.noreply.github.com> Date: Thu, 2 Jan 2020 12:26:07 +0100 Subject: [PATCH 29/35] Bump sinatra from 2.0.8 to 2.0.8.1 (#11601) Bumps [sinatra](https://github.com/sinatra/sinatra) from 2.0.8 to 2.0.8.1. - [Release notes](https://github.com/sinatra/sinatra/releases) - [Changelog](https://github.com/sinatra/sinatra/blob/master/CHANGELOG.md) - [Commits](https://github.com/sinatra/sinatra/compare/v2.0.8...v2.0.8.1) Signed-off-by: dependabot-preview[bot] Co-authored-by: null <27856297+dependabot-preview[bot]@users.noreply.github.com> --- Gemfile | 2 +- Gemfile.lock | 8 ++++---- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/Gemfile b/Gemfile index 21a95182769..bd668c466be 100644 --- a/Gemfile +++ b/Gemfile @@ -18,7 +18,7 @@ group :jekyll_plugins do gem 'jekyll-commonmark', '1.3.1' end -gem 'sinatra', '2.0.8' +gem 'sinatra', '2.0.8.1' gem 'nokogiri', '1.10.7' # Windows and JRuby does not include zoneinfo files, so bundle the tzinfo-data gem diff --git a/Gemfile.lock b/Gemfile.lock index fb8e7fa3903..49dcc096717 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -80,7 +80,7 @@ GEM forwardable-extended (~> 2.6) public_suffix (4.0.1) rack (2.0.8) - rack-protection (2.0.8) + rack-protection (2.0.8.1) rack rake (13.0.1) rb-fsevent (0.10.3) @@ -98,10 +98,10 @@ GEM ffi (~> 1.9) sassc (2.2.1-x64-mingw32) ffi (~> 1.9) - sinatra (2.0.8) + sinatra (2.0.8.1) mustermann (~> 1.0) rack (~> 2.0) - rack-protection (= 2.0.8) + rack-protection (= 2.0.8.1) tilt (~> 2.0) stringex (2.8.5) terminal-table (1.8.0) @@ -128,7 +128,7 @@ DEPENDENCIES nokogiri (= 1.10.7) rake (= 13.0.1) sass-globbing (= 1.1.5) - sinatra (= 2.0.8) + sinatra (= 2.0.8.1) stringex (= 2.8.5) tzinfo (~> 2.0) tzinfo-data From ea749a53ba09c2576ff03987c5f521299392b655 Mon Sep 17 00:00:00 2001 From: Alexander Schneider Date: Thu, 2 Jan 2020 04:02:36 -0800 Subject: [PATCH 30/35] Update ZWave installation instructions (#11589) --- source/_docs/installation/freenas.markdown | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/source/_docs/installation/freenas.markdown b/source/_docs/installation/freenas.markdown index b95d8ed5e66..78945280e6b 100644 --- a/source/_docs/installation/freenas.markdown +++ b/source/_docs/installation/freenas.markdown @@ -184,12 +184,17 @@ pkg install libudev-devd Then you can install the zwave package ```bash -pip3 install homeassistant-pyozw==0.1.4 +su homeassistant +cd /usr/local/share/homeassistant +source ./bin/activate.csh +pip3 install homeassistant-pyozw==0.1.7 +deactivate +exit ``` Stop the hass Jail ```bash -sudo iocage stop hass +sudo iocage stop HomeAssistant ``` Edit the devfs rules on the Freenas Host @@ -213,12 +218,12 @@ Set it to 7 Start the hass jail ```bash -sudo iocage start hass +sudo iocage start HomeAssistant ``` Connect to the hass jail and verify that you see the modem devices ```bash -sudo iocage console hass +sudo iocage console HomeAssistant ``` ```bash From 58b4c774b4c37aa1a0da4749dfbbf4dc29f0f875 Mon Sep 17 00:00:00 2001 From: John Hollowell Date: Fri, 3 Jan 2020 05:00:38 -0500 Subject: [PATCH 31/35] Update stream.markdown (#11612) integration doesn't do any replacements in the filename, so removed ambiguous/incorrect section --- source/_integrations/stream.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/stream.markdown b/source/_integrations/stream.markdown index 3b581f5e48c..e98e8a42a6a 100644 --- a/source/_integrations/stream.markdown +++ b/source/_integrations/stream.markdown @@ -33,7 +33,7 @@ Both `duration` and `lookback` options are suggestions, but should be consistent | Service data attribute | Optional | Description | | ---------------------- | -------- | ----------- | | `stream_source` | no | The input source for the stream, e.g., `rtsp://my.stream.feed:554`. | -| `filename` | no | The file name string. Variable is `entity_id`, e.g., `/tmp/my_stream.mp4`. | +| `filename` | no | The file name string. e.g., `/tmp/my_stream.mp4`. | | `duration` | yes | Target recording length (in seconds). Default: 30 | | `lookback` | yes | Target lookback period (in seconds) to include in addition to duration. Only available if there is currently an active HLS stream for `stream_source`. Default: 0 | From 650b674c01f09f7e16609627ad4c8376d698575f Mon Sep 17 00:00:00 2001 From: Ronald Dehuysser Date: Fri, 3 Jan 2020 11:10:42 +0100 Subject: [PATCH 32/35] entity_id is not optional anymore - Media_player services (#11609) --- source/_integrations/media_player.markdown | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/source/_integrations/media_player.markdown b/source/_integrations/media_player.markdown index 3570768d7b1..43a14095c69 100644 --- a/source/_integrations/media_player.markdown +++ b/source/_integrations/media_player.markdown @@ -17,34 +17,34 @@ Available services: `turn_on`, `turn_off`, `toggle`, `volume_up`, `volume_down`, | Service data attribute | Optional | Description | | ---------------------- | -------- | ------------------------------------------------ | -| `entity_id` | yes | Target a specific media player. Defaults to all. | +| `entity_id` | no | Target a specific media player. To target all media players, use `all`. | #### Service `media_player.volume_mute` | Service data attribute | Optional | Description | |------------------------|----------|--------------------------------------------------| -| `entity_id` | yes | Target a specific media player. Defaults to all. | +| `entity_id` | no | Target a specific media player. To target all media players, use `all`. | | `is_volume_muted` | no | True/false for mute/unmute | #### Service `media_player.volume_set` | Service data attribute | Optional | Description | |------------------------|----------|--------------------------------------------------| -| `entity_id` | yes | Target a specific media player. Defaults to all. | +| `entity_id` | yes | Target a specific media player. To target all media players, use `all`. | | `volume_level` | no | Float for volume level. Range 0..1 | #### Service `media_player.media_seek` | Service data attribute | Optional | Description | |------------------------|----------|--------------------------------------------------------| -| `entity_id` | yes | Target a specific media player. Defaults to all. | +| `entity_id` | no | Target a specific media player. To target all media players, use `all`. | | `seek_position` | no | Position to seek to. The format is platform dependent. | #### Service `media_player.play_media` | Service data attribute | Optional | Description | | -----------------------| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `entity_id` | yes | Target a specific media player. Defaults to all. | +| `entity_id` | no | Target a specific media player. To target all media players, use `all`. | | `media_content_id` | no | A media identifier. The format of this is integration dependent. For example, you can provide URLs to Sonos and Cast but only a playlist ID to iTunes. | | `media_content_type` | no | A media type. Must be one of `music`, `tvshow`, `video`, `episode`, `channel` or `playlist`. For example, to play music you would set `media_content_type` to `music`. | @@ -52,7 +52,7 @@ Available services: `turn_on`, `turn_off`, `toggle`, `volume_up`, `volume_down`, | Service data attribute | Optional | Description | | ---------------------- | -------- | ---------------------------------------------------- | -| `entity_id` | yes | Target a specific media player. Defaults to all. | +| `entity_id` | no | Target a specific media player. To target all media players, use `all`. | | `source` | no | Name of the source to switch to. Platform dependent. | #### Service `media_player.select_sound_mode` From 1993bd4f0354f002e60f667315c2a5b70b1dfee6 Mon Sep 17 00:00:00 2001 From: mannte Date: Fri, 3 Jan 2020 11:13:02 +0100 Subject: [PATCH 33/35] Update google_assistant.markdown (#11600) --- source/_addons/google_assistant.markdown | 60 +++++++----------------- 1 file changed, 17 insertions(+), 43 deletions(-) diff --git a/source/_addons/google_assistant.markdown b/source/_addons/google_assistant.markdown index 7b6766f4a07..8af7a422b50 100644 --- a/source/_addons/google_assistant.markdown +++ b/source/_addons/google_assistant.markdown @@ -4,12 +4,6 @@ description: "Enhance your Hass.io installation with Google Assistant." featured: true --- -
- -These instructions are outdated - the add-on has been updated and these are no longer accurate or complete. - -
-
If you want to integrate your Google Home or mobile phone running Google Assistant, with Home Assistant, then you want the [Google Assistant component](/integrations/google_assistant/). @@ -23,36 +17,11 @@ To enable access to the Google Assistant API, do the following: 1. In the [Cloud Platform Console][project], go to the Projects page. Select an existing project or create a new project 1. Open the project. In the top of the page search for Google Assistant API or use [this link][API] and enable it. 1. Create an [OAuth Client ID][oauthclient], pick type "Other", click "Create" and download the JSON file by clicking the Download JSON button on the right side. +1. Upload your "google_assistant.json" file to the "hassio/share" folder, for example by using the [Samba] add-on. +1. In the config window, fill in your "project-id", which can be found in your "google_assistant.json" file or in on the [Cloud Platform Resource Manager][cloudConsole]. Also choose a "model_id". +1. Below the "Config" window select the microphone and speaker that you want to use. On a Raspberry Pi 3, card 0 - device 0 is the built-in headset port, card 0 - device 1 is the HDMI port. -Now install and activate the [Samba] add-on so you can upload your credential file. Connect to the "share" Samba share and copy your credentials over. Name the file `google_assistant.json`. - -Now it's time to start Google Assistant for the first time. When the Google Assistant add-on starts, it will output your audio devices in the "Logs" card. You might have to hit "refresh" to get the latest logs: - -```text -**** List of PLAYBACK Hardware Devices **** -card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA] - Subdevices: 8/8 - Subdevice #0: subdevice #0 - Subdevice #1: subdevice #1 - Subdevice #2: subdevice #2 - Subdevice #3: subdevice #3 - Subdevice #4: subdevice #4 - Subdevice #5: subdevice #5 - Subdevice #6: subdevice #6 - Subdevice #7: subdevice #7 -card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 ALSA [bcm2835 IEC958/HDMI] - Subdevices: 1/1 - Subdevice #0: subdevice #0 -card 1: Microphone [Yeti Stereo Microphone], device 0: USB Audio [USB Audio] - Subdevices: 1/1 - Subdevice #0: subdevice #0 -``` - -You need to use this information to point the add-on at the right speakers and microphone. The information describes different cards and devices. On a Raspberry Pi 3, card 0 - device 0 is the built-in headset port, card 0 - device 1 is the HDMI port. In the example above, the USB microphone showed up as card 1 - device 0. - -Find the microphone and speakers that you want to use and note down their device and card number. We will need that to configure the add-on options `mic` (microphone to use) and `speaker` (speaker to use). The format for these options is `,`. Change the configuration options and click save. - -The next step is to authenticate your Google account with Google Assistant. Start the add-on and click on the "OPEN WEB UI" button to start authentication. +You are now ready to start the add-on. The next step is to authenticate your Google account with Google Assistant. After starting the add-on and click on the "OPEN WEB UI" button to start authentication. ### Add-on configuration @@ -60,19 +29,23 @@ Configuration example that uses the USB microphone and the built-in headset audi ```json { - "mic": "1,0", - "speaker": "0,0", - "client_secrets": "google_assistant.json" + "client_secrets": "google_assistant.json", + "project_id": null, + "model_id": null } ``` {% configuration %} -mic: - description: This is the hardware address of your microphone. Look at the add-on output. +client_secrets: + description: The file downloaded from the Google Cloud Platform Console - Google Assistant API page. By default the add-on look in the "hassio/share" folder. required: true - type: float -speaker: - description: This is the hardware address of your speakers. Look at the add-on output. + type: string +project_id: + description: The project id can be found in your "google_assistant.json" file. + required: true + type: string +model_id: + description: A chosen model_id. required: true type: string {% endconfiguration %} @@ -88,3 +61,4 @@ Use the Home Assistant [DialogFlow component][comp] to integrate the add-on into [project]: https://console.cloud.google.com/project [API]: https://console.developers.google.com/apis/api/embeddedassistant.googleapis.com/overview [oauthclient]: https://console.developers.google.com/apis/credentials/oauthclient +[cloudConsole]: https://console.cloud.google.com/cloud-resource-manager From f5c2a557206029f630758592b3a18ae133e3a16d Mon Sep 17 00:00:00 2001 From: LWD Date: Fri, 3 Jan 2020 10:26:50 +0000 Subject: [PATCH 34/35] Update limitlessled.markdown (#11606) Removing link to MiLight.com. This site is no longer active. I've personally lost money from this site. There is a 94% bad rating on TrustPilot - https://uk.trustpilot.com/review/www.easybulb.com --- source/_integrations/limitlessled.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/limitlessled.markdown b/source/_integrations/limitlessled.markdown index b1e336b0146..e5594392c16 100644 --- a/source/_integrations/limitlessled.markdown +++ b/source/_integrations/limitlessled.markdown @@ -8,7 +8,7 @@ ha_iot_class: Assumed State ha_release: pre 0.7 --- -`limitlessled` can control your LimitlessLED lights from within Home Assistant. The lights are also known as EasyBulb, AppLight, AppLamp, [MiLight](https://www.milight.com/), LEDme, dekolight, or iLight. +`limitlessled` can control your LimitlessLED lights from within Home Assistant. The lights are also known as EasyBulb, AppLight, AppLamp, MiLight, LEDme, dekolight, or iLight. LimitlessLED bulbs are controlled via groups, so you can only control an individual bulb via the bridge if it is in a group by itself. From a607910d89433cfb38fae9b885b4de2549cb86f0 Mon Sep 17 00:00:00 2001 From: cogneato Date: Fri, 3 Jan 2020 03:27:41 -0700 Subject: [PATCH 35/35] Update to suggest Companion app (#11605) * Update to suggest Companion app Removed Owntracks suggestion for Android and point to HA Companion app for both iOS and Android * replace redirecting ios link replace /ios which was redirecting to companion.home-assistant.io * Remove owntracks video Remove video and add basic description of location setup for the Companion app * Update source/getting-started/presence-detection.markdown Co-Authored-By: Franck Nijhof * Update source/getting-started/presence-detection.markdown Co-Authored-By: Franck Nijhof Co-authored-by: Franck Nijhof --- source/getting-started/presence-detection.markdown | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/source/getting-started/presence-detection.markdown b/source/getting-started/presence-detection.markdown index 548b4090dc8..21eb5c2502c 100644 --- a/source/getting-started/presence-detection.markdown +++ b/source/getting-started/presence-detection.markdown @@ -17,11 +17,10 @@ Screenshot of Home Assistant showing a school, work and home zone and two people There are different ways of setting up presence detection. Usually the easiest way to detect presence is by checking which devices are connected to the network. You can do that if you have one of our [supported routers][routers]. By leveraging what your router already knows, you can easily detect if people are at home. -It's also possible to run an app on your phone to provide detailed location information to your Home Assistant instance. If you're on iOS we suggest to use the [Home Assistant iOS app](/ios/). For Android, we suggest [OwnTracks][ha-owntracks]. +It's also possible to run an app on your phone to provide detailed location information to your Home Assistant instance. For iOS and Android, we suggest using the [Home Assistant Companion app][companion]. + +During the setup of Home Assistant Companion on your mobile device, the app will ask for permission to allow the device's location to be provided to Home Assistant. Allowing this will create a `device_tracker` entity for that device which can be used in automations and conditions. -
- -
### Zones @@ -37,7 +36,6 @@ The map view will hide all devices that are home. [nmap]: /integrations/nmap_tracker [ha-bluetooth]: /integrations/bluetooth_tracker [ha-bluetooth-le]: /integrations/bluetooth_le_tracker -[ha-owntracks]: /integrations/owntracks/ [ha-locative]: /integrations/locative [ha-gpslogger]: /integrations/gpslogger [ha-presence]: /integrations/#presence-detection @@ -47,5 +45,6 @@ The map view will hide all devices that are home. [trigger]: /getting-started/automation-trigger/#zone-trigger [condition]: /getting-started/automation-condition/#zone-condition [ha-map]: /integrations/map/ +[companion]: https://companion.home-assistant.io/ ### [Next step: Join the Community »](/getting-started/join-the-community/)