The Philips Hue integration allows you to control and monitor the lights and sensors connected to your Hue bridge.
There is currently support for the following device types within Home Assistant:
- Motion sensors (including temperature and light level sensors)
- Hue remotes/switches (as device triggers for automations and also exposed as battery sensors when they are battery-powered)
To add the Philips Hue integration to your Home Assistant instance, use this My button:
Philips Hue can be auto-discovered by Home Assistant. If an instance was found, it will be shown as Discovered. You can then set it up right away.
If it wasn’t discovered automatically, don’t worry! You can set up a manual integration entry:
The Hue concept is based on Rooms and Zones. Although the underlying Hue lights are exposed directly to Home Assistant, it might also be useful to interact with the
grouped lights of the Hue ecosystem, for example, to turn all lights in a Hue group on/off at the same time.
Home Assistant creates lights for each Hue zone/room automatically but disables them by default.
If you’d like to use those
grouped lights, you can enable them from Settings –> Integrations –> Hue –> entities.
In the Hue concept you can create (dynamic) scenes for the lights within rooms and zones. You can create, edit and delete Hue scenes from the (official) Hue app on iOS and Android. Each Zone/Room can have its own scenes assigned and there is a large library of preset scenes for specific moods. These Hue scenes are automatically imported in Home Assistant and they’re available as
scene entities. Creating or editing Hue scenes in Home Assistant is not supported.
It is advised to use Hue scenes for controlling multiple lights at once for a smooth experience. If you individually control multiple lights and/or use Home Assistant scenes, each light command will be sent to each light one by one which doesn’t give a very good user experience, while using a Hue scene sends commands to all lights at once in an optimized way, resulting in a smooth experience.
To have more control over Hue scenes we’ve implemented a secondary, more advanced service to activate a Hue scene and set some properties at the same time, such as the Dynamic mode and/or brightness.
|Service Data Attribute
|Entity ID of the Hue Scene entity you want to activate.
|Transition duration (in seconds) it takes to bring devices to the state defined in the scene.
|Enable (true) or Disable (false) dynamic mode for the scene.
|Set the speed (of the dynamic palette) for this scene.
|Set the brightness for this scene.
You can use this service for example if you’d like to start/stop Dynamic Mode.
Hue remotes such as the Dimmer Switch are stateless devices, meaning that they do not have a on/off state like regular entities in Home Assistant. Instead, such devices emit the event
hue_event when a button is pressed. You can test what events come in using the event developer tools in Home Assistant and subscribe to the
hue_event. Once you know what the event data looks like, you can use this to create automations.
At the time of writing, there’s a limitation on the Hue API that each device can only send one event per second. This means that button events are rate-limited to 1 per second. This is brought to the attention of Signify and it will hopefully be fixed soon.
Philips/Signify released a new version of their Hue bridge (square shape) and their legacy/V1 bridge (round shape) is now end of life and no longer supported by them. Home Assistant will continue to support the V1 Hue bridge as long as it is technically possible, although with a few limitations:
- Scene entities are not automatically created for V1 bridges. To call a Hue scene on a V1 bridge from Home Assistant we provide a service call to call a Hue scene by name.
- State updates for devices/entities on a V1 bridges are not received instantly but polled on interval.
- Light entities for Hue rooms are not automatically created for V1 bridges, you can opt-in for creating entities for rooms within the Integration’s options.