jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-29 12:17:01 +00:00
Code Issues Packages Projects Releases Wiki Activity

Address comments from

Browse Source 
https://github.com/home-assistant/home-assistant/issues/9135
This commit is contained in:
Fabian Affolter 2017-08-26 13:08:53 +02:00
parent 00f9cf7cd6
commit 9224600683
No known key found for this signature in database
GPG Key ID: DDF3D6F44AAB1336
1 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
source/_components/discovery.markdown
View File

@ -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
@ -67,26 +67,26 @@ Valid values for ignore are:
* `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
<p class='note'>
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.
</p>
If you are developing a new platform, please read [how to make your platform discoverable]({{site_root}}/developers/add_new_platform/#discovery).
<p class='note warning'>
There is currently a <a href='https://bitbucket.org/al45tair/netifaces/issues/17/dll-fails-to-load-windows-81-64bit'>known issue</a> with running this platform on a 64-bit version of Python and Windows.
There is currently a <a href='https://bitbucket.org/al45tair/netifaces/issues/17/dll-fails-to-load-windows-81-64bit'>known issue</a> with running this component on a 64-bit version of Python and Windows.
</p>
<p class='note'>
If you are on Windows and you're using Python 3.5, download the Netifaces dependency <a href='http://www.lfd.uci.edu/~gohlke/pythonlibs/#netifaces'>here</a>.
If you are on Windows and you're using Python 3.5, download the [Netifaces](http://www.lfd.uci.edu/~gohlke/pythonlibs/#netifaces) dependency.
</p>
<p class='note'>
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.
</p>
If you are developing a new platform, please read [how to make your platform discoverable](/developers/component_discovery/) for further details.