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-09 10:26:52 +00:00
Code Issues Packages Projects Releases Wiki Activity
home-assistant.io/source/_components/discovery.markdown
Franck Nijhof 4369499e89 Component(s) -> Integration(s) (#9705)
2019-06-27 20:10:56 -07:00

5.6 KiB
Raw Blame History

layout, title, description, date, sidebar, comments, sharing, footer, logo, ha_category, ha_qa_scale, ha_release
layout title description date sidebar comments sharing footer logo ha_category ha_qa_scale ha_release
page Discovery Instructions on how to setup Home Assistant to discover new devices. 2015-01-24 14:39 true false true true home-assistant.png
Other
internal 0.7

Home Assistant can discover and automatically configure zeroconf/mDNS and uPnP devices on your network. Currently the discovery integration can detect:

It will be able to add Google Chromecasts and Belkin WeMo switches automatically, for Philips Hue it will require some configuration from the user.

Zeroconf discoverable integrations [Axis](/components/axis/)/[ESPHome](/components/esphome/)/[HomeKit](/components/homekit_controller/)/[Tradfri](/components/tradfri/) have been migrated to use [zeroconf](/components/zeroconf) integration to initiate discovery.

To load this component, add the following lines to your configuration.yaml:

# Example configuration.yaml entry
discovery:
  ignore:
    - sonos
    - samsung_tv
  enable:
    - homekit

{% configuration discovery %} ignore: description: A list of platforms that never will be automatically configured by discovery. required: false type: list enable: description: A list of platforms not enabled by default that discovery should discover. required: false type: list {% endconfiguration %}

Valid values for ignore are:

  • apple_tv: Apple TV
  • belkin_wemo: Belkin WeMo switches
  • bluesound: Bluesound speakers
  • bose_soundtouch: Bose Soundtouch speakers
  • denonavr: Denon network receivers
  • directv: DirecTV receivers
  • enigma2: Enigma2 media players
  • frontier_silicon: Frontier Silicon internet radios
  • google_cast: Google Cast
  • harmony: Logitech Harmony Hub
  • igd: Internet Gateway Device
  • logitech_mediaserver: Logitech media server (Squeezebox)
  • netgear_router: Netgear routers
  • octoprint: Octoprint
  • openhome: Linn / Openhome
  • panasonic_viera: Panasonic Viera
  • philips_hue: Philips Hue
  • plex_mediaserver: Plex media server
  • roku: Roku media player
  • sabnzbd: SABnzbd downloader
  • samsung_printer: Samsung SyncThru Printer
  • samsung_tv: Samsung TVs
  • sonos: Sonos speakers
  • songpal : Songpal
  • tellstick: Telldus Live
  • wink: Wink Hub
  • yamaha: Yamaha media player
  • yeelight: Yeelight lamps and bulbs (not only Yeelight Sunflower bulb)
  • xiaomi_gw: Xiaomi Aqara gateway

Valid values for enable are:

  • dlna_dmr: DLNA DMR enabled devices

{% linkable_title Troubleshooting %}

{% linkable_title 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 use switch --net=host to put it on the host's network.

{% linkable_title Windows %}

{% linkable_title 64-bit Python %}

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

{% linkable_title Python 3.5 %}

If you are on Windows and you're using Python 3.5, download the Netifaces dependency.

{% linkable_title 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.

{% linkable_title DSM and Synology %}

For DSM/Synology, install via debian-chroot see this forum post.