From e49ea96b6693bfe7a47358be7d50011830b9414b Mon Sep 17 00:00:00 2001 From: Geert Date: Wed, 15 Jan 2020 22:57:41 +0100 Subject: [PATCH 01/33] Fixed sentence in acupsd.markdown (#11757) Removed unnecessary "is enabled" in line 13. Alternatively, replacing the "is enabled" by "and enabled" would also work. --- source/_integrations/apcupsd.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/apcupsd.markdown b/source/_integrations/apcupsd.markdown index 54f99a94435..b7572a5ec51 100644 --- a/source/_integrations/apcupsd.markdown +++ b/source/_integrations/apcupsd.markdown @@ -10,7 +10,7 @@ ha_release: 0.13 ha_iot_class: Local Polling --- -[APCUPSd](http://www.apcupsd.org/) status information can be integrated into Home Assistant when the Network Information Server (NIS) [is configured](http://www.apcupsd.org/manual/manual.html#nis-server-client-configuration-using-the-net-driver) is enabled on the APC device. +[APCUPSd](http://www.apcupsd.org/) status information can be integrated into Home Assistant when the Network Information Server (NIS) [is configured](http://www.apcupsd.org/manual/manual.html#nis-server-client-configuration-using-the-net-driver) on the APC device. There is currently support for the following device types within Home Assistant: From e77e5adeb7495b037c912bccffdfc9c0b4d7dd39 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Wed, 15 Jan 2020 15:22:53 -0800 Subject: [PATCH 02/33] Add link to Bas config --- source/_posts/2020-01-15-release-104.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_posts/2020-01-15-release-104.markdown b/source/_posts/2020-01-15-release-104.markdown index 1c1fb9b166a..b188867f84d 100644 --- a/source/_posts/2020-01-15-release-104.markdown +++ b/source/_posts/2020-01-15-release-104.markdown @@ -179,7 +179,7 @@ time for him to show off his Lovelace dashboard, featuring this lovely theme.
I keep seeing my own theme on Reddit, so now it's my turn! [OC] from r/homeassistant
-His theme is [publicly available on GitHub](https://github.com/basnijholt/lovelace-ios-dark-mode-theme/). +His theme is [publicly available on GitHub](https://github.com/basnijholt/lovelace-ios-dark-mode-theme/) and so is [his config](https://github.com/basnijholt/home-assistant-config). ## New Integrations From 5a2e3f539d40b8bfc11cffe20c3089ef49f71259 Mon Sep 17 00:00:00 2001 From: silfa718 Date: Thu, 16 Jan 2020 03:53:06 -0500 Subject: [PATCH 03/33] Update webostv.markdown (#11761) --- source/_integrations/webostv.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/webostv.markdown b/source/_integrations/webostv.markdown index 07862e807ae..f0c43aaf982 100644 --- a/source/_integrations/webostv.markdown +++ b/source/_integrations/webostv.markdown @@ -44,7 +44,7 @@ name: required: false type: string standby_connection: - description: Keep connection alive when TV is in standby (this should be set to try if and only if the "Standby+" option is enabled in the TV UI.) + description: Keep connection alive when TV is in standby (this should be set to true if and only if the "Standby+" option is enabled in the TV UI.) required: false type: boolean default: false From e30c46283f2a8b55c8e99023d44774f546083ec9 Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Thu, 16 Jan 2020 10:36:33 +0100 Subject: [PATCH 04/33] Remove legacy api_password occurances (#11763) --- source/_docs/configuration/yaml.markdown | 12 ++++++------ source/_docs/tools/credstash.markdown | 4 ++-- source/_integrations/http.markdown | 4 ---- 3 files changed, 8 insertions(+), 12 deletions(-) diff --git a/source/_docs/configuration/yaml.markdown b/source/_docs/configuration/yaml.markdown index 435e9f38fef..2290839f8fd 100644 --- a/source/_docs/configuration/yaml.markdown +++ b/source/_docs/configuration/yaml.markdown @@ -10,7 +10,6 @@ For integrations that you want to use in Home Assistant, you add code in your `c The following example entry assumes that you would like to set up the [notify component](/integrations/notify) with the [pushbullet platform](/integrations/pushbullet). - ```yaml notify: platform: pushbullet @@ -66,11 +65,12 @@ sensor: ## Including values ### Environmental variables + You can include values from your system's environment variables with `!env_var`. Note that this will only work in a scenario where it is possible to specify these. Hass.io users are recommended to use `!include` statements instead. ```yaml -http: - api_password: !env_var PASSWORD +example: + password: !env_var PASSWORD ``` #### Default value @@ -78,8 +78,8 @@ http: If an environment variable is not set, you can fallback to a default value. ```yaml -http: - api_password: !env_var PASSWORD default_password +example: + password: !env_var PASSWORD default_password ``` ### Including entire files @@ -102,7 +102,7 @@ If you see the following message: found character '\t' that cannot start any token ``` -This means that you've mistakenly entered a tab character, instead of spaces. +This means that you've mistakenly entered a tab character, instead of spaces. ### Upper and lower case diff --git a/source/_docs/tools/credstash.markdown b/source/_docs/tools/credstash.markdown index 8833cd09013..cede4f23e0c 100644 --- a/source/_docs/tools/credstash.markdown +++ b/source/_docs/tools/credstash.markdown @@ -14,8 +14,8 @@ $ hass --script credstash --help To store a password in credstash, replace your password or API key with `!secret` and an identifier in `configuration.yaml` file. ```yaml -http: - api_password: !secret http_password +example: + password: !secret example_password ``` Create an entry in your credstash store. diff --git a/source/_integrations/http.markdown b/source/_integrations/http.markdown index 55f4b1f0559..40f759fc2a4 100644 --- a/source/_integrations/http.markdown +++ b/source/_integrations/http.markdown @@ -32,10 +32,6 @@ http: ``` {% configuration %} -api_password: - description: "**Deprecated since 0.90 release. Configuration moved to [Legacy API password auth provider](/docs/authentication/providers/#legacy-api-password).** Protect the Home Assistant API with a password - this password can also be used to log in to the frontend. Where your client or other software supports it, you should use [long lasting access token](/docs/authentication/#your-account-profile) instead, as [shown in the REST API](https://developers.home-assistant.io/docs/en/external_api_rest.html) and [websocket API](https://developers.home-assistant.io/docs/en/external_api_websocket.html) documentation." - required: false - type: string server_host: description: "Only listen to incoming requests on specific IP/host. By default it will accept all IPv4 connections. Use `server_host: ::0` if you want to listen to (and only) IPv6." required: false From ee3ce9405a090f032f8bccf720795a5dedc875c9 Mon Sep 17 00:00:00 2001 From: Ian Richardson Date: Thu, 16 Jan 2020 11:17:16 -0600 Subject: [PATCH 05/33] =?UTF-8?q?=F0=9F=93=9D=20Update=20Lovelace=20change?= =?UTF-8?q?log=20for=200.104=20(#11772)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- source/lovelace/changelog.markdown | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/source/lovelace/changelog.markdown b/source/lovelace/changelog.markdown index a20db478d2e..1e455f522c5 100644 --- a/source/lovelace/changelog.markdown +++ b/source/lovelace/changelog.markdown @@ -2,6 +2,11 @@ title: "Lovelace Changelog" description: "Changelog of the Lovelace UI." --- +## Changes in 0.104.0 +- ❤️ Add ability to remove Lovelace config [#4430](https://github.com/home-assistant/home-assistant-polymer/pull/4430) @bramkragten +- ❤️ Add support to add all device entities to Lovelace [#4356](https://github.com/home-assistant/home-assistant-polymer/pull/4356) @bramkragten +- 📣 Upgrade MDI icons to 4.7.95 [#4341](https://github.com/home-assistant/home-assistant-polymer/pull/4341) @bonanitech + ## Changes in 0.101.0 - ❤️ [entities card]: Add actions on rows [#4023](https://github.com/home-assistant/home-assistant-polymer/pull/4023) @iantrich - ❤️ [entities card]: New `icon` option for title [#4024](https://github.com/home-assistant/home-assistant-polymer/pull/4024) @iantrich From 1e2586bd84c4355905a2723fef4adfbf86f9b72d Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Thu, 16 Jan 2020 11:28:45 -0800 Subject: [PATCH 06/33] Add Hue to breaking changes (#11773) * Add Hue to breaking changes * Update hue docs * Remove breaking change, will mark it deprecated in 104.1 * Hue breaking change * Reinstate formatting config --- source/_integrations/hue.markdown | 24 +++++++------------ source/_posts/2020-01-15-release-104.markdown | 6 +++-- 2 files changed, 12 insertions(+), 18 deletions(-) diff --git a/source/_integrations/hue.markdown b/source/_integrations/hue.markdown index 8a4274fe3b6..4e4c1e79415 100644 --- a/source/_integrations/hue.markdown +++ b/source/_integrations/hue.markdown @@ -7,11 +7,11 @@ ha_category: - Light ha_iot_class: Local Polling featured: true -ha_release: '0.60' +ha_release: "0.60" ha_config_flow: true ha_quality_scale: platinum ha_codeowners: - - '@balloob' + - "@balloob" --- Philips Hue support is integrated into Home Assistant as a hub that can drive the light and sensor platforms. The preferred way to set up the Philips Hue platform is by enabling the [discovery component](/integrations/discovery/). @@ -46,10 +46,6 @@ allow_unreachable: required: false type: boolean default: false -filename: - description: Make this unique if specifying multiple Hue bridges. - required: false - type: string allow_hue_groups: description: Disable this to stop Home Assistant from importing the groups defined on the Hue bridge. required: false @@ -70,18 +66,14 @@ hue: ### Multiple Hue bridges -Multiple Hue bridges work transparently with discovery, so you don't have to do anything special to set them up. If you prefer to configure them manually and use multiple Hue bridges, then you need to provide a configuration file for every bridge. The bridges can't share a single configuration file. - -Add `filename` to your Hue configuration entry in your `configuration.yaml` file: +Multiple Hue bridges work transparently with discovery, so you don't have to do anything special to set them up. ```yaml # Example configuration.yaml entry hue: bridges: - host: BRIDGE1_IP_ADDRESS - filename: phue.conf - host: BRIDGE2_IP_ADDRESS - filename: phue2.conf ``` ### Using Hue Groups in Home Assistant @@ -135,12 +127,12 @@ script: scene_name: "Porch Orange" ``` -| Service data attribute | Optional | Description | -| ---------------------- | -------- | ----------- | -| `group_name` | no | The group/room name of the lights. Find this in the official Hue app. -| `scene_name` | no | The name of the scene. Find this in the official Hue app. +| Service data attribute | Optional | Description | +| ---------------------- | -------- | --------------------------------------------------------------------- | +| `group_name` | no | The group/room name of the lights. Find this in the official Hue app. | +| `scene_name` | no | The name of the scene. Find this in the official Hue app. | -*Note*: `group_name` is not a reference to a Home Assistant group name. It can only be the name of a group/room in the Hue app. +_Note_: `group_name` is not a reference to a Home Assistant group name. It can only be the name of a group/room in the Hue app. ### Finding Group and Scene Names diff --git a/source/_posts/2020-01-15-release-104.markdown b/source/_posts/2020-01-15-release-104.markdown index b188867f84d..ae3eab6780b 100644 --- a/source/_posts/2020-01-15-release-104.markdown +++ b/source/_posts/2020-01-15-release-104.markdown @@ -235,6 +235,8 @@ Make sure to fill in all fields of the issue template, that is helping us a lot! ([@balloob] - [#23789]) ([automation docs]) ([calendar docs]) ([cover docs]) ([device_tracker docs]) ([fan docs]) ([light docs]) ([lock docs]) ([plant docs]) ([remember_the_milk docs]) ([remote docs]) ([script docs]) ([switch docs]) ([vacuum docs]). +- __Hue__ - Hue will no longer import existing authentication from disk. It has not written this authentication to disk since March 2018. The config option has been deprecated and will be removed in 0.106. ([@balloob] - [#30000]) ([hue docs]) + - __UPnP__ - UPnP/IGD units of measurement have been aligned with other integrations and common uses, they're now kB and kB/s instead of kbyte and kbyte/sec respectively. - ([@scop] - [#29552]) ([upnp docs]) - __Worx Landroid__ - The `worxlandroid` sensor has been changed to not return the hardcoded state values `manual-stop`, `charging`, `charging-complete`, `going-home`, `mowing`, instead use the states given from the Landroid to Home Assistant. @@ -242,7 +244,7 @@ Make sure to fill in all fields of the issue template, that is helping us a lot! This includes the state `idle`, which means that something is broken with the mower. You can use this as a notification to check the physical state of the mower. You need to update any automations that depend on the state of the sensor. - + ([@geraldhansen] - [#27453]) ([worxlandroid docs]) - __Apple iCloud__ - The iCloud component is no longer part of the device tracker platform and is now an integration, which is configurable via the UI. The iCloud cookie folder moved from `[HA_dir]/icloud` to `[HA_dir]/.storage/icloud`.- ([@Quentame] - [#28968]) ([icloud docs]) @@ -366,7 +368,7 @@ Make sure to fill in all fields of the issue template, that is helping us a lot! - __Binary Sensor (Locks)__ - Updated ON/OFF condition and triggers to match the documentation and UI. This change inverts the logic of automations relating to binary sensor with the `lock` device class, but only for automations triggering on the lock state (rather than triggering a lock/unlock action). If you already created automations, you will need to check those, as they probably need to be inverted. The text displayed in the trigger or condition dropdowns in Lovelace will now be correct. - + One possible scenario is if you have set an automation using the state of one lock to trigger an action on other lock(s). This change would cause the action to trigger on `locking` if it was previously triggering on `unlocking`. - ([@davet2001] - [#30663]) ([binary_sensor docs]) ## Beta Fixes From d53d59b7387e66518798cfa7083eb587bcd998f8 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Thu, 16 Jan 2020 12:48:25 -0800 Subject: [PATCH 07/33] 0.104.1 --- _config.yml | 4 +- source/_posts/2020-01-15-release-104.markdown | 43 +++++++++++++++++++ 2 files changed, 45 insertions(+), 2 deletions(-) diff --git a/_config.yml b/_config.yml index 126c3c527f7..9d8133312f8 100644 --- a/_config.yml +++ b/_config.yml @@ -101,8 +101,8 @@ social: # Home Assistant release details current_major_version: 0 current_minor_version: 104 -current_patch_version: 0 -date_released: 2020-01-15 +current_patch_version: 1 +date_released: 2020-01-16 # 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/2020-01-15-release-104.markdown b/source/_posts/2020-01-15-release-104.markdown index ae3eab6780b..fe5d4827d54 100644 --- a/source/_posts/2020-01-15-release-104.markdown +++ b/source/_posts/2020-01-15-release-104.markdown @@ -405,6 +405,49 @@ Make sure to fill in all fields of the issue template, that is helping us a lot! - Refactor Ring data handling ([@balloob] - [#30777]) ([ring docs]) (beta fix) - Restore unit_of_measurement from entity registry ([@Jc2k] - [#30780]) (beta fix) +## Release 0.104.1 - January 16 + +- 0.104.0 ([@frenck] - [#30803]) +- Update emulated_roku to 0.1.9 ([@jdeluyck] - [#30791]) ([emulated_roku docs]) +- update to aiopylgtv 0.2.7 ([@bendavid] - [#30797]) ([webostv docs]) +- Fix setup error of Mikrotik ([@springstan] - [#30810]) ([mikrotik docs]) +- Handle no host info in ignored config entries ([@balloob] - [#30822]) ([hue docs]) +- Fix mpd time issue ([@pvizeli] - [#30825]) ([mpd docs]) +- Fix play_media in webostv ([@bendavid] - [#30828]) ([webostv docs]) +- Fix iCloud when no family members (issue #30829) ([@Quentame] - [#30836]) ([icloud docs]) +- Reinstate and deprecate filename option for hue config ([@balloob] - [#30846]) ([hue docs]) +- Fixes issue about messages not being reset after sending it to microsoft teams. ([@peroyvind] - [#30849]) ([msteams docs]) +- Fix sensor type creation with multiple Ambient weather stations ([@bachya] - [#30850]) ([ambient_station docs]) + +[#30791]: https://github.com/home-assistant/home-assistant/pull/30791 +[#30797]: https://github.com/home-assistant/home-assistant/pull/30797 +[#30803]: https://github.com/home-assistant/home-assistant/pull/30803 +[#30810]: https://github.com/home-assistant/home-assistant/pull/30810 +[#30822]: https://github.com/home-assistant/home-assistant/pull/30822 +[#30825]: https://github.com/home-assistant/home-assistant/pull/30825 +[#30828]: https://github.com/home-assistant/home-assistant/pull/30828 +[#30836]: https://github.com/home-assistant/home-assistant/pull/30836 +[#30846]: https://github.com/home-assistant/home-assistant/pull/30846 +[#30849]: https://github.com/home-assistant/home-assistant/pull/30849 +[#30850]: https://github.com/home-assistant/home-assistant/pull/30850 +[@Quentame]: https://github.com/Quentame +[@bachya]: https://github.com/bachya +[@balloob]: https://github.com/balloob +[@bendavid]: https://github.com/bendavid +[@frenck]: https://github.com/frenck +[@jdeluyck]: https://github.com/jdeluyck +[@peroyvind]: https://github.com/peroyvind +[@pvizeli]: https://github.com/pvizeli +[@springstan]: https://github.com/springstan +[ambient_station docs]: /integrations/ambient_station/ +[emulated_roku docs]: /integrations/emulated_roku/ +[hue docs]: /integrations/hue/ +[icloud docs]: /integrations/icloud/ +[mikrotik docs]: /integrations/mikrotik/ +[mpd docs]: /integrations/mpd/ +[msteams docs]: /integrations/msteams/ +[webostv docs]: /integrations/webostv/ + ## All changes - Move imports to top for decora_wifi ([@springstan] - [#29439]) ([decora_wifi docs]) From 2bb2bd1065726e4a064d44ce505e6886fb8af7e7 Mon Sep 17 00:00:00 2001 From: 4lloyd <4lloyd@users.noreply.github.com> Date: Fri, 17 Jan 2020 11:44:27 +0100 Subject: [PATCH 08/33] Small typo in description Stookalert (#11783) Typo in description: a -> A --- source/_integrations/stookalert.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/stookalert.markdown b/source/_integrations/stookalert.markdown index 74f85fe668a..f08da8299b2 100644 --- a/source/_integrations/stookalert.markdown +++ b/source/_integrations/stookalert.markdown @@ -26,7 +26,7 @@ binary_sensor: {% configuration %} province: - description: a province to use for the binary sensor's state. Currently only provinces in the Netherlands are supported. Valid values are `Drenthe`, `Flevoland`, `Friesland`, `Gelderland`, `Groningen`, `Limburg`, `Noord-Brabant`, `Noord-Holland`, `Overijssel`, `Utrecht`, `Zeeland` or `Zuid-Holland`. + description: A province to use for the binary sensor's state. Currently only provinces in the Netherlands are supported. Valid values are `Drenthe`, `Flevoland`, `Friesland`, `Gelderland`, `Groningen`, `Limburg`, `Noord-Brabant`, `Noord-Holland`, `Overijssel`, `Utrecht`, `Zeeland` or `Zuid-Holland`. required: true type: string name: From 128de23ab116b933a32682e4f2631a9e30af489d Mon Sep 17 00:00:00 2001 From: mountainsandcode Date: Fri, 17 Jan 2020 12:18:34 +0100 Subject: [PATCH 09/33] Mention deconz breaking change in blog post for 0.104 (#11784) * Mention deconz breaking change in blog post for 0.104 * :pencil2: Tweak Co-authored-by: Franck Nijhof --- source/_posts/2020-01-15-release-104.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/_posts/2020-01-15-release-104.markdown b/source/_posts/2020-01-15-release-104.markdown index fe5d4827d54..9eb59faa0c0 100644 --- a/source/_posts/2020-01-15-release-104.markdown +++ b/source/_posts/2020-01-15-release-104.markdown @@ -237,6 +237,8 @@ Make sure to fill in all fields of the issue template, that is helping us a lot! - __Hue__ - Hue will no longer import existing authentication from disk. It has not written this authentication to disk since March 2018. The config option has been deprecated and will be removed in 0.106. ([@balloob] - [#30000]) ([hue docs]) +- __deCONZ__ - Due to changes to configuration handling, deCONZ groups will be assigned new identifiers in Home Assistant. As a result, deCONZ groups will be duplicated. Remove any group devices from the registry prior to upgrading or alternatively delete the obsolete entries after the upgrade to eliminate the duplicates. ([#30875]) ([deconz docs]) + - __UPnP__ - UPnP/IGD units of measurement have been aligned with other integrations and common uses, they're now kB and kB/s instead of kbyte and kbyte/sec respectively. - ([@scop] - [#29552]) ([upnp docs]) - __Worx Landroid__ - The `worxlandroid` sensor has been changed to not return the hardcoded state values `manual-stop`, `charging`, `charging-complete`, `going-home`, `mowing`, instead use the states given from the Landroid to Home Assistant. From 8a92d97914b3e8a1fe42f4d2f7eb247e2e982ea6 Mon Sep 17 00:00:00 2001 From: Dominik Moritz Date: Fri, 17 Jan 2020 03:26:03 -0800 Subject: [PATCH 10/33] Fix spelling of iOS (#11781) --- source/_integrations/signal_messenger.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/signal_messenger.markdown b/source/_integrations/signal_messenger.markdown index 6376857d6af..211231d2e0c 100644 --- a/source/_integrations/signal_messenger.markdown +++ b/source/_integrations/signal_messenger.markdown @@ -9,7 +9,7 @@ ha_codeowners: - '@bbernhard' --- -The `signal_messenger` integration uses the [Signal Messenger REST API](https://github.com/bbernhard/signal-cli-rest-api) to deliver notifications from Home Assistant to your Android or iOs device. +The `signal_messenger` integration uses the [Signal Messenger REST API](https://github.com/bbernhard/signal-cli-rest-api) to deliver notifications from Home Assistant to your Android or iOS device. ## Setup From 84c7fe33d408a4c51332a7f8de02a2e81d27971b Mon Sep 17 00:00:00 2001 From: nuhi <34368632+noohi@users.noreply.github.com> Date: Fri, 17 Jan 2020 18:48:24 +0100 Subject: [PATCH 11/33] Update kef.markdown (#11786) Just a minor change to reflect the platform position in the configuration file (media_player) and LSX was successfully tested, have 2 pairs here, let me know if you need more specific tests. Thanks anyway. --- source/_integrations/kef.markdown | 25 ++++++++++++++----------- 1 file changed, 14 insertions(+), 11 deletions(-) diff --git a/source/_integrations/kef.markdown b/source/_integrations/kef.markdown index 6700b4614da..3e200e6b087 100644 --- a/source/_integrations/kef.markdown +++ b/source/_integrations/kef.markdown @@ -15,7 +15,7 @@ The `kef` platform allows you to control the [KEF LS50 Wireless](https://interna Supported devices: - KEF LS50 Wireless -- KEF LSX (untested) +- KEF LSX To add KEF Speakers to your installation, add the following to your `configuration.yaml` file: @@ -23,9 +23,10 @@ To add KEF Speakers to your installation, add the following to your `configurati ```yaml # Example configuration.yaml entry -- platform: kef - host: IP_ADDRESS - type: LS50 +media_player: + - platform: kef + host: IP_ADDRESS + type: LS50 ``` {% configuration %} @@ -72,16 +73,18 @@ standby_time: ```yaml # Example configuration.yaml entry -- platform: kef - host: IP_ADDRESS - type: LS50 - name: My KEF speakers - maximum_volume: 0.6 - volume_step: 0.05 +media_player: + - platform: kef + host: IP_ADDRESS + type: LS50 + name: My KEF speakers + maximum_volume: 0.6 + volume_step: 0.05 ``` Notes: -- The LS50 Wireless is tested with the latest firmware of 19-11-2019: `p6.3001902221.105039422` and older firmware: `p6.2101809171.105039422` +- The LS50 Wireless was tested with the latest firmware of 19-11-2019: `p6.3001902221.105039422` and older firmware: `p6.2101809171.105039422` +- The LSX Wireless was tested with the latest firmware of 10-10-2019 v4.1: `p20.4101909240.105243` [KEF Speakers]: /integrations/kef/ From de55bfa47742a5d40351606868fcc5dc3a0aac4d Mon Sep 17 00:00:00 2001 From: Othou Date: Fri, 17 Jan 2020 19:49:31 +0200 Subject: [PATCH 12/33] Update signal_messenger.markdown (#11788) Configuration entry must have quotation marks around phone numbers. e.g. "+123456789" --- source/_integrations/signal_messenger.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_integrations/signal_messenger.markdown b/source/_integrations/signal_messenger.markdown index 211231d2e0c..ea581dd5e69 100644 --- a/source/_integrations/signal_messenger.markdown +++ b/source/_integrations/signal_messenger.markdown @@ -32,9 +32,9 @@ notify: - name: signal platform: signal_messenger url: "http://127.0.0.1:8080" # the URL where the Signal Messenger REST API is listening - number: YOUR_PHONE_NUMBER # the sender number + number: "YOUR_PHONE_NUMBER" # the sender number recipients: # one or more recipients - - RECIPIENT1 + - "RECIPIENT1" ``` {% configuration %} From 90f2d0e19b13236ceef6b03b47c2a0d76444f8b6 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Fri, 17 Jan 2020 16:27:54 -0800 Subject: [PATCH 13/33] 104.2 --- _config.yml | 4 +-- source/_posts/2020-01-15-release-104.markdown | 36 +++++++++++++++++++ 2 files changed, 38 insertions(+), 2 deletions(-) diff --git a/_config.yml b/_config.yml index 9d8133312f8..11a12b7952f 100644 --- a/_config.yml +++ b/_config.yml @@ -101,8 +101,8 @@ social: # Home Assistant release details current_major_version: 0 current_minor_version: 104 -current_patch_version: 1 -date_released: 2020-01-16 +current_patch_version: 2 +date_released: 2020-01-17 # 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/2020-01-15-release-104.markdown b/source/_posts/2020-01-15-release-104.markdown index 9eb59faa0c0..b91f402957f 100644 --- a/source/_posts/2020-01-15-release-104.markdown +++ b/source/_posts/2020-01-15-release-104.markdown @@ -450,6 +450,42 @@ Make sure to fill in all fields of the issue template, that is helping us a lot! [msteams docs]: /integrations/msteams/ [webostv docs]: /integrations/webostv/ +## Release 0.104.2 - January 17 + +- 0.104.0 ([@frenck] - [#30803]) +- add multistate back ([@dmulcahey] - [#30889]) ([zha docs]) +- Fix missing switch groups of HomematicIP Cloud ([@SukramJ] - [#30903]) ([homematicip_cloud docs]) +- Fix issue with group unique id when normalising bridge id ([@Kane610] - [#30904]) ([deconz docs]) +- Fix Alexa semantics for covers with tilt support. ([@ochlocracy] - [#30911]) ([alexa docs]) +- camera endpoint likes to timeout, catch it. ([@balloob] - [#30919]) ([ring docs]) +- Fix service device refresh calling state update ([@Kane610] - [#30920]) ([deconz docs]) +- Updated frontend to 20200108.2 ([@bramkragten] - [#30921]) ([frontend docs]) +- Fix hue accepting filename ([@balloob] - [#30924]) ([hue docs]) + +[#30803]: https://github.com/home-assistant/home-assistant/pull/30803 +[#30889]: https://github.com/home-assistant/home-assistant/pull/30889 +[#30903]: https://github.com/home-assistant/home-assistant/pull/30903 +[#30904]: https://github.com/home-assistant/home-assistant/pull/30904 +[#30911]: https://github.com/home-assistant/home-assistant/pull/30911 +[#30919]: https://github.com/home-assistant/home-assistant/pull/30919 +[#30920]: https://github.com/home-assistant/home-assistant/pull/30920 +[#30921]: https://github.com/home-assistant/home-assistant/pull/30921 +[#30924]: https://github.com/home-assistant/home-assistant/pull/30924 +[@Kane610]: https://github.com/Kane610 +[@SukramJ]: https://github.com/SukramJ +[@balloob]: https://github.com/balloob +[@bramkragten]: https://github.com/bramkragten +[@dmulcahey]: https://github.com/dmulcahey +[@frenck]: https://github.com/frenck +[@ochlocracy]: https://github.com/ochlocracy +[alexa docs]: /integrations/alexa/ +[deconz docs]: /integrations/deconz/ +[frontend docs]: /integrations/frontend/ +[homematicip_cloud docs]: /integrations/homematicip_cloud/ +[hue docs]: /integrations/hue/ +[ring docs]: /integrations/ring/ +[zha docs]: /integrations/zha/ + ## All changes - Move imports to top for decora_wifi ([@springstan] - [#29439]) ([decora_wifi docs]) From 67d8c8da27fe63580a7882743d83200d1f022093 Mon Sep 17 00:00:00 2001 From: Aaron Godfrey Date: Sat, 18 Jan 2020 04:08:18 -0800 Subject: [PATCH 14/33] Updates vacuum.xioami_miio docs (#11795) Also added an example on how to reset the counter for consumables (filter, brushes and sensors). --- .../_integrations/vacuum.xiaomi_miio.markdown | 57 ++++++++++++++----- 1 file changed, 44 insertions(+), 13 deletions(-) diff --git a/source/_integrations/vacuum.xiaomi_miio.markdown b/source/_integrations/vacuum.xiaomi_miio.markdown index 8a4f3ecc9d9..cb87f950b2d 100644 --- a/source/_integrations/vacuum.xiaomi_miio.markdown +++ b/source/_integrations/vacuum.xiaomi_miio.markdown @@ -189,23 +189,29 @@ In addition to [all of the attributes provided by the `vacuum` component](/integ - `main_brush_left` - `side_brush_left` - `filter_left` +- `sensor_dirty_left` - `cleaning_count` - `total_cleaned_area` - `total_cleaning_time` +- `clean_start` +- `clean_end` The following table shows the units of measurement for each attribute: -| Attribute | Unit of measurement | Description | -|---------------------------|---------------------|-------------------------------------------------------| -| `do_not_disturb` | | DND mode on / off | -| `cleaning_time` | minutes | Last / actual cleaning time in minutes | -| `cleaned_area` | square meter | Last / actual cleaned area in square meters | -| `main_brush_left` | hours | Hours left until a change of the main brush is needed | -| `side_brush_left` | hours | Hours left until a change of the side brush is needed | -| `filter_left` | hours | Hours left until a change of the filter is needed | -| `cleaning_count` | | Number of total cleaning cycles | -| `total_cleaned_area` | square meter | Total cleaned area in square meters | -| `total_cleaning_time` | minutes | Total cleaning time in minutes | +| Attribute | Unit of measurement | Description | +|---------------------------|---------------------|----------------------------------------------------------------| +| `do_not_disturb` | | DND mode on / off | +| `cleaning_time` | minutes | Last / actual cleaning time in minutes | +| `cleaned_area` | square meter | Last / actual cleaned area in square meters | +| `main_brush_left` | hours | Hours left until a change of the main brush is needed | +| `side_brush_left` | hours | Hours left until a change of the side brush is needed | +| `filter_left` | hours | Hours left until a change of the filter is needed | +| `sensor_dirty_left` | hours | Hours left until the wall and cliff sensors should be cleaned | +| `cleaning_count` | | Number of total cleaning cycles | +| `total_cleaned_area` | square meter | Total cleaned area in square meters | +| `total_cleaning_time` | minutes | Total cleaning time in minutes | +| `clean_start` | datetime | The last date/time the vacuum started cleaning (offset naive) | +| `clean_end` | datetime | The last date/time the vacuum finished cleaning (offset naive) | ## Retrieving the Access Token @@ -224,7 +230,7 @@ This token (32 hexadecimal characters) is required for the Xiaomi Mi Robot Vacuu ### Android (not rooted) -> If using an Android device to retrieve the Access Token only `v5.4.49` of Mi Home is confirmed working (December 2019). +> If using an Android device to retrieve the Access Token only `v5.4.49` of Mi Home is confirmed working (December 2019). 1. To begin, set up your Robovac with the latest version of Mi Home on your primary Android device as you normally would. 2. Using `v5.4.49` of Mi Home locate a text file under the `Smarthome/logs` folder where the 32 character token is stored. @@ -333,12 +339,37 @@ vacuum_kitchen: Where params specify room numbers, for multiple rooms, params can be specified like `[17,18]`. -Valid room numbers can be retrieved using miio command-line tool. It will only give room numbers and not the room names. To get the room names, one can just test the app_segment_clean command and see which room it cleans. +Valid room numbers can be retrieved using miio command-line tool. It will only give room numbers and not the room names. To get the room names, one can just test the app_segment_clean command and see which room it cleans. ```bash miio protocol call get_room_mapping ``` +## Example on how to reset maintenance hours (brushes, filter, sensors) + +The vacuum entity stores attribute values for when brushes, filters and sensors need to be +cleaned or replaced (`main_brush_left`, `side_brush_left`, `filter_left` and +`sensor_dirty_left`). The values are measured in hours. Once the parts are cleaned +or replaced you can then reset those values on the vacuum. Here is an example script using +[`vacuum.send_command`](/integrations/vacuum/) to reset the hours for the main brush: + +```yaml +reset_main_brush_left: + alias: "Reset hours for main brush replacement" + sequence: + - service: vacuum.send_Command + data: + entity_id: vacuum.xiaomi_vacuum_cleaner + command: reset_consumable + params: ['main_brush_work_time'] +``` + +Allowed `params` for the `reset_consumable` command: +* `['main_brush_work_time']` +* `['side_brush_work_time']` +* `['filter_work_time']` +* `['sensor_dirty_time']` + ## Retrieving Zoned Cleaning Coordinates ### Using FloleVac (Android) From 9834a94c1c8c5d82555c3c560d7016d191290e09 Mon Sep 17 00:00:00 2001 From: Allan Persson <46043392+allanpersson@users.noreply.github.com> Date: Sat, 18 Jan 2020 13:21:10 +0100 Subject: [PATCH 15/33] Added how to get DSN to documentation (#11797) --- source/_integrations/sentry.markdown | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/source/_integrations/sentry.markdown b/source/_integrations/sentry.markdown index 9fdfba3307c..75e781f2009 100644 --- a/source/_integrations/sentry.markdown +++ b/source/_integrations/sentry.markdown @@ -33,3 +33,12 @@ environment: required: false type: string {% endconfiguration %} + +### Getting the DSN + +Follow these steps to get the DSN: +- Go to **Projects**. +- Click **Create project**. +- Fill out **Give your project a name** and **choose Assign a Team** fields and click Create project button. +- Click **Get your DSN** link in top of the page. +- Your DSN is now visable and looks like https://sdasdasdasdsadsadas@sentry.io/sdsdfsdf From 665c66ec69dc38cac8d0382ce7c6e979e11ae162 Mon Sep 17 00:00:00 2001 From: Geoff Davis Date: Sat, 18 Jan 2020 04:22:51 -0800 Subject: [PATCH 16/33] Update browser list with webos failure (#11794) --- source/_docs/frontend/browsers.markdown | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/source/_docs/frontend/browsers.markdown b/source/_docs/frontend/browsers.markdown index 36261fcbb09..c5fac552d01 100644 --- a/source/_docs/frontend/browsers.markdown +++ b/source/_docs/frontend/browsers.markdown @@ -64,11 +64,17 @@ We would appreciate if you help to keep this page up-to-date and add feedback. There are reports that devices running with iOS prior to iOS 10, especially old iPads, are having trouble. +## webOS + +| Browser | Release | State | Comments | +| :-------------------- |:---------------|:-----------|:-------------------------| +| [LG webOS TV Built-in]| 2019-2020 | fails | loads empty page | + [Chrome]: https://www.google.com/chrome/ [Chromium]: https://www.chromium.org/ [Conkeror]: http://conkeror.org/ [Edge]: https://www.microsoft.com/en-us/windows/microsoft-edge -[elinks]: http://elinks.or.cz/ +[elinks]: http://elinks.or.cz/ [Epiphany]: https://wiki.gnome.org/Apps/Web [Firefox]: https://www.mozilla.org/en-US/firefox/ [IE]: https://support.microsoft.com/en-us/help/17621/internet-explorer-downloads @@ -83,3 +89,4 @@ There are reports that devices running with iOS prior to iOS 10, especially old [Uzbl]: https://www.uzbl.org/ [w3m]: http://w3m.sourceforge.net/ [Waterfox]: https://www.waterfoxproject.org +[LG webOS TV Built-In]: https://www.lg.com/uk/support/solutions/tv/smart-tv/internet-browsing From bcb54e26bd7419c4dad4f88b4f489f676ddc42bb Mon Sep 17 00:00:00 2001 From: Alexandre Leites <1256013+xalexslx@users.noreply.github.com> Date: Sat, 18 Jan 2020 09:24:05 -0300 Subject: [PATCH 17/33] Update discovery page to add IOT Link (#11793) --- source/_docs/mqtt/discovery.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_docs/mqtt/discovery.markdown b/source/_docs/mqtt/discovery.markdown index cbde6f94195..feab0e06175 100644 --- a/source/_docs/mqtt/discovery.markdown +++ b/source/_docs/mqtt/discovery.markdown @@ -233,6 +233,7 @@ The following software has built-in support for MQTT discovery: - [room-assistant](https://github.com/mKeRix/room-assistant) (starting with 1.1.0) - [Zigbee2mqtt](https://github.com/koenkk/zigbee2mqtt) - [Zwave2Mqtt](https://github.com/OpenZWave/Zwave2Mqtt) (starting with 2.0.1) +- [IOTLink](https://iotlink.gitlab.io) (starting with 2.0.0) ### Examples From c4e7c03587ea4c0353a64bb15191208a6cb66d64 Mon Sep 17 00:00:00 2001 From: Daniel Shokouhi Date: Sat, 18 Jan 2020 04:40:54 -0800 Subject: [PATCH 18/33] Add breaking change for google assistant (#11777) * Add breaking change for google assistant * Move the links * Review comments --- source/_posts/2020-01-15-release-104.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/_posts/2020-01-15-release-104.markdown b/source/_posts/2020-01-15-release-104.markdown index b91f402957f..efdb991faac 100644 --- a/source/_posts/2020-01-15-release-104.markdown +++ b/source/_posts/2020-01-15-release-104.markdown @@ -373,6 +373,8 @@ Make sure to fill in all fields of the issue template, that is helping us a lot! One possible scenario is if you have set an automation using the state of one lock to trigger an action on other lock(s). This change would cause the action to trigger on `locking` if it was previously triggering on `unlocking`. - ([@davet2001] - [#30663]) ([binary_sensor docs]) +- __Google Assistant__ - The `api_key` for manual installs is now deprecated and will be removed in 0.105. To correct this you will need to remove `api_key` from the `configuration.yaml` and switch to using `service_account` instead. - ([@elupus] - [#30402]) ([google_assistant docs]) + ## Beta Fixes - Fix upnp raw sensor state formatting when None ([@pnbruckner] - [#30444]) ([upnp docs]) (beta fix) From de0501cf3828e64a0c5ebd0527fc519d336a0f41 Mon Sep 17 00:00:00 2001 From: Ken Davidson Date: Sat, 18 Jan 2020 07:45:22 -0500 Subject: [PATCH 19/33] Wording tweaks (#11775) --- source/_integrations/alexa.markdown | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/source/_integrations/alexa.markdown b/source/_integrations/alexa.markdown index e293f349124..a01cd306120 100644 --- a/source/_integrations/alexa.markdown +++ b/source/_integrations/alexa.markdown @@ -13,7 +13,7 @@ ha_codeowners: ## 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. +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/). @@ -21,19 +21,19 @@ For Home Assistant Cloud Users, documentation can be found [here](https://www.na There are a few ways that you can use Amazon Alexa and Home Assistant together. -- [Build custom commands to use](/integrations/alexa.intent/) +- [Build custom commands](/integrations/alexa.intent/) - [Create a new Flash Briefing source](/integrations/alexa.flash_briefings/) -- [Use the Smart Home API to control lights, etc](/integrations/alexa.smart_home/) -- Alternative: use the [Emulated Hue integration][emulated-hue-component] to trick Alexa to thinking Home Assistant is a Philips Hue hub. +- [Use the Smart Home API to control lights, etc.](/integrations/alexa.smart_home/) +- Alternative: use the [Emulated Hue integration][emulated-hue-component] to trick Alexa into thinking Home Assistant is a Philips Hue hub. ### Requirements -Manual setup the integration with Amazon Alexa needs several requirements +Manual setup of the integration with Amazon Alexa has several requirements: - Amazon Developer Account. You can sign up [here][amazon-dev-console]. -- Building custom commands and Flash Briefing requires your Home Assistant instance to be accessible from the Internet with HTTPS on port 443. -- An [AWS account](https://aws.amazon.com/free/) is needed if you want to use the Smart Home Skill API. A part of your Smart Home Skill will be hosted on [AWS Lambda](https://aws.amazon.com/lambda/pricing/). However, you don't need to worry about costs, AWS Lambda allows free to use up to 1 million requests and 1GB outbound data transfer per month. -- Smart Home API also needs your Home Assistant instance accessible from the Internet. +- Building custom commands and Flash Briefing require your Home Assistant instance to be accessible from the Internet with HTTPS on port 443. +- An [AWS account](https://aws.amazon.com/free/) is needed if you want to use the Smart Home Skill API. A part of your Smart Home Skill will be hosted on [AWS Lambda](https://aws.amazon.com/lambda/pricing/). However, you don't need to worry about costs; AWS Lambda is free for up to 1 million requests and 1GB of outbound data transfer per month. +- Smart Home API also needs your Home Assistant instance to be accessible from the Internet. [amazon-dev-console]: https://developer.amazon.com [emulated-hue-component]: /integrations/emulated_hue/ From 0606595f91492a46c805c3ec6dab8c6e4a56c1ad Mon Sep 17 00:00:00 2001 From: Roelof Schuiling Date: Sat, 18 Jan 2020 21:49:30 +0100 Subject: [PATCH 20/33] Fixed header styling (#11801) This improves readability --- 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 875a00463e5..60281c21b63 100644 --- a/source/_docs/z-wave/installation.markdown +++ b/source/_docs/z-wave/installation.markdown @@ -215,7 +215,7 @@ 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. -## Random unreachable Z-Wave nodes: ModemManager interference +### Random unreachable Z-Wave nodes: ModemManager interference 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. From 310adf43577be8e16e14d90d181a0fe478dd1b3e Mon Sep 17 00:00:00 2001 From: Daniel Shokouhi Date: Sat, 18 Jan 2020 15:05:31 -0800 Subject: [PATCH 21/33] Add notes about deprecated api_key (#11778) * Add notes about deprecated api_key * Review comments --- source/_integrations/google_assistant.markdown | 13 +++++-------- 1 file changed, 5 insertions(+), 8 deletions(-) diff --git a/source/_integrations/google_assistant.markdown b/source/_integrations/google_assistant.markdown index 458c0b49351..f2965b3ca34 100644 --- a/source/_integrations/google_assistant.markdown +++ b/source/_integrations/google_assistant.markdown @@ -28,7 +28,7 @@ To use Google Assistant, your Home Assistant configuration has to be [externally -You need to create an API Key with the [Google Cloud API Console](https://console.cloud.google.com/apis/api/homegraph.googleapis.com/overview) which allows you to update devices without unlinking and relinking an account (see [below](#troubleshooting-the-request_sync-service)). If you don't provide one, the `google_assistant.request_sync` service is not exposed. It is recommended to set up this configuration key as it also allows the usage of the following command, "Ok Google, sync my devices". Once you have set up this component, you will need to call this service (or command) each time you add a new device in Home Assistant that you wish to control via the Google Assistant integration. +You will need to create a service account [Create Service account key](https://console.cloud.google.com/apis/credentials/serviceaccountkey) which allows you to update devices without unlinking and relinking an account (see [below](#troubleshooting-the-request_sync-service)). If you don't provide the service account, the `google_assistant.request_sync` service is not exposed. It is recommended to set up this configuration key as it also allows the usage of the following command, "Ok Google, sync my devices". Once you have set up this component, you will need to call this service (or command) each time you add a new device in Home Assistant that you wish to control via the Google Assistant integration. See Step 2 after the note for more details. 1. Create a new project in the [Actions on Google console](https://console.actions.google.com/). 1. Add/Import a project and give it a name. @@ -75,11 +75,9 @@ If you've added Home Assistant to your phone's home screen, you have to first re 6. For the Key type, select the JSON option. 7. Click Create. A JSON file that contains your key downloads to your computer. 8. Use the information in this file or the file directly to add to the `service_account` key in the configuration. -3. If you didn't specify a service account and want to use the `google_assistant.request_sync` service, to update devices without unlinking and relinking, in Home Assistant, then enable HomeGraph API for your project: - 1. Go to the [Google API Console](https://console.cloud.google.com/apis/api/homegraph.googleapis.com/overview). - 2. Select your project and click Enable HomeGraph API. - 3. Go to Credentials, which you can find on the left navigation bar under the key icon, and select API Key from Create Credentials. - 4. Note down the generated API Key and use this in the configuration. + 9. Go to the [Google API Console](https://console.cloud.google.com/apis/api/homegraph.googleapis.com/overview). + 10. Select your project and click Enable HomeGraph API. + ### Configuration @@ -89,7 +87,6 @@ Now add your setup to your `configuration.yaml` file, such as: # Example configuration.yaml entry google_assistant: project_id: YOUR_PROJECT_ID - api_key: YOUR_API_KEY service_account: !include SERVICE_ACCOUNT.JSON report_state: true exposed_domains: @@ -117,7 +114,7 @@ secure_devices_pin: type: string default: "" api_key: - description: Your HomeGraph API key (for the `google_assistant.request_sync` service). This is not required if a service_account is specified. + description: Your HomeGraph API key (for the `google_assistant.request_sync` service). This is not required if a service_account is specified. This has been deprecated and will be removed in 0.105, you must setup a `service_account` now. required: false type: string service_account: From 436675ce03228b3c1bd2aa20b707fadf5e0e9f1e Mon Sep 17 00:00:00 2001 From: Alex Cragg Date: Sun, 19 Jan 2020 14:37:46 +0000 Subject: [PATCH 22/33] Add TP-Link HS303 to supported devices (#11805) Update list of supported devices to include 'HS303 (powerstrip 3-outlet)'. I've confirmed this is working. --- source/_integrations/tplink.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_integrations/tplink.markdown b/source/_integrations/tplink.markdown index 3b5fd130f95..a4ab48dd27f 100644 --- a/source/_integrations/tplink.markdown +++ b/source/_integrations/tplink.markdown @@ -39,6 +39,7 @@ The following devices are known to work with this component. - HS107 (indoor 2-outlet) - HS300 (powerstrip 6-outlet) +- HS303 (powerstrip 3-outlet) - KP400 (outdoor 2-outlet) - KP200 (indoor 2-outlet) From a775092a3c93539580f008cc53b1a4b4030b998f Mon Sep 17 00:00:00 2001 From: Teppo Rekola Date: Mon, 20 Jan 2020 10:27:34 +0200 Subject: [PATCH 23/33] Update philips_js.markdown (#11806) * Update philips_js.markdown note that not all listed jointspace-devices wont have json-api * Minor changes Co-authored-by: Fabian Affolter --- source/_integrations/philips_js.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/philips_js.markdown b/source/_integrations/philips_js.markdown index a32946bd45a..de761e932fb 100644 --- a/source/_integrations/philips_js.markdown +++ b/source/_integrations/philips_js.markdown @@ -10,7 +10,7 @@ ha_codeowners: - '@elupus' --- -The `philips_js` platform allows you to control Philips TVs which expose the [jointSPACE](http://jointspace.sourceforge.net/) API. Instructions on how to activate the API and if your model is supported can be found [here](http://jointspace.sourceforge.net/download.html). +The `philips_js` platform allows you to control Philips TVs which expose the [jointSPACE](http://jointspace.sourceforge.net/) JSON-API. Instructions on how to activate the API and if your model is supported can be found [here](http://jointspace.sourceforge.net/download.html). Note that not all listed, jointSPACE-enabled devices won't have JSON-interface running on port 1925. This is true at least for some models before year 2011. To add your TV to your installation, add the following to your `configuration.yaml` file: From f40f7c4d8db0260c7f7be505094133ecda6e78b4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fr=C3=A9d=C3=A9ric=20Sagnes?= Date: Mon, 20 Jan 2020 01:12:36 -0800 Subject: [PATCH 24/33] Prevent failure when reloading fail2ban (#11814) fail2ban complains about a double `bantime` directive when reloading the service, suggest people change the value later rather than include two statements in the configuration file --- source/_cookbook/fail2ban.markdown | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/source/_cookbook/fail2ban.markdown b/source/_cookbook/fail2ban.markdown index 9f698f8aaa8..7b09d9b4ee1 100644 --- a/source/_cookbook/fail2ban.markdown +++ b/source/_cookbook/fail2ban.markdown @@ -87,8 +87,7 @@ filter = ha logpath = /home/homeassistant/.homeassistant/home-assistant.log # 3600 seconds = 1 hour -bantime = 3600 -bantime = 30 # during testing it is useful to have a short ban interval, comment out this line later +bantime = 30 # during testing it is useful to have a short ban interval, change this to 3600 later # Maximum amount of login attempts before IP is blocked maxretry = 3 From bc5c88e5347466437a073e41e81287d22a6c62c0 Mon Sep 17 00:00:00 2001 From: Fredrik Erlandsson Date: Mon, 20 Jan 2020 10:29:43 +0100 Subject: [PATCH 25/33] Daikin Auto is called heat_cold (#11803) --- source/_integrations/daikin.markdown | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/source/_integrations/daikin.markdown b/source/_integrations/daikin.markdown index aa70c271d66..5516f98fbbf 100644 --- a/source/_integrations/daikin.markdown +++ b/source/_integrations/daikin.markdown @@ -56,12 +56,12 @@ hosts: The `daikin` climate platform integrates Daikin air conditioning systems into Home Assistant, enabling control of setting the following parameters: -- [**set_hvac_mode**](/integrations/climate/#service-climateset_hvac_mode) (off, heat, cool, auto, or fan only) -- [**target temperature**](https://www.home-assistant.io/integrations/climate#service-climateset_temperature) -- [**turn on/off**](https://www.home-assistant.io/integrations/climate#service-climateturn_on) -- [**fan mode**](https://www.home-assistant.io/integrations/climate#service-climateset_fan_mode) (speed) -- [**swing mode**](https://www.home-assistant.io/integrations/climate#service-climateset_swing_mode) -- [**set_preset_mode**](https://www.home-assistant.io/integrations/climate#service-climateset_preset_mode) (away, none) +- [**set_hvac_mode**](/integrations/climate/#service-climateset_hvac_mode) (`off`, `heat`, `cool`, `heat_cool`, or `fan_only`) +- [**target temperature**](/integrations/climate#service-climateset_temperature) +- [**turn on/off**](/integrations/climate#service-climateturn_on) +- [**fan mode**](/integrations/climate#service-climateset_fan_mode) (speed) +- [**swing mode**](/integrations/climate#service-climateset_swing_mode) +- [**set_preset_mode**](/integrations/climate#service-climateset_preset_mode) (away, none) Current inside temperature is displayed. From e2494979d2419e8b940d141901ef6cc868e401b4 Mon Sep 17 00:00:00 2001 From: Allan Persson <46043392+allanpersson@users.noreply.github.com> Date: Mon, 20 Jan 2020 10:41:21 +0100 Subject: [PATCH 26/33] Added quota warning (#11818) --- source/_integrations/sentry.markdown | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/source/_integrations/sentry.markdown b/source/_integrations/sentry.markdown index 75e781f2009..cba271d572c 100644 --- a/source/_integrations/sentry.markdown +++ b/source/_integrations/sentry.markdown @@ -11,6 +11,12 @@ ha_codeowners: - '@dcramer' --- +
+ + The free Sentry account allows 5000 events per month. Depending on the amount of events sent to Sentry you will either have to upgrade your Sentry account or have a period without data flowing from Home Assistant to Sentry. + +
+ The `sentry` integration integrates with [Sentry](https://sentry.io/) to capture both logged errors as well as unhandled exceptions in Home Assistant. ## Configuration From ce1589ecf3a8bc81cdb18b4a0718ced8c9cf4260 Mon Sep 17 00:00:00 2001 From: Bernhard B Date: Mon, 20 Jan 2020 10:49:45 +0100 Subject: [PATCH 27/33] fixed small error in signal_messenger documentation (#11802) * 'data' section was missing --- source/_integrations/signal_messenger.markdown | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/source/_integrations/signal_messenger.markdown b/source/_integrations/signal_messenger.markdown index ea581dd5e69..e53243e64e9 100644 --- a/source/_integrations/signal_messenger.markdown +++ b/source/_integrations/signal_messenger.markdown @@ -79,5 +79,6 @@ action: service: notify.NOTIFIER_NAME data: message: "Alarm in the living room!" - attachment: "/tmp/surveillance_camera.jpg" + data: + attachment: "/tmp/surveillance_camera.jpg" ``` From 2f3943044d6439776f4d9cc8f3f89a3bee6b43ff Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Mon, 20 Jan 2020 17:13:41 +0100 Subject: [PATCH 28/33] Remove old and obsolete SceneGen (#11822) --- source/_docs/scene/scenegen.markdown | 164 ------------------ source/_includes/asides/docs_navigation.html | 1 - .../2016-06-01-community-highlights.markdown | 3 +- ...05-hacktoberfest-influxdb-weather.markdown | 2 +- 4 files changed, 2 insertions(+), 168 deletions(-) delete mode 100644 source/_docs/scene/scenegen.markdown diff --git a/source/_docs/scene/scenegen.markdown b/source/_docs/scene/scenegen.markdown deleted file mode 100644 index a3a758b8bc9..00000000000 --- a/source/_docs/scene/scenegen.markdown +++ /dev/null @@ -1,164 +0,0 @@ ---- -title: "SceneGen" -description: "Scenegen is a scene generation tool for Home Assistant" -redirect_from: /ecosystem/scenegen/ ---- - -Scenegen is a scene generation tool for [Home Assistant](/) home automation software. It creates scenes by example, by reading the current states of devices and outputting a corresponding scene. Scenegen is written in python using Home Assistant's RESTful API so can be run from anywhere. It currently supports lights and switches only. - -## Installation - -### Clone the Repository -Clone the [**scenegen**](https://github.com/home-assistant/scenegen) repository to the current local directory on your machine. - -```bash -git clone https://github.com/home-assistant/scenegen.git -``` - -Change your working directory to the repository root. Moving forward, we will be working from this directory. - -```bash -cd scenegen -``` - -## Install Prerequisites - -Before running `SceneGen` you will need to add some python prerequisites: - -```bash -sudo pip3 install configparser -``` - -You should now be ready to run `scenegen` - -## Basic Operation - -```text -usage: scenegen [-h] [-k KEY] [-s SCENENAME] [-m MAPFILE] [-f FILTER] - [-c {xy_color,rgb_color,color_temp,color_name}] [-t TYPES] - url - -positional arguments: - url url for Home Assistant instance - -optional arguments: - -h, --help show this help message and exit - -k KEY, --key KEY API Key of Home Assistant instance - -s SCENENAME, --scenename SCENENAME - Name of scene to generate - -m MAPFILE, --mapfile MAPFILE - Name of mapfile to enable device filtering - -f FILTER, --filter FILTER - Comma separated list of device collections as defined - in mapfile - -c {xy_color,rgb_color,color_temp,color_name}, --colortype {xy_color,rgb_color,color_temp,color_name} - color type to use - -t TYPES, --types TYPES - list of device types to include - -``` - -For basic operation just supply the url and optionally the api key (using the --key option) on the command line and scenegen will output a list of all lights and switches with their attributes. Optionally use the `--scenename` flag to explicitly set the scenename. - -```bash -$ ./scenegen.py https:// -k -name: My New Scene -entities: - light.bedroom: - state: on - brightness: 28 - light.kitchen: - state: off - light.living_room: - state: off - light.bedside: - state: on - brightness: 125 - color_temp: 412 - light.office_level_29: - state: on - brightness: 28 -``` - -This output can be cut and pasted into your configuration.yaml file as required (ensuring correct indentation of course). - -Scenegen supports all documented effects for lights including transitions and flash effects, however generally it is easier to run scenegen to get the basic setup and add any effects manually later. - -Note that depending on the type of light there may be a delay in actually setting up its parameters and Home Assistant actually receiving that state. For instance, if you set a scene up with the Hue App, Home Assistant won't see those changes for up to 10 seconds. Turning on a ZWave light might not be seen for an entire poll interval. For this reason, its good practice to wait for a while after the scene is setup before running scenegen. Alternatively, perform all setup using the Home Assistant frontend and it will instantly have the required state for capture. - -## Advanced Usage - -For a more advanced way to use the output try the following. In configuration.yaml add the following line: - -```yaml -scene: !include_dir_list scenes -``` - -This will tell Home Assistant to look in the subdirectory `scenes` for yaml files containing scene information. Each file will be named for the scene it will create and should contain information formatted as above. Then simply run Scenegen and redirect its output to the scenes subdirectory: - -```bash -./scenegen.py https:// -k > scenes/my_new_scene.yaml -``` - -This will create a new scene called `my_new_scene` which will automatically be picked up by Home Assistant on the next restart. - -## Colors - -Scenegen allows colors to be captured, and in fact Home Assistant light entities store up to 4 different ways of specifying the colors. This is redundant for creating scenes so Scenegen picks 1 and goes with it. The default is `color_temp` but you can change this with the `--colortype` flag, supported options are `xy_color`, `rgb_color`, `color_temp` and `color_name`. - -## Types - -By default, Scenegen will list all lights and switches. To restrict the device type use the `--types` option and supply a comma separated list (no spaces) of types to output. e.g.: - -```bash -./scenegen.py https:// -k --types light,switch -``` - -or: - -```bash -./scenegen.py https:// -k --types light -``` - -This will make more sense as and when more types are added. - -## Maps and Filters - -Maps allow you to specify and label various subsets of devices that you want to work on together. A mapfile is specified using the `--mapfile` option and is a `.ini` style file consisting of section headers and entries. The section headers specify a region or zone or otherwise organized selection of entities you want to filter on, and it is mandatory to have at least one. If you create a map file like this: - -```text -[entities] -light.living_room: -light.dining_room: -``` - -The trailing colons are necessary to prevent parsing errors for including just keys, as opposed to key=value so just go with it - it reminds us of YAML ;) - -If you run scenegen with the `--mapfile` argument pointing to that file you will only get output for the listed entities (the name of the section is irrelevant if not using the `--filter` option). A more complex mapfile might look like this: - -```text -[Outside] -light.porch: -switch.path_lights: -[Living Room] -light.living_room_front: -light.living_room_back: -[Bedroom] -light.bedside: -``` - -Again, if you run with that map file it will output all of the entities listed, however you now have the possibility of restricting output devices based on the sections they are in, using the `--filter` option and supplying a comma separated list of sections you want to include, for instance: - -```bash -./scenegen.py https:// -k --mapfile map.cfg --filter "Outside,Living Room" -``` - -The intended use of the mapfile and filter is that you create a map of all your devices and organize them into zones that you are interested in creating scenes for and use the filter to limit output to that zone. For instance you might want to create 3 or 4 scenes for your living room, and once the map is set up you can easily do so without the addition of unwanted devices. - -## Updating SceneGen -To update SceneGen after a new version is released, just run the following command to update your copy: - -```bash -git pull -``` - diff --git a/source/_includes/asides/docs_navigation.html b/source/_includes/asides/docs_navigation.html index 5d7c4855a38..5cd250206f8 100644 --- a/source/_includes/asides/docs_navigation.html +++ b/source/_includes/asides/docs_navigation.html @@ -132,7 +132,6 @@ {% active_link /docs/scene/ Scenes %}
  • {% active_link /docs/scene/editor/ Editor %}
    • -
  • {% active_link /docs/scene/scenegen/ scenegen %}
  • diff --git a/source/_posts/2016-06-01-community-highlights.markdown b/source/_posts/2016-06-01-community-highlights.markdown index 755532a5968..6dfe83f7d91 100644 --- a/source/_posts/2016-06-01-community-highlights.markdown +++ b/source/_posts/2016-06-01-community-highlights.markdown @@ -13,7 +13,7 @@ Our community is amazingly helpful and creative. If you haven't been there yet, ### SceneGen - cli for making scenes -[SceneGen] is a new command line utility developed by [Andrew Cockburn] that helps with creating scene configurations for Home Assistant. To use it, you put your house in the preferred state, run SceneGen and it will print the scene configuration for your current states. +SceneGen is a new command line utility developed by [Andrew Cockburn] that helps with creating scene configurations for Home Assistant. To use it, you put your house in the preferred state, run SceneGen and it will print the scene configuration for your current states. ### Videos @@ -36,7 +36,6 @@ Muhammed Kilic has created a video how to make your Home Assistant instance acce [chat room]: https://discord.gg/c5DvZ4e -[SceneGen]: https://github.com/acockburn/scenegen [Andrew Cockburn]: https://github.com/acockburn [BRUH Automation]: http://www.bruhautomation.com/ [Nick Touran]: https://partofthething.com diff --git a/source/_posts/2016-11-05-hacktoberfest-influxdb-weather.markdown b/source/_posts/2016-11-05-hacktoberfest-influxdb-weather.markdown index c203587f26f..e613bda7bc2 100644 --- a/source/_posts/2016-11-05-hacktoberfest-influxdb-weather.markdown +++ b/source/_posts/2016-11-05-hacktoberfest-influxdb-weather.markdown @@ -104,7 +104,7 @@ We've added a warning to 0.32 to catch platforms accidentally slowing down Home Our website has now an additional category called "Ecosystem". This will become the place where tools, apps, and other helper for the Home Assistant ecosystem can store their documentation or guides. - [iOS](/ecosystem/ios/) -- [SceneGen](/ecosystem/scenegen/) +- SceneGen ### Breaking changes From 97f318a99bcd27cac1922f7d5a28fcfeb5a7d01f Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Tue, 21 Jan 2020 06:27:50 +0100 Subject: [PATCH 29/33] Remove obsolete homebridge_* settings (#11823) --- .../_docs/configuration/customizing-devices.markdown | 11 +---------- source/_integrations/universal.markdown | 12 +++++------- 2 files changed, 6 insertions(+), 17 deletions(-) diff --git a/source/_docs/configuration/customizing-devices.markdown b/source/_docs/configuration/customizing-devices.markdown index aa7a7154d19..e3d7d0da8fe 100644 --- a/source/_docs/configuration/customizing-devices.markdown +++ b/source/_docs/configuration/customizing-devices.markdown @@ -27,6 +27,7 @@ Under the *Configuration* menu you'll find the *Customization* menu. If this men homeassistant: customize: !include customize.yaml ``` + #### Possible values {% configuration customize %} @@ -34,20 +35,11 @@ friendly_name: description: Name of the entity as displayed in the UI. required: false type: string -homebridge_name: - description: Name of the entity in `HomeBridge`. - required: false - type: string hidden: description: Set to `true` to hide the entity. required: false type: boolean default: false -homebridge_hidden: - description: Set to `true` to hide the entity from `HomeBridge`. - required: false - type: boolean - default: false emulated_hue_hidden: description: Set to `true` to hide the entity from `emulated_hue` (this will be deprecated in the near future and should be configured in [`emulated_hue`](/integrations/emulated_hue)). required: false @@ -133,7 +125,6 @@ homeassistant: "scene.month_*_colors": hidden: true emulated_hue_hidden: false - homebridge_hidden: true ``` ### Reloading customize diff --git a/source/_integrations/universal.markdown b/source/_integrations/universal.markdown index 5bc4449896b..74fd4128e1d 100644 --- a/source/_integrations/universal.markdown +++ b/source/_integrations/universal.markdown @@ -76,13 +76,14 @@ When providing `select_source` as a command, it is recommended to also provide t ## Usage examples -#### Chromecast & Kodi control with switches +### Chromecast & Kodi control with switches In this example, a switch is available to control the power of the television. Switches are also available to turn the volume up, turn the volume down, and mute the audio. These could be command line switches or any other entity in Home Assistant. The `turn_on` and `turn_off` commands will be redirected to the television, and the volume commands will be redirected to an audio receiver. The `select_source` command will be passed directly to an A/V receiver. The children are a Chromecast and a Kodi player. If the Chromecast is playing, the Universal Media Player will reflect its status. If the Chromecast is idle and Kodi is playing, the universal media player will change to reflect its status. {% raw %} + ```yaml media_player: platform: universal @@ -129,6 +130,7 @@ media_player: source: media_player.receiver|source source_list: media_player.receiver|source_list ``` + {% endraw %} #### Kodi CEC-TV control @@ -139,24 +141,19 @@ We store the state of the attached TV in a hidden [input boolean](/integrations/ Because the input boolean used to store the TV state is only changing when using the Home Assistant `turn_on` and `turn_off` actions, and Kodi could be controlled by so many ways, we also define some automations to update this Input Boolean when needed. -In an Apple HomeKit scene, we can now expose this universal media player as an on/off switch in Homebridge, and, that way, use Siri to turn on and off the TV. - The complete configuration is: {% raw %} + ```yaml homeassistant: customize: input_boolean.kodi_tv_state: hidden: true - homebridge_hidden: true media_player.kodi: hidden: true - homebridge_hidden: true media_player.kodi_tv: friendly_name: Kodi - homebridge_name: Kodi - homebridge_media_player_switch: on_off input_boolean: kodi_tv_state: @@ -236,4 +233,5 @@ automation: - service: media_player.turn_off entity_id: media_player.kodi_tv ``` + {% endraw %} From e1474d6f1944d0aeb75bfa4c6fb51d6a6c46c6d1 Mon Sep 17 00:00:00 2001 From: Alex Cragg Date: Tue, 21 Jan 2020 10:18:53 +0000 Subject: [PATCH 30/33] Update tplink.markdown (#11831) I got the device model number wrong in #11805, it's KP303, not HS303, apologies. --- source/_integrations/tplink.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/tplink.markdown b/source/_integrations/tplink.markdown index a4ab48dd27f..10ff20ae4a0 100644 --- a/source/_integrations/tplink.markdown +++ b/source/_integrations/tplink.markdown @@ -39,7 +39,7 @@ The following devices are known to work with this component. - HS107 (indoor 2-outlet) - HS300 (powerstrip 6-outlet) -- HS303 (powerstrip 3-outlet) +- KP303 (powerstrip 3-outlet) - KP400 (outdoor 2-outlet) - KP200 (indoor 2-outlet) From 7febd86275f6b31b94401971511bf64cb7f11177 Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Tue, 21 Jan 2020 13:31:08 +0100 Subject: [PATCH 31/33] 0.104.3 --- _config.yml | 4 ++-- source/_posts/2020-01-15-release-104.markdown | 23 +++++++++++++++++++ 2 files changed, 25 insertions(+), 2 deletions(-) diff --git a/_config.yml b/_config.yml index 11a12b7952f..cca4f990d00 100644 --- a/_config.yml +++ b/_config.yml @@ -101,8 +101,8 @@ social: # Home Assistant release details current_major_version: 0 current_minor_version: 104 -current_patch_version: 2 -date_released: 2020-01-17 +current_patch_version: 3 +date_released: 2020-01-21 # 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/2020-01-15-release-104.markdown b/source/_posts/2020-01-15-release-104.markdown index efdb991faac..caf7b796e2e 100644 --- a/source/_posts/2020-01-15-release-104.markdown +++ b/source/_posts/2020-01-15-release-104.markdown @@ -488,6 +488,29 @@ Make sure to fill in all fields of the issue template, that is helping us a lot! [ring docs]: /integrations/ring/ [zha docs]: /integrations/zha/ +## Release 0.104.3 - January 21 + +- Catch all Ring timeout errors ([@balloob] - [#30960]) ([ring docs]) +- Update emulated_roku to 0.2.0 ([@jdeluyck] - [#30974]) ([emulated_roku docs]) +- Ring camera fix ([@steve-gombos] - [#30975]) ([ring docs]) +- Fix capability_attributes when supported_features is None ([@JeffLIrion] - [#30993]) ([water_heater docs]) +- Fix deCONZ update entry from Hassio discovery ([@frenck] - [#31015]) ([deconz docs]) + +[#30960]: https://github.com/home-assistant/home-assistant/pull/30960 +[#30974]: https://github.com/home-assistant/home-assistant/pull/30974 +[#30975]: https://github.com/home-assistant/home-assistant/pull/30975 +[#30993]: https://github.com/home-assistant/home-assistant/pull/30993 +[#31015]: https://github.com/home-assistant/home-assistant/pull/31015 +[@JeffLIrion]: https://github.com/JeffLIrion +[@balloob]: https://github.com/balloob +[@frenck]: https://github.com/frenck +[@jdeluyck]: https://github.com/jdeluyck +[@steve-gombos]: https://github.com/steve-gombos +[deconz docs]: /integrations/deconz/ +[emulated_roku docs]: /integrations/emulated_roku/ +[ring docs]: /integrations/ring/ +[water_heater docs]: /integrations/water_heater/ + ## All changes - Move imports to top for decora_wifi ([@springstan] - [#29439]) ([decora_wifi docs]) From 473f9f8884458f39fbb993bf39921c4a9c1dc841 Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Tue, 21 Jan 2020 17:48:12 +0100 Subject: [PATCH 32/33] Add note about hosting files in www folder (#11834) --- source/_integrations/http.markdown | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/source/_integrations/http.markdown b/source/_integrations/http.markdown index 40f759fc2a4..81ebaf9d5c5 100644 --- a/source/_integrations/http.markdown +++ b/source/_integrations/http.markdown @@ -162,6 +162,12 @@ If you want to use Home Assistant to host or serve static files then create a di +
    + + Files served from the `www`/`local` folder, aren't protected by the Home Assistant authentication. Files stored in this folder, if the URL is known, can be accessed by anybody without authentication. + +
    + ## Binary Sensor The HTTP binary sensor is dynamically created with the first request that is made to its URL. You don't have to define it in the configuration first. From 5f020d213d8460df4604ec307a470ae693ed8825 Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Tue, 21 Jan 2020 18:09:10 +0100 Subject: [PATCH 33/33] Update issue and PR templates (#11836) * Update issue and PR templates * Remove lorem ipsum * Small wording improvement * Update .github/ISSUE_TEMPLATE/config.yml Co-Authored-By: Bram Kragten Co-authored-by: Bram Kragten --- .github/ISSUE_TEMPLATE/DOCS_ISSUE.md | 11 +++++++ .github/ISSUE_TEMPLATE/config.yml | 14 +++++++++ .github/PULL_REQUEST_TEMPLATE.md | 45 ++++++++++++++++++++++++---- 3 files changed, 65 insertions(+), 5 deletions(-) create mode 100644 .github/ISSUE_TEMPLATE/DOCS_ISSUE.md create mode 100644 .github/ISSUE_TEMPLATE/config.yml diff --git a/.github/ISSUE_TEMPLATE/DOCS_ISSUE.md b/.github/ISSUE_TEMPLATE/DOCS_ISSUE.md new file mode 100644 index 00000000000..878ec4b21cb --- /dev/null +++ b/.github/ISSUE_TEMPLATE/DOCS_ISSUE.md @@ -0,0 +1,11 @@ +--- +name: Website/Docs bug report +about: Report incorrect/missing information or other issues with our website. +--- +## The problem + + + diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml new file mode 100644 index 00000000000..4270779b426 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -0,0 +1,14 @@ +blank_issues_enabled: false +contact_links: + - name: Report a bug/issue with Home Assistant itself + url: https://github.com/home-assistant/home-assistant/issues + about: This is the issue tracker for our website. Please report issues with Home Assistant in the main repository. + - name: I have a question or need support + url: https://www.home-assistant.io/help + about: We use GitHub for tracking bugs, check our website for resources on getting help. + - name: Feature Request + url: https://community.home-assistant.io/c/feature-requests + about: Please use our Community Forum for doing feature requests. + - name: I'm unsure where to go + url: https://www.home-assistant.io/join-chat + about: If you are unsure where to go, then joining our chat is recommended; Just ask! diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index 439b1e26c04..3b14fa350b9 100644 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -1,11 +1,46 @@ -**Description:** +## Proposed change + -**Pull request in home-assistant (if applicable):** home-assistant/home-assistant# -## Checklist: +## Type of change + -- [ ] Branch: `next` is for changes and new documentation that will go public with the next Home Assistant release. Fixes, changes and adjustments for the current release should be created against `current`. -- [ ] The documentation follows the [standards][standards]. +- [ ] Spelling, grammar or other readability improvements (`current` branch). +- [ ] Adjusted missing or incorrect information in the current documentation (`current` branch). +- [ ] Added documentation for a new integration I'm adding to Home Assistant (`next` branch). +- [ ] Added documentation for a new feature I'm adding to Home Assistant (`next` branch). +- [ ] Removed stale or deprecated documentation. + +## Additional information + + +- Link to parent pull request in the codebase: +- This PR fixes or closes issue: + +## Checklist + + +- [ ] This PR uses the correct branch, based on one of the following: + - I made a change to the existing documentation and used the `current` branch. + - I made a change that is related to an upcoming version of Home Assistant and used the `next` branch. +- [ ] The documentation follows the Home Assistant documentation [standards][]. [standards]: https://developers.home-assistant.io/docs/documentation_standards.html