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, 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.
When you configure the Hue bridge from HA, it writes a token to a file in your HA configuration directory. That token authenticates the HA communication with the Hue bridge. This token uses the IP Address of the Hue Bridge. If the IP address for the Hue Bridge changes, you will need to register the Hue Bridge with home assistant again. TO avoid this you may set up DHCP registration for your Hue Bridge, so that it always has the same IP address.
+When you configure the Hue bridge from Home Assistant, it writes a token to a file in your Home Assistant configuration directory. That token authenticates the communication with the Hue bridge. This token uses the IP Address of the Hue Bridge. If the IP address for the Hue Bridge changes, you will need to register the Hue Bridge with Home Assistant again. To avoid this you may set up DHCP registration for your Hue Bridge, so that it always has the same IP address.
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 component without relying on the discovery component, add the following lines to your configuration.yaml:
# Example configuration.yaml entry
@@ -87,9 +87,7 @@
Configuration variables:
host (Optional): IP address of the device, eg. 192.168.1.10. Required if not using the discovery component to discover Hue bridges.
discovery component to discover Hue bridges.emulated_hue component.Note: group_name is not linked to Home Assistant group name.
** Finding Group and Scene Names **
How do you find these names?
-The easiest way to do this is only use the scenes from the 2nd generation Hue app. That is organized by Room (Group) and Scene
-Name. Use the values of Room name and Scene name that you see in the app. You can test these work on the dev-service console of your Home Assistant instance.
The easiest way to do this is only use the scenes from the 2nd generation Hue app. That is organized by Room (Group) and Scene Name. Use the values of Room name and Scene name that you see in the app. You can test these work on the dev-service console of your Home Assistant instance.
Alternatively, you can dump all rooms and scene names using this gist. This does not tell you which groups and scenes work together but it’s sufficient to get values that you can test in the dev-service console.
** Caveats **
The Hue API doesn’t activate Scenes directly, only on a Hue Group (typically Rooms, especially if using the 2nd gen app). But Hue Scenes don’t actually reference their group. So heuristic matching is used.
diff --git a/sitemap.xml b/sitemap.xml index 2f45e8e0d1..1a2208364b 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -3823,62 +3823,62 @@