From a5fb7eaf119b219b88862b7bf57e9e4932156c4a Mon Sep 17 00:00:00 2001 From: Muhammad Sheraz Lodhi Date: Mon, 4 May 2020 18:37:04 +0400 Subject: [PATCH 01/14] Update samsungtv.markdown (#13290) * Update samsungtv.markdown * :pencil2: Tweak Co-authored-by: Klaas Schoute --- source/_integrations/samsungtv.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_integrations/samsungtv.markdown b/source/_integrations/samsungtv.markdown index 0431e6e28e8..5d48c132cd3 100644 --- a/source/_integrations/samsungtv.markdown +++ b/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 From 4ae78a3302fc30aa625267463fb3aa4aa320944a Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Mon, 4 May 2020 20:07:18 -0700 Subject: [PATCH 02/14] 0.109.4 (#13301) --- _config.yml | 4 +-- source/_posts/2020-04-29-release-109.markdown | 32 +++++++++++++++++++ 2 files changed, 34 insertions(+), 2 deletions(-) diff --git a/_config.yml b/_config.yml index 172ba688925..1ae1d2ad2bb 100644 --- a/_config.yml +++ b/_config.yml @@ -101,8 +101,8 @@ social: # Home Assistant release details current_major_version: 0 current_minor_version: 109 -current_patch_version: 3 -date_released: 2020-05-02 +current_patch_version: 4 +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. diff --git a/source/_posts/2020-04-29-release-109.markdown b/source/_posts/2020-04-29-release-109.markdown index 7d38a8ce56f..f2a599e0eb1 100644 --- a/source/_posts/2020-04-29-release-109.markdown +++ b/source/_posts/2020-04-29-release-109.markdown @@ -494,6 +494,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
From bcb3a173d62c347177159dfdd0f9fc58607a8f98 Mon Sep 17 00:00:00 2001 From: Lukas Ecklmayr Date: Tue, 5 May 2020 09:32:18 +0200 Subject: [PATCH 03/14] Add supported Model (#13299) Add supported Model TX-55ASM655 --- source/_integrations/panasonic_viera.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_integrations/panasonic_viera.markdown b/source/_integrations/panasonic_viera.markdown index 3ad8f224323..912e9cc6efe 100644 --- a/source/_integrations/panasonic_viera.markdown +++ b/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). From 560803afc8820b3139321a298f6385f8537c537c Mon Sep 17 00:00:00 2001 From: ews99 Date: Tue, 5 May 2020 09:37:18 +0200 Subject: [PATCH 04/14] Added firewall setup (#13293) * Added firewall setup * Minor change Co-authored-by: Fabian Affolter --- source/_integrations/homekit.markdown | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/source/_integrations/homekit.markdown b/source/_integrations/homekit.markdown index a28348833da..b90a0cb9551 100644 --- a/source/_integrations/homekit.markdown +++ b/source/_integrations/homekit.markdown @@ -358,7 +358,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: From 13559cee89551a20998ecaa6df10febe0734666d Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Tue, 5 May 2020 09:39:55 +0200 Subject: [PATCH 05/14] Removal of some stale Windows references (#13286) --- source/_docs/authentication.markdown | 3 ++- source/_docs/configuration.markdown | 1 - source/_docs/installation/python.markdown | 9 ++++---- source/_integrations/ffmpeg.markdown | 3 ++- source/help/reporting_issues.markdown | 27 +++++++++-------------- 5 files changed, 18 insertions(+), 25 deletions(-) diff --git a/source/_docs/authentication.markdown b/source/_docs/authentication.markdown index f62ea7a62ab..81ae30d9e97 100644 --- a/source/_docs/authentication.markdown +++ b/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 diff --git a/source/_docs/configuration.markdown b/source/_docs/configuration.markdown index aa496c85f4b..afe48dbf883 100644 --- a/source/_docs/configuration.markdown +++ b/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`. diff --git a/source/_docs/installation/python.markdown b/source/_docs/installation/python.markdown index 367cf4e6d0f..8e1e16f1158 100644 --- a/source/_docs/installation/python.markdown +++ b/source/_docs/installation/python.markdown @@ -19,13 +19,12 @@ hass --open-ui Running these commands will: - - Install Home Assistant - - Launch Home Assistant and serve the web interface on [http://localhost:8123](http://localhost:8123) +- Install Home Assistant +- 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) - - [Ubuntu 14.04](https://www.youtube.com/watch?v=SXaAG1lGNH0) +- [macOS](https://www.youtube.com/watch?v=hej6ipN86ls) +- [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. diff --git a/source/_integrations/ffmpeg.markdown b/source/_integrations/ffmpeg.markdown index a2f69d7165e..1aa89f6c6a3 100644 --- a/source/_integrations/ffmpeg.markdown +++ b/source/_integrations/ffmpeg.markdown @@ -12,7 +12,8 @@ The `ffmpeg` integration allows other Home Assistant integrations to process vid
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. +
## Configuration diff --git a/source/help/reporting_issues.markdown b/source/help/reporting_issues.markdown index 6dac514943c..893ea9db372 100644 --- a/source/help/reporting_issues.markdown +++ b/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 -$ 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 +## 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. - From a81ca326f7cb72da66bfc7e36b5a2c07ad95935e Mon Sep 17 00:00:00 2001 From: Erik Montnemery Date: Tue, 5 May 2020 09:40:45 +0200 Subject: [PATCH 06/14] Update 2020-04-29-release-109.markdown (#13298) --- source/_posts/2020-04-29-release-109.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/source/_posts/2020-04-29-release-109.markdown b/source/_posts/2020-04-29-release-109.markdown index f2a599e0eb1..c86a1ee8f2f 100644 --- a/source/_posts/2020-04-29-release-109.markdown +++ b/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** From 6b5ea2d20e8079dcb4042223039fbd9dacc074a8 Mon Sep 17 00:00:00 2001 From: Sean Mooney Date: Tue, 5 May 2020 03:41:52 -0400 Subject: [PATCH 07/14] Adds note about Advanced Mode and add-ons (#13303) Some supervisor add-ons like SSH are now only visible if Advanced Mode is turned on in your user profile page. Also changed a reference from Hass.io to Home Assistant --- source/addons/index.html | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/source/addons/index.html b/source/addons/index.html index 2cfbc5099a8..e39ff8420fc 100644 --- a/source/addons/index.html +++ b/source/addons/index.html @@ -17,12 +17,13 @@ regenerate: false

- 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.

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.

From 405168bdcbdb3c2dac1b26ea38c45e866777b05d Mon Sep 17 00:00:00 2001 From: Sean Mooney Date: Tue, 5 May 2020 03:43:36 -0400 Subject: [PATCH 08/14] Minor edit to Lovelace intro page (#13292) 24 cards -> 25 cards (Entity card is a recent addition). Also updated home-assistant-polymer to new repo name, frontend. --- source/lovelace/index.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/lovelace/index.markdown b/source/lovelace/index.markdown index 623fcd687c1..43981cc24cb 100644 --- a/source/lovelace/index.markdown +++ b/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 From 946a187277009b7d2cbfabb6c073211a63e104ed Mon Sep 17 00:00:00 2001 From: Erik Montnemery Date: Tue, 5 May 2020 09:44:54 +0200 Subject: [PATCH 09/14] Add more trouble shooting hints for mDNS (#13291) * Add more trouble shooting hints for mDNS * Update discovery.markdown * Apply suggestions from code review Co-authored-by: Jakob Reiter * Tweak Co-authored-by: Jakob Reiter --- source/_integrations/discovery.markdown | 27 ++++++++++++++++++++++++- 1 file changed, 26 insertions(+), 1 deletion(-) diff --git a/source/_integrations/discovery.markdown b/source/_integrations/discovery.markdown index 278e6413c4d..27985eb2a3a 100644 --- a/source/_integrations/discovery.markdown +++ b/source/_integrations/discovery.markdown @@ -100,9 +100,34 @@ 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 can be enabled to 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. + +For a Linux server acting as router, set up avahi-reflector on the server to make mDNS work between the networks: + +{% raw %} +```text +# Install the Avahi-daemon +sudo apt-get install avahi-daemon +# Turn on the reflector. Go into /etc/avahi/avahi-daemon.conf and change the reflector section to: + [reflector] + enable-reflector=yes + reflect-ipv=no +# (re)start the Avahi daemon to reload config +sudo service avahi-daemon restart +``` +{% endraw %} + ### Windows #### 64-bit Python From 4d56c879eddc428dff362eb70169f960ea8b71b8 Mon Sep 17 00:00:00 2001 From: Sean Mooney Date: Tue, 5 May 2020 03:45:19 -0400 Subject: [PATCH 10/14] Update Lovelace actions (#13294) Reasons for following changes: * Support for hold action and double tap action was added to Light card, but not mentioned here. * Entity Button card was renamed to Button a few versions ago * Renamed "Entity" card to "Entities" as that is the proper name, and there's an actual Entity card now (which doesn't support actions). So it was wrong. --- source/lovelace/actions.markdown | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/source/lovelace/actions.markdown b/source/lovelace/actions.markdown index 7d49c9e912e..fafba26b913 100644 --- a/source/lovelace/actions.markdown +++ b/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/) -- [Entity Button](/lovelace/entity-button/) +- [Button](/lovelace/button/) +- [Entities](/lovelace/entities/) - [Glance](/lovelace/glance/) +- [Light](/lovelace/light/) - [Picture](/lovelace/picture/) - [Picture Element](/lovelace/picture-elements/) - [Picture Entity](/lovelace/picture-entity/) From 618230768251f41d544829d7e249d0ff5dd3d4b1 Mon Sep 17 00:00:00 2001 From: Ivan Bessarabov Date: Tue, 5 May 2020 11:31:17 +0300 Subject: [PATCH 11/14] yandextts is only working with old API keys (#13240) --- source/_integrations/yandextts.markdown | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/source/_integrations/yandextts.markdown b/source/_integrations/yandextts.markdown index 8f2c6986682..7c0f366be21 100644 --- a/source/_integrations/yandextts.markdown +++ b/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. +
+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). +
+ ## Configuration To enable text-to-speech with Yandex SpeechKit, add the following lines to your `configuration.yaml`: From 357bc3ff602442fa925f8c71501b25bdeed91e18 Mon Sep 17 00:00:00 2001 From: Thomas Le Gentil <20202649+kifeo@users.noreply.github.com> Date: Tue, 5 May 2020 10:46:21 +0200 Subject: [PATCH 12/14] deprecate fortigate integration (#13197) * deprecate fortigate integration the fortigate integration will be remove in order to only use the fortios one * highlighted text highlighted text and added link to the fortios integration * used a 'note warning' css class * Minor changes Co-authored-by: Fabian Affolter --- source/_integrations/fortigate.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/source/_integrations/fortigate.markdown b/source/_integrations/fortigate.markdown index 6a5028fcb9c..1d19660a35e 100644 --- a/source/_integrations/fortigate.markdown +++ b/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 +
+This integration will be deprecated. Please use the [FortiOS](/integrations/fortios) integration. +
+ ## FortiGate set up Configure the FortiGate with a USERNAME API user and assign its minimum rights profile: From b5cd87e3b4eb2fc6ea8f3230f1c7eb50254100af Mon Sep 17 00:00:00 2001 From: Malcolm <56974882+malcolmcdixon@users.noreply.github.com> Date: Tue, 5 May 2020 08:47:09 +0000 Subject: [PATCH 13/14] Update tls_self_signed_certificate.markdown (#13179) --- .../certificates/tls_self_signed_certificate.markdown | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/source/_docs/ecosystem/certificates/tls_self_signed_certificate.markdown b/source/_docs/ecosystem/certificates/tls_self_signed_certificate.markdown index 7926fedadcb..90d4701308b 100644 --- a/source/_docs/ecosystem/certificates/tls_self_signed_certificate.markdown +++ b/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: From 0b39bd73da09b11f4f47afe4775166786d09e01c Mon Sep 17 00:00:00 2001 From: Erik Montnemery Date: Tue, 5 May 2020 13:41:03 +0200 Subject: [PATCH 14/14] Fix remarks from PR 13291 (#13306) --- source/_integrations/discovery.markdown | 23 ++++------------------- 1 file changed, 4 insertions(+), 19 deletions(-) diff --git a/source/_integrations/discovery.markdown b/source/_integrations/discovery.markdown index 27985eb2a3a..d50efb97b5c 100644 --- a/source/_integrations/discovery.markdown +++ b/source/_integrations/discovery.markdown @@ -105,28 +105,13 @@ Home Assistant should be on the same network as the devices for mDNS and UPnP di 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 +- 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 can be enabled to allow mDNS discovery between networks. +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. - -For a Linux server acting as router, set up avahi-reflector on the server to make mDNS work between the networks: - -{% raw %} -```text -# Install the Avahi-daemon -sudo apt-get install avahi-daemon -# Turn on the reflector. Go into /etc/avahi/avahi-daemon.conf and change the reflector section to: - [reflector] - enable-reflector=yes - reflect-ipv=no -# (re)start the Avahi daemon to reload config -sudo service avahi-daemon restart -``` -{% endraw %} +mDNS forwarding is a configurable option in some routers. It can also be called mDNS reflector or mDNS repeater, depending on the manufacturer. ### Windows