From 92246006836db4db271349952e699a2554fe3bd8 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sat, 26 Aug 2017 13:08:53 +0200 Subject: [PATCH] Address comments from https://github.com/home-assistant/home-assistant/issues/9135 --- source/_components/discovery.markdown | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/source/_components/discovery.markdown b/source/_components/discovery.markdown index 43152eb5f98..41c7e2392d1 100644 --- a/source/_components/discovery.markdown +++ b/source/_components/discovery.markdown @@ -12,7 +12,7 @@ ha_category: Other --- -Home Assistant can discover and automatically configure zeroconf/mDNS and uPnP devices on your network. Currently the `discovery` component can detect: +Home Assistant can discover and automatically configure [zeroconf](https://en.wikipedia.org/wiki/Zero-configuration_networking)/[mDNS](https://en.wikipedia.org/wiki/Multicast_DNS) and [uPnP](https://en.wikipedia.org/wiki/Universal_Plug_and_Play) devices on your network. Currently the `discovery` component can detect: * Google Chromecast * Belkin WeMo switches @@ -54,7 +54,7 @@ Configuration variables: Valid values for ignore are: * `apple_tv`: Apple TV - * `axis`: (Axis Communications security devices) + * `axis`: Axis Communications security devices * `bose_soundtouch`: Bose Soundtouch speakers * `denonavr`: Denon Network Receivers * `directv`: DirecTV @@ -62,31 +62,31 @@ Valid values for ignore are: * `google_cast`: Google Chromecast * `ikea_tradfri`: IKEA Trådfri * `logitech_mediaserver`: Logitech media server - Squeezebox player - * `openhome`: Linn / Openhome + * `openhome`: Linn/Openhome * `panasonic_viera`: Panasonic Viera * `philips_hue`: Philips Hue * `plex_mediaserver`: Plex media server * `roku`: Roku media player - * `samsung_tv`: (Samsung TV + * `samsung_tv`: Samsung TV * `sonos`: Sonos Speakers * `yamaha`: Yamaha media player * `yeelight`: Yeelight Sunflower Bulb

Home Assistant must be on the same network as the devices for uPnP discovery to work. -If running Home Assistant in a Docker container use switch `--net=host` to put it on the host's network. +If running Home Assistant in a [Docker container](/docs/installation/docker/) use switch `--net=host` to put it on the host's network.

-If you are developing a new platform, please read [how to make your platform discoverable]({{site_root}}/developers/add_new_platform/#discovery). -

-There is currently a known issue with running this platform on a 64-bit version of Python and Windows. +There is currently a known issue with running this component on a 64-bit version of Python and Windows.

-If you are on Windows and you're using Python 3.5, download the Netifaces dependency here. +If you are on Windows and you're using Python 3.5, download the [Netifaces](http://www.lfd.uci.edu/~gohlke/pythonlibs/#netifaces) dependency.

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, discovery should work. If you still get an error, check if you have a compiler (`gcc`) available on your system.

+ +If you are developing a new platform, please read [how to make your platform discoverable](/developers/component_discovery/) for further details.