Philips Hue support is integrated into Home Assistant as a light platform. The preferred way to setup the Philips Hue platform is by enabling the the discovery component.
+Philips Hue support is integrated into Home Assistant as a light platform. The preferred way to setup the Philips Hue platform is by enabling the discovery component.
-Once discovered, locate “configurator.philips_hue” in the entities list ( < > ) and add it to configuration.yaml. Restart home assistant so that it is visible in the home assistant dashboard. Once home assistant is restarted, locate and click on configurator.philips_hue to bring up the initiation dialog. This will prompt you to press the Hue button to register the Hue hub in home assistant. Once complete, the configurator entity can be removed from configuration.yaml.
+Once discovered, if you have a custom default view, locate configurator.philips_hue in the entities list ( < > ) and add it to a group in configuration.yaml. Restart Home Assistant so that the configurator is visible in the Home Assistant dashboard. Once Home Assistant is restarted, locate and click on configurator.philips_hue to bring up the initiation dialog. This will prompt you to press the Hue button to register the Hue hub in home assistant. Once complete, the configurator entity isn’t needed anymore and can be removed from any visible group in configuration.yaml.
Restarting home assistant once more should result in the Hue lights listed as “light” entities. Add these light entities to configuration.yaml and restart home assistant once more to complete the installation.
+Restarting Home Assistant once more should result in the Hue lights listed as “light” entities. Add these light entities to configuration.yaml and restart home assistant once more to complete the installation.
-If you want to enable the light component directly, add the following lines to your configuration.yaml:
If you want to enable the component without relying on the discovery component, add the following lines to your configuration.yaml:
# Example configuration.yaml entry
light:
diff --git a/components/media_player.yamaha/index.html b/components/media_player.yamaha/index.html
index 977f5d8cec..cf09494cb8 100644
--- a/components/media_player.yamaha/index.html
+++ b/components/media_player.yamaha/index.html
@@ -114,6 +114,8 @@
- name (Optional): Name of the device
- host (Optional): IP address or hostname of the device
+ - source_ignore (Optional): List of sources to hide in the front-end
+ - source_names (Optional): Mapping of internal AVR source names to custom ones, allowing to rename e.g.
HDMI1 to ChromeCast
A few notes:
@@ -122,9 +124,22 @@
Not specifying the host variable will result in automatically searching your network for Yamaha Receivers. It will add a media player device for each one.
In some cases, autodiscovery fails due to a known bug in the receiver’s firmware. It is possible to manually specify the reveiver’s IP address or via it’s hostname (if it is discoverably by your DNS) then.
Please note: If adding the IP address or hostname manually, you must enable network standby on your receiver, or else startup of Home Assistant will hang if you have your receiver switched off.
- Currently the only controls that are available is Power On/Off, Mute, and Volume control. Other functions such as source select are in progress of being developed.
+ Currently, this component supports powering on/off, mute, volume control and source selection.
+A full configuration example will look like the sample below:
+# Example configuration.yaml entry
+media_player:
+ - platform: yamaha
+ host: 192.168.0.10
+ source_ignore:
+ - "AUX"
+ - "HDMI6"
+ source_names:
+ - HDMI1: "ChromeCast"
+ - AV4: "Vinyl"
+
+
diff --git a/sitemap.xml b/sitemap.xml
index 8e1373f256..4737695923 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -2168,62 +2168,62 @@
https://home-assistant.io/demo/frontend.html
-2016-10-12T20:17:39+00:00
+2016-10-13T13:39:58+00:00
https://home-assistant.io/demo/index.html
-2016-10-12T20:17:39+00:00
+2016-10-13T13:39:58+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-event.html
-2016-10-12T20:17:39+00:00
+2016-10-13T13:39:58+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-info.html
-2016-10-12T20:17:39+00:00
+2016-10-13T13:39:58+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-service.html
-2016-10-12T20:17:39+00:00
+2016-10-13T13:39:58+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-state.html
-2016-10-12T20:17:39+00:00
+2016-10-13T13:39:58+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-template.html
-2016-10-12T20:17:39+00:00
+2016-10-13T13:39:58+00:00
https://home-assistant.io/demo/panels/ha-panel-history.html
-2016-10-12T20:17:39+00:00
+2016-10-13T13:39:58+00:00
https://home-assistant.io/demo/panels/ha-panel-iframe.html
-2016-10-12T20:17:39+00:00
+2016-10-13T13:39:58+00:00
https://home-assistant.io/demo/panels/ha-panel-logbook.html
-2016-10-12T20:17:39+00:00
+2016-10-13T13:39:58+00:00
https://home-assistant.io/demo/panels/ha-panel-map.html
-2016-10-12T20:17:39+00:00
+2016-10-13T13:39:58+00:00
https://home-assistant.io/googlef4f3693c209fe788.html
-2016-10-12T20:17:39+00:00
+2016-10-13T13:39:58+00:00
https://home-assistant.io/static/fonts/roboto/DESCRIPTION.en_us.html
-2016-10-12T20:17:39+00:00
+2016-10-13T13:39:58+00:00
https://home-assistant.io/static/fonts/robotomono/DESCRIPTION.en_us.html
-2016-10-12T20:17:39+00:00
+2016-10-13T13:39:58+00:00
https://home-assistant.io/static/mdi-demo.html
-2016-10-12T20:17:39+00:00
+2016-10-13T13:39:58+00:00