From a1aed5543262f4e8420f9af9abecb07376ee70d7 Mon Sep 17 00:00:00 2001 From: Erik Montnemery Date: Fri, 1 May 2020 23:28:03 +0200 Subject: [PATCH] mDNS requires HA to be on same network as devices (#13245) --- source/_integrations/discovery.markdown | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/source/_integrations/discovery.markdown b/source/_integrations/discovery.markdown index 42cb8ed194f..278e6413c4d 100644 --- a/source/_integrations/discovery.markdown +++ b/source/_integrations/discovery.markdown @@ -98,17 +98,17 @@ Valid values for enable are: ## Troubleshooting -### UPnP +### mDNS and UPnP Home Assistant must be on the same network as the devices for UPnP discovery to work. -If running Home Assistant in a [Docker container](/docs/installation/docker/) use switch `--net=host` to put it on the host's network. +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. ### Windows #### 64-bit Python There is currently a known issue with running this integration on a 64-bit version of Python and Windows. -### could not install dependency netdisco +### Could not install dependency netdisco If you see `Not initializing discovery because could not install dependency netdisco==0.6.1` in the logs, you will need to install the `python3-dev` or `python3-devel` package on your system manually (eg. `sudo apt-get install python3-dev` or `sudo dnf -y install python3-devel`). On the next restart of Home Assistant, the discovery should work. If you still get an error, check if you have a compiler (`gcc`) available on your system.