2.1 KiB
layout, title, description, date, sidebar, comments, sharing, footer, logo, ha_category
| layout | title | description | date | sidebar | comments | sharing | footer | logo | ha_category |
|---|---|---|---|---|---|---|---|---|---|
| page | Discovery | Instructions how to setup Home Assistant to discover new devices. | 2015-01-24 14:39 | true | false | true | true | home-assistant.png | Other |
Home Assistant can discover and automatically configure zeroconf/mDNS and uPnP devices on your network. Currently the discovery component can detect:
- Google Chromecast
- Belkin WeMo switches
- Philips Hue
- Netgear routers
- Plex media server
- Panasonic Viera
- Roku media player
- Sonos Speakers
- Yamaha media player
- Logitech media server (Squeezebox)
- DirecTV
It will be able to add Google Chromecasts and Belkin WeMo switches automatically, for Philips Hue it will require some configuration from the user.
To load this component, add the following lines to your configuration.yaml:
# Example configuration.yaml entry
discovery:
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 you are developing a new platform, please read how to make your platform discoverable.
There is currently a known issue with running this platform 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 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.