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 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:
If you want to enable the component without relying on the discovery component, add the following lines to your configuration.yaml file:
# Example configuration.yaml entry
light:
- platform: hue
- host: DEVICE_IP_ADDRESS
+ - platform: hue
+ host: DEVICE_IP_ADDRESS
Configuration variables:
@@ -93,6 +93,19 @@emulated_hue component.If you use multiple Hue bridges then it’s needed that you provide a configuration file for every bridge. The bridges can’t share a single configuration file.
+Add filename to your Hue configuration entry in your configuration.yaml file:
# Example configuration.yaml entry
+light:
+ - platform: hue
+ host: BRIDGE1_IP_ADDRESS
+ filename: phue.conf
+ - platform: hue
+ host: BRIDGE2_IP_ADDRESS
+ filename: phue2.conf
+The Hue API allows you to group lights. Home Assistant also supports grouping of entities natively, but sometimes it can be usefull to use Hue Groups to group light bulbs. By doing so, Home Assistant only needs to send one API call to change the state of all the bulbs in those groups instead of one call for every light in the group. This causes all the bulbs to change state simultaniously.
These Hue Groups can be a Luminaire, Lightsource, LightGroup or Room. The Luminaire and Lightsource can’t be created manually since the Hue bridge manages these automatically based on the discovered bulbs. The Room and LightGroup can be created manually through the API, or the mobile app. A bulb can only exist in one Room, but can exist in multiple LightGroup. The LightGroup can be usefull to link certain bulbs together since.
More information can be found on the Philips Hue API documentation website.
The Hue platform has it’s own concept of Scenes for setting the colors of a group of lights at once. Hue Scenes are very cheap, get created by all kinds of apps (as it is the only way to have 2 or more lights change at the same time), and are rarely deleted. A typical Hue hub might have hundreds of scenes stored in them, many that you’ve never used, almost all very poorly named.
-To avoid user interface overload we don’t expose Scenes directly. Instead there is a light.hue_activate_scene service which can be used by automation or script components.
-This will have all the bulbs transitioned at once, instead of one at a time using standard scenes in Home Assistant.
-For instance:
The Hue platform has it’s own concept of scenes for setting the colors of a group of lights at once. Hue Scenes are very cheap, get created by all kinds of apps (as it is the only way to have 2 or more lights change at the same time), and are rarely deleted. A typical Hue hub might have hundreds of scenes stored in them, many that you’ve never used, almost all very poorly named.
+To avoid user interface overload we don’t expose scenes directly. Instead there is a light.hue_activate_scene service which can be used by automation or script components.
+This will have all the bulbs transitioned at once, instead of one at a time using standard scenes in Home Assistant.
For instance:
script:
porch_on:
sequence:
@@ -143,19 +156,19 @@ For instance:
scene_nameno
- The name of the Scene. Find this in the Hue official app.
+ The name of the scene. Find this in the Hue official app.
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.
-Neither Group names or Scene names are guaranteed unique in Hue. If you are getting non deterministic behavior, adjust your Hue scenes via the App to be more identifying.
-The Hue hub has limitted spaces for Scenes, and will delete Scenes if new ones get created that would overflow that space. The API docs say this is based on Least Recently Used.
+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.
+Neither group names or scene names are guaranteed unique in Hue. If you are getting non deterministic behavior, adjust your Hue scenes via the App to be more identifying.
+The Hue hub has limitted spaces for scenes, and will delete scenes if new ones get created that would overflow that space. The API docs say this is based on “Least Recently Used”.