To contribute to this page, edit the following file

Philips 7099860PH #

Model	7099860PH
Vendor	Philips
Description	LivingColors Aura
Exposes	light (state, brightness, color_xy, color_hs), effect, linkquality
Picture

Notes #

Pairing #

Factory resetting a Hue bulb can be accomplished in 5 ways. After resetting the bulb will automatically connect.

Touchlink factory reset #

See Touchlink

Hue bridge #

When the bulb is still connected to the Hue bridge, you can simply factory reset the bulb by removing it from the bridge via the Hue app. Orphaned bulbs (configured to connect to a non-existing Zigbee network) can be adopted by a Hue bridge by entering the 6 character serial number in the Philips Hue app.

Hue dimmer switch #

With one of the two Hue Dimmer switches it is possible to put the bulbs into a factory reset.

1. Power-supply the bulb
2. Bring the dimmer switch next to the bulb, as close as possible
3. Hold the I/On and 0/Off button pressed simultaneously for 10 to 12 seconds until…
4. The bulb flashes a couple of times. Don’t release the buttons until the last flash + a safety second
5. Switch the bulb off and on again: it can now be paired again.

See also the VIDEO: Factory reset a Hue bulb with Hue dimmer switch.

Bluetooth (if supported by device) #

Install the Philips Hue Bluetooth app for Android or iOS. You can use the app to trigger a factory reset on a paired light. (Note: The light will only be in bluetooth pairing (Note: The light will only be in bluetooth pairing mode for a couple of minutes after power-on)

TRADFRI remote control #

This may also be possible with the Tradfri Remote Control by pressing and holding the reset button on the bottom of the remote (next to the battery). This may not always work, even if the Hue bulb starts flashing.

Power-on behavior #

This device allows you to set the power-on behavior. Note that this requires at least November/December ‘18 firmware update of the device. Send a MQTT command to zigbee2mqtt/FRIENDLY_NAME/set with the following payload.

{
    "hue_power_on_behavior": "on",          // default, on, off, recover
    "hue_power_on_brightness": 125,         // same values as brightness
    "hue_power_on_color_temperature": 280,  // same values as color_temp
    "hue_power_on_color": "#0000FF",        // color in hex notation, e.g. #0000FF = blue

}

Attribute Value	Description
default	reset to factory default value
on	bulb on after power loss with configured brightness, color-temperature and color
off	bulb off after power loss
recover	last running state after power loss

Rules:

• hue_power_on_behavior value always has to be provided
• hue_power_on_brightness, hue_power_on_color_temperature and hue_power_on_color can only be provided when hue_power_on_behavior = on
• hue_power_on_color_temperature and hue_power_on_color cannot be provided together, only one can be set
• When setting hue_power_on_behavior = on, any not provided values will be reset to their factory defaults

Note: if hue_power_on_behavior is set to off, then the only way to turn the bulb on will be through a paired smart device (see pairing above). You will NOT be able to turn the bulb on by sequentially switching power on and off.

Device type specific configuration #

How to use device type specific configuration

• color_sync: Synchronizes the color values in the state, e.g. if the state contains color_temp and color.xy and the color_temp is set, color.xy will be updated to match the color_temp. (default: true)

• transition: Controls the transition time (in seconds) of on/off, brightness, color temperature (if applicable) and color (if applicable) changes. Defaults to 0 (no transition). Note that this value is overridden if a transition value is present in the MQTT command payload.

• hue_correction: (optional) Corrects hue values based on a correction map for matching color rendition to other lights. Provide a minimum of 2 data sets in the correction map. To build a map:

  • choose one of your other lights to be the color reference
  • send a sample color to both lights (reference and non-reference)
  • modify hue value for non-reference light until it color matches the reference light
  • take note of the in and out values, where
    • in is the hue value you sent to your reference light
    • out is the hue value you had to dial your non-reference light to
  • repeat with a few other sample colors (4-5 should suffice)

  Example correction map:

    hue_correction:
        - in: 28
          out: 45
        - in: 89
          out: 109
        - in: 184
          out: 203
        - in: 334
          out: 318
  

OTA updates #

This device supports OTA updates, for more information see OTA updates.

Exposes #

Light #

This light supports the following features: state, brightness, color_xy, color_hs.

• state: To control the state publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set with payload {"state": "ON"}, {"state": "OFF"} or {"state": "TOGGLE"}. To read the state send a message to zigbee2mqtt/FRIENDLY_NAME/get with payload {"state": ""}.
• brightness: To control the brightness publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set with payload {"brightness": VALUE} where VALUE is a number between 0 and 254. To read the brightness send a message to zigbee2mqtt/FRIENDLY_NAME/get with payload {"brightness": ""}.
• color_xy: To control the XY color (CIE 1931 color space) publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set with payload {"color": {"x": X_VALUE, "y": Y_VALUE}} (e.g. {"color":{"x":0.123,"y":0.123}}). To read the XY color send a message to zigbee2mqtt/FRIENDLY_NAME/get with payload {"color":{"x":"","y":""}}. Alternatively it is possible to set the XY color via RGB:
  • {"color": {"r": R, "g": G, "b": B}} e.g. {"color":{"r":46,"g":102,"b":150}}
  • {"color": {"rgb": "R,G,B"}} e.g. {"color":{"rgb":"46,102,150"}}
  • {"color": {"hex": HEX}} e.g. {"color":{"hex":"#547CFF"}}
• color_hs: To control the hue/saturation (color) publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set with payload {"color": {"hue": HUE, "saturation": SATURATION}} (e.g. {"color":{"hue":360,"saturation":100}}). To read the hue/saturation send a message to zigbee2mqtt/FRIENDLY_NAME/get with payload {"color":{"hue":"","saturation":""}}. Alternatively it is possible to set the hue/saturation via:
  • HSB space (hue, saturation, brightness): {"color": {"h": H, "s": S, "b": B}} e.g. {"color":{"h":360,"s":100,"b":100}} or {"color": {"hsb": "H,S,B"}} e.g. {"color":{"hsb":"360,100,100"}}
  • HSV space (hue, saturation, brightness):{"color": {"h": H, "s": S, "v": V}} e.g. {"color":{"h":360,"s":100,"v":100}} or {"color": {"hsv": "H,S,V"}} e.g. {"color":{"hsv":"360,100,100"}}
  • HSL space (hue, saturation, lightness){"color": {"h": H, "s": S, "l": L}} e.g. {"color":{"h":360,"s":100,"l":100}} or {"color": {"hsl": "H,S,L"}} e.g. {"color":{"hsl":"360,100,100"}}

Transition #

For all of the above mentioned features it is possible to do a transition of the value over time. To do this add an additional property transition to the payload which is the transition time in seconds. Examples: {"brightness":156,"transition":3}, {"color_temp":241,"transition":1}.

Moving/stepping #

Instead of setting a value (e.g. brightness) directly it is also possible to:

• move: this will automatically move the value over time, to stop send value stop or 0.
• step: this will increment/decrement the current value by the given one.

The direction of move and step can be either up or down, provide a negative value to move/step down, a positive value to move/step up. To do this send a payload like below to zigbee2mqtt/FRIENDLY_NAME/set

NOTE: brightness move/step will stop at the minimum brightness and won’t turn on the light when it’s off. In this case use brightness_move_onoff/brightness_step_onoff

{
  "brightness_move": -40, // Starts moving brightness down at 40 units per second
  "brightness_move": 0, // Stop moving brightness
  "brightness_step": 40 // Increases brightness by 40
  "hue_move": 40, // Starts moving hue up at 40 units per second, will endlessly loop (allowed value range: -255 till 255)
  "hue_step": -90, // Decrease hue by 90 (allowed value range: -255 till 255)
  "saturation_move": -55, // Starts moving saturation down at -55 units per second (allowed value range: -255 till 255)
  "saturation_step": 66, // Increase saturation by 66 (allowed value range: -255 till 255)
}

Effect (enum) #

Triggers an effect on the light (e.g. make light blink for a few seconds). Value will not be published in the state. It’s not possible to read (/get) this value. To write (/set) a value publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set with payload {"effect": NEW_VALUE}. The possible values are: blink, breathe, okay, channel_change, finish_effect, stop_effect.

Linkquality (numeric) #

Link quality (signal strength). Value can be found in the published state on the linkquality property. It’s not possible to read (/get) or write (/set) this value. The minimal value is 0 and the maximum value is 255. The unit of this value is lqi.

Manual Home Assistant configuration #

Although Home Assistant integration through MQTT discovery is preferred, manual integration is possible with the following configuration:

light:
  - platform: "mqtt"
    state_topic: "zigbee2mqtt/<FRIENDLY_NAME>"
    availability_topic: "zigbee2mqtt/bridge/state"
    brightness: true
    schema: "json"
    command_topic: "zigbee2mqtt/<FRIENDLY_NAME>/set"
    brightness_scale: 254
    color_mode: true
    supported_color_modes: 
      - "xy"
    effect: true
    effect_list: 
      - "blink"
      - "breathe"
      - "okay"
      - "channel_change"
      - "finish_effect"
      - "stop_effect"

sensor:
  - platform: "mqtt"
    state_topic: "zigbee2mqtt/<FRIENDLY_NAME>"
    availability_topic: "zigbee2mqtt/bridge/state"
    value_template: "{{ value_json.linkquality }}"
    unit_of_measurement: "lqi"
    enabled_by_default: false
    icon: "mdi:signal"
    state_class: "measurement"

sensor:
  - platform: "mqtt"
    state_topic: "zigbee2mqtt/<FRIENDLY_NAME>"
    availability_topic: "zigbee2mqtt/bridge/state"
    icon: "mdi:update"
    value_template: "{{ value_json['update']['state'] }}"
    enabled_by_default: false

binary_sensor:
  - platform: "mqtt"
    state_topic: "zigbee2mqtt/<FRIENDLY_NAME>"
    availability_topic: "zigbee2mqtt/bridge/state"
    payload_on: true
    payload_off: false
    value_template: "{{ value_json.update_available}}"
    enabled_by_default: false