From 7e88577a05b9928a42ff8276c32f622e1ccc8b86 Mon Sep 17 00:00:00 2001 From: Mauricio Bonani Date: Thu, 22 Oct 2020 02:55:05 -0400 Subject: [PATCH 01/21] Fix link for Ecowitt GW1000 Weather Station (#15349) --- source/_integrations/ambient_station.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/ambient_station.markdown b/source/_integrations/ambient_station.markdown index b7735741fb1..5d04ebe152a 100644 --- a/source/_integrations/ambient_station.markdown +++ b/source/_integrations/ambient_station.markdown @@ -47,7 +47,7 @@ app_key: This integration communicates with Ambient Weather PWS units via the Ambient Weather Cloud. Users wishing to explore a local option are encouraged to explore the -[Ecowitt GW1000](http://www.ecowitt.com/wifi_weather/80.html), a small device that is +[Ecowitt GW1000](https://www.ecowitt.com/shop/goodsDetail/16), a small device that is able to read RF signals directly from the PWS and transmit them to a variety of other applications, including [`ecowitt2mqtt`](https://github.com/bachya/ecowitt2mqtt) (which supports [MQTT Discovery](/docs/mqtt/discovery)). From 1f179d4503ed6db8e95b28a7a5677baec43d767f Mon Sep 17 00:00:00 2001 From: Mauricio Bonani Date: Thu, 22 Oct 2020 02:56:18 -0400 Subject: [PATCH 02/21] Fix Device Triggers link (#15348) --- source/_integrations/kodi.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/kodi.markdown b/source/_integrations/kodi.markdown index dfe5c051b9f..e709daf3efc 100644 --- a/source/_integrations/kodi.markdown +++ b/source/_integrations/kodi.markdown @@ -38,7 +38,7 @@ If you do not remove it, your configuration will be imported with the following You can customize your turn on and off actions through automations. Simply use the relevant Kodi device triggers and your automation will be called to perform the `turn_on` or `turn_off` sequence; see the [Kodi turn on/off samples](#kodi-turn-onoff-samples) section for scripts that can be used. -These automations can be configured through the UI (see [Device Triggers](/automation/trigger/#device-triggers) for automations). If you prefer YAML, you'll need to get the device ID from the UI automation editor. Automations would be of the form: +These automations can be configured through the UI (see [Device Triggers](/docs/automation/trigger/#device-triggers) for automations). If you prefer YAML, you'll need to get the device ID from the UI automation editor. Automations would be of the form: ```yaml automation: From 0d42009b51adf5ab7bb80b611944df0c42d402d1 Mon Sep 17 00:00:00 2001 From: kplachecki <45486014+kplachecki@users.noreply.github.com> Date: Thu, 22 Oct 2020 08:56:51 +0200 Subject: [PATCH 03/21] Update denonavr.markdown (#15347) --- source/_integrations/denonavr.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_integrations/denonavr.markdown b/source/_integrations/denonavr.markdown index eadf88edef6..cb2389471be 100644 --- a/source/_integrations/denonavr.markdown +++ b/source/_integrations/denonavr.markdown @@ -26,6 +26,7 @@ Known supported devices: - Denon AVR-X2100W - Denon AVR-X2200W - Denon AVR-X2300W +- Denon AVR-X2400H - Denon AVR-X3200W - Denon AVR-X3300W - Denon AVR-X3400H From a1fd7c6ce43d25c98aef14b4ea052cf063c04af6 Mon Sep 17 00:00:00 2001 From: tocklime <1396183+tocklime@users.noreply.github.com> Date: Thu, 22 Oct 2020 08:13:59 +0100 Subject: [PATCH 04/21] Add warning about impending switch off date. (#15346) Co-authored-by: Franck Nijhof --- source/_integrations/loopenergy.markdown | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/source/_integrations/loopenergy.markdown b/source/_integrations/loopenergy.markdown index e990cbeb0cb..537b90f4a36 100644 --- a/source/_integrations/loopenergy.markdown +++ b/source/_integrations/loopenergy.markdown @@ -10,6 +10,12 @@ ha_codeowners: - '@pavoni' --- +
+ +Loop Energy has said that on November 13, 2020, they will [switch off the servers which this integration uses](https://email.loop.homes/action-required-how-to-claim-your-free-loop-upgrade-1). This integration will stop working then. + +
+ Integrate your [Loop Energy](https://www.your-loop.com/) meter information into Home Assistant. To use this sensor you need the client serial number and secret keys for your devices. The library used to get the data isn't officially supported and the only way to get the keys is to log into loop energy's website and type a command into your browser console. From 811655d04a6f23d7ffe2881e5ab11a7af40900df Mon Sep 17 00:00:00 2001 From: OzGav Date: Thu, 22 Oct 2020 17:53:47 +1000 Subject: [PATCH 05/21] Add instructions on how to find UUID (#14939) --- source/_integrations/cast.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/cast.markdown b/source/_integrations/cast.markdown index 82251167c38..49c072a9b23 100644 --- a/source/_integrations/cast.markdown +++ b/source/_integrations/cast.markdown @@ -109,7 +109,7 @@ media_player: type: list keys: uuid: - description: UUID of a Cast device to add to Home Assistant. Use only if you don't want to add all available devices. The device won't be added until discovered through mDNS. + description: UUID of a Cast device to add to Home Assistant. Use only if you don't want to add all available devices. The device won't be added until discovered through mDNS. In order to find the UUID for your device use a mDNS browser or advanced users can use the following Python command (adjust friendly names as required) - python3 -c "import pychromecast; print(pychromecast.get_listed_chromecasts(friendly_names=["Living Room TV", "Bedroom TV", "Office Chromecast"]))" required: false type: string ignore_cec: From 7efe4e5ebb54d616eb0e6d80a29abf0b425f5f97 Mon Sep 17 00:00:00 2001 From: 1DontEx1st Date: Thu, 22 Oct 2020 05:22:19 -0400 Subject: [PATCH 06/21] Update xbee.markdown (#15341) updated zigbee URLs --- source/_integrations/xbee.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_integrations/xbee.markdown b/source/_integrations/xbee.markdown index 9477335f151..1b20a51ef31 100644 --- a/source/_integrations/xbee.markdown +++ b/source/_integrations/xbee.markdown @@ -11,7 +11,7 @@ ha_iot_class: Local Polling ha_domain: xbee --- -[Zigbee](https://zigbee.org/what-is-zigbee/) integration for Home Assistant allows you to utilize modules such as the [XBee](https://www.digi.com/xbee) as wireless General Purpose Input/Output (GPIO) devices. The integration requires a local Xbee device to be connected to a serial port. Through this, it will send and receive commands to and from other devices on the Zigbee mesh network. +[Zigbee](https://zigbeealliance.org/solution/zigbee/) integration for Home Assistant allows you to utilize modules such as the [XBee](https://www.digi.com/xbee) as wireless General Purpose Input/Output (GPIO) devices. The integration requires a local Xbee device to be connected to a serial port. Through this, it will send and receive commands to and from other devices on the Zigbee mesh network. There is currently support for the following device types within Home Assistant: @@ -134,7 +134,7 @@ on_state: ## Sensor -There are two types of [Zigbee](https://zigbee.org/) sensor available to Home Assistant: +There are two types of [Zigbee](https://zigbeealliance.org/) sensor available to Home Assistant: - [Analog input pin](#analog-input-pin) - [Temperature sensor](#temperature-sensor) (XBee Pro) From eaea6a813593168cf41f469e455bb2c3ca3b7f6f Mon Sep 17 00:00:00 2001 From: Josh McCarty Date: Thu, 22 Oct 2020 11:45:56 -0700 Subject: [PATCH 07/21] Add Cover category to OpenGarage integration (#15357) --- source/_integrations/opengarage.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_integrations/opengarage.markdown b/source/_integrations/opengarage.markdown index 59fb42a55fb..03eb4abc273 100644 --- a/source/_integrations/opengarage.markdown +++ b/source/_integrations/opengarage.markdown @@ -2,6 +2,7 @@ title: OpenGarage description: Instructions on how to integrate OpenGarage.io covers within Home Assistant. ha_category: + - Cover - DIY ha_iot_class: Local Polling ha_release: 0.44 From fdb14e2da18cf8eb74bc27992ee34b1a59f400b5 Mon Sep 17 00:00:00 2001 From: Pascal Vizeli Date: Fri, 23 Oct 2020 13:39:09 +0200 Subject: [PATCH 08/21] Update OS to 4.15 (#15368) --- source/hassio/installation.markdown | 34 ++++++++++++++--------------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/source/hassio/installation.markdown b/source/hassio/installation.markdown index 68542f943a0..a9641980771 100644 --- a/source/hassio/installation.markdown +++ b/source/hassio/installation.markdown @@ -105,23 +105,23 @@ If you would like to test next release before anyone else, you can install the b [balenaEtcher]: https://www.balena.io/etcher [hassos-network]: https://github.com/home-assistant/operating-system/blob/dev/Documentation/network.md -[pi0-w]: https://github.com/home-assistant/operating-system/releases/download/4.14/hassos_rpi0-w-4.14.img.gz -[pi1]: https://github.com/home-assistant/operating-system/releases/download/4.14/hassos_rpi-4.14.img.gz -[pi2]: https://github.com/home-assistant/operating-system/releases/download/4.14/hassos_rpi2-4.14.img.gz -[pi3-32]: https://github.com/home-assistant/operating-system/releases/download/4.14/hassos_rpi3-4.14.img.gz -[pi3-64]: https://github.com/home-assistant/operating-system/releases/download/4.14/hassos_rpi3-64-4.14.img.gz -[pi4-32]: https://github.com/home-assistant/operating-system/releases/download/4.14/hassos_rpi4-4.14.img.gz -[pi4-64]: https://github.com/home-assistant/operating-system/releases/download/4.14/hassos_rpi4-64-4.14.img.gz -[tinker]: https://github.com/home-assistant/operating-system/releases/download/4.14/hassos_tinker-4.14.img.gz -[odroid-c2]: https://github.com/home-assistant/operating-system/releases/download/4.14/hassos_odroid-c2-4.14.img.gz -[odroid-n2]: https://github.com/home-assistant/operating-system/releases/download/4.14/hassos_odroid-n2-4.14.img.gz -[odroid-xu4]: https://github.com/home-assistant/operating-system/releases/download/4.14/hassos_odroid-xu4-4.14.img.gz -[intel-nuc]: https://github.com/home-assistant/operating-system/releases/download/4.14/hassos_intel-nuc-4.14.img.gz -[vmdk]: https://github.com/home-assistant/operating-system/releases/download/4.14/hassos_ova-4.14.vmdk.gz -[vhdx]: https://github.com/home-assistant/operating-system/releases/download/4.14/hassos_ova-4.14.vhdx.gz -[vdi]: https://github.com/home-assistant/operating-system/releases/download/4.14/hassos_ova-4.14.vdi.gz -[qcow2]: https://github.com/home-assistant/operating-system/releases/download/4.14/hassos_ova-4.14.qcow2.gz -[Virtual Appliance]: https://github.com/home-assistant/operating-system/releases/download/4.14/hassos_ova-4.14.ova +[pi0-w]: https://github.com/home-assistant/operating-system/releases/download/4.15/hassos_rpi0-w-4.15.img.gz +[pi1]: https://github.com/home-assistant/operating-system/releases/download/4.15/hassos_rpi-4.15.img.gz +[pi2]: https://github.com/home-assistant/operating-system/releases/download/4.15/hassos_rpi2-4.15.img.gz +[pi3-32]: https://github.com/home-assistant/operating-system/releases/download/4.15/hassos_rpi3-4.15.img.gz +[pi3-64]: https://github.com/home-assistant/operating-system/releases/download/4.15/hassos_rpi3-64-4.15.img.gz +[pi4-32]: https://github.com/home-assistant/operating-system/releases/download/4.15/hassos_rpi4-4.15.img.gz +[pi4-64]: https://github.com/home-assistant/operating-system/releases/download/4.15/hassos_rpi4-64-4.15.img.gz +[tinker]: https://github.com/home-assistant/operating-system/releases/download/4.15/hassos_tinker-4.15.img.gz +[odroid-c2]: https://github.com/home-assistant/operating-system/releases/download/4.15/hassos_odroid-c2-4.15.img.gz +[odroid-n2]: https://github.com/home-assistant/operating-system/releases/download/4.15/hassos_odroid-n2-4.15.img.gz +[odroid-xu4]: https://github.com/home-assistant/operating-system/releases/download/4.15/hassos_odroid-xu4-4.15.img.gz +[intel-nuc]: https://github.com/home-assistant/operating-system/releases/download/4.15/hassos_intel-nuc-4.15.img.gz +[vmdk]: https://github.com/home-assistant/operating-system/releases/download/4.15/hassos_ova-4.15.vmdk.gz +[vhdx]: https://github.com/home-assistant/operating-system/releases/download/4.15/hassos_ova-4.15.vhdx.gz +[vdi]: https://github.com/home-assistant/operating-system/releases/download/4.15/hassos_ova-4.15.vdi.gz +[qcow2]: https://github.com/home-assistant/operating-system/releases/download/4.15/hassos_ova-4.15.qcow2.gz +[Virtual Appliance]: https://github.com/home-assistant/operating-system/releases/download/4.15/hassos_ova-4.15.ova [local]: http://homeassistant.local:8123 [samba]: /addons/samba/ [ssh]: /addons/ssh/ From b6e8086c44e72f5d167e6fd82a0368d7e868ba9c Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Fri, 23 Oct 2020 13:44:06 +0200 Subject: [PATCH 09/21] Bump tzinfo-data from 1.2020.3 to 1.2020.4 (#15364) Bumps [tzinfo-data](https://github.com/tzinfo/tzinfo-data) from 1.2020.3 to 1.2020.4. - [Release notes](https://github.com/tzinfo/tzinfo-data/releases) - [Commits](https://github.com/tzinfo/tzinfo-data/compare/v1.2020.3...v1.2020.4) Signed-off-by: dependabot[bot] Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> --- Gemfile.lock | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Gemfile.lock b/Gemfile.lock index 5ad61fadc5d..130746eb286 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -109,7 +109,7 @@ GEM tilt (2.0.10) tzinfo (2.0.2) concurrent-ruby (~> 1.0) - tzinfo-data (1.2020.3) + tzinfo-data (1.2020.4) tzinfo (>= 1.0.0) unicode-display_width (1.7.0) From c87716be4524e76d59cc01a65e6fce61cd21924e Mon Sep 17 00:00:00 2001 From: Hedda Date: Fri, 23 Oct 2020 21:06:18 +0200 Subject: [PATCH 10/21] CC265x and CC135x with Z-Stack 3 is stable in ZHA with zigpy-znp (#15366) --- source/_integrations/zha.markdown | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/source/_integrations/zha.markdown b/source/_integrations/zha.markdown index c98beaf8bd8..3bf87377bec 100644 --- a/source/_integrations/zha.markdown +++ b/source/_integrations/zha.markdown @@ -64,6 +64,9 @@ ZHA integration uses a hardware independent Zigbee stack implementation with mod - Telegesis ETRX357USB (Note! This first have to be flashed with other EmberZNet firmware) - Telegesis ETRX357USB-LRS (Note! This first have to be flashed with other EmberZNet firmware) - Telegesis ETRX357USB-LRS+8M (Note! This first have to be flashed with other EmberZNet firmware) +- Texas Instruments based radios with Z-Stack 3.x.x (via the [zigpy-znp](https://github.com/zha-ng/zigpy-znp) library for zigpy) + - [CC2652P/CC2652R/CC2652RB USB stick or dev board hardware flashed with Z-Stack 3.x.x coordinator firmware](https://www.zigbee2mqtt.io/information/supported_adapters) + - [CC1352P/CC1352R USB stick or dev board hardware flashed with Z-Stack 3.x.x coordinator firmware](https://www.zigbee2mqtt.io/information/supported_adapters) - Digi XBee Zigbee based radios (via the [zigpy-xbee](https://github.com/zigpy/zigpy-xbee) library for zigpy) - Digi XBee Series 3 (xbee3-24) modules - Digi XBee Series 2C (S2C) modules @@ -71,9 +74,6 @@ ZHA integration uses a hardware independent Zigbee stack implementation with mod ### Experimental support for additional Zigbee radio modules -- Texas Instruments based radios with Z-Stack 3.x.x (via the [zigpy-znp](https://github.com/zha-ng/zigpy-znp) library for zigpy) - - [CC2652P/CC2652R/CC2652RB USB stick or dev board hardware flashed with Z-Stack 3.x.x coordinator firmware](https://www.zigbee2mqtt.io/information/supported_adapters) - - [CC1352P/CC1352R USB stick or dev board hardware flashed with Z-Stack 3.x.x coordinator firmware](https://www.zigbee2mqtt.io/information/supported_adapters) - Texas Instruments based radios with Z-Stack Home 1.2.x (via the [zigpy-cc](https://github.com/zigpy/zigpy-cc) library for zigpy) - [CC2531 USB stick hardware flashed with Z-Stack Home 1.2.x coordinator firmware](https://www.zigbee2mqtt.io/information/supported_adapters) - [CC2530 + CC2591/CC2592 USB stick hardware flashed with Z-Stack Home 1.2.x coordinator firmware](https://www.zigbee2mqtt.io/information/supported_adapters) From be15ab6d55a499fc7cfdf332e5e7b039e5153650 Mon Sep 17 00:00:00 2001 From: matchett808-gh <55803404+matchett808-gh@users.noreply.github.com> Date: Fri, 23 Oct 2020 20:19:49 +0100 Subject: [PATCH 11/21] Update eafm.md (#15376) Add note about coverage --- source/_integrations/eafm.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/source/_integrations/eafm.md b/source/_integrations/eafm.md index f3382d7197d..46dedd7499c 100644 --- a/source/_integrations/eafm.md +++ b/source/_integrations/eafm.md @@ -13,6 +13,12 @@ ha_codeowners: The `eafm` integration offers integration with the [UK Environment Agency Flood Monitoring](https://flood-warning-information.service.gov.uk/) API to provide sensors for nearby water levels. Combined with Home Assistant notifications, you could give yourself a warning if a nearby river was likely to flood your local cycle path or the only road out of your village. +
+ +The UK Environment Agency Flood Monitoring only provides data for England - Northern Ireland, Scotland and Wales have their own flood agencies. + +
+ ## Configuration Home Assistant offers the flood monitoring integration through **Configuration** -> **Integrations** -> **Environment Agency Flood Gauges**. From 4f7ea4d127d6e10f42f6bbd9cae8300c693f25af Mon Sep 17 00:00:00 2001 From: blissarts <54777977+blissarts@users.noreply.github.com> Date: Fri, 23 Oct 2020 22:54:40 +0200 Subject: [PATCH 12/21] Add more clear description of unit (#15370) it was not clear from this documentation how the unit of the derivative sensor is set if the "unit" parameter is not set. This PR should fix that --- source/_integrations/derivative.markdown | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/source/_integrations/derivative.markdown b/source/_integrations/derivative.markdown index 8177b716b67..b1e264e015a 100644 --- a/source/_integrations/derivative.markdown +++ b/source/_integrations/derivative.markdown @@ -49,12 +49,12 @@ unit_prefix: default: None type: string unit_time: - description: SI unit of time of the derivative. Available units are s, min, h, d. + description: SI unit of time of the derivative. Available units are s, min, h, d. If this parameter is set, the attribute **unit_of_measurement** will be set like x/y where x is the unit of the sensor given via the **source** parameter and y is the value given here. required: false default: h type: string unit: - description: Unit of Measurement to be used for the derivative. + description: Unit of Measurement to be used for the derivative. This will overwrite the automatically set **unit_of_measurement** as explained above. required: false type: string time_window: @@ -78,6 +78,6 @@ sensor: source: sensor.temperature name: Temperature change per hour round: 1 - unit_time: h + unit_time: h # the resulting "unit_of_measurement" will be °C/h if the sensor.temperate has set °C as it's unit time_window: "00:30:00" # we look at the change over the last half hour ``` From a84647f7231f46e2dbaf9f7e67e19e578d4c5e95 Mon Sep 17 00:00:00 2001 From: juho20 <73366654+juho20@users.noreply.github.com> Date: Sat, 24 Oct 2020 14:33:06 +0200 Subject: [PATCH 13/21] Update panasonic_viera.markdown (#15379) Add working model TX-55FX680W --- source/_integrations/panasonic_viera.markdown | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/source/_integrations/panasonic_viera.markdown b/source/_integrations/panasonic_viera.markdown index d30e163dd41..4473c45ce9e 100644 --- a/source/_integrations/panasonic_viera.markdown +++ b/source/_integrations/panasonic_viera.markdown @@ -120,7 +120,8 @@ script: - TX-P50GT60E - TH-32ES500 - TX-42AS650 -- TX55ASW654 +- TX-55ASW654 +- TX-55FX680W - TX-55FZ802B - TX-55ASM655 From 6eb16d28462bdcb596b8140d0abbd3013c8c3112 Mon Sep 17 00:00:00 2001 From: Greg Dowling Date: Sun, 25 Oct 2020 11:35:50 +0000 Subject: [PATCH 14/21] Improve roon media player docs for current integration. (#15339) --- source/_integrations/media_player.markdown | 2 +- source/_integrations/roon.markdown | 15 ++++++++++++++- 2 files changed, 15 insertions(+), 2 deletions(-) diff --git a/source/_integrations/media_player.markdown b/source/_integrations/media_player.markdown index 41f723353e4..e0b80da1319 100644 --- a/source/_integrations/media_player.markdown +++ b/source/_integrations/media_player.markdown @@ -67,7 +67,7 @@ Currently only supported on [Denon AVR](/integrations/denonavr/) and [Songpal]( #### Service `media_player.shuffle_set` -Currently only supported on [Sonos](/integrations/sonos), [Spotify](/integrations/spotify), [MPD](/integrations/mpd), [Kodi](/integrations/kodi), [Squeezebox](/integrations/squeezebox) and [Universal](/integrations/universal). +Currently only supported on [Sonos](/integrations/sonos), [Spotify](/integrations/spotify), [MPD](/integrations/mpd), [Kodi](/integrations/kodi), [Roon](/integrations/roon), [Squeezebox](/integrations/squeezebox) and [Universal](/integrations/universal). | Service data attribute | Optional | Description | | ---------------------- | -------- | ---------------------------------------------------- | diff --git a/source/_integrations/roon.markdown b/source/_integrations/roon.markdown index 29ab836e29d..b19387a7407 100644 --- a/source/_integrations/roon.markdown +++ b/source/_integrations/roon.markdown @@ -19,7 +19,7 @@ To integrate with Roon, you need to provide Home Assistant with the Hostname or If you use an IP address, please assign a static IP address to the machine that runs Roon Core. This ensures that it won't change IP addresses, so you won't have to change the configuration in Home Assistant if it reboots and changes IP address. See your router's manual for details on how to set this up. -### Configuration +## Configuration You need the Hostname or IP address of the machine that runs your Roon Core. This might be a machine name (which can be followed by `.local`, e.g., `myserver.local`) or can be an IP address. @@ -28,3 +28,16 @@ You need the Hostname or IP address of the machine that runs your Roon Core. Thi 3. Home Assistant will then contact your Roon Core and ask to be authorized. You will need to enable this extension in the Room Application. Go to **Settings** and then **Extensions**, there you will see an entry for Home Assistant with a button next to it. Click **Enable**. 4. Roon core will then provide Home Assistant with the details of your media players. 5. In Home Assistant you can then pick an area for each of your music players, and add them to Home Assistant. + +#### Service `media_player.play_media` + +Roon doesn't use file names or URLs to track media and so the roon integration is currently limited in how it supports this call. + +| Service data attribute | Optional | Description | +| -----------------------| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `entity_id` | yes | Target a specific media player. To target all media players, use `all`. | +| `media_content_id` | no | The text for roon to search for in your library. | +| `media_content_type` | no | A media type. Currently supported are `radio`, `playlist` and `genre` | + + + For example to play BBC Radio 4 you would set `media_content_type` to `radio` and `media_content_id` to `BBC Radio 4` \ No newline at end of file From b2d50728d4911e1ad3756a0c83737bc9b4363319 Mon Sep 17 00:00:00 2001 From: Matej Plavevski Date: Sun, 25 Oct 2020 13:01:21 +0100 Subject: [PATCH 15/21] IOT class for Logbook (#15389) --- source/_integrations/logbook.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_integrations/logbook.markdown b/source/_integrations/logbook.markdown index bba544c7cba..9e2afb2154c 100644 --- a/source/_integrations/logbook.markdown +++ b/source/_integrations/logbook.markdown @@ -5,6 +5,7 @@ ha_category: - History ha_release: 0.7 ha_domain: logbook +ha_iot_class: ~ --- From 2b4bdfe080f14b9f4642c2e32eaab591011c8e37 Mon Sep 17 00:00:00 2001 From: ericvitale Date: Sun, 25 Oct 2020 09:55:18 -0400 Subject: [PATCH 16/21] Integration panasonic_viera was removed form legacy discovery in 0.109.6 (#15355) The panasonic_viera integration was removed from legacy discovery in 0.109.6 via: Commit: https://github.com/home-assistant/core/pull/34909/commits/238ba3207b2cce37efd542db2b07524493ba3c2f Pull Request: https://github.com/home-assistant/core/pull/34909 --- source/_integrations/discovery.markdown | 1 - 1 file changed, 1 deletion(-) diff --git a/source/_integrations/discovery.markdown b/source/_integrations/discovery.markdown index cc62aacde26..c5f41361b94 100644 --- a/source/_integrations/discovery.markdown +++ b/source/_integrations/discovery.markdown @@ -23,7 +23,6 @@ Home Assistant can discover and automatically configure [zeroconf](https://en.wi * [Logitech Harmony Hub](/integrations/harmony) * [Logitech Media Server (Squeezebox)](/integrations/squeezebox) * [NETGEAR routers](/integrations/netgear) - * [Panasonic Viera](/integrations/panasonic_viera) * [Philips Hue](/integrations/hue) * [SABnzbd downloader](/integrations/sabnzbd) * [Samsung SyncThru Printer](/integrations/syncthru) From 0222cb35e7d089019caa5cfcdf5a332924363c47 Mon Sep 17 00:00:00 2001 From: Andreas Setterlind Date: Sun, 25 Oct 2020 14:59:40 +0100 Subject: [PATCH 17/21] Rewritten "ZHA exception and deviation handling" explanation for readability. (#14960) --- source/_integrations/zha.markdown | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/source/_integrations/zha.markdown b/source/_integrations/zha.markdown index 3bf87377bec..7f9cc8037cc 100644 --- a/source/_integrations/zha.markdown +++ b/source/_integrations/zha.markdown @@ -40,9 +40,11 @@ There is also support for grouping of lights, switches, and fans (i.e. support f ## ZHA exception and deviation handling -Zigbee devices that deviate from or do not fully conform to the standard specifications set by the [Zigbee Alliance](https://zigbeealliance.org) may require the development of custom [ZHA Device Handlers](https://github.com/dmulcahey/zha-device-handlers) (ZHA custom quirks handler implementation) for all their functions to work properly with the ZHA integration in Home Assistant. These ZHA Device Handlers for Home Assistant can thus be used to parse custom messages to and from Zigbee devices. +The ZHA implementation in Home Assistant relies on a library called "[ZHA Device Handlers](https://github.com/zigpy/zha-device-handlers)" to resolve issues with Zigbee devices that do not fully conform with the Zigbee standards. The few devices that deviate from the Zigbee specifications set by the [Zigbee Alliance](https://zigbeealliance.org) may therefore require proper bug reports with debug logs from users to assistant the developers in writing custom [ZHA Device Handlers](https://github.com/zigpy/zha-device-handlers/blob/dev/README.md) for all of a device functions to work properly with the ZHA integration. -The custom quirks implementations for zigpy implemented as ZHA Device Handlers for Home Assistant are a similar concept to that of [Hub-connected Device Handlers for the SmartThings Classics platform](https://docs.smartthings.com/en/latest/device-type-developers-guide/) as well as that of [Zigbee-Shepherd Converters as used by Zigbee2mqtt](https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html), meaning they are each virtual representations of a physical device that expose additional functionality that is not provided out-of-the-box by the existing integration between these platforms. +Such a custom "ZHA Device Handler" are Python scripts that internally is also referred to as a "quirk" because they fix "quirks" as in deviations from the standard specifications. ZHA Device Handles do this by transparently acting as a translator, translating and converting non-compliant device messages and instead present them to the application as coming from a virtual compliant device. These ZHA Device Handlers for Home Assistant can thus be used to parse custom messages to and from Zigbee devices. The ZHA Device Handlers that are made can then be reused by all users in future versions of Home Assistant. + +The custom quirks implementations for zigpy implemented as ZHA Device Handlers for Home Assistant are a similar concept to that of [Hub-connected Device Handlers for the SmartThings Classics platform](https://docs.smartthings.com/en/latest/device-type-developers-guide/) as well as that of [Zigbee-Herdsman Converters (formerly Zigbee-Shepherd Converters) as used by Zigbee2mqtt](https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html), meaning they are each virtual representations of a physical device that expose additional functionality that is not provided out-of-the-box by the existing integration between these platforms. ## Compatible hardware From a93c4951114cfc5108dcab0eb9388ee49f5aad88 Mon Sep 17 00:00:00 2001 From: Ben Mckeown Date: Sun, 25 Oct 2020 17:37:33 +0000 Subject: [PATCH 18/21] Add IoT class to Notify (#15400) #14661 --- source/_integrations/notify.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_integrations/notify.markdown b/source/_integrations/notify.markdown index 33103429b20..d560d849e97 100644 --- a/source/_integrations/notify.markdown +++ b/source/_integrations/notify.markdown @@ -8,6 +8,7 @@ ha_quality_scale: internal ha_codeowners: - '@home-assistant/core' ha_domain: notify +ha_iot_class: ~ --- The `notify` integration makes it possible to send notifications to a wide variety of platforms. To use it you have to setup at least one notification target (notifier), check the [integrations list](/integrations/#notifications) for one that fits your use case. From abfe6222926e07294674ca8e2034f1a051df1eb3 Mon Sep 17 00:00:00 2001 From: Christophe Trefois Date: Sun, 25 Oct 2020 21:14:31 +0100 Subject: [PATCH 19/21] Update clicksend.markdown (#15408) --- source/_integrations/clicksend.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/clicksend.markdown b/source/_integrations/clicksend.markdown index 4e7de523b20..d5b6e09f501 100644 --- a/source/_integrations/clicksend.markdown +++ b/source/_integrations/clicksend.markdown @@ -54,7 +54,7 @@ recipient: required: true type: [string, list] sender: - description: The name or number of the sender. + description: The name or number of the sender. (Limited to 11 characters.) required: false type: string default: 'hass' From 1d910474dea67fd90f9b6d3de1c63cc7b5148f68 Mon Sep 17 00:00:00 2001 From: Narmishka <73436375+Narmishka@users.noreply.github.com> Date: Sun, 25 Oct 2020 22:03:58 +0100 Subject: [PATCH 20/21] Add new switch platform to Synology DSM in current release (#15404) --- source/_posts/2020-10-07-release-116.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/_posts/2020-10-07-release-116.markdown b/source/_posts/2020-10-07-release-116.markdown index 65022e06a43..f4ca91afdee 100644 --- a/source/_posts/2020-10-07-release-116.markdown +++ b/source/_posts/2020-10-07-release-116.markdown @@ -174,6 +174,8 @@ We welcome the following new integration this release: The following integration got support for a new platform: - [Synology DSM][synology_dsm docs] now supports cameras, added by [@shenxn] +- [Synology DSM][synology_dsm docs] now has a switch to control home mode in + Surveillance Station [@Quentame] - [HVV Departures][hvv_departures docs] added binary sensors to show elevator statuses. Added by [@vigonotion] - Support for covers was added to [Modbus][modbus docs], by [@vzahradnik] From c7eba68a6aa82fee55ed6792884f67836d1acd59 Mon Sep 17 00:00:00 2001 From: Ben Mckeown Date: Sun, 25 Oct 2020 21:10:34 +0000 Subject: [PATCH 21/21] Add IoT class to Search (#15402) #14661 --- source/_integrations/search.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_integrations/search.markdown b/source/_integrations/search.markdown index c81b823715e..5f6316cccd2 100644 --- a/source/_integrations/search.markdown +++ b/source/_integrations/search.markdown @@ -8,6 +8,7 @@ ha_quality_scale: internal ha_codeowners: - '@home-assistant/core' ha_domain: search +ha_iot_class: ~ --- The `search` integration is an internally used integration by the