Merge branch 'current' into next

_config.yml

@@ -101,8 +101,8 @@ social:
 # Home Assistant release details
 current_major_version: 0
 current_minor_version: 109
-current_patch_version: 3
+current_patch_version: 4
-date_released: 2020-05-02
+date_released: 2020-05-04
 
 # Either # or the anchor link to latest release notes in the blog post.
 # Must be prefixed with a # and have double quotes around it.

source/_docs/authentication.markdown

@@ -95,7 +95,8 @@ You have to use a domain name, not IP address, to remote access Home Assistant o
 
 This is because we only allow an IP address as a client ID when your IP address is an internal network address (e.g., `192.168.0.1`) or loopback address (e.g., `127.0.0.1`).
 
-If you don't have a valid domain name for your Home Assistant instance, you can modify the `hosts` file on your computer to fake one. On Windows, edit the `C:\Windows\System32\Drivers\etc\hosts` file with administrator privilege, or on Linux the `/etc/hosts` file,  and add following entry:
+If you don't have a valid domain name for your Home Assistant instance, you can modify the `hosts` file on your computer to fake one.
+On Linux edit the `/etc/hosts` file, and add following entry:
 
 ```text
 12.34.56.78 homeassistant.home

source/_docs/configuration.markdown

@@ -15,7 +15,6 @@ The location of the folder differs between operating systems:
 | Docker         | `/config`                  |
 | macOS          | `~/.homeassistant`         |
 | Linux          | `~/.homeassistant`         |
-| Windows        | `%APPDATA%/.homeassistant` |
 
 If you want to use a different folder for configuration, use the configuration command line parameter: `hass --config path/to/config`.
 

source/_docs/ecosystem/certificates/tls_self_signed_certificate.markdown

@@ -50,6 +50,14 @@ http:
   ssl_key: /home/your_user/.homeassistant/privkey.pem
 ```
 
+Docker:
+
+```yaml
+http:
+  ssl_certificate: /config/fullchain.pem
+  ssl_key: /config/privkey.pem
+```
+
 A restart of Home Assistant is required for the new certificate to take effect.
 
 If you get any log error about *ssl_key* or *ssl_certificate* that is **not a file for dictionary value** when run Home Assistant, you need to change owner or access permission of the `.pem` files as following:

source/_docs/installation/python.markdown

@@ -19,13 +19,12 @@ hass --open-ui
 
 Running these commands will:
 
- - Install Home Assistant
+- Install Home Assistant
- - Launch Home Assistant and serve the web interface on [http://localhost:8123](http://localhost:8123)
+- Launch Home Assistant and serve the web interface on [http://localhost:8123](http://localhost:8123)
 
 Video tutorials of this process for various operating systems are available here:
 
- - [Windows 10](https://www.youtube.com/watch?v=X27eVvuqwnY)
+- [macOS](https://www.youtube.com/watch?v=hej6ipN86ls)
- - [macOS](https://www.youtube.com/watch?v=hej6ipN86ls)
+- [Ubuntu 14.04](https://www.youtube.com/watch?v=SXaAG1lGNH0)
- - [Ubuntu 14.04](https://www.youtube.com/watch?v=SXaAG1lGNH0)
 
 Keep in mind that the operating systems used and the software releases shown may be outdated.

source/_integrations/discovery.markdown

@@ -99,9 +99,19 @@ Valid values for enable are:
 
 ### mDNS and UPnP
 
-Home Assistant must be on the same network as the devices for UPnP discovery to work.
+Home Assistant should be on the same network as the devices for mDNS and UPnP discovery to work.
+
 When running Home Assistant Core in a [Docker container](/docs/installation/docker/) command line option `--net=host` or the compose file equivalent `network_mode: host` must be used to put it on the host's network, otherwise mDNS and UPnP will not work.
 
+If mDNS is still not working:
+- Make sure there are no firewall rules blocking mDNS traffic. mDNS relies on sending and receiving UDP multicast packets on port 5353.
+- mDNS traffic may not be forwarded correctly between the wired and wireless interfaces of a Wi-Fi AP or router.
+
+#### mDNS forwarding
+If it's not possible to have Home Assistant and the devices on the same network, mDNS forwarding may allow mDNS discovery between networks.
+
+mDNS forwarding is a configurable option in some routers. It can also be called mDNS reflector or mDNS repeater, depending on the manufacturer.
+
 ### Windows
 
 #### 64-bit Python

source/_integrations/ffmpeg.markdown

@@ -12,7 +12,8 @@ The `ffmpeg` integration allows other Home Assistant integrations to process vid
 <div class='note'>
 
 If you are running Home Assistant Core in a Python environment, you'll need have the `ffmpeg` binary in your system path.
-On Debian 8 or Raspbian (Jessie) you can install it from [debian-backports](https://backports.debian.org/Instructions/). If you want [hardware acceleration](https://trac.ffmpeg.org/wiki/HWAccelIntro) support on a Raspberry Pi, you will need to build from source by yourself. Windows binaries are available on the [FFmpeg](http://www.ffmpeg.org/) website.
+On Debian 8 or Raspbian (Jessie) you can install it from [debian-backports](https://backports.debian.org/Instructions/). If you want [hardware acceleration](https://trac.ffmpeg.org/wiki/HWAccelIntro) support on a Raspberry Pi, you will need to build from source by yourself.
+
 </div>
 
 ## Configuration

source/_integrations/fortigate.markdown

@@ -12,6 +12,10 @@ ha_domain: fortigate
 
 This is a FortiGate presence sensor based on device detection of the FortiGate API
 
+<div class='note warning'>
+This integration will be deprecated. Please use the [FortiOS](/integrations/fortios) integration.
+</div>
+
 ## FortiGate set up
 
 Configure the FortiGate with a USERNAME API user and assign its minimum rights profile:

source/_integrations/homekit.markdown

@@ -369,7 +369,14 @@ homekit:
 ```
 
 Restart your Home Assistant instance. This feature requires running an mDNS forwarder on your Docker host, e.g., `avahi-daemon` in reflector mode. This kind of setup most likely requires `safe_mode` during the bridge setup.
- 
+
+## Firewall
+
+If you have a firewall configured on your Home Assistant system, make sure you open the following ports:
+
+- UDP: 5353 
+- TCP: 51827
+
 ## Supported Components
 
 The following integrations are currently supported:

source/_integrations/panasonic_viera.markdown

@@ -114,5 +114,6 @@ script:
 - TX-42AS650
 - TX55ASW654
 - TX-55FZ802B
+- TX-55ASM655
 
 If your model is not on the list, give it a test. If everything works correctly, then add it to the list on [GitHub](https://github.com/home-assistant/home-assistant.io/blob/current/source/_integrations/panasonic_viera.markdown).

source/_integrations/samsungtv.markdown

@@ -124,6 +124,7 @@ For example: for model `UN55NU7100`, the `UN55` would mean it's an LED, North Am
 - NU8070
 - U6000
 - U6300
+- RU7100
 - RU7172
 
 #### Models tested but not yet working

source/_integrations/yandextts.markdown

@@ -9,6 +9,12 @@ ha_domain: yandextts
 
 The `yandextts` text-to-speech platform uses [Yandex SpeechKit](https://tech.yandex.com/speechkit/) Text-to-Speech engine to read a text with natural sounding voices.
 
+<div class='note warning'>
+This integration is working only with old API keys.
+  
+For the new API keys this intergration is not working. There is a custom component that is working with new API keys [Yandex-tts-speechkit-FIX](https://github.com/tayanov/Yandex-tts-speechkit-FIX).
+</div>
+
 ## Configuration
 
 To enable text-to-speech with Yandex SpeechKit, add the following lines to your `configuration.yaml`:

source/_posts/2020-04-29-release-109.markdown

@@ -348,6 +348,10 @@ Experiencing issues introduced by this release? Please report them in our [issue
   Home Assistant Core 0.111. Configuration is now done through the UI.-
   ([@jjlawren] - [#34546]) ([plex docs])
 
+- **Google Cast** - Connecting to Cast devices now depends on mDNS even when IP
+  addresses of the Cast Devices are manually entered.-
+  ([@emontnemery] - [#33922]) ([cast docs])
+
 ## Farewell to the following
 
 - **Pushetta**
@@ -494,6 +498,38 @@ Pushetta has been offline since September 2019 and the Yahoo Weather API has bee
 [synology_dsm docs]: /integrations/synology_dsm/
 [unifi docs]: /integrations/unifi/
 
+## Release 0.109.4 - May 4
+
+- Fix Synology NAS discovered multiple times ([@Quentame] - [#35094]) ([synology_dsm docs])
+- Correct typo Asssitant -> Assistant ([@ludeeus] - [#35117]) ([websocket_api docs])
+- Hue: Guard for when there is no brightness ([@balloob] - [#35151]) ([hue docs])
+- Bump pyiCloud to 0.9.7 + do not warn when pending devices ([@Quentame] - [#35156]) ([icloud docs])
+- Fix Canary KeyError: 'ffmpeg_arguments' ([@frenck] - [#35158]) ([canary docs])
+- Fix UVC doing I/O inside the event loop ([@frenck] - [#35169]) ([uvc docs])
+- Fix utility_meter calibration with float values ([@dgomes] - [#35186]) ([utility_meter docs])
+- Fix Synology DSM sensor to be False or 0 ([@Quentame] - [#35208]) ([synology_dsm docs])
+
+[#35094]: https://github.com/home-assistant/core/pull/35094
+[#35117]: https://github.com/home-assistant/core/pull/35117
+[#35151]: https://github.com/home-assistant/core/pull/35151
+[#35156]: https://github.com/home-assistant/core/pull/35156
+[#35158]: https://github.com/home-assistant/core/pull/35158
+[#35169]: https://github.com/home-assistant/core/pull/35169
+[#35186]: https://github.com/home-assistant/core/pull/35186
+[#35208]: https://github.com/home-assistant/core/pull/35208
+[@Quentame]: https://github.com/Quentame
+[@balloob]: https://github.com/balloob
+[@dgomes]: https://github.com/dgomes
+[@frenck]: https://github.com/frenck
+[@ludeeus]: https://github.com/ludeeus
+[canary docs]: /integrations/canary/
+[hue docs]: /integrations/hue/
+[icloud docs]: /integrations/icloud/
+[synology_dsm docs]: /integrations/synology_dsm/
+[utility_meter docs]: /integrations/utility_meter/
+[uvc docs]: /integrations/uvc/
+[websocket_api docs]: /integrations/websocket_api/
+
 ## All changes
 
 <details>

source/addons/index.html

@@ -17,12 +17,13 @@ regenerate: false
 
 <p class="img">
   <img src="/images/addons/addon-store.png"/>
-  Add-ons for Hass.io are freely available in the add-on store.
+  Add-ons for Home Assistant are freely available in the add-on store.
 </p>
 
 <p>
   To install add-ons, navigate to the Supervisor panel in your Home Assistant
     frontend, and click on the "ADD-ON STORE" tab. All add-ons, including their documentation, are available right from the store.
+    Some advanced add-ons will only be visible after you opt-in to "Advanced Mode" which can be changed on your user profile page.
     Click on a add-on you are interested in, to read the documentation or to install the add-on.
 </p>
 

source/help/reporting_issues.markdown

@@ -4,33 +4,27 @@ description: "Reporting issues about Home Assistant"
 sidebar: false
 ---
 
-If you have an installation, a setup or a configuration issue please use our [Forum](https://community.home-assistant.io/) to get help. We have a big community which will help you if they can. 
+If you have an installation, a setup or a configuration issue please use our [Forum](https://community.home-assistant.io/) to get help. We have a big community which will help you if they can.
 
-If you found a bug then please report it in one of our [trackers](/help/#bugs-feature-requests-and-alike). To help you and our developers to identify the issue quickly, please fill out the provided template. The "weird" content you will see is there to render your entry in a nice format after submitting. It's just [markdown](https://guides.github.com/features/mastering-markdown/). 
+If you found a bug then please report it in one of our [trackers](/help/#bugs-feature-requests-and-alike). To help you and our developers to identify the issue quickly, please fill out the provided template. The "weird" content you will see is there to render your entry in a nice format after submitting. It's just [markdown](https://guides.github.com/features/mastering-markdown/).
 
-Use the command below to get the Home Assistant release you are running from a command-line.
+Please refer to the **Info** page, which is accessible in the **Developer tools** in the Home Assistant frontend.
 
-```bash
+## First Home Assistant release with the issue
-$ hass --version
-```
-
-Otherwise check the **About** page which is accessible in the **Developer tools** of the Home Assistant frontend.
-
-### First Home Assistant release with the issue
 
 Please provide the release which contains the issue.
 
-### Last working Home Assistant release (if known)
+## Last working Home Assistant release (if known)
 
 If possible, provide the latest release of which you know that the integration or platform was working. Home Assistant is evolving very fast and issues may already be addressed or be introduced by a recent change.
 
-### Operating environment (Hass.io/Docker/Windows/etc.)
+## Operating environment
 
-There are many different ways to run Home Assistant. In this section please mention which you are using, e.g., manual installation, [Hass.io](/hassio/), Hasbian or as container (Docker). It can help if you mention which operating system you are using because not all are supported on the same level.
+There are many different ways to run Home Assistant. In this section please mention which you are using, e.g., Home Assistant (using the Home Assistant Operating System), Home Assistant Supervised, Home Assistant Core in Docker or a manual installation of the Home Assistant Core. It can help if you mention which operating system you are using because not all are supported on the same level.
 
-### Integration/platform
+## Integration
 
-Please add the link to the documention of the integration/platform in question. E.g.,
+Please add the link to the documentation of the integration in question. E.g.,
 
 - issue with the `random` sensor: [/integrations/random#sensor](/integrations/random#sensor)
 - issue with the `hue` integration: [/integrations/hue/](/integrations/hue/)
@@ -43,7 +37,7 @@ There are integrations and platform which require additional steps (installing t
 
 ### Problem-relevant `configuration.yaml` entries
 
-To exclude configuration issues and allow the developers to quickly test, and perhaps reproduce, your issue, add the relevant part of your `configuration.yaml` file. This file is located in your [configuration folder](/docs/configuration/). 
+To exclude configuration issues and allow the developers to quickly test, and perhaps reproduce, your issue, add the relevant part of your `configuration.yaml` file. This file is located in your [configuration folder](/docs/configuration/).
 
 ```yaml
 sensor:
@@ -64,4 +58,3 @@ Traceback (most recent call last):
 ### Additional information
 
 This section can contain additional details or other observation. Often the little things can help as well.
-

source/lovelace/actions.markdown

@@ -7,9 +7,10 @@ Some Lovelace cards have support for tap actions. These actions define what will
 
 Actions can be enabled on:
 
-- [Entity](/lovelace/entities/)
+- [Button](/lovelace/button/)
-- [Entity Button](/lovelace/entity-button/)
+- [Entities](/lovelace/entities/)
 - [Glance](/lovelace/glance/)
+- [Light](/lovelace/light/)
 - [Picture](/lovelace/picture/)
 - [Picture Element](/lovelace/picture-elements/)
 - [Picture Entity](/lovelace/picture-entity/)

source/lovelace/index.markdown

@@ -7,7 +7,7 @@ redirect_from:
 
 Lovelace is the Home Assistant user interface. It's a fast, customizable and powerful way for users to manage their homes, working on mobile or desktop.
 
-- 24 different cards to place and configure as you like.
+- 25 different cards to place and configure as you like.
 - UI Editor. A configuration UI to manage your Lovelace UI including live preview when editing cards.
 - Fast. Using a static configuration allows us to build up the UI once.
 - Customizable.
@@ -26,7 +26,7 @@ To try it yourself, check out [the demo](https://demo.home-assistant.io).
 
 ## Discuss Lovelace
 
-- Suggestions are welcome in the [home-assistant-polymer repository](https://github.com/home-assistant/home-assistant-polymer/)
+- Suggestions are welcome in the [frontend repository](https://github.com/home-assistant/frontend/)
 - For help with Lovelace, join the `#frontend` channel on [our chat](/join-chat/) or [our forums](https://community.home-assistant.io/c/projects/frontend)
 
 ## Additional Lovelace Resources